From: Goffredo Baroncelli <kreijack@gmail.com>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: Option LABEL
Date: Sun, 06 Jan 2013 17:02:03 +0100 [thread overview]
Message-ID: <50E99FFB.5020107@gmail.com> (raw)
In-Reply-To: <CO8jf1hPCXB@helmut.hullen.de>
Hello Helmut
On 01/03/2013 10:52 PM, Helmut Hullen wrote:
> 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
"btrfs-show" and "btrfs filesystem show" behave differently.
The former (which is deprecated) scans every block device found under
/dev. The latter scans every block device found in /proc/partition.
For "btrfs filesystem show" it is possible to have the old behaviour
passing the "--all-devices" option.
The same switch exists also for "btrfs device scan".
In order to avoid misunderstanding I suggest you to use "btrfs
filesystem show"
>
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2013-01-06 16:01 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 [this message]
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=50E99FFB.5020107@gmail.com \
--to=kreijack@gmail.com \
--cc=Hullen@t-online.de \
--cc=helmut@hullen.de \
--cc=kreijack@inwind.it \
--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).