| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
check for btrfs in /proc/filesystems instead of /proc/modules
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|
| |
|
|
|
|
|
|
| |
the init script calls the old btrfsctl util, which is not included in
btrfs-progs anymore. Update the init script to call "btrfs device scan"
which assembles multi device btrfs filesystems.
Signed-off-by: Stefan Hellermann <stefan@the2masters.de>
|
|
|
bump to 3.17.3, add LICENSE and MAINTAINER info, bump license header,
add missing dependencies, ...
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
|