public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Grant <mggr@pml.ac.uk>
To: "Svavar Örn Eysteinsson" <svavar@fiton.is>
Cc: xfs@oss.sgi.com
Subject: Re: Recommendation on XFS Filesystem Creation, Lefthand P4500, iSCSI ?
Date: Tue, 19 Jun 2012 13:17:11 +0100	[thread overview]
Message-ID: <4FE06DC7.2060204@pml.ac.uk> (raw)
In-Reply-To: <4FE050C2.8060601@fiton.is>

Hi Svavar,

On 06/19/2012 11:13 AM, Svavar Örn Eysteinsson wrote:
> We recently purchased HP Lefthand 4500 G2 24TB iSCSI SAN Box.
> The Box is configured in RAID6. (and yes, we are going to expand that with
> another boxes in near future).
> I need to create a 7TB volume at the start, and grow it in near future.

We have a couple of NAS servers (just direct disk connection, not iSCSI) 
with XFS filesystems up to ~30TB, but didn't do anything special for 
those (just defaults on everything, iirc).

The only problem we had was with filesystems bigger than that, where we 
get kernel crashes due to XFS overflowing the stack.  Apparently this 
may be worse if you NFS-share XFS layered over LVM (more stuff on the 
stack, I guess), but I imagine you'd be fine with 7TB.

Cheers,

Mike.

<br />
<hr />
<p><font face="Arial" size="1">
Plymouth Marine Laboratory<br />
Registered Office: <br />
Prospect Place<br />
The Hoe<br />
Plymouth  PL1 3DH
</font></p>

<p><font face="Arial" size="1">Website: <a href="http://www.pml.ac.uk">www.pml.ac.uk</a>
<br />
<a href="http://www.pml.ac.uk/pdf/PML%20Annual%20Review%202011_2.pdf">Click here for the latest PML Annual Review</a>
<br />
Registered Charity No. 1091222<br />
PML is a company limited by guarantee<br />
registered in England & Wales<br />
company number 4178503</font></p>

<p><font face="Arial" size="1" color="green">Please think before you print.</font></p>

<hr />

<p><font face="Arial" size="1">This e-mail, its content and any file attachments are confidential.</font></p>

<p><font face="Arial" size="1">If you have received this e-mail in error please do not copy, disclose it to any third party or use the contents or attachments in any way. Please notify the sender by replying to this e-mail or e-mail forinfo@pml.ac.uk and then delete the email without making any copies or using it in any other way.</font></p>

<p><font face="Arial" size="1">The content of this message may contain personal views which are not the views of Plymouth Marine Laboratory unless specifically stated.</font></p>

<p><font face="Arial" size="1">You are reminded that e-mail communications are not secure and may contain viruses. Plymouth Marine Laboratory accepts no liability for any loss or damage which may be caused by viruses.</font></p>

<hr />
<br />
<br />

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-06-19 12:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 10:13 Recommendation on XFS Filesystem Creation, Lefthand P4500, iSCSI ? Svavar Örn Eysteinsson
2012-06-19 12:17 ` Mike Grant [this message]
2012-06-19 17:00 ` Peter Grandi

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=4FE06DC7.2060204@pml.ac.uk \
    --to=mggr@pml.ac.uk \
    --cc=svavar@fiton.is \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox