© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
As an idea; for people who can reproduce it easily, preferably one of you who have been doing this on a relatively small (20-40GB filesystem), maybe you would be willing to do the following?
(a) Load up the filesystem with the test set of files that, when deleted, will product the hang.
(b) Run e2image -r /dev/sdXX - | bzip2 > /media/
(c) Run "sync" to make sure the e2image file is safely written to your USB drive, or other filesystem
(d) Try to reproduce the crash by running rm -rf to delete the filesystem.
Repeat steps (a) through (d) until you get a crash. Then contact me off-line and send me the sdXX.e2i.bz2 file. Also tell me exactly what kernel you were running at the time of the kernel.
Couple of caveats --- the compressed raw e2image file will not contain any filesystem data, but will contain file names. I promise not to look at them any more than necessary to debug this issue, and I certainly promise not to divulge them, but you should be aware of this from a privacy perspective.
What I will be able to do is to uncompress the raw e2image, and then try to reproduce the crash using exactly your filesystem layout. Thanks in advance for anyone who is willing to lend a hand.