mirror of
https://github.com/systemd/systemd.git
synced 2024-11-02 19:21:53 +03:00
f8adf25d65
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 |
||
|---|---|---|
| .. | ||
| 50-udev-default.rules.in | ||
| 60-block.rules | ||
| 60-cdrom_id.rules | ||
| 60-drm.rules | ||
| 60-evdev.rules | ||
| 60-input-id.rules | ||
| 60-persistent-alsa.rules | ||
| 60-persistent-input.rules | ||
| 60-persistent-storage-tape.rules | ||
| 60-persistent-storage.rules | ||
| 60-persistent-v4l.rules | ||
| 60-sensor.rules | ||
| 60-serial.rules | ||
| 64-btrfs.rules.in | ||
| 70-joystick.rules | ||
| 70-mouse.rules | ||
| 70-touchpad.rules | ||
| 75-net-description.rules | ||
| 75-probe_mtd.rules | ||
| 78-sound-card.rules | ||
| 80-drivers.rules | ||
| 80-net-setup-link.rules | ||
| 99-systemd.rules.in | ||
| meson.build | ||