[Top] [All Lists]

Re: mount: Structure needs cleaning

To: xfs@xxxxxxxxxxx
Subject: Re: mount: Structure needs cleaning
From: Brian Candler <B.Candler@xxxxxxxxx>
Date: Tue, 28 Feb 2012 09:14:41 +0000
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; s=sasl; bh=eKJ9tmC+PpkJpJTJG4QjqMLI5ao=; b=SukmT+W WlVxPokBL7lNMzbKzsdyIhPAMV/ksxQ8o79NVcUpuc6BcJ94lv1F6glnlNwQqZTE uU1Hhh9APB95Ifc+zxOFeZpC72GtHAZpl6WzbyXFhn8KtaWO0WntMGL8SUTZY+AS dt50L02Au6hcKazxTmS1XIoLH0HrWbEXNc50=
Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=sasl; b=M32UHkVVvFEkKJ7aVL8x39jxZTEtYeneg WKK020n6FN5Yb/NlWr7wQlhmWSY0iS9wSCMQ9iy1s9ZZQeSH5fogAO2eDo8ti0Iv /xhUOfnMpuqr7LPv+31bwOh1dy/sce4FzE8Sx5xUp1yXJDxuW9iKG17iH+V4jfU4 zVZ+6aWr28=
In-reply-to: <20120228014813.GU3592@dastard>
References: <33393100.post@xxxxxxxxxxxxxxx> <4F49B693.4080309@xxxxxxxxxxxxxxxxx> <33393429.post@xxxxxxxxxxxxxxx> <20120227004902.GQ3592@dastard> <33397518.post@xxxxxxxxxxxxxxx> <20120228014813.GU3592@dastard>
User-agent: Mutt/1.5.21 (2010-09-15)
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?

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.

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.



<Prev in Thread] Current Thread [Next in Thread>