From: Arjan van de Ven <arjan@infradead.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Grzegorz Kulewski <kangur@polcom.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to flush data to disk reliably?
Date: Mon, 02 May 2005 19:17:16 -0400 [thread overview]
Message-ID: <1115075836.6501.2.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.3.96.1050502182749.28303A-100000@gatekeeper.tmr.com>
On Mon, 2005-05-02 at 18:30 -0400, Bill Davidsen wrote:
> On Mon, 2 May 2005, Alan Cox wrote:
>
> > On Llu, 2005-05-02 at 20:18, Grzegorz Kulewski wrote:
> > > What about other filesystems? Does anybody know anwser for Reiserfs3,
> > > Reiser4, JFS, XFS and any other popular server filesystems? I assume that
> > > if log file is some block device (like partition) both O_SYNC and fsync
> > > will work? What about ext2? What about some strange RAID/DM/NBD
> > > configurations? (I do not know in advance what our customers will use so I
> > > need portable method.)
> >
> > RAID does stripe sized rewrites so you get into the same situation as
> > with actual disks - a physical media failure might lose you old data
> > (but then if the disk goes bang so does the data...)
>
> I hope I'm reading that wrong, and that rewriting a single sector of a
> file doesn't result in r-a-w of the entire stripe. That would be a large
> memory hit for filesystems with large stripes for mostly sequential i/o.
it results in a read of the entire stripe and at least two writes (the
actual data and the new parity)
the alternative (and I don't think linux does that) is to read the old
data sector, and do an differential xor.
prev parent reply other threads:[~2005-05-02 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 13:23 How to flush data to disk reliably? Grzegorz Kulewski
2005-05-02 17:52 ` Alan Cox
2005-05-02 19:18 ` Grzegorz Kulewski
2005-05-02 21:41 ` Alan Cox
2005-05-02 22:30 ` Bill Davidsen
2005-05-02 23:17 ` Arjan van de Ven [this message]
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=1115075836.6501.2.camel@localhost.localdomain \
--to=arjan@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
/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