On 3/7/13 7:04 AM, 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 ?
$ mkfs.xfs -dfile,name=fsfile,size=1536g
meta-data=fsfile isize=256 agcount=4, agsize=100663296 blks
= sectsz=512 attr=2, projid32bit=0
data = bsize=4096 blocks=402653184, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=196608, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Default would be 768M w/ current xfsprogs.
So I'd say yes it's short. You might do well to re-examine any old, crufty
"engineer left a while ago" tunings. Defaults are defaults for a reason,
if you don't know why you're tuning something it may well be the wrong
choice.
-Eric
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
