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: 04 Jan 2013 13:11:00 +0100	[thread overview]
Message-ID: <COClHaZuCXB@helmut.hullen.de> (raw)
In-Reply-To: <20130103212342.GE19051@carfax.org.uk>

Hallo, Hugo,

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.

Very very strange ...

I've tested the commands on another laptop, with another (older) kernel,  
the same btrfs-progs-packet and the same "blkid" version.

"blkid" doesn't hang searching the (non existent) floppy drive.

  mkfs.btrfs -d raid0 -m raid1 -L mylabel /dev/sdb1 /dev/sdb2 /dev/sdb3

works,

        blkid

then shows all 3 btrfs partitions with the same label,

        findfs LABEL=mylabel

shows one (the first?) partition with this label.

Fine. But why does that work on the one laptop but not on the other?


------------------

I'll test this behaviour on the other laptop with the older kernel  
(3.3.7), but it's yet busy, backung up some TBytes of data.

------------------

Some minutes later: "blkid" hangs again.

[...]

access("/dev/sda1", F_OK)               = 0
access("/dev/sda2", F_OK)               = 0
access("/dev/sda3", F_OK)               = 0
access("/dev/sda4", F_OK)               = 0
access("/dev/sdb1", F_OK)               = 0
access("/dev/sdb2", F_OK)               = 0
access("/dev/sdb3", F_OK)               = 0
access("/dev/sdb4", F_OK)               = 0
read(3, "", 4096)                       = 0
_llseek(3, 1240, [1240], SEEK_SET)      = 0
close(3)                                = 0
munmap(0x40025000, 4096)                = 0
open("/run/blkid/blkid.tab", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=1240, ...}) = 0
close(3)                                = 0
open("/proc/evms/volumes", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/proc/lvm/VGs", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/dev", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3
getdents64(3, /* 1084 entries */, 32768) = 32752
getdents64(3, /* 749 entries */, 32768) = 22672
getdents64(3, /* 0 entries */, 32768)   = 0
close(3)                                = 0
openat(AT_FDCWD, "/devfs", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/devices", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
open("/proc/partitions", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40025000
read(3, "major minor  #blocks  name\n\n   2"..., 1024) = 384
stat64("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(2, 0), ...}) = 0
access("/dev/fd0", F_OK)                = 0
time(NULL)                              = 1357301320
stat64("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(2, 0), ...}) = 0
open("/dev/fd0", O_RDONLY|O_LARGEFILE)  = 4
fadvise64_64(4, 0, 0, POSIX_FADV_RANDOM) = 0
fstat64(4, {st_mode=S_IFBLK|0660, st_rdev=makedev(2, 0), ...}) = 0
uname({sys="Linux", node="ElNath.wm8.hullen.de", ...}) = 0
ioctl(4, BLKGETSIZE64, 0x8050dbc)       = 0
_llseek(4, 0, [0], SEEK_SET)            = 0
read(4, 0x8051804, 1024)                = -1 EIO (Input/output error)
_llseek(4, 0, [0], SEEK_SET)            = 0
read(4, 0x8051804, 1024)                = -1 EIO (Input/output error)
_llseek(4, 0, [0], SEEK_SET)            = 0
read(4,  <unfinished ...>

# ------------------------------------

Is there something like "/dev/dice" running?

Viele Gruesse!
Helmut

  parent reply	other threads:[~2013-01-04 12:56 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
2013-01-03 21:52                     ` Helmut Hullen
2013-01-06 16:02                       ` Goffredo Baroncelli
2013-01-04 12:11                     ` Helmut Hullen [this message]
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=COClHaZuCXB@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.