systemd/rules/64-btrfs.rules.in

# do not edit this file, it will be overwritten on update

SUBSYSTEM!="block", GOTO="btrfs_end"
ACTION=="remove", GOTO="btrfs_end"
ENV{ID_FS_TYPE}!="btrfs", GOTO="btrfs_end"

# let the kernel know about this btrfs filesystem, and check if it is complete
IMPORT{builtin}="btrfs ready $devnode"

# mark the device as not ready to be used by the system
ENV{ID_BTRFS_READY}=="0", ENV{SYSTEMD_READY}="0"

# reconsider pending devices in case when multidevice volume awaits
ENV{ID_BTRFS_READY}=="1", RUN+="@rootbindir@/udevadm trigger -s block -p ID_BTRFS_READY=0"

LABEL="btrfs_end"
udev: add btrfs support All "btrfs" file systems will be registered with the kernel when they show up. Incomplete multi-device volumes will set SYSTEMD_READY=0, to prevent access until the volume is complete and fully registered. 2012-09-17 01:31:11 +04:00			`# do not edit this file, it will be overwritten on update`

			`SUBSYSTEM!="block", GOTO="btrfs_end"`
			`ACTION=="remove", GOTO="btrfs_end"`
			`ENV{ID_FS_TYPE}!="btrfs", GOTO="btrfs_end"`

			`# let the kernel know about this btrfs filesystem, and check if it is complete`
			`IMPORT{builtin}="btrfs ready $devnode"`

			`# mark the device as not ready to be used by the system`
			`ENV{ID_BTRFS_READY}=="0", ENV{SYSTEMD_READY}="0"`

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 10:58:12 +03:00			`# reconsider pending devices in case when multidevice volume awaits`
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 22:28:24 +03:00			`ENV{ID_BTRFS_READY}=="1", RUN+="@rootbindir@/udevadm trigger -s block -p ID_BTRFS_READY=0"`
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 10:58:12 +03:00
udev: add btrfs support All "btrfs" file systems will be registered with the kernel when they show up. Incomplete multi-device volumes will set SYSTEMD_READY=0, to prevent access until the volume is complete and fully registered. 2012-09-17 01:31:11 +04:00			`LABEL="btrfs_end"`