I have been having a problem with disk corruption in the last few days. Tracked it down to the system suspend. I wonder if anyone has some insight before I submit this issue as a bug.
I am running a dell studio 17 laptop with Fedora kernel:
Linux MrRoboto.XXX 3.5.4-1.fc17.x86_64 #1 SMP Mon Sep 17 15:03:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I have been running this version of the OS for several months with no problems. The other day I accepted the latest round of updates for this system. That's when i started noticing some disk issues when doing development work with express and android SDK. When I rebooted the system I was confronted with a UNEXPECTED INCONSISTENCY message and I had to discover which device was a problem so I could run fsck. e.g.:
I found that this set of circumstance only occurs if I allow a system suspend, which I had set after the lid is closed--this is nothing new, I had been using suspend this way successfully.
It appears that this is a bug that was recently introduced into the code stream recently. But I thought I might run it by the forum before I submit a bug.
Does anyone have any ideas about this?