Am Wed, 22 Nov 2017 20:42:20 +0100
schrieb Stefan Priebe - Profihost AG [off-list ref]:

Hi Coly,
  Hi Michael,


Am 22.11.2017 um 20:06 schrieb Stefan Priebe - Profihost AG:

quoted

Am 22.11.2017 um 18:51 schrieb Michael Lyle:  

quoted

Hi Coly, Stefan--

On 11/22/2017 05:14 AM, Stefan Priebe - Profihost AG wrote:  

 [...]  
 [...]  

quoted

quoted

I don't think there's any chance this patch will do anything.  If
there's a deadlock, the whole thing will become stuck forever and
never allow registration or progress on the device again-- which
doesn't match the symptoms here.  

No it does not ;-)
  

quoted

This probably relates to udev configuration in your environment
somehow.  

I found the problem the device is not detected as bcache by blkid -
see here:

'/sbin/blkid -o udev -p /dev/sdf1'(out) 'ID_FS_AMBIVALENT=other:bcache
other:xfs_external_log'

normally it looks like this:
'/sbin/blkid -o udev -p /dev/sdg1'(out) 'ID_FS_TYPE=bcache'

so instead of setting the FS_TYPE to bcache it's ID_FS_AMBIVALENT
which skips the bcache udev rules.

Just no idea how to fix that.

Maybe move bcache ontop of other FS in /etc/filesystems?

There's maybe an orphan XFS superblock hanging around. You could
disassemble the bcache device, wipefs, and recreate.


-- 
Regards,
Kai

Replies to list-only preferred.