public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] LVM/RAID/FS integration
Date: Mon, 09 Jul 2007 14:09:46 -0400	[thread overview]
Message-ID: <469279EA.4020702@cfl.rr.com> (raw)
In-Reply-To: <6f703f960706271609m6fdfb9c1ha3555a68fe1d9d55@mail.gmail.com>

Kent Overstreet wrote:
> The trouble is it's completely impractical with current tools; we need
> tighter integration between md and LVM. Basically, we need a new type
> of VG; you'd only be able to make it out of PVs that are the same size
> (or close). Then, when you create an LV you decide what kind of
> redundancy you want; the LVM internally creates multiple LVs and raids
> them together to make the LV the fs sees.

In theory LVM is meant to handle the raid bits as well, once the mirror 
target is improved to properly handle error correction, and the raid5 
target stabilizes.  Thus md won't be needed, you will just need an 
interface between the filesystem and lvm.

> This could, sort of, be done in userspace, but I think it'll work
> better if dm and md are better integrated in the kernel. I thought i'd
> throw out my ideas before I get too far in. Thoughts?

This is the kind of thing that should go in userspace.  The filesystem 
should just fire off events that tell a userspace daemon things like 
"the raid5 volume is now at x% use" and let it choose the policy, 
possibly by asking lvm to resize the underlying volume, then sending a 
message back to the fs that the volume has been resized, and it can 
start using the extra space.


      parent reply	other threads:[~2007-07-09 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 23:09 [RFC] LVM/RAID/FS integration Kent Overstreet
2007-06-29  9:39 ` Andi Kleen
2007-07-09 18:09 ` Phillip Susi [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=469279EA.4020702@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=kent.overstreet@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