[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090319170340.GC3899@duck.suse.cz>
Date: Thu, 19 Mar 2009 18:03:40 +0100
From: Jan Kara <jack@...e.cz>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Nick Piggin <nickpiggin@...oo.com.au>,
Ying Han <yinghan@...gle.com>, Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, guichaz@...il.com,
Alex Khesin <alexk@...gle.com>,
Mike Waychison <mikew@...gle.com>,
Rohit Seth <rohitseth@...gle.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: ftruncate-mmap: pages are lost after writing to mmaped file.
On Thu 19-03-09 09:51:59, Linus Torvalds wrote:
>
>
> On Fri, 20 Mar 2009, Nick Piggin wrote:
> >
> > Yeah, probably no need to hold private_lock while tagging the radix
> > tree (which is what my version did). So maybe this one is a little
> > better. I did test mine, it worked, but it didn't solve the problem.
>
> Ahh, so you re-created it? On ext2 only, or is it visible on ext3 as well?
> I've not even tested - I assumed that I would have to boot into less
> memory and downgrade my filesystem to ext2, which made me hope somebody
> else would pick it up first ;)
In thread http://lkml.org/lkml/2009/3/4/179 I've reported similar problem
- write lost. I'm able to reproduce under UML linux at will. ext3 takes
with 1KB blocksize about 20 minutes to hit the corruption, ext2 with 1 KB
blocksize about an hour, ext2 with 4KB blocksize several hours...
I've reported that also ordinary write() got lost once but that might
have been an error in me reading the fsx logs since I never saw it again...
Honza
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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