On 08/26/2013 11:27 PM, Gabriel de Perthuis wrote:
Possibly /dev/sdc1 or /dev/sdd1 has a stray non-bcache superblock.
You're right, see below. That was an ugly one.
Do you think having blkid identify bcache itself would have helped, or
is there always a chance of contradictive signatures which may confuse
blkid?
You can check with wipefs, and remove it with wipefs -a.
The evidence:
[root@localhost ~]# wipefs /dev/sda3
[root@localhost ~]# wipefs /dev/sdb1
offset type
----------------------------------------------------------------
0x218 LVM2_member [raid]
UUID: ZSSjZv-FU0H-Zeaa-92GU-37Zs-KyLS-JMF03Y
[root@localhost ~]# wipefs /dev/sdc1
[root@localhost ~]# wipefs /dev/sdd1
[root@localhost ~]# blkid /dev/sdb1
/dev/sdb1: UUID="ZSSjZv-FU0H-Zeaa-92GU-37Zs-KyLS-JMF03Y" TYPE="LVM2_member"
[root@localhost ~]#
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
