From 28be65e12016d365783ac9646bf588ec68352b75 Mon Sep 17 00:00:00 2001

From: Peter Rajnoha <prajnoha@redhat.com>

Date: Mon, 10 Mar 2014 22:58:14 +0100

Subject: [PATCH] rules: mark loop device as SYSTEMD_READY=0 if no file is

 attached

Check existence of loop/backing_file in sysfs and mark loop devices with

SYSTEMD_READY if missing. Such loop files is uninitialized and it's not

ready for use yet (there's no file attached).

(cherry picked from commit ebc54302d7fc70927d5dc119e178ff03f6a911ed)

---

 rules/99-systemd.rules.in | 3 +++

 1 file changed, 3 insertions(+)

diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in

index 021359a..04a59c4 100644

--- a/rules/99-systemd.rules.in

+++ b/rules/99-systemd.rules.in

@@ -22,6 +22,9 @@ SUBSYSTEM=="block", KERNEL!="ram*", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_T

 SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", TEST!="md/array_state", ENV{SYSTEMD_READY}="0"

 SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", ATTR{md/array_state}=="|clear|inactive", ENV{SYSTEMD_READY}="0"

+# Ignore loop devices that don't have any file attached

+SUBSYSTEM=="block", KERNEL=="loop[0-9]*", TEST!="loop/backing_file", ENV{SYSTEMD_READY}="0"

+

 # Ignore nbd devices in the "add" event, with "change" the nbd is ready

 ACTION=="add", SUBSYSTEM=="block", KERNEL=="nbd*", ENV{SYSTEMD_READY}="0"