From: Nathan Scott <nathans@sgi.com>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: Jan Kasprzak <kas@fi.muni.cz>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: XFS information leak during crash
Date: Thu, 3 Nov 2005 11:38:01 +1100 [thread overview]
Message-ID: <20051103113801.E6081538@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0511030116160.2023@artax.karlin.mff.cuni.cz>; from mikulas@artax.karlin.mff.cuni.cz on Thu, Nov 03, 2005 at 01:19:10AM +0100
On Thu, Nov 03, 2005 at 01:19:10AM +0100, Mikulas Patocka wrote:
> >> either). Does XFS support a something like ext3's "data=ordered" mount
> >> option?
> >
> > No, it doesn't.
>
> BTW. Why does it sometimes overwrite files with zeros after crash and
> journal replay then? I thought that this was because it tries to avoid
> users seeing uninitialized data.
No, thats kinda related but not the same issue, its more to do
with a truncate (or open(O_TRUNC)) followed by buffered writes
to an existing file, which some applications do, and how that
interacts poorly with delayed allocation (nothing is "overwritten
with zeroes", its actually just a "hole").
But I do intend to get _some_ work done today, so you can google
for a more detailed answer there if you're interested.
cheers.
--
Nathan
next prev parent reply other threads:[~2005-11-03 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 21:27 Jan Kasprzak
2005-11-02 23:11 ` Nathan Scott
2005-11-02 23:36 ` Jan Kasprzak
2005-11-02 23:49 ` Nathan Scott
2005-11-03 0:03 ` Jan Kasprzak
2005-11-03 0:11 ` Nathan Scott
2005-11-03 12:45 ` Alan Cox
2005-11-03 17:05 ` Theodore Ts'o
2005-11-09 16:55 ` Jan Kasprzak
2005-11-03 0:19 ` Mikulas Patocka
2005-11-03 0:38 ` Nathan Scott [this message]
2005-11-03 0:41 ` Glen Overby
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=20051103113801.E6081538@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=kas@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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
all inboxes | Powered by JetHome®