Just a short notice, as I don't have any extra info on this. One of my
machines showed an "error 990" just out of the blue, 3 days ago.
I couldn't find anything - there was a loose inode and that was it.
What puzzles me is that this machine has a load of almost 0; the file with
problems was /usr/share/mysql/portuguese/errmsg.sys - which is not in use in
disconnected inode 410362, nlink 1
link count mismatch for inode 7536890 (name ?), nlink 0, counted 1
... xfs_repair put the thing in /lost+found and moving this to
/usr/share/mysql/portuguese/errmsg.sys resolved the issue, but it leaves me
wondering how this came about? No error messages in the kernel log, no disk
errors (used "dd" to read the whole disk to /dev/null).
Linux 2.4.19 on a Pentium 133, 48Mb
SGI XFS 1.2pre4 with ACLs, quota, no debug enabled
(And a VIA vt82c586 (rev 02) IDE controller)
Any ideas? Or is this just a single bit that fell of the drive accidentally?
Oh, BTW, this was the first time I actually needed xfs_repair and it felt a
bit uneasy to see that you can't repair mounted fs's. Well, it's in the faq,
I should have read that fine manual before use, I know ;-)
http://www.openoffice.nl/ Open Office - Linux Office Solutions
Valentijn Sessink valentyn+sessink@xxxxxxxxxxxxxxxxxxxx