From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: Option LABEL
Date: 03 Jan 2013 22:52:00 +0100 [thread overview]
Message-ID: <CO8jf1hPCXB@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.
Hmmm - I'll test it on another system.
>> Strange - in another way.
>>
>> Here "blkid" (without any device) hangs. See the attachment ("strace
>> blkid").
> [snip]
>> 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="izar", ...}) = 0
>> ioctl(4, BLKGETSIZE64, 0x8050d5c) = 0
>> _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, 0x80517a4, 1024) = -1 EIO (Input/output
>> error) _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, 0x80517a4, 1024) = -1 EIO (Input/output
>> error) _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, 0x80517a4, 1024) = -1 EIO (Input/output
>> error) _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, 0x80517a4, 1024) = -1 EIO (Input/output
>> error) _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, 0x80517a4, 1024) = -1 EIO (Input/output
>> error) _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, 0x80517a4, 1024) = -1 EIO (Input/output
>> error) _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, 0x80517a4, 1024) = -1 EIO (Input/output
>> error) _llseek(4, 0, [0], SEEK_SET) = 0
>> read(4, <unfinished ...>
> This is waiting for /dev/fd0 to return some data. I guess it'll
> give up after a few times round (8? 10?) and return some results.
I've waited 10 minutes ...
I know a similar behaviour p.e. when I run
btrfs-show
Then btrfs seems to test all block devices in "/dev" (no "udev" system)
and then tells most times
failed to read /dev/<nonexistent device>: No such device or address
But those (unnecessary) messages come quick, with only some seconds
delay.
-----------------
The above log file comes from a machine without floppy disk (a laptop).
Running "blkid" on an elder tower (with installed and usable floppy
disk) also checks for "/dev/fd0" and then tells "ok".
Tomorrow I'll test this behaviour on another laptop. Could be a "blkid"
error.
Viele Gruesse!
Helmut
next prev parent 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
2013-01-03 21:52 ` Helmut Hullen [this message]
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=CO8jf1hPCXB@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).