linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Chris Allen <chris@cjx.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multiple raids on one machine?
Date: Tue, 27 Jun 2006 17:08:59 +0100	[thread overview]
Message-ID: <87odwefun8.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <44A117A3.5040203@cjx.com> (Chris Allen's message of "Tue, 27 Jun 2006 12:33:55 +0100")

On Tue, 27 Jun 2006, Chris Allen wondered:
> Nix wrote:
>> There is a third alternative which can be useful if you have a mess of
>> drives of widely-differing capacities: make several RAID arrays so as to tesselate
>> space across all the drives, and then pile an LVM on the top of all of them to
>> fuse them back into one again.
> 
> But won't I be stuck with the same problem? ie I'll have a single 12TB
> lvm, and won't be able to use EXT3 on it?

Not without ext3 patches (until the very-large-ext3 patches now pending
on l-k go in), sure. But because it's LVMed you could cut it into a couple
of exg3 filesystems easily. (I find it hard to imagine a single *directory*
whose children contain 12Tb of files in a form that you can't cut into
pieces with suitable use of bind mounts, but still, perhaps such exists.)

-- 
`NB: Anyone suggesting that we should say "Tibibytes" instead of
 Terabytes there will be hunted down and brutally slain.
 That is all.' --- Matthew Wilcox

      reply	other threads:[~2006-06-27 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25 22:37 Multiple raids on one machine? Chris Allen
2006-06-25 22:44 ` Jim Buttafuoco
2006-06-25 22:46 ` H. Peter Anvin
2006-06-26  0:16 ` Bill Davidsen
2006-06-26  8:05 ` Gordon Henderson
2006-06-26  8:47   ` Chris Allen
2006-06-27  9:56 ` Nix
2006-06-27 11:33   ` Chris Allen
2006-06-27 16:08     ` Nix [this message]

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=87odwefun8.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=chris@cjx.com \
    --cc=linux-raid@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).