Util-Linux package development
 help / color / mirror / Atom feed
From: Xen <list@xenhideout.nl>
To: util-linux-ng@vger.kernel.org
Cc: util-linux@vger.kernel.org
Subject: PV on disk without partitions not recognised as LVM2_member
Date: Thu, 18 Aug 2016 22:39:30 +0200	[thread overview]
Message-ID: <c3d87222fe4f87eed72f61b6bc501344@dds.nl> (raw)

I am not getting a majordomo response (as usual, I guess, within a 
reasonable amount of time :p) to subscribe to this list, but....



Perchance,

Would someone be will to fix the issue that a Physical Volume from LVM2 
(PV) when placed directly on disk (no partitions or partition tables) 
will not be recognised as LVM2_member but rather as something else, such 
as "dos" (if nothing else is found) or e.g. some RAID device (if a RAID 
signature exists at the end of the device.

Ie. I had a disk that had a "promise fasttrack raid member" (from 
memory) signature at the end of the disk (last 1MB) and was recognised 
as such. When I wiped the signature, it was recognised as "dos":

/dev/sda: PTUUID="ef39c6e5" PTTYPE="dos"


pvck /dev/sda:

   Found label on /dev/sda, sector 1, type=LVM2 001
   Found text metadata area: offset=4096, size=1044480


The LVM2 udev rules for lvm-metad depend on blkid currently to report 
the nature of a block device such that they can know whether to activate 
it; as such a PV directly on disk will not get activated by udev rules.

Will also not get scanned, the whole pvscan --cache --activate ay 
command will not get executed.

It seems it would be best to solve it at the root of the issue rather 
than changing LVM's udev scripts.

Regards.

             reply	other threads:[~2016-08-19  2:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 20:39 Xen [this message]
2016-08-19  9:45 ` PV on disk without partitions not recognised as LVM2_member Xen
2016-08-19 11:14 ` Karel Zak
2016-08-19 15:10   ` Xen
2016-08-20 13:30   ` Xen
2016-08-20 14:13   ` Xen
2016-08-22  8:40     ` Karel Zak
2016-08-22 12:16       ` Xen
2016-08-30 10:24   ` Karel Zak

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=c3d87222fe4f87eed72f61b6bc501344@dds.nl \
    --to=list@xenhideout.nl \
    --cc=util-linux-ng@vger.kernel.org \
    --cc=util-linux@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