blkid always detects FS
Hi,
since commit 0b57e166ae86d525ef42842cabf7692fc7c44039 in bcache tools all my bcache devices do not register anymore.
For all my bcache devices blkid returns:
# /sbin/blkid -o udev /dev/sdd1 ID_FS_UUID=6937d2e6-c8e3-4590-954b-65937fc23a52 ID_FS_UUID_ENC=6937d2e6-c8e3-4590-954b-65937fc23a52 ID_FS_TYPE=xfs
What's wrong here? All disks have XFS on top of bcache running.
Greets,
Stefan
Quoted 8 lines · Stefan Priebe - Profihost AG
For all my bcache devices blkid returns:
# /sbin/blkid -o udev /dev/sdd1 ID_FS_UUID=6937d2e6-c8e3-4590-954b-65937fc23a52 ID_FS_UUID_ENC=6937d2e6-c8e3-4590-954b-65937fc23a52 ID_FS_TYPE=xfsWhat's wrong here? All disks have XFS on top of bcache running.
The udev rules were changed to reject bcache devices with a pre-existing superblock (xfs in your case).
This was done to fail early when there's a risk of exposing an unsynchronised backend device, which would be a bad thing™.
You can remove the stray superblocks with wipefs.
Am 27.08.2013 13:59, schrieb Gabriel de Perthuis:
Quoted 10 lines · Stefan Priebe - Profihost AG
Quoted 8 lines
For all my bcache devices blkid returns:
# /sbin/blkid -o udev /dev/sdd1 ID_FS_UUID=6937d2e6-c8e3-4590-954b-65937fc23a52 ID_FS_UUID_ENC=6937d2e6-c8e3-4590-954b-65937fc23a52 ID_FS_TYPE=xfsWhat's wrong here? All disks have XFS on top of bcache running.
Quoted 7 lines
The udev rules were changed to reject bcache devices with a pre-existing superblock (xfs in your case).
This was done to fail early when there's a risk of exposing an unsynchronised backend device, which would be a bad thing™.
You can remove the stray superblocks with wipefs.
shouldn't bcache-create wipe the superblock?
Stefan