public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: david@lang.hm
Cc: xfs@oss.sgi.com
Subject: Re: 128TB filesystem limit?
Date: Thu, 25 Mar 2010 23:35:28 -0500	[thread overview]
Message-ID: <4BAC3990.30403@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1003251900110.12435@asgard.lang.hm>

david@lang.hm wrote:
> On Fri, 26 Mar 2010, Dave Chinner wrote:

...

>> Is there any reason for putting partitions on these block devices?
>> You could just use the block devices without partitions, and that
>> will avoid alignment potential problems....
> 
> I would like to raid to auto-assemble and I can't do that without
> partitions, can I

I think you can.... it's not like MD is putting anything in the partition
table; you just give it block devices, I doubt it cares if it's a whole
disk or some partition.

Worth a check anyway ;)

...


> the next fun thing is figuring out what sort of stride, etc parameters I
> should have used for this filesystem.

mkfs.xfs should suss that out for you automatically based on talking to md;
of course you'd want to configure md to line up well with the hardware
alignment.

-Eric

> David Lang

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

  reply	other threads:[~2010-03-26  4:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 23:15 128TB filesystem limit? david
2010-03-25 23:54 ` Dave Chinner
2010-03-26  0:03   ` david
2010-03-26  0:35     ` Dave Chinner
2010-03-26  2:02       ` david
2010-03-26  4:35         ` Eric Sandeen [this message]
2010-03-26  4:56           ` david
2010-03-26  6:09             ` Stan Hoeppner
2010-03-26  7:26             ` Steve Costaras
2010-03-27  9:06 ` Emmanuel Florac
2010-03-27 14:28   ` Steve Costaras
2010-03-27 18:45   ` david
2010-03-28 21:17 ` 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=4BAC3990.30403@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@lang.hm \
    --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