fsck doesn't work on a partition (signal 11)

From: Shabam (chalupa_at_yomama-nospam.com)
Date: 07/18/05

  • Next message: Mark Hobley: "Re: fsck doesn't work on a partition (signal 11)"
    Date: Sun, 17 Jul 2005 21:15:58 -0700
    
    

    A Red Hat Linux system I have crashed and upon reboot it said fsck had
    encountered problems so I had to manually run fsck and fix the errors on
    /dev/hda7.

    I did that and typed "y" to a few inode errors. When done at the end there
    was a message "exited with signal 11". Rebooting doesn't work and the same
    thing would occur again, with the exact same inode errors, making me think
    nothing was fixed.

    Running fsck on the other partitions resulted in success. Only hda7 had
    this problem. Does anyone know what could be causing this?


  • Next message: Mark Hobley: "Re: fsck doesn't work on a partition (signal 11)"

    Relevant Pages

    • fsck doesnt work on a partition (signal 11)
      ... A Red Hat Linux system I have crashed and upon reboot it said fsck had ... encountered problems so I had to manually run fsck and fix the errors on ... I did that and typed "y" to a few inode errors. ...
      (alt.os.linux)
    • Re: fsck doesnt work on a partition (signal 11)
      ... > A Red Hat Linux system I have crashed and upon reboot it said fsck had ... > encountered problems so I had to manually run fsck and fix the errors on ... to it fix things smartly if possible. ...
      (alt.linux)
    • Re: fsck doesnt work on a partition (signal 11)
      ... > A Red Hat Linux system I have crashed and upon reboot it said fsck had ... > encountered problems so I had to manually run fsck and fix the errors on ... to it fix things smartly if possible. ...
      (alt.os.linux)
    • 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)
    • 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)