From: Fredrik Tolf <fredrik@dolda2000.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM onFly features
Date: Sun, 11 Dec 2005 15:08:55 +0100 [thread overview]
Message-ID: <1134310136.26999.4.camel@pc7.dolda2000.com> (raw)
In-Reply-To: <1cbd6f830512101938g4ec7d36dq4fd9a081658edf47@mail.gmail.com>
On Sat, 2005-12-10 at 22:38 -0500, Mag Gam wrote:
> thanks everyone for their kind replies.
>
> So, will LVM and FS (ext2/3 in particular )ever be considered as 1?
> This would be nice for ease of devt.
If they would be considered as one, it wouldn't be LVM anymore. LVM is a
pure block device layer, and as such will always have to FS layered
above.
However, stuff like Solaris ZFS does make sense, too, if you ask me.
Having a filesystem managing several block devices allows for pretty
neat stuff, such as per-file replication or striping, which would be
really sweet.
That said, such a thing would, of course, be completely unrelated to
LVM.
Fredrik Tolf
next prev parent reply other threads:[~2005-12-11 14:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 19:38 [linux-lvm] LVM onFly features Mag Gam
2005-12-10 19:48 ` Marc-Jano Knopp
2005-12-10 20:03 ` Michael Loftis
2005-12-10 20:06 ` Marc-Jano Knopp
2005-12-10 20:14 ` Michael Loftis
2005-12-10 20:22 ` Marc-Jano Knopp
2005-12-10 22:10 ` Michael Loftis
2005-12-10 22:31 ` Marc-Jano Knopp
2005-12-10 22:44 ` Michael Loftis
2005-12-10 22:51 ` Michael Loftis
2005-12-10 23:03 ` Marc-Jano Knopp
2005-12-11 3:38 ` Mag Gam
2005-12-11 7:43 ` Michael Loftis
2005-12-11 14:08 ` Fredrik Tolf [this message]
2005-12-11 15:32 ` Mag Gam
2005-12-15 20:44 ` David Johnston
2005-12-18 0:27 ` Mag Gam
2005-12-11 22:15 ` Nathan Scott
2005-12-12 1:14 ` Michael Loftis
2005-12-12 2:28 ` Nathan Scott
2005-12-10 20:47 ` Graham Wood
2005-12-13 16:56 ` Stephen C. Tweedie
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=1134310136.26999.4.camel@pc7.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).