Announcement

Collapse
No announcement yet.

orphaned inodes and other troubles

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    orphaned inodes and other troubles

    Hi - I'm seeing the "orphaned inode" messages on startup, which i'm presuming to be related to one of these bugs:

    https://bugs.launchpad.net/ubuntu/+s...rt/+bug/672177
    https://bugs.launchpad.net/ubuntu/+s....1/+bug/688541
    https://bugs.launchpad.net/ubuntu/+s...ux/+bug/568594
    https://bugs.launchpad.net/ubuntu/+s...it/+bug/618786

    Out of curiosity, I did a "sudo fsck -n /" to see if anything else had gone wrong. It turned up a page of errors, including but not limited to:

    Code:
    Deleted inode 291464 has zero dtime. Fix? no
...
Entry 'sessionstore.js' in /home/myusername/.mozilla/firefox/myprofile (453443) has deleted/unused inode 454657. Clear? no                                            
...
Block bitmap differences: -1837084 -1838678 +1838679 +1839266                                                                                          
...
Free blocks count wrong for group #56 (193, counted=192).
    I haven't noticed any errors or issues in the system (besides the startup messages).

    My plan is to boot to sysrescd, do a partimage backup of the partition, run fsck for real on the partition, and see what happens.

    (My impression is that partimage et al. backup at a lower logical level than missing inodes, etc, so that restoring the backup restores those errors as well.)

    Any feedback on my plan? :-)

    Thanks,
    -c
    Tags: None
    • Top
    • Bottom
    #2
    Re: orphaned inodes and other troubles

    Got things straightened out, I think...

    fsck doesn't mention this (afaik) but e2fsck, which I understand to be the program fsck uses for an ext3 partition, says in the man page:

    Note that in general it is not safe to run e2fsck on mounted filesystems. The only exception is if the -n option
    is specified, and -c, -l, or -L options are not specified. However, even if it is safe to do so, the results printed by e2fsck
    are not valid if the filesystem is mounted. If e2fsck asks whether or not you should check a filesystem which is mounted,
    the only correct answer is ``no''.
    When I booted into a system rescue CD I first tried to do a partimage clone of the partition, it would not work, reporting some kind of disk error. Then I ran

    Code:
    fsck -f /dev/sda3
    ...it found no errors. However when I ran

    Code:
    fsck -f -c -c /dev/sda3
    ...which in turn runs the badblocks program with particular configuration info set, it found a few inodes pointing to "multiply-claimed" blocks. I allowed it to fix these and then again ran

    Code:
    fsck -f -c -c /dev/sda3
    ...which then showed no errors. Another fsck -f /dev/sda3 for good measure showed no errors. Then I tried the partition backup and all went well. Subsequent use of the computer has shown no obvious symptoms.

    I have no idea how the hard drive got corrupted, but there you go, fwiw.

    -c
    • Top
    • Bottom

    Comment

    Previous template Next
    Working...
    X