From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Can't mount or run fdisk on an existing logical volume, help!
Date: Wed, 22 Jul 2009 17:49:55 +0100 [thread overview]
Message-ID: <1248281395.14407.167.camel@breeves.fab.redhat.com> (raw)
In-Reply-To: <4A673358.2050104@whgl.uni-frankfurt.de>
On Wed, 2009-07-22 at 17:42 +0200, Sven Eschenberg wrote:
> All 'logical' block devices behave pretty much like physical ones.
>
> So you are free to put partition tables on top of lvs or dmcrypt block
> devices, you can aswell put each other on top of each other. It just
> adds possible layers of failure and or overhead.
Not really; Linux block devices don't have to support partitioning in
the kernel and this is the case for device-mapper devices.
In practice it doesn't make much difference since device-mapper also
allows arbitrary regions of existing devices to be mapped into a new
device. With a tool that can read and interpret partition table metadata
this allows partitioning to be added in user space for those devices
that don't support it natively.
> Since LVs give you the opportunity to be created in whatever size you
> wish, in many usage cases it is perfectly normal and straight forward to
> put a filesystem ontop of an LV instead of a partition table.
Yes, this is the typical usage. Partitioning LVs is mostly of use when
you for some reason want to treat the LV as a whole-disk image for a
device that would normally be partitioned, e.g. an image for a
virtualised system.
Regards,
Bryn.
next prev parent reply other threads:[~2009-07-22 16:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 19:55 [linux-lvm] Can't mount or run fdisk on an existing logical volume, help! Adam Olsen
2009-07-21 19:58 ` Ray Van Dolson
2009-07-21 20:01 ` Adam Olsen
2009-07-21 20:07 ` Ray Van Dolson
2009-07-21 20:29 ` Adam Olsen
2009-07-21 20:35 ` Ray Van Dolson
2009-07-21 20:46 ` Sven Eschenberg
2009-07-21 20:47 ` Adam Olsen
2009-07-21 21:07 ` Ray Van Dolson
2009-07-21 21:24 ` Adam Olsen
2009-07-21 21:59 ` Ray Van Dolson
2009-07-21 22:09 ` Adam Olsen
2009-07-21 22:21 ` Ray Van Dolson
2009-07-21 22:43 ` Adam Olsen
2009-07-21 22:50 ` Ray Van Dolson
2009-07-22 13:08 ` Bryn M. Reeves
2009-07-24 1:38 ` Ron Johnson
2009-07-22 13:17 ` Bryn M. Reeves
2009-07-22 5:26 ` Ron Johnson
2009-07-22 5:41 ` Adam Olsen
2009-07-22 5:49 ` Ron Johnson
2009-07-22 6:01 ` Adam Olsen
2009-07-22 15:42 ` Sven Eschenberg
2009-07-22 16:49 ` Bryn M. Reeves [this message]
2009-07-23 23:42 ` Adam Olsen
2009-07-22 13:06 ` Bryn M. Reeves
2009-07-22 13:05 ` Bryn M. Reeves
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=1248281395.14407.167.camel@breeves.fab.redhat.com \
--to=bmr@redhat.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).