[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87vdisq7bh.fsf@rimspace.net>
Date: Wed, 07 Oct 2009 13:14:10 +1100
From: Daniel Pittman <daniel@...space.net>
To: Henrique de Moraes Holschuh <hmh@....eng.br>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
linux-pm@...ts.linux-foundation.org,
Maxim Levitsky <maximlevitsky@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Massive ext4 filesystem corruption after a failed s2disk/ram cycle
Henrique de Moraes Holschuh <hmh@....eng.br> writes:
> On Wed, 07 Oct 2009, Rafael J. Wysocki wrote:
>> On Wednesday 07 October 2009, Henrique de Moraes Holschuh wrote:
>> > On Tue, 06 Oct 2009, Rafael J. Wysocki wrote:
>> > > > 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.
>> >
>> > Which ones?
>>
>> XFS for one example.
>
> Interesting. So XFS is not only a Bad Idea for /, but also for anything
> that might enter S3/S4. Not nice. I sure hope it doesn't do a
> half-assed job of flushing and checkpointing itself during machine
> shutdown/restart like it apparently does when told to "sync" before
> S3/S4...
For what it is worth, I would also be quite interested to know /why/ XFS is
bad in this regard. Is it just the previously stated "XFS writes to disk
despite freezing kernel threads" issue, or something deeper?
Daniel
--
✣ Daniel Pittman ✉ daniel@...space.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists