I got the crash image. Unfortunately the beginning of the Oops message was cut off, which might have been valuable. There are some new patches that are newer than what has been backported to 2.6.28.7; some of them are in the for-stable branch of the ext4 git tree, and have been queued for 2.6.28.8. The call stack doesn't look like one of the known bugs, though. Hmm... can you send us the output of dumpe2fs on the filesystem? And something that would be very useful would be a raw e2image of the filesystem, created thusly: e2image -r /dev/sdXXX - | bzip2 > sdXXX.e2i.bz2 This image will contain the basic filesystem metadata, including the directory blocks (and directory names), but none of the data blocks. It is therefore much smaller, and if you are willing to let me see your directory file names, I can take that image and try to replicate the problem on one of my systems. If you have a spare 20gb of disk space, you can also unpack the raw image dump and try reproducing the problem on the raw image dump. If you can trigger it easily with an rm -rf operation, it should be just as reproducible on the raw image dump. Regards, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
