4 Commits

Author	SHA1	Message	Date
Peter Rajnoha	c1ce99cd81	Detect the lvm binary path in lvmetad udev rules. ... We can't use 'DM_SBIN_PATH'. This one is set only for DM devices but not for all block devices - the pvscan is run on all relevant block devices! This LVM_SBIN_PATH (as well as DM_SBIN_PATH) detection should be removed eventually but for upstream solution, we still have to do that as there are known cases where the binaries are put either in /sbin or /usr/sbin (some installation systems, initrd systems etc.).	2012-03-12 08:59:55 +00:00
Alasdair Kergon	9f354a1cae	Switch pvscan --cache major:minor to --major --minor.	2012-03-06 02:30:49 +00:00
Alasdair Kergon	fdfa12d956	Change pvscan --lvmetad to pvscan --cache.	2012-03-02 18:09:46 +00:00
Peter Rajnoha	a80e4e0d1f	Add skeleton for lvmetad udev rules - 69-dm-lvm-metad.rules. ... Why using the order 69: - Storage processing in general happens in 60-persistent-storage.rules, including the blkid call that adds some usable information we can use for filtering and speedup (these rules are part of upstream udev and the order is preserved on most distros) - There's still some other storage-related processing done after 60-persistent-storage.rules in general. These might add some detailed storage-related information we might use to filter devices effectively (e.g. MD udev rules, ...). - We need lvmetad rules to be processed before any consumers can use the output - so the metadata cache is ready soon enough (e.g. udisks rules). - There's no official (upstream udev) document about assigning the order, so this number is chosen in best belief it will suit all scenarios.	2012-02-24 09:53:12 +00:00