public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-pm@lists.linux-foundation.org,
	Maxim Levitsky <maximlevitsky@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Massive ext4 filesystem corruption after a failed s2disk/ram cycle
Date: Wed, 07 Oct 2009 13:14:10 +1100	[thread overview]
Message-ID: <87vdisq7bh.fsf@rimspace.net> (raw)
In-Reply-To: <20091007012930.GA7022@khazad-dum.debian.net> (Henrique de Moraes Holschuh's message of "Tue, 6 Oct 2009 22:29:30 -0300")

Henrique de Moraes Holschuh <hmh@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@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

  reply	other threads:[~2009-10-07  2:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 21:06 Massive ext4 filesystem corruption after a failed s2disk/ram cycle Maxim Levitsky
2009-10-06 21:42 ` Theodore Tso
2009-10-06 23:02   ` Maxim Levitsky
2009-10-07 14:25     ` Jindrich Makovicka
2009-10-06 21:58 ` [linux-pm] " Rafael J. Wysocki
2009-10-06 22:53   ` Henrique de Moraes Holschuh
2009-10-06 23:02     ` Rafael J. Wysocki
2009-10-07  1:29       ` Henrique de Moraes Holschuh
2009-10-07  2:14         ` Daniel Pittman [this message]
2009-10-07 16:16           ` Christoph Hellwig
2009-11-04  2:18             ` KOSAKI Motohiro
2009-11-05  9:56               ` Henrique de Moraes Holschuh
2009-11-07 22:22                 ` Thomas Fjellstrom
2009-11-08  8:29               ` Dave Chinner
2009-11-08 16:49                 ` Christoph Hellwig
2009-11-09  9:42                   ` Henrique de Moraes Holschuh
2009-10-10  3:26 ` ext4 filesystem corruption Maxim Levitsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vdisq7bh.fsf@rimspace.net \
    --to=daniel@rimspace.net \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=maximlevitsky@gmail.com \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox