• Bug#266159: e2fsprogs: fails to correct broken filesystem

    From Theodore Ts'o@1:229/2 to Simon Richter on Fri Aug 20 20:10:10 2004
    From: [email protected]

    On Wed, Aug 18, 2004 at 10:58:16PM +0200, Simon Richter wrote:

    There is nothing about that in the kernel logs, and I ran e2fsck on the
    file before I gzipped it to make sure it is not a hardware problem.


    Um, stupid question, you did send me a copy of the file from *before*
    you ran e2fsck on it, right? If you ran e2fsck on the file and then
    shipped it to me, e2fsck would have destroyed ("fixed") all of the
    evidence. :-(

    + e2fsck -yf brokenfs
    e2fsck 1.35 (28-Feb-2004)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    Block bitmap differences: -1008609
    Fix? yes

    Block bitmap differences: -1008609
    Fix? yes

    Block bitmap differences: -1008609
    Fix? yes

    This is certainly wrong; e2fsck shouldn't be repeating itself like
    that. Could this be a corrupted binary or a compiler bug? I'd
    certainly want to try running this under a debugger to see exactly
    what the heck is going on here; the code just shouldn't be doing this
    under any conditions.

    0.263733 33
    0.116960 28
    0.061751 9
    157.271740 13

    ??? What are these numbers?

    - Ted


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Simon Richter@1:229/2 to All on Tue Aug 17 00:30:12 2004
    From: [email protected]

    Package: e2fsprogs
    Version: 1.35-6
    Severity: important

    Hi,

    for an obscure reason one of my ext3 filesystems got corrupted, and
    e2fsck is unable to repair it, sometimes looping while trying to correct
    a bitmap block, sometimes just pretending to repair the filesystem while
    not doing anything to it.

    A gzipped e2image of the filesystem in question can be found at http;//people.debian.org/~sjr/brokenfs.gz .

    Simon

    -- System Information:
    Debian Release: 3.1
    APT prefers unstable
    APT policy: (500, 'unstable')
    Architecture: powerpc (ppc)
    Kernel: Linux 2.4.22
    Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8

    Versions of packages e2fsprogs depends on:
    ii e2fslibs 1.35-6 The EXT2 filesystem libraries
    ii libblkid1 1.35-6 Block device id library
    ii libc6 2.3.2.ds1-15 GNU C Library: Shared libraries an ii libcomerr2 1.35-6 The Common Error Description libra ii libss2 1.35-6 Command-line interface parsing lib ii libuuid1 1.35-6 Universally unique id library

    -- no debconf information

    --
    GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD ADC6 18A0 CC8D 5706 A4B4

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.5 (GNU/Linux)

    iD8DBQFBIS+tGKDMjVcGpLQRAva9AKCpwmPmlHCSN2RRGFQDptLuYObWXwCbB2Au Iy+iXBMef0hxqcAV4Mv4eEA=
    =KyLO
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Theodore Ts'o@1:229/2 to Simon Richter on Tue Aug 17 04:10:08 2004
    From: [email protected]

    On Tue, Aug 17, 2004 at 12:05:33AM +0200, Simon Richter wrote:
    for an obscure reason one of my ext3 filesystems got corrupted, and
    e2fsck is unable to repair it, sometimes looping while trying to correct
    a bitmap block, sometimes just pretending to repair the filesystem while
    not doing anything to it.

    A gzipped e2image of the filesystem in question can be found at http;//people.debian.org/~sjr/brokenfs.gz .

    Hi, could you please check the permissions on the file, please? Many
    thanks!!

    - Ted


    % wget http://people.debian.org/~sjr/brokenfs.gz
    --21:51:17-- http://people.debian.org/%7Esjr/brokenfs.gz
    => `brokenfs.gz'
    Resolving people.debian.org... done.
    Connecting to people.debian.org[192.25.206.10]:80... connected.
    HTTP request sent, awaiting response... 403 Forbidden
    21:51:19 ERROR 403: Forbidden.



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Simon Richter@1:229/2 to All on Tue Aug 17 11:10:15 2004
    From: [email protected]

    Hi,

    A gzipped e2image of the filesystem in question can be found at http;//people.debian.org/~sjr/brokenfs.gz .

    Hi, could you please check the permissions on the file, please? Many thanks!!

    *blush* Of course.

    Simon

    --
    GPG Fingerprint: 040E B5F7 84F1 4FBC CEAD ADC6 18A0 CC8D 5706 A4B4

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.5 (GNU/Linux)

    iD8DBQFBIcbHGKDMjVcGpLQRAjzVAJ9zJr9JpzDrNP3+3jz3clSsAAxQcgCgibu4 ouOCH2WBTJJxiis5i/fYIB4=
    =hF1a
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Theodore Ts'o@1:229/2 to Simon Richter on Wed Aug 18 18:40:07 2004
    From: [email protected]

    On Tue, Aug 17, 2004 at 12:05:33AM +0200, Simon Richter wrote:
    for an obscure reason one of my ext3 filesystems got corrupted, and
    e2fsck is unable to repair it, sometimes looping while trying to correct
    a bitmap block, sometimes just pretending to repair the filesystem while
    not doing anything to it.

    A gzipped e2image of the filesystem in question can be found at http;//people.debian.org/~sjr/brokenfs.gz .

    Hi there, I'm not seeing any problem with this filesystem image:

    <tytso@think> {/usr/home/tytso}
    515% gunzip < brokenfs.gz | src/make-sparse brokenfs.img
    <tytso@think> {/usr/home/tytso}
    516% e2fsck -fy brokenfs.img
    e2fsck 1.35 (28-Feb-2004)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    brokenfs.img: 25592/675840 files (3.9% non-contiguous), 530743/1350720 blocks

    (All make-sparse is a quickie little program that takes data from
    standard input and produces a sparse file.... i.e., it notices blocks
    of all zero's, and uses lseek() instead write() in order to keep the
    number of physical blocks used to a minimum. Something that should be
    built-in into gunzip but isn't, alas.)

    Could you check the following?

    1) That you don't have any hardware problems that might be causing
    intermittent I/O errors? This will cause e2fsck to give bad results,
    although e2fsck generally is very verbose when the kernel returns I/O
    errors. Still, you should try checking dmesg, /var/log/message, and /var/log/syslog for any kernel printk's indicating I/O errors.

    2) Check to make sure you ran e2image on the correct partition.

    3) After you create the e2image file, copy it to a test file, and then
    try running e2fsck on the test file. If you can't reproduce the
    problem on the e2image file, but the problem persists when you run
    e2fsck on the device, then it is extremely likely that you have some
    sort of hardware problem.

    - Ted



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)