From: Richard Scobie <richard@sauce.co.nz>
To: xfs@oss.sgi.com
Subject: Re: XFS over LVM over md RAID
Date: Sat, 11 Sep 2010 11:08:11 +1200 [thread overview]
Message-ID: <4C8ABA5B.7080604@sauce.co.nz> (raw)
Stan Hoeppner wrote:
> What is the reasoning behind adding so many terabytes under a single
filesystem?
Heavily scripted project environments, where initial storage estimates
are exceeded and more needs to be added without the complications of
managing seperate filesystems part way through.
It is unlikely that more than 2 arrays would be involved and I used the
example to try and understand how XFS adapts to changing topologies.
Regards,
Richard
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-09-10 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 23:08 Richard Scobie [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-09 22:58 XFS over LVM over md RAID Richard Scobie
2010-09-10 0:25 ` Michael Monnerie
2010-09-10 0:52 ` Richard Scobie
2010-09-10 1:14 ` Richard Scobie
2010-09-10 1:30 ` Dave Chinner
2010-09-10 2:29 ` Richard Scobie
2010-09-10 14:24 ` Eric Sandeen
2010-09-10 21:42 ` Richard Scobie
2010-09-10 22:19 ` Stan Hoeppner
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=4C8ABA5B.7080604@sauce.co.nz \
--to=richard@sauce.co.nz \
--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