public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Miguel Sousa Filipe <miguel.filipe@gmail.com>
Cc: david@lang.hm, Diego Calleja <diegocg@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: FEATURE REQUEST: merge MD software raid and LVM in one unique layer.
Date: Thu, 03 May 2007 09:08:22 +0100	[thread overview]
Message-ID: <46399876.2030800@dgreaves.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705021756210.5342@asgard.lang.hm>

david@lang.hm wrote:
> On Wed, 2 May 2007, Miguel Sousa Filipe wrote:
> 
>> On 5/2/07, Diego Calleja <diegocg@gmail.com> wrote:
>>>  El Wed, 2 May 2007 20:18:55 +0100, "Miguel Sousa Filipe"
>>>  <miguel.filipe@gmail.com> escribió:
>>>
>>> >  I find it high irritanting having two kernel interfaces and two
>>> >  userland tools that provide the same funcionality, which one should I
>>> >  use?
>>>
>>>  I doubt users care about kernel's design; however the lack of
>>> unification of  userspace tools is a real problem. Just my 2¢.

>> This is also a problem for any developer who tries to improve
>> usability in this area by creating some unified userland tools to
>> manipulate MD & LVM. (Imagining myself implementing some userland tool
>> to create some "storage devices" + mount points.. doesn't  seem easy
>> nor fun..).
> 
> why do you care if the userspace tool that does the resizing makes
> system calls to one layer or to two layers? how would you know?

Indeed!!

EVMS

http://evms.sourceforge.net/

Enterprise Volume Management System

In order to make the transition to EVMS as smooth as possible, EVMS includes
compatibility with a number of existing storage and volume management systems.
Currently, EVMS recognizes:

    * All locally attached disks
    * DOS-style disk partitions (used extensively on Linux systems)
    * GPT disk partitions (mainly used on IA-64)
    * S/390 disk partitions (CDL/LDL)
    * BSD disk partitions
    * Macintosh disk partitions
    * Linux MD/Software-RAID devices
    * Linux LVM volume groups and logical volumes (versions 1 and 2)

Anything else?

Oh... yes:

In addition to providing compatibility with these existing systems, EVMS also
provides new functionality that can be built on top of any of the above
"volumes" that EVMS already recognizes. Features that are currently included are:

    * Bad Block Relocation
    * Linear Drive Linking
    * Generic Snapshotting

Enough? or would you like:
In addition to these volume-level features, the EVMS tools provide convenient
integration with numerous filesystem tools, to allow tasks such as mkfs and fsck
directly from the EVMS user interfaces. Currently, the following filesystems are
supported:

    * Ext2/3
    * JFS
    * ReiserFS
    * XFS
    * Swap
    * OCFS2
    * NTFS
    * FAT

??
Oh, and for the l33t there's a GUI and screenshots...

Of course, in keeping with ZFS, this management layer is all proprietary and
costs megabucks - or is it GPL, can never remember...

Damn that "irritanting" architecture - keeps us from doing cool things...

Seriously - I hope this is useful ;)

David

  parent reply	other threads:[~2007-05-03  8:38 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 ` FEATURE REQUEST: merge MD software raid and LVM in one unique layer Miguel Sousa Filipe
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         ` David Greaves [this message]
2007-05-03  9:25           ` FEATURE REQUEST: merge MD software raid and LVM in one unique layer 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=46399876.2030800@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=david@lang.hm \
    --cc=diegocg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.filipe@gmail.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