>BTW what kind of unhappiness can we expect from this "inode
problem"? Just
>things that e2fsck will make go away?
That's all I was able to reproduce myself: bad block counts in the
various block groups. Other people have reported file corruption,
though.
After installing .541 as up2date for .538, I saw bad counts in the freelist.
So I did an fsck, and found bad counts in the sizes of a few dozen (50? 70?)
files (the files had all "grown" by a few blocks or so), and bad filetypes
(usually involving to/from filetype 7). I said 'y' to all fsck questions,
and have not had trouble since. I double checked with fsck from RHEL3.
--
John Reiser, jreiser(a)BitWagon.com