All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: minor ID for btrfs-control
Date: 03 Apr 2011 11:42:00 +0200	[thread overview]
Message-ID: <Bj8m7qCT1uB@helmut.hullen.de> (raw)
In-Reply-To: <20110402172936.GA24370@mother.jarsat.pl>

Hallo, Tomasz,

Du meintest am 02.04.11:

>> 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


> If you do not use udev, you need to synchronise /dev/
> node with /sys/class/misc/btrfs-control/dev manually on each boot.

Solved (something like reverse engineering).

I re-create the (permanent) entry /dev/btrfs-control using the actual  
contents of "/sys/class/misc/btrfs-control/dev", and btrfs is happy (and  
me too).

Works now on two of my machines for the next long time test ...

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

I'll watch who changes the data ... some part of some program must have  
defined 234 as minor ID.

Viele Gruesse!
Helmut

  parent reply	other threads:[~2011-04-03  9:42 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 [this message]
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
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=Bj8m7qCT1uB@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.