public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Xiaoming Li" <forrubm2@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [help]How to block new write in a "Thin Provisioning" logical volume manager as a virtual device driver when physical spaces run out?
Date: Thu, 29 May 2008 11:31:59 +0100	[thread overview]
Message-ID: <20080529113159.113a7f06@core> (raw)
In-Reply-To: <5f7c1d2c0805290212i45aece46j7fae2dcf9c158b92@mail.gmail.com>

> As a result, with LVM, you can never export a "logical volume" with
> claimed storage space larger than of the underlying physical storage
> devices (e.g. SATA disks, Hardware RAID array etc.); but with ASD, you
> can export "logical volumes" which have much larger logical storage
> space.

Why do that ?

> Does anyone have some ideas for a better solution?

Take one file system such as ext3, or even a cluster file system like
GFS2 or OCFS. Create top level subdirectories in it for each machine.
Either export the subdirectory via NFS. Alternatively mount the clustered
file system somewhere on each node and then remount the subdirectory into
the right place in the file tree

(And for a clustered/shared pool root you can use pivot_root() to start
from initrd or local disk and then switch to running entirely within the
clusterfs)

Alan


  reply	other threads:[~2008-05-29 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29  9:12 [help]How to block new write in a "Thin Provisioning" logical volume manager as a virtual device driver when physical spaces run out? Xiaoming Li
2008-05-29 10:31 ` Alan Cox [this message]
2008-05-29 16:08   ` Rik van Riel
2008-05-29 23:04     ` Dave Chinner
2008-05-30  7:31       ` Christoph Hellwig
2008-06-02 17:22   ` Xiaoming Li
2008-06-02 19:41     ` Alan Cox

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=20080529113159.113a7f06@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=forrubm2@gmail.com \
    --cc=linux-kernel@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