From: Mark Lord <lkml@rtr.ca>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why does stat() return invalid st_dev field for btrfs ??
Date: Mon, 17 Aug 2009 22:01:26 -0400 [thread overview]
Message-ID: <4A8A0B76.1030800@rtr.ca> (raw)
In-Reply-To: <ac3eb2510908171729k2e53914fu6ffe49483310aeba@mail.gmail.com>
Kay Sievers wrote:
> On Mon, Aug 17, 2009 at 22:47, Mark Lord<lkml@rtr.ca> wrote:
>> Chris / list,
>>
>> stat(2) seems to return invalid major/minor device info
>> for btrfs filesystems.
>>
>> Why? Is this a bug?
>
> This is not invalid and not a bug. It's a superblock without a device,
> and expected behavior.
>
> There is no one-to-one relation from a btrfs mountpoint to a device,
> it's a tree, and therefore therefore there can not be a single
> major/minor.
..
Sure there is for the most common case.
When there is only a single device, stat() should return that device.
When there are several, it should do something different.
But really, it should be using DM/LVM when there are multiple devices.
next prev parent reply other threads:[~2009-08-18 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A89C1DA.6040601@rtr.ca>
[not found] ` <4A89C86A.1040207@rtr.ca>
[not found] ` <m3eirads6m.fsf@pullcord.laptop.org>
[not found] ` <4A89D2AC.5080006@rtr.ca>
2009-08-17 22:03 ` Why does stat() return invalid st_dev field for btrfs ?? Mark Lord
[not found] ` <ac3eb2510908171729k2e53914fu6ffe49483310aeba@mail.gmail.com>
2009-08-18 2:01 ` Mark Lord [this message]
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=4A8A0B76.1030800@rtr.ca \
--to=lkml@rtr.ca \
--cc=chris.mason@oracle.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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