mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chris Wedgwood <cw@f00f.org>
Cc: Al Boldi <a1426z@gawab.com>, "'Nathan Scott'" <nathans@sgi.com>,
	linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: SPAM: Re: XFS corruption during power-blackout
Date: 30 Jun 2005 01:11:03 +0200	[thread overview]
Message-ID: <p73irzw3gjc.fsf@verdi.suse.de> (raw)
In-Reply-To: <254889.27725ab660aa106eb6acc07307d71ef1fbd5b6fd366aebef9e2f611750fbcb467e46e8a4.IBX@taniwha.stupidest.org.suse.lists.linux.kernel>

Chris Wedgwood <cw@f00f.org> writes:

> If caching is enabled I still lose data.  Linux does have a concept of
> write barriers but these are presently not implemented for XFS right
> now.

I implemented them some time ago for log writes in XFS. Not for fsync though,
although fsync usually does a log write afterwards so it should work
in practice too. fdatasync might not.

Don't know if the code hasn't bit rotted away and it also was a bit
dumb. It was definitely there at some point.

But then a lot of ATA disks and SCSI don't support barriers. Or at least
the IDE barrier tests fails on several of my machines.

-Andi

       reply	other threads:[~2005-06-29 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050629001847.GB850@frodo.suse.lists.linux.kernel>
     [not found] ` <200506290453.HAA14576@raad.intranet.suse.lists.linux.kernel>
     [not found]   ` <556815.441dd7d1ebc32b4a80e049e0ddca5d18e872c6e8a722b2aefa7525e9504533049d801014.ANY@taniwha.stupidest.org.suse.lists.linux.kernel>
     [not found]     ` <42C2E0BC.8040508@xfs.org.suse.lists.linux.kernel>
     [not found]       ` <254889.27725ab660aa106eb6acc07307d71ef1fbd5b6fd366aebef9e2f611750fbcb467e46e8a4.IBX@taniwha.stupidest.org.suse.lists.linux.kernel>
2005-06-29 23:11         ` Andi Kleen [this message]
2005-06-30  4:34           ` Chris Wedgwood

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=p73irzw3gjc.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=a1426z@gawab.com \
    --cc=cw@f00f.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=nathans@sgi.com \
    --cc=reiserfs-list@namesys.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 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®