We should only import ID_FS_XXX variables if they are not set, otherwise we might be overwriting existing results.
Signed-off-by: Hannes Reinecke <h...@suse.de> --- multipath/11-dm-mpath.rules | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/multipath/11-dm-mpath.rules b/multipath/11-dm-mpath.rules index 2e7076d..5559af3 100644 --- a/multipath/11-dm-mpath.rules +++ b/multipath/11-dm-mpath.rules @@ -7,11 +7,11 @@ ENV{DM_UUID}!="mpath-?*", GOTO="mpath_end" # We'd like to avoid this, especially within udev processing. ENV{DM_NR_VALID_PATHS}!="?*", IMPORT{db}="DM_NR_VALID_PATHS" ENV{DM_NR_VALID_PATHS}!="0", GOTO="mpath_blkid_end" -IMPORT{db}="ID_FS_TYPE" -IMPORT{db}="ID_FS_USAGE" -IMPORT{db}="ID_FS_UUID" -IMPORT{db}="ID_FS_UUID_ENC" -IMPORT{db}="ID_FS_VERSION" +ENV{ID_FS_TYPE}!="?*", IMPORT{db}="ID_FS_TYPE" +ENV{ID_FS_USAGE}!="?*", IMPORT{db}="ID_FS_USAGE" +ENV{ID_FS_UUID}!="?*", IMPORT{db}="ID_FS_UUID" +ENV{ID_FS_ENC}!="?*", IMPORT{db}="ID_FS_UUID_ENC" +ENV{ID_FS_VERSION}!="?*", IMPORT{db}="ID_FS_VERSION" LABEL="mpath_blkid_end" # Also skip all foreign rules if no path is available. -- 2.6.6 -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel