Re: Label multimeanings : doc bug?
Hello,
On Wed, Feb 27, 2019 at 09:37:58AM +0300, Reco wrote:
> Running parted on a logical volume is definitely not the best of ideas.
As an aside, I do this all the time and it works fine.
The logical volumes are exported to virtual machines as their main disk,
so they may appear as /dev/vgname/lvname on the host which when
partitioned and presented to a guest will show as /dev/xvda{1,2,…}.
If I want to later manipulate the partition table from outside the
guest I may run parted on the /dev/vgname/lvname.
Similar is expected to work on disk image files.
Direct access in the host to the partitions on such a thing as block
devices can be enabled by using kpartx (or fiddling with offsets in
losetup, but life is too short!).
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Label multimeanings : doc bug?
Le 27/02/2019 à 18:53, Richard Hector a écrit : On 27/02/19 9:57 PM, Reco wrote: A disklabel, as they call it in parted(8) applies to a disk device. Or a LUN. Or any other partitionable block device, such as a software RAID array or a loop device. A LABEL= is a filesystem attribute, it's impossible to have one without a filesystem. A swap area can have a LABEL but is not a filesystem. It appears that GPT also supports a partition label, separate from any filesystem label, and different from a BSD disklabel. In blkid terminology this is called PARTLABEL (along with PARTUUID) to distinguish them from filesystem LABEL/UUID.
Re: Label multimeanings : doc bug?
On 27/02/19 9:57 PM, Reco wrote: > Hi. > > On Tue, Feb 26, 2019 at 11:12:43PM -0800, Rusi Mody wrote: >> Reco wrote: >> Running parted on a logical volume is definitely not the best of ideas >> >> Sure! >> >> My point was however that for a tool (eg gparted) where label already has >> the LABEL= sense this other (disklabel) terminology, more common in the BSD >> world, seems to be an avoidable confusion. > > I see nothing to be confused about. > A disklabel, as they call it in parted(8) applies to a disk device. Or a LUN. > > A LABEL= is a filesystem attribute, it's impossible to have one without a > filesystem. It appears that GPT also supports a partition label, separate from any filesystem label, and different from a BSD disklabel. Richard signature.asc Description: OpenPGP digital signature
Re: Label multimeanings : doc bug?
Hi. On Tue, Feb 26, 2019 at 11:12:43PM -0800, Rusi Mody wrote: > Reco wrote: > Running parted on a logical volume is definitely not the best of ideas > > Sure! > > My point was however that for a tool (eg gparted) where label already has the > LABEL= sense this other (disklabel) terminology, more common in the BSD > world, seems to be an avoidable confusion. I see nothing to be confused about. A disklabel, as they call it in parted(8) applies to a disk device. Or a LUN. A LABEL= is a filesystem attribute, it's impossible to have one without a filesystem. Reco
Re: Label multimeanings : doc bug?
Reco wrote: Running parted on a logical volume is definitely not the best of ideas Sure! My point was however that for a tool (eg gparted) where label already has the LABEL= sense this other (disklabel) terminology, more common in the BSD world, seems to be an avoidable confusion.
Re: Label multimeanings : doc bug?
And the space between "disk" and "label" hardly helps any!
Re: Label multimeanings : doc bug?
Hi. On Tue, Feb 26, 2019 at 10:02:24PM -0800, Rusi Mody wrote: > My question: In his parted output he has > > Error: /dev/mapper/lubuntu--vg-home: unrecognised disk label > > In which sense is this 'label' used?? In this context, a disklabel is a "partition table type", like "msdos" or "gpt" or "sun". Running parted on a logical volume is definitely not the best of ideas. Reco
