6 Commits

Author	SHA1	Message	Date
Peter Rajnoha	ed166a3b1d	wiping: wipe DM_snapshot_cow signature without prompt in newly created LVs ... The libblkid can detect DM_snapshot_cow signature and when creating new LVs with blkid wiping used (allocation/use_blkid_wiping=1 lvm.conf setting and --wipe y used at the same time - which it is by default). Do not issue any prompts about this signature when new LV is created and just wipe it right away without asking questions. Still keep the log in verbose mode though.	2014-02-10 13:28:13 +01:00
Peter Rajnoha	6a1957badc	pvcreate: do not issue warning about any existing PV ... If we're calling pvcreate on a device that already has a PV label, the blkid detects the existing PV and then we consider it for wiping before we continue creating the new PV label and we issue a warning with a prompt whether such old PV label should be removed. We don't do this with native signature detection code. Let's make it consistent with old behaviour. But still keep this "PV" (identified as "LVM1_member" or "LVM2_member" by blkid) detection when creating new LVs to avoid unexpected PV label appeareance inside LV.	2013-11-28 13:14:46 +01:00
Peter Rajnoha	eaa23d3273	wiping: add support for blkid wiping ... This is actually the wipefs functionailty as a matter of fact (wipefs uses the same libblkid calls). libblkid is more rich when it comes to detecting various signatures, including filesystems and users can better decide what to erase and what should be kept. The code is shared for both pvcreate (where wiping is necessary to complete the pvcreate operation) and lvcreate where it's up to the user to decide. The verbose output contains a bit more information about the signature like LABEL and UUID. For example: raw/~ # lvcreate -L16m vg WARNING: linux_raid_member signature detected on /dev/vg/lvol0 at offset 4096. Wipe it? [y/n] or more verbose one: raw/~ # lvcreate -L16m vg -v ... Found existing signature on /dev/vg/lvol0 at offset 4096: LABEL="raw.virt:0" UUID="da6af139-8403-5d06-b8c4-13f6f24b73b1" TYPE="linux_raid_member" USAGE="raid" WARNING: linux_raid_member signature detected on /dev/vg/lvol0 at offset 4096. Wipe it? [y/n] The verbose output is the same output as found in blkid.	2013-11-27 15:49:15 +01:00
Peter Rajnoha	03c941a4ca	device: cleanup signature wiping functions ... The wipe_known_signatures fn now wraps the _wipe_signature fn that is called for each known signature (currently md, swap and luks). This patch makes the code more readable, not repeating the same sequence when used anywhere in the code. We're going to reuse this code later...	2013-11-27 12:56:58 +01:00
Alasdair G Kergon	527db4645f	gcc: replace #ifdef linux with __linux__	2013-11-13 13:56:29 +00:00
Peter Rajnoha	c6f48b7c1a	refactor: make device type recognition code common for general use ... Changes: - move device type registration out of "type filter" (filter.c) to a separate and new dev-type.[ch] for common use throughout the code - the structure for keeping the major numbers detected for available device types and available partitioning available is stored in "dev_types" structure now - move common partitioning detection code to dev-type.[ch] as well together with other device-related functions bound to dev_types (see dev-type.h for the interface) The dev-type interface contains all common functions used to detect subsystems/device types, signature/superblock recognition code, type-specific device properties and other common device properties (bound to dev_types), including partitioning support. - add dev_types instance to cmd context as cmd->dev_types for common use - use cmd->dev_types throughout as a central point for providing information about device types	2013-06-12 12:08:56 +02:00