All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: Option LABEL
Date: 03 Jan 2013 23:07:00 +0100	[thread overview]
Message-ID: <CO8jfs0uCXB@helmut.hullen.de> (raw)
In-Reply-To: <125D7A41-DBE8-40C0-B8EE-B64DD2D95A93@colorremedies.com>

Hallo, Chris,

Du meintest am 03.01.13:

>>> On my system (a bundle of /dev/sdb, /dev/sdc, /dev/sdd)
>>>
>>>        btrfs fi label /dev/sdb mylabel
>>>
>>> only sets the label on the (unmounted) device /dev/sdb. "/dev/sdc"
>>> and "/dev/sdd" remain without label.

>>   This is a bug.

> It's a bug that appears to be fixed. I inadvertently tested it first
> on CentOS 6.0 which has quite an older kernel and btrfsprogs. And
> Fedora 18 of course has a much newer kernel and btrfs-progs so I have
> no idea when in between those two this was fixed.

> Helmut what kernel and btrfs-progs or distribution are you using? I
> think newer progs fixes this.

Kernel 3.4.6 (self made), btrfs-progs downloaded and compiled 2 days ago  
(Mason version, not Mills version).

I've just brewed Kernel 3.6.11 but I have to wait some days (backing up  
some Tbytes of data) before I can test btrfs with this newer kernel.

But looking for btrfs in the ChangeLog files for kernels 3.4 to 3.6  
doesn't show any entry which might be related to the above error.
(Kernels 3.4.3, 3.4.5, 3.4.8, 3.5.1, 3.5.4)

Viele Gruesse!
Helmut

  reply	other threads:[~2013-01-03 22:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 15:14 Option LABEL Helmut Hullen
2013-01-03 16:08 ` Hugo Mills
2013-01-03 16:29   ` Helmut Hullen
2013-01-03 17:01     ` Hugo Mills
2013-01-03 17:43       ` james northrup
2013-01-03 17:57       ` Helmut Hullen
2013-01-03 18:10         ` cwillu
2013-01-03 18:20           ` Helmut Hullen
2013-01-03 19:18             ` Chris Murphy
2013-01-03 19:35               ` Chris Murphy
2013-01-03 20:28                 ` Helmut Hullen
2013-01-03 21:23                   ` Hugo Mills
2013-01-03 21:27                     ` Chris Murphy
2013-01-03 22:07                       ` Helmut Hullen [this message]
2013-01-03 21:52                     ` Helmut Hullen
2013-01-06 16:02                       ` Goffredo Baroncelli
2013-01-04 12:11                     ` Helmut Hullen
2013-01-04 20:59                     ` Helmut Hullen
2013-01-04 21:41                       ` Chris Murphy
2013-01-03 19:59               ` Helmut Hullen
2013-01-03 21:17                 ` Chris Murphy
2013-01-04 12:56                   ` Helmut Hullen
2013-01-03 18:33         ` Hugo Mills
2013-01-03 19:08           ` Helmut Hullen
2013-01-03 19:28             ` Hugo Mills
2013-01-03 20:18               ` Helmut Hullen
2013-01-05 11:36                 ` Martin Steigerwald
2013-01-05 12:44                   ` Helmut Hullen
2013-01-05 19:08                     ` Chris Murphy
2013-01-05 13:15   ` Helmut Hullen
2013-01-05 19:10     ` Chris Murphy
2013-01-05 19:13       ` Hugo Mills
2013-01-05 21:03       ` Helmut Hullen
2013-01-05 21:21         ` Chris Murphy

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=CO8jfs0uCXB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --cc=linux-btrfs@vger.kernel.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.