From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Eric Sandeen <sandeen@redhat.com>,
Aioanei Rares <krnl.list@gmail.com>,
linux-ext4@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Mild filesystem corruption on ext4 (no journal)
Date: Fri, 05 Jun 2009 22:42:41 +0100 [thread overview]
Message-ID: <4A299151.3040109@tuffmail.co.uk> (raw)
In-Reply-To: <ac3eb2510906050951o200c3aeex56dcb32bf29d0607@mail.gmail.com>
Kay Sievers wrote:
> On Fri, Jun 5, 2009 at 18:43, Alan Jenkins<alan-jenkins@tuffmail.co.uk> wrote:
>
>
>> If I remove the corrupted file and copy a "known good" copy into it's place,
>> then the corruption doesn't happen. I've verified this a couple of times.
>> The corruption only occurs if the file was created by "locale-gen".
>>
>
> Does it use things like: fallocate()?
>
> Kay
>
Not quite. Ted says it's already reported as
http://bugzilla.kernel.org/show_bug.cgi?id=13292
It includes an strace log which implicates the use of both mmap() and
write() on the same file. Sounds scary :-).
Alan
next prev parent reply other threads:[~2009-06-05 21:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 10:49 Mild filesystem corruption on ext4 (no journal) Alan Jenkins
2009-06-05 14:40 ` Aioanei Rares
2009-06-05 14:49 ` Alan Jenkins
2009-06-05 15:20 ` Eric Sandeen
2009-06-05 16:43 ` Alan Jenkins
2009-06-05 16:51 ` Kay Sievers
2009-06-05 16:51 ` Kay Sievers
2009-06-05 21:42 ` Alan Jenkins [this message]
2009-06-06 4:17 ` Henrique de Moraes Holschuh
2009-06-05 18:12 ` Eric Sandeen
2009-06-05 21:32 ` Alan Jenkins
2009-06-05 22:02 ` Eric Sandeen
2009-06-05 18:01 ` Theodore Tso
2009-06-05 21:34 ` Alan Jenkins
2009-06-05 21:34 ` Alan Jenkins
2009-06-05 21:42 ` Curt Wohlgemuth
2009-06-05 21:42 ` Curt Wohlgemuth
2009-06-09 4:15 ` Michael Rubin
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=4A299151.3040109@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=kay.sievers@vrfy.org \
--cc=krnl.list@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.