lkml.org 
[lkml]   [2008]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 0/4] (RESEND) ext3[34] barrier changes
    On Mon, May 19 2008, Chris Mason wrote:
    > On Monday 19 May 2008, Chris Mason wrote:
    > >
    > > Here's a test workload that corrupts ext3 50% of the time on power fail
    > > testing for me. The machine in this test is my poor dell desktop (3ghz,
    > > dual core, 2GB of ram), and the power controller is me walking over and
    > > ripping the plug out the back.
    >
    > Here's a new version that still gets about corruptions 50% of the
    > time, but does it with fewer files by using longer file names (240
    > chars instead of 160 chars).
    >
    > I tested this one with a larger FS (40GB instead of 2GB) and larger
    > log (128MB instead of 32MB). barrier-test -s 32 -p 1500 was still
    > able to get a 50% corruption rate on the larger FS.

    I ran this twice, killing power after 'renames ready'. The first time it
    was fine, the second time I got:

    centera:~/e2fsprogs-1.40.9/e2fsck # ./e2fsck -f /dev/sdb1
    e2fsck 1.40.9 (27-Apr-2008)
    /dev/sdb1: recovering journal
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Problem in HTREE directory inode 2395569: node (281) has bad max hash
    Problem in HTREE directory inode 2395569: node (849) has bad max hash
    Problem in HTREE directory inode 2395569: node (1077) has bad max hash
    Problem in HTREE directory inode 2395569: node (1718) has bad max hash
    Problem in HTREE directory inode 2395569: node (4609) has bad max hash
    Problem in HTREE directory inode 2395569: node (4864) has bad max hash
    Problem in HTREE directory inode 2395569: node (5092) has bad max hash
    Problem in HTREE directory inode 2395569: node (5148) has bad max hash
    Problem in HTREE directory inode 2395569: node (5853) has bad max hash
    Problem in HTREE directory inode 2395569: node (7588) has bad max hash
    Problem in HTREE directory inode 2395569: node (8663) has bad max hash
    Invalid HTREE directory inode 2395569 (/barrier-test). Clear HTree
    index<y>? yes

    Pass 3: Checking directory connectivity
    Pass 3A: Optimizing directories
    Duplicate entry
    '0650419c70f3beadaa9a2c2f4999745a9c02066a0650419c70f3beadaa9a2c2f4999745a9c02066a0650419c70f3beadaa9a2c2f4999745a9c02066a0650419c70f3beadaa9a2c2f4999745a9c02066a0650419c70f3beadaa9a2c2f4999745a9c02066a0650419c70f3beadaa9a2c2f4999745a9c02066a.0'
    in /barrier-test (2395569) found. Clear? yes

    and tons of 'duplicate entry' errors after that. And then

    Pass 4: Checking reference counts
    Inode 168 ref count is 0, should be 1. Fix? yes

    Unattached zero-length inode 255. Clear? yes

    Inode 1221 ref count is 0, should be 1. Fix? yes

    Inode 1253 ref count is 1, should be 2. Fix? yes

    Inode 2692 ref count is 0, should be 1. Fix? yes

    Inode 3465 ref count is 0, should be 1. Fix? yes

    and lots of those too. So definitely easy to trigger. Test fs was ext3
    of 40gb on a 320gb maxtor drive.

    --
    Jens Axboe



    \
     
     \ /
      Last update: 2008-05-20 10:29    [W:0.024 / U:91.776 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site