https://bugzilla.kernel.org/show_bug.cgi?id=25832 --- Comment #39 from Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> 2011-03-06 15:59:05 --- It is expected that processes will try to access files on a drive after it has been removed. After all, they have no way of knowing that the drive is gone. I'm not convinced that the timing with respect to your resume is relevant. After all, you mentioned that the crashes are subject to random delays, sometimes happening several seconds after the system resumes. Also, the kernel does not automatically unmount missing drives. Unmounting is a separate operation from removal. Unmounting takes place only when the user (or a program) does the equivalent of running the umount command. You did say that this problem doesn't arise in 2.6.36. Your best chance of tracking it down might be to try doing a git bisection between 2.6.36 and 2.6.37. However, for this to work, you have to be able to detect reliably whether or not a particular kernel has the bug. The test you used in comment #31 might do the job. If you can narrow this down to an individual kernel change, that would be a big help. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
