3 Commits

Author	SHA1	Message	Date
Franck Bui	f8adf25d65	rules: skip btrfs check if devices are not ready in 64-btrfs.rules (#8304) ... If any devices are marked with 'SYSTEMD_READY=0' then we shouldn't run any btrfs check on them. Indeed there's no point in running "btrfs ready" on devices that already have SYSTEMD_READY=0 set. Most probably such devices are members of a higher layer aggregate device such as dm-multipath or software RAID. Doing IO on them wastes time at best, and may cause delays, timeouts, or even hangs at worst (think active-passive multipath or degraded RAID, for example). It was initially reported at: https://bugzilla.opensuse.org/show_bug.cgi?id=872929	2018-02-28 10:36:06 +01:00
Christian Hesse	d75b31837c	fix path in btrfs rule (#6844) ... Commit 0e8856d2 (assemble multidevice btrfs volumes without external tools (#6607)) introduced a call to udevadm. That lives in @rootbindir@, not @rootlibexecdir@. So fix the path.	2017-09-15 21:28:24 +02:00
g0tar	0e8856d25a	assemble multidevice btrfs volumes without external tools (#6607) ... assemble multidevice btrfs volumes without external tools This self-contained approach introduce very little overhead, unless someone has a large number of devices composing many btrfs volumes, in which case btrfs device scan would be faster. Still, having robust implementation is a nice to have alternative for btrfs-progs.	2017-09-07 09:58:12 +02:00