On Thu, 08 Jun 2006, Matt Price wrote:
> terrifying bit) the inode for /usr/lib. So when I boot into the
> system, /usr/lib is missing, and anything that resides there is gone.
> xfs_repair says something about "moving to lost+found", but I don't
> know really whatthat means.
It means everything ends up in the lost+found dir inside the filesystem
being repaired.
Your choices now are three:
1. You have a backup of /usr/lib: use it.
2. You don't mind a reinstall: reinstall the system.
3. You do a apt-get --reinstall install run for everything in the system,
after using dpkg -i to manually (re)install everything
apt-get/dpkg/debconf/ucf might need from /usr/lib.
> SO now I wonder: what can I do to fix this now? and how could
> something so catastrophic happen so easily? It turns me rather sour
I didn't read the rest of the thread, so I don't know if you explained how
you got the corruption, but memory errors and on-disk bit-flips are not a
good thing for XFS (since it basically never does a repair-any-small-errors-
before-they-get-big pass with that fake fsck.xfs crap).
XFS also does *not* tolerate power-loss or hard-resets of any sort on
systems without full write barriers down to the disk platter (hint: *maybe*
2.6.17 has this for SATA, SCSI has it. And your HDs need to implement it
properly too, and unless it is SCSI, chances are it doesn't). And even for
those, you lose all user data (as opposed to filesystem metadata) not
fsync()'ed in the last 5-10s.
> I suppose I could try apt-get install --reinstall <everything> but
> even if that works I guess all the other missing inodes will stil lbe
> missing, right?
Yes.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
