[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BCA1DFB.5030501@redhat.com>
Date: Sat, 17 Apr 2010 15:45:47 -0500
From: Eric Sandeen <sandeen@...hat.com>
To: Bernd Schubert <bernd.schubert@...tmail.fm>
CC: Andre Noll <maan@...temlinux.org>,
Andrew Vasquez <andrew.vasquez@...gic.com>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
Linux Driver <Linux-Driver@...gic.com>,
Thomas Helle <Helle@...bingen.mpg.de>
Subject: Re: ext4: (2.6.34-rc4): This should not happen!! Data will be lost
Bernd Schubert wrote:
...
> Altogether filesystem unrelated. The filesystem just might be the reason for a
> synchronize-cache, e.g. barriers, etc.
Interesting that it only happens at enospc time though - the fs would
be sending barriers in general usage.
Although, as ext4 fills, it does do more syncing/flushing to try to
eke out that last bit of space.... hmm....
Andre, just for fun, you might try mounting -o nodelalloc, fill it again,
and see if you see the same behavior.
If not, you might do it again w/ defaults, and capture blktrace data, which
I think will trace barrier requests as well.
(or, maybe also try testing with -o nobarrier)
I still don't think it's likely a filesystem problem but maybe you can
pinpoint the fs behavior that triggers it.
-Eric
> Greetings from Tübingen,
> Bernd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists