From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: Massive ext4 filesystem corruption after a failed s2disk/ram cycle Date: Tue, 6 Oct 2009 23:58:32 +0200 Message-ID: <200910062358.32417.rjw@sisk.pl> References: <1254863215.11577.23.camel@maxim-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1254863215.11577.23.camel@maxim-laptop> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: linux-pm@lists.linux-foundation.org Cc: linux-kernel List-Id: linux-pm@vger.kernel.org On Tuesday 06 October 2009, Maxim Levitsky wrote: > Hi, > > Just prior to 2.6.32 cycle I tried -next tree and noticed that after a > failed s2ram (here it works only once, and I test once in a whileto see > if fixed accidentally) I got a minor filesystem corruption. I am sorry I > didn't report that back then. > > Now I have installed 2.6.32-rc2 (well -rc1...) and things were sort of > ok, I have even thought that hibernation is once again stable > (somewhere in the not that distinct past the hibernation which used to > work, began to fail randomly on resume) > > Few days ago, I got a read-only filesystem again, an fsck, few more > corrupted files..., It should have had rung the bell for me (I have > still used hibernation, trying to understand why it fails sometimes) > > Yesterday, however, I have decided to fix that once and for all, and for > that I have set up a loop + rtc wakealarm to make it cycle through > hibernation. > > Needless to say I didn't run that loop more that maybe 3 cycles (and no > failures), but noticed that rtc clock is dead on resume. > > I sort of fixed that (this is hpet emulation that strikes again), I will > post when I test the fix (trivial), because when I had rebooted the > system into the modified kernel, I got that readonly filesystem again, > and this time the damage had spread over lots of files. > (I have even lost most of dpkg database..., many programs, > libraries,..., settings) > > Yet, thanks to Linux flexibility, after a day, and some study of > nautilus source, I had the system recovered fully. > (Now am doing backups.....) > > But I don't want that to happen again... > > Another clue that I have seen was that ext4 driver reported that it > aborts journal replay. > > I know that for now there is not much you can do, but just to let you > know that something is there... > > What is especially interesting is that there were no s2ram'disk faulure > preceding the corruption, but my theory is that corruption wasn't > detected for a while from last failure, probably giving such bad > consequences. > > You do sync file-systems before entering the hibernation, don't you? Yes, a sync is there, but it is not effective on some filesystems. Thanks, Rafael