* blkid always detects FS
@ 2013-08-27 9:31 Stefan Priebe - Profihost AG
2013-08-27 11:59 ` Gabriel de Perthuis
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Priebe - Profihost AG @ 2013-08-27 9:31 UTC (permalink / raw)
To: Kent Overstreet; +Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: blkid always detects FS
2013-08-27 9:31 blkid always detects FS Stefan Priebe - Profihost AG
@ 2013-08-27 11:59 ` Gabriel de Perthuis
2013-08-27 13:04 ` Stefan Priebe - Profihost AG
0 siblings, 1 reply; 3+ messages in thread
From: Gabriel de Perthuis @ 2013-08-27 11:59 UTC (permalink / raw)
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA
On Tue, 27 Aug 2013 11:31:41 +0200, Stefan Priebe - Profihost AG wrote:
> 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.
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: blkid always detects FS
2013-08-27 11:59 ` Gabriel de Perthuis
@ 2013-08-27 13:04 ` Stefan Priebe - Profihost AG
0 siblings, 0 replies; 3+ messages in thread
From: Stefan Priebe - Profihost AG @ 2013-08-27 13:04 UTC (permalink / raw)
To: Gabriel de Perthuis; +Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA
Am 27.08.2013 13:59, schrieb Gabriel de Perthuis:
> On Tue, 27 Aug 2013 11:31:41 +0200, Stefan Priebe - Profihost AG wrote:
>> 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.
>
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-08-27 13:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-27 9:31 blkid always detects FS Stefan Priebe - Profihost AG
2013-08-27 11:59 ` Gabriel de Perthuis
2013-08-27 13:04 ` Stefan Priebe - Profihost AG
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox