From: Goffredo Baroncelli <kreijack@libero.it>
To: helmut@hullen.de
Cc: Helmut Hullen <Hullen@t-online.de>, linux-btrfs@vger.kernel.org
Subject: Re: minor ID for btrfs-control
Date: Sun, 03 Apr 2011 00:35:28 +0200 [thread overview]
Message-ID: <4D97A4B0.6010207@libero.it> (raw)
In-Reply-To: <Bj4lB4gT1uB@helmut.hullen.de>
On 04/02/2011 06:45 PM, Helmut Hullen wrote:
> Hallo,
>
> if I've understood some mails in this list correct, then btrfs needs a
> character device "btrfs-control" with the ID 10:55
>
> When I look for this device in
>
> /sys/class/misc/btrfs-control/dev
>
> I see 10:234
>
> And when I run the command
>
> mkfs.btrfs -d raid0 -m raid1 /dev/sda1 /dev/sdc1
>
> I get the error messages
>
> failed to open /dev/btrfs-control skipping device registration
>
> ---
>
> ls -l /dev/bt*
>
> shows
>
> crw-rw-rw- 1 root root 10,55 2. Apr 17:55 /dev/btrfs-control
>
> ---
>
> Kernel 2.6.38.1 (self made), no udev, no initrd, no tempfs. btrfs from
> nov. 2010
>
> What goes wrong?
As wrote by Tomasz the minor number of the btrfs-control is allocated
dynamically. A lot of drivers create a device which is registered
dynamically in the "misc" group. In linux this is a well established
behavior from a long time.
If you don't want to use udev you have two choices:
- use devtmpfs
- create manually a device. But nobody guarantee that the minor/major
will not change.
>
>
> 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
> .
>
next prev parent reply other threads:[~2011-04-02 22:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 16:45 minor ID for btrfs-control Helmut Hullen
2011-04-02 17:29 ` Tomasz Torcz
2011-04-02 18:06 ` Helmut Hullen
2011-04-03 9:42 ` Helmut Hullen
2011-04-03 12:28 ` Peter Stuge
2011-04-03 13:33 ` Helmut Hullen
2011-04-03 14:00 ` Peter Stuge
2011-04-03 14:33 ` Helmut Hullen
2011-04-02 22:35 ` Goffredo Baroncelli [this message]
2011-04-02 23:30 ` Peter Stuge
2011-04-03 4:12 ` Helmut Hullen
2011-04-03 3:11 ` Helmut Hullen
2011-04-03 10:24 ` Goffredo Baroncelli
2011-04-03 10:52 ` Helmut Hullen
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=4D97A4B0.6010207@libero.it \
--to=kreijack@libero.it \
--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).