From: Dave Chinner <david@fromorbit.com>
To: Brian Candler <B.Candler@pobox.com>
Cc: xfs@oss.sgi.com
Subject: Re: mount: Structure needs cleaning
Date: Wed, 29 Feb 2012 14:50:44 +1100 [thread overview]
Message-ID: <20120229035044.GY3592@dastard> (raw)
In-Reply-To: <20120228091441.GA1562@nsrc.org>
On Tue, Feb 28, 2012 at 09:14:41AM +0000, Brian Candler wrote:
> On Tue, Feb 28, 2012 at 12:48:13PM +1100, Dave Chinner wrote:
> > > Write cache: enabled
> >
> > There's your problem. You should read all the relevant sections on
> > write caches in the XFS FAQ. e.g:
> >
> > http://xfs.org/index.php/XFS_FAQ#Q._Which_settings_does_my_RAID_controller_need_.3F
>
> As a side question to this: if I am using Linux's md software RAID with an
> HBA, and XFS is using write barriers (as I believe it does by default), is
> it still necessary to disable write caching on the drives?
No. The MD layers pass the correct flushes to the drives now.
> My reading of the FAQ suggests that the write barrier by itself should be
> sufficient - but this requires that the md RAID driver implements write
> barriers correctly. I seem to remember reading a long time ago that LVM
> and/or dmraid didn't, although that may be different now.
It has since about 2.6.35.
> Incidentally I'm using 'mdadm ... -b internal' to ensure that the RAID array
> marks dirty areas, so that if a write part-completes (e.g. a block is
> written to only one half of a RAID1) then at next power-up this should be
> made consistent again.
Assuming that the dirty area tracking uses write cache flushes
correctly.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-29 3:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 3:15 mount: Structure needs cleaning MikeJeezy
2012-02-26 4:35 ` Stan Hoeppner
2012-02-26 7:22 ` MikeJeezy
2012-02-26 17:07 ` Stan Hoeppner
2012-02-27 0:49 ` Dave Chinner
2012-02-27 3:11 ` MikeJeezy
2012-02-27 6:28 ` Stan Hoeppner
2012-02-27 18:32 ` MikeJeezy
2012-02-28 1:48 ` Dave Chinner
2012-02-28 9:14 ` Brian Candler
2012-02-29 3:50 ` Dave Chinner [this message]
2012-02-29 7:40 ` Brian Candler
-- strict thread matches above, loose matches on Subject: below --
2014-10-12 8:43 Mount: " tommason
2014-10-12 14:20 ` Brian Foster
2014-10-12 22:39 ` tom mason
2014-10-12 22:48 ` tom mason
2014-10-12 22:51 ` tom mason
2014-10-12 23:10 ` Dave Chinner
2014-10-13 10:05 ` Tom Mason
2014-10-13 10:19 ` Emmanuel Florac
2014-10-13 10:40 ` Tom Mason
2014-10-13 9:26 ` Emmanuel Florac
2014-10-13 20:33 Tom Mason
2014-10-13 22:09 ` Dave Chinner
2014-10-13 22:25 ` Tom Mason
2014-10-13 23:44 ` Dave Chinner
2014-10-13 22:38 ` Tom Mason
2014-10-13 23:47 ` Dave Chinner
2014-10-14 10:55 ` Emmanuel Florac
2014-10-14 15:46 ` Tom Mason
2014-10-14 16:38 ` Emmanuel Florac
2014-10-14 16:43 ` Tom Mason
2014-10-21 20:44 ` Tom Mason
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=20120229035044.GY3592@dastard \
--to=david@fromorbit.com \
--cc=B.Candler@pobox.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 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.