[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: LSI MegaRAID SAS 9240-4i hangs system at boot



On Thu, 14 Jun 2012 08:38:27 -0500
Stan Hoeppner <stan@hardwarefreak.com> wrote:

> Couldn't hurt.  And while you're at it, mount with "inode64" in your
> fstab immediately after you create the XFS.  You were running with
> inode32, which sticks all the inodes at the front of AG0 causing lots
> of seeks.  Inode64 puts file/dir inodes in the AG where the file gets
> written.  In short, inode64 is more efficient for most workloads.  And
> this is also why getting the agcount correct is so critical with
> tiered linear/striped parity setups such as this.
> 
> When you recreate the XFS use 'agcount=6'.  That's the smallest you
> can go with 2TB disks.  A force will be required since you already
> have an XFS on the device.

Sorry I haven't much time now. I'm invoted to a BBQ and already
hungry :-)

I just wanted to create the filesystem and start to copy the files.

So I tried and got this warning:

~$ sudo mkfs.xfs -f -d agcount=6,su=131072,sw=3 /dev/md0
Warning: AG size is a multiple of stripe width.  This can cause
performance problems by aligning all AGs on the same disk.  To avoid
this, run mkfs with an AG size that is one stripe unit smaller, for
example 244189120.

Should I take this seriously?


Btw: Should I mount every xfs filesystem (also the one for the mythtv
recordings) with inode64.
This is not true for the smaller ext4 filesystems I use for the os and
the home dir I suppose?


Cheers
Ramon


Reply to: