From: Chris Ball <cjb@laptop.org>
To: Mark Lord <lkml@rtr.ca>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Why does stat() return invalid st_dev field for btrfs ??
Date: Mon, 17 Aug 2009 17:52:17 -0400 [thread overview]
Message-ID: <m3eirads6m.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <4A89C86A.1040207@rtr.ca> (Mark Lord's message of "Mon, 17 Aug 2009 17:15:22 -0400")
Hi,
> Mmm.. btrfs appears to configure itself as a "pseudo" filesystem,
> which is why it returns fake device numbers via stat(), similar
> to procfs or sysfs.
Probably because a single btrfs filesystem can be composed of multiple
devices; one major/minor would not be sufficient.
- Chris.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2009-08-17 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 20:47 Why does stat() return invalid st_dev field for btrfs ?? Mark Lord
2009-08-17 21:15 ` Mark Lord
2009-08-17 21:52 ` Chris Ball [this message]
2009-08-17 21:59 ` Mark Lord
2009-08-17 22:03 ` Mark Lord
2009-08-18 0:29 ` Kay Sievers
2009-08-18 2:01 ` Mark Lord
2009-08-18 2:40 ` Chris Samuel
2009-08-18 21:21 ` Jens Axboe
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=m3eirads6m.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkml@rtr.ca \
/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