[Top] [All Lists]

Re: XFS filesystem corruption

To: Julien FERRERO <jferrero06@xxxxxxxxx>
Subject: Re: XFS filesystem corruption
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 11 Mar 2013 09:11:45 +1100
Cc: stan@xxxxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CAPcwv6yAHAsmwgROs12gRtCbqTXBvTPrx8F-e4kYab2YApsobg@xxxxxxxxxxxxxx>
References: <CAPcwv6wZJSBtgF-L6KNSn6N6Y+wUZJFXdbcg+zYRwoaB2sDdjw@xxxxxxxxxxxxxx> <51380FD3.5010302@xxxxxxxxxxxxxxxxx> <CAPcwv6yAHAsmwgROs12gRtCbqTXBvTPrx8F-e4kYab2YApsobg@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Mar 07, 2013 at 02:04:32PM +0100, Julien FERRERO wrote:
> > It may be unrelated to your corruption, problem but I'm curious why you
> > are specifying a 32MB log section instead of letting mkfs.xfs make the
> > log size decision.
> I honestly don' know, the rebuild script was written 8 years ago by an
> engineer that since left the company.
> Is 32MB a short log space for a 1.5 TB of data ?

Depends on your workload.

And to tell the truth, the tiny log is probably the only reason that
your filesystems have gone this long without corruption, as the
small size will force frequent log writes and hence issue cache
flushes regularly....


Dave Chinner

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