Comment 86 for bug 330824

Just wanted to register myself as another user experiencing this bug and give some details on the conditions under which I have been able to reproduce it as they do not exactly correlate with some of the comments above.

Latest kernel in repository - 2.6.28.11.14
4.5TB ext4 partition on top of a same size dmcrypt partition, ~3 weeks old
3.9TB free - Indicates that a low amount of free space is not necessarily a large contributing factor

I was able to reliably cause this problem by deleting a folder (rm -rf) that contained two files of ~90GB. This is a data partition and I am reasonably confident (97%) that there were no other operations being performed on that partition at the time.

Lockup could also be caused by directly deleting the file (rm largefile.test) - Indicates that a directory tree traversal is not always necessary

Following a number of repeats of the process -
1. Start deletion of large file
2. Experience lock-up
3. Reboot
4. Repeat
The file was no longer present upon rebooting the machine.

The problem was reproducible though by creating new large files and then attempting to delete them.

I am very interested in getting this bug fixed and happy to help with any diagnosis I can.

Best of luck,
David