We saw issues like this in Ubuntu 11.10 as well, and it was resolved by figuring out what is left running just before shutdown.
If you can edit /etc/init.d/umountroot and add this, just before the line starting with ' mount', which on my 12.10 system is line 86:
/usr/sbin/lsof -n > /last-shutdown-lsof
(You may need to sudo apt-get install lsof)
This will record all open files just before root is remounted. Then after verifying that the FS was detected as dirty (please, stop calling it corrupt, it is not corrupt, just dirty) and fsck was run, upload the file /last-shutdown-lsof to this bug and we can take a look at it.
(please check the content of that file. I don't think it will have any sensitive data in it, but please check before uploading as this bug is public).
Judging from the reports, I doubt very much that this has anything to do with the kernel other than Ted T'so's suggestion that the kernel is simply exposing the dirty filesystem.
We saw issues like this in Ubuntu 11.10 as well, and it was resolved by figuring out what is left running just before shutdown.
If you can edit /etc/init. d/umountroot and add this, just before the line starting with ' mount', which on my 12.10 system is line 86:
/usr/sbin/lsof -n > /last-shutdown-lsof
(You may need to sudo apt-get install lsof)
This will record all open files just before root is remounted. Then after verifying that the FS was detected as dirty (please, stop calling it corrupt, it is not corrupt, just dirty) and fsck was run, upload the file /last-shutdown-lsof to this bug and we can take a look at it.
(please check the content of that file. I don't think it will have any sensitive data in it, but please check before uploading as this bug is public).
Judging from the reports, I doubt very much that this has anything to do with the kernel other than Ted T'so's suggestion that the kernel is simply exposing the dirty filesystem.