mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Miguel Sousa Filipe" <miguel.filipe@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: FEATURE REQUEST: merge MD software raid and LVM in one unique layer.
Date: Wed, 2 May 2007 20:18:55 +0100	[thread overview]
Message-ID: <f058a9c30705021218p4fdb4747kb5b4b9000ad50ef2@mail.gmail.com> (raw)
In-Reply-To: <f058a9c30705021214k75da330ai4d79a2b6b2806652@mail.gmail.com>

Hello kernel hackers,

Some weeks ago, in a ZFS related thread, some kernel hackers asked the
user what did they liked in ZFS that linux didn't have, so that they
could (possibly) work on it.

So, here is my feature request:
- merge MD software raid framework and LVM in one unique
API/framework, to be controled/managed by one unique userland
toolset.


Any sysadmin which needs to do device & volume management and FS
management in Linux has do use three diferent tools, for 3 diferent
layers (that I think shouldn't be 3 layers.. but only 2).
- md :
   MD is a software raid framework, with raid0, 1, 4, 5, 6, append and others..
- lvm :
  The logical volume manager: this allows you to manage logical disks
(devices), grow a  device, add phisical devices to a existing volume,
snapshot.. etc..
- fs
 duh... the FileSystem level.


However, MD and LVM have feature replications:
- raid1 / mirroring
- raid0 / stripping
- append / concatenate

I find it high irritanting having two kernel interfaces and two
userland tools that provide the same funcionality, which one should I
use?

I also don't understand from the point of view of code maintenance..
shurely there is some unneeded duplicate code lying in the kernel
tree.

One of the  good things (my opinion) about ZFS is putting these things
in one unique place, with a good user interface (the zpool & other zfs
command tools are quite easy and simple to use).

On linux, I find myself having to setup each layer by hand, each with
its own peculiarities and command line tools.. I consede that maybe
the FS layer and the device management layer shouldn't be merged.
But clearly that in Linux we have too different layers (that aren't
really layers since they do not depend on one another) for the same
purpose:
- device manangement.

I'm no kernel hacker, I'm just a simple user, but this is my *pretty
please* that some kernel hackers work together to unite and simplify
the work that has to be made to use software raid and volume
management on Linux.

In essence, I believe that bringing the funcionality that is unique to
MD integrated in LVM would suffice (leaving MD there for legacy compat.. but
warning users about future improvements on LVM only)

Thank you very much,


PS: I'm not subscribed to lkml yet, please CC me any reply
-- 
Miguel Sousa Filipe

       reply	other threads:[~2007-05-02 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f058a9c30705021214k75da330ai4d79a2b6b2806652@mail.gmail.com>
2007-05-02 19:18 ` Miguel Sousa Filipe [this message]
2007-05-02 20:10   ` Diego Calleja
2007-05-02 20:51     ` Miguel Sousa Filipe
2007-05-03  0:58       ` david
2007-05-03  1:33         ` It's a bug of printk? gshan
2007-05-03  8:08         ` FEATURE REQUEST: merge MD software raid and LVM in one unique layer David Greaves
2007-05-03  9:25           ` Miguel Sousa Filipe

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=f058a9c30705021218p4fdb4747kb5b4b9000ad50ef2@mail.gmail.com \
    --to=miguel.filipe@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

all inboxes | Powered by JetHome®