packages/utils/btrfs-progs/files/btrfs-scan.init

#!/bin/sh

preinit_btrfs_scan() {
	if grep -q btrfs /proc/filesystems; then
		btrfs device scan -d > /dev/kmsg
	fi
}

boot_hook_add preinit_main preinit_btrfs_scan
btrfs-progs: scan devices in preinit instead of init script There is no gain to do device scan in init. Commonly we want to always scan BTRFS devices to ensure that after boot raids are correctly linked. It should be done before any init script tries to mount any raid FS. Comparing init scripts and preinit scripts there are I think two primary considerations. First is if user is expected to restart/reload/stop given service on will. I think that there is no such reason for this as user can easily enough just call btrfs utility it self. Second consideration is if it makes sense to have it optional. This means if we want to have ability to enable and disable given service. I think that there is no such need in this case. It is pretty much doing nothing if you don't have BTRFS FS connected and when you have you probably want to scan it. Signed-off-by: Karel Kočí <karel.koci@nic.cz> 2019-08-05 19:47:17 +08:00			`#!/bin/sh`
btrfs-progs: import from oldpackges bump to 3.17.3, add LICENSE and MAINTAINER info, bump license header, add missing dependencies, ... Signed-off-by: Daniel Golle <daniel@makrotopia.org> 2014-12-06 00:11:04 +08:00
btrfs-progs: scan devices in preinit instead of init script There is no gain to do device scan in init. Commonly we want to always scan BTRFS devices to ensure that after boot raids are correctly linked. It should be done before any init script tries to mount any raid FS. Comparing init scripts and preinit scripts there are I think two primary considerations. First is if user is expected to restart/reload/stop given service on will. I think that there is no such reason for this as user can easily enough just call btrfs utility it self. Second consideration is if it makes sense to have it optional. This means if we want to have ability to enable and disable given service. I think that there is no such need in this case. It is pretty much doing nothing if you don't have BTRFS FS connected and when you have you probably want to scan it. Signed-off-by: Karel Kočí <karel.koci@nic.cz> 2019-08-05 19:47:17 +08:00			`preinit_btrfs_scan() {`
btrfs-progs: fix check for btrfs in btrfs scan The previous implementation always succeeded so no scan was performed. This now fixes that and it correctly scans for BTRFS devices if BTRFS support is in kernel. Signed-off-by: Karel Kočí <karel.koci@nic.cz> 2020-03-09 21:59:29 +08:00			`if grep -q btrfs /proc/filesystems; then`
btrfs-progs: add "btrfs device scan" before overlay/extroot If users choose to build OpenWrt with btrfs included and want to use a btrfs RAID for overlay/extroot, then devices need to be scanned before mounting overlay/extroot. If not, btrfs won't find all RAID drives and fail to mount. This commit: - creates a duplicate (symlink) of the btrfs scan script so that it runs both before and after overlay/extroot mount, - changes the scan command to not depend on blkid (-d), - outputs the scan results to kernel log to show what's being detected, as the system logger is not yet running. Signed-off-by: Marius Dinu <m95d+git@psihoexpert.ro> 2022-04-17 18:23:51 +08:00			`btrfs device scan -d > /dev/kmsg`
btrfs-progs: fix check for btrfs in btrfs scan The previous implementation always succeeded so no scan was performed. This now fixes that and it correctly scans for BTRFS devices if BTRFS support is in kernel. Signed-off-by: Karel Kočí <karel.koci@nic.cz> 2020-03-09 21:59:29 +08:00			`fi`
btrfs-progs: import from oldpackges bump to 3.17.3, add LICENSE and MAINTAINER info, bump license header, add missing dependencies, ... Signed-off-by: Daniel Golle <daniel@makrotopia.org> 2014-12-06 00:11:04 +08:00			`}`

btrfs-progs: scan devices in preinit instead of init script There is no gain to do device scan in init. Commonly we want to always scan BTRFS devices to ensure that after boot raids are correctly linked. It should be done before any init script tries to mount any raid FS. Comparing init scripts and preinit scripts there are I think two primary considerations. First is if user is expected to restart/reload/stop given service on will. I think that there is no such reason for this as user can easily enough just call btrfs utility it self. Second consideration is if it makes sense to have it optional. This means if we want to have ability to enable and disable given service. I think that there is no such need in this case. It is pretty much doing nothing if you don't have BTRFS FS connected and when you have you probably want to scan it. Signed-off-by: Karel Kočí <karel.koci@nic.cz> 2019-08-05 19:47:17 +08:00			`boot_hook_add preinit_main preinit_btrfs_scan`