I've attached the output of dmesg after mounting the filesystem in question with 3.6-trunk-amd64 from experimental and then running "ls -l" on the root of the filesystem in question.
3.6 is a significant improvement in that although the filesystem is mounted read-only I can access at least some of the data. With the wheezy kernel programs like ls enter D state and never return and a hardware reset is the only option. I tried to umount the filesystem but umount got stuck in D state with nothing in the kernel log about it. So there's still some serious problems. I think that the kernel should be able to correct the filesystem and even if that's not possible umount should always succeed (if this was a server it would cause downtime). -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
dmesg-3.6.txt.gz
Description: GNU Zip compressed data
