Finding files affected by crash+fsck

From: Robert Dodier (robert_dodier_at_yahoo.com)
Date: 11/25/03 

Date: 25 Nov 2003 08:21:51 -0800

Hello,

I'm running RH 7.1 (kernel 2.4.2, ancient indeed). Recently
the UPS became an IPS (ha, ha) and a power glitch caused the
machine to reboot suddenly. Fast forward a couple of days,
after X crashes upon trying to restart gdm, the usual boot-up
sequence tells me to run fsck manually.

OK, so I run fsck and it tells me there is an inode that
needs to be fixed and some other bits that need twiddling.
I tell fsck "y" to all proposed changes. The machine reboots
OK after that.

However, I notice that my desktop config is messed up.
That's not a big deal, but I didn't expect that, because
the only file placed in /lost+found is a CDDB config file.
So apparently some files were clobbered or modified but
fsck didn't put them in /lost+found.

I don't really care much about the desktop, but how can I
find out if there are any other files that were modified
during the crash and subsequent fsck? (I'm hoping there is
a way that doesn't involve comparing checksums to backups.)

Thanks for your help,
Robert Dodier

Relevant Pages

  • Re: [Bug 14354] Re: ext4 increased intolerance to unclean shutdown?
    ... I went through this bug report and here are some immediately ... the power button on my laptop when it is doing nothing. ... by another reboot only to have X fail to start and NetWorkManager ... After another fsck and a reboot it finally comes up. ...
    (Linux-Kernel)
  • Finding files affected by crash+fsck
    ... machine to reboot suddenly. ... sequence tells me to run fsck manually. ... I notice that my desktop config is messed up. ... the only file placed in /lost+found is a CDDB config file. ...
    (comp.os.linux.questions)
  • Re: The ext3 way of journalling
    ... If these reasons are good ones then the correct way to really handle this would be to do regular background scrubbing during runtime; ideally with metadata checksums so that you can actually detect all corruption. ... Leave some extra space in your LVM volume group (enough for 1 snapshot over the time it takes to do an FSCK). ... If it succeeds you can adjust the "last checked" date to the time when the snapshot was taken and if it fails you can schedule an FSCK at next reboot. ...
    (Linux-Kernel)
  • Re: Printer not working after a short circuit
    ... > system will reboot when you leave the shell. ... Give root password for maintenance or type Control-D to ... Run fsck manually. ... > entire file system and prompted me as to whether or not to continue. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Spontaneous unclean reboots
    ... I would still fsck / just to make sure there are no errors, ... I'm going to do that from the Knoppix cd I have, ... Did you run a checksum on the Opera download before installing it? ... It shouldn't have reboot at all, ...
    (alt.os.linux)