From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: label devices got removed after format
Date: Fri, 12 Jul 2013 11:40:56 +0000 (UTC) [thread overview]
Message-ID: <kroq08$tfo$3@ger.gmane.org> (raw)
In-Reply-To: 51DFDE21.2040309@profihost.ag
On Fri, 12 Jul 2013 12:44:49 +0200, Stefan Priebe - Profihost AG wrote:
> Am 12.07.2013 12:33, schrieb Gabriel de Perthuis:
>> On Thu, 11 Jul 2013 18:28:06 -0700, Kent Overstreet wrote:
>>> On Thu, Jul 11, 2013 at 11:43:22AM +0200, Stefan Priebe - Profihost AG wrote:
>>>> Hi,
>>>>
>>>> after doing mkfs.xfs -f /dev/bcache/by-label/mybcachelabel
>>>>
>>>> /dev/bcache/by-label/mybcachelabel gots removed...
>>>>
>>>> Only a reboot brings it back.
>>>>
>>>> Stefan
>>>
> To me it happens alays when a udev event is triggered. It seems the
> label isn't republished. To me the whole Folder /dev/bcache gets removed.
>
> May i've used the wrong kernel patches on top of 3.10?
After discussing this on IRC:
The Squeeze version of udev chokes on newlines in labels, to the point
that all the device's symlinks are removed; the uuid symlinks aren't
even involved in label uevents.
As a workaround, the latest commit in [1] strips endlines when setting
the label.
[1] https://github.com/g2p/linux/commits/v3.10%2Bbcache-for-3.11
next prev parent reply other threads:[~2013-07-12 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 9:43 label devices got removed after format Stefan Priebe - Profihost AG
[not found] ` <51DE7E3A.5070709-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2013-07-12 1:28 ` Kent Overstreet
2013-07-12 5:15 ` Stefan Priebe - Profihost AG
2013-07-12 10:33 ` Gabriel de Perthuis
2013-07-12 10:44 ` Stefan Priebe - Profihost AG
2013-07-12 11:40 ` Gabriel de Perthuis [this message]
2013-07-16 21:37 ` Kent Overstreet
2013-07-16 22:16 ` Gabriel de Perthuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='kroq08$tfo$3@ger.gmane.org' \
--to=g2p.code-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.