[Bug 13676] New: unmount after fsstress on a ramdisk causes orphan inode list corruption

[bugzilla-daemon@bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=13676

           Summary: unmount after fsstress on a ramdisk causes orphan
                    inode list corruption
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.30-6.fc12
          Platform: All
        OS/Version: Linux
              Tree: Fedora
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@kernel-bugs.osdl.org
        ReportedBy: sandeen@redhat.com
        Regression: No


Created an attachment (id=22143)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=22143)
debug messages & oops.

Running a test like this on 2.6.30-6.fc12 :

#!/bin/bash

mkfs.ext3 /dev/ram0

i=0
while (true); do
    i=`expr $i + 1`
    echo -------------------------------------------------------------
    echo Cycle $i
    date
    echo Mounting
    sleep 1
    mount -t ext3 /dev/ram0 /mnt/test || exit 1
    echo Removing old fsstress data
    rm -rf /mnt/test/work
    mkdir /mnt/test/work || exit 1
    echo Starting fsstress
    fsstress -d /mnt/test/work -p 3 -n 100000000 &
    echo Sleeping 30 seconds
    sleep 30
    echo Stopping fsstress
    while (ps -e | grep fsstress);do
        pkill fsstress
        sleep 1
    done
    echo Unmounting
    umount /mnt/test || exit 1
    echo Checking
    sleep 1
    e2fsck -fvp /dev/ram0 || exit 1
done

I get an assertion failure on the unmount, see attachment.

This testcase was originally reported at http://lkml.org/lkml/2008/11/14/121,
though the end result was different, in that case corruption was found.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.