From: Mark Lord <lkml@rtr.ca>
To: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Why does stat() return invalid st_dev field for btrfs ??
Date: Mon, 17 Aug 2009 16:47:22 -0400 [thread overview]
Message-ID: <4A89C1DA.6040601@rtr.ca> (raw)
Chris / list,
stat(2) seems to return invalid major/minor device info
for btrfs filesystems.
Why? Is this a bug?
Eg.
[~] uname -r
2.6.31-rc6
[~] mkfs.btrfs /dev/sdb
WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
fs created label (null) on /dev/sdb
nodesize 4096 leafsize 4096 sectorsize 4096 size 30.06GB
Btrfs Btrfs v0.19
[~] mount /dev/sdb /x -t btrfs
[~] stat --format="%04D" /x
0017
[~] touch /x/junk
[~] stat --format="%04D" /x/junk
0017
This gives major=0x00, minor=0x17 for /dev/sdb,
which should have major=8, minor=0x10.
???
next reply other threads:[~2009-08-17 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 20:47 Mark Lord [this message]
2009-08-17 21:15 ` Why does stat() return invalid st_dev field for btrfs ?? Mark Lord
2009-08-17 21:52 ` Chris Ball
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=4A89C1DA.6040601@rtr.ca \
--to=lkml@rtr.ca \
--cc=chris.mason@oracle.com \
--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