All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: database for device scan
Date: 31 Oct 2010 15:18:00 +0100	[thread overview]
Message-ID: <BZur8RLD1uB@helmut.hullen.de> (raw)

Hallo, linux-btrfs,

I've used for some days btrfs-progs-20100717, now I'm using "btrfs- 
progs-201030" (built with the "SlackBuild" script for slackware).

Works fine, but the actual version works in another way than the  
previous when I say

        mkfs.btrfs /dev/sdb1

(or how the device may be named).
The previous version finished its work within some seconds, the actual  
version first tests all block devices in "/dev".

If I'd run "udev" that may be no big problem. But I prefer not using  
"udev", I prefer working with static device entries, and that leads to  
many entries for devices which really don't exist. And "scan" scans all  
of them.

Maybe it's a better idea not to use "/dev" as database, using "proc/ 
partitions" may be the better way.

Viele Gruesse!
Helmut

                 reply	other threads:[~2010-10-31 14:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BZur8RLD1uB@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.