From: Jeremy Higdon <jeremy@sgi.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: XFS write speed drop
Date: Wed, 24 May 2006 00:16:00 -0700 [thread overview]
Message-ID: <20060524071600.GF586512@sgi.com> (raw)
In-Reply-To: <20060524091741.D267844@wobbly.melbourne.sgi.com>
On Wed, May 24, 2006 at 09:17:41AM +1000, Nathan Scott wrote:
> On Wed, May 24, 2006 at 08:22:19AM +1000, Nathan Scott wrote:
> >
> > Not sure what you're trying to say here. Yes, barriers are on
> > by default now if the hardware supports them, yes, they will
> > slow things down relative to write-cache-without-barriers, and
> > yes we all knew that ... its not the case that someone "did not
> > notice" or forgot about something. There is no doubt that this
> > is the right thing to be doing by default - there's no way that
> > I can tell from inside XFS in the kernel that you have a UPS. ;)
>
> Oh, I realised I've slightly misread your mail, you said...
>
> | I do not actually need barriers (or an UPS, to poke on another thread),
> | because power failures are rather rare in Germany.
>
> Hmm, even harder for us to detect at runtime, in the kernel,
> that you're in Germany. :)
>
> Power failures aren't the only thing to cause crashes, however.
There have been several examples of filesystem corruption without
power failures too, though that is a common cause. It can even happen
on a normal system shutdown if there is no synchronize operation to
the disk at shutdown time, depending on how much data is in the cache
and how long you have until the ATA chip is reset.
jeremy
next prev parent reply other threads:[~2006-05-24 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 9:34 XFS write speed drop Jan Engelhardt
2006-05-22 0:53 ` Nathan Scott
2006-05-22 12:21 ` Jan Engelhardt
2006-05-22 22:43 ` Nathan Scott
2006-05-23 13:23 ` Jan Engelhardt
2006-05-23 22:22 ` Nathan Scott
2006-05-23 23:17 ` Nathan Scott
2006-05-24 7:16 ` Jeremy Higdon [this message]
2006-05-26 7:20 ` Helge Hafting
2006-05-26 8:51 ` Jan Engelhardt
2006-05-26 21:06 ` Bernd Eckenfels
2006-05-23 1:26 ` David Chinner
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=20060524071600.GF586512@sgi.com \
--to=jeremy@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=xfs@oss.sgi.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