Comment 2 for bug 1581169

The problem is reproducible on demand :

root@dob2-bfs-r5n09:~# udevadm --debug info -ap /sys/block/sdf
calling: info
device 0x154a300 has devpath '/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host2/target2:0:0/2:0:0:5/block/sdf'

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device '/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host2/target2:0:0/2:0:0:5/block/sdf':
KERNEL=="sdf"
SUBSYSTEM=="block"
DRIVER==""
ATTR{ro}=="0"
ATTR{size}=="1562758832"
ATTR{stat}==" 526 0 168573 232 11691 5205 2997588 3820 0 4016 4040"
ATTR{range}=="16"
ATTR{discard_alignment}=="0"
ATTR{events}==""
ATTR{ext_range}=="256"
ATTR{events_poll_msecs}=="-1"
ATTR{alignment_offset}=="0"
ATTR{inflight}==" 0 0"
ATTR{removable}=="0"
ATTR{capability}=="50"
ATTR{events_async}==""

device 0x154b220 has devpath '/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host2/target2:0:0/2:0:0:5'
looking at parent device '/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host2/target2:0:0/2:0:0:5':
KERNELS=="2:0:0:5"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{rev}=="7.02"
ATTRS{type}=="0"
ATTRS{scsi_level}=="6"
ATTRS{lunid}=="0x0500004000000000"
ATTRS{model}=="LOGICAL VOLUME "
ATTRS{state}=="running"
ATTRS{queue_type}=="simple"
ATTRS{iodone_cnt}=="0x328b"
ATTRS{iorequest_cnt}=="0x328b"
ATTRS{unique_id}=="600508B1001C6ACDCAA167F467871EAB"
ATTRS{queue_ramp_up_period}=="120000"
ATTRS{device_busy}=="0"
ATTRS{evt_capacity_change_reported}=="0"
ATTRS{timeout}=="30"
ATTRS{evt_media_change}=="0"
ATTRS{ioerr_cnt}=="0x2"
ssh: Write failed: Broken pipe