All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Chris Ball <cjb@laptop.org>
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:59:08 -0400	[thread overview]
Message-ID: <4A89D2AC.5080006@rtr.ca> (raw)
In-Reply-To: <m3eirads6m.fsf@pullcord.laptop.org>

Chris Ball wrote:
> 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.
..

So I'm seeing in the code.

But for the 99% common case (personal computers, one drive), it would be
rather useful it it would comply with filesystem standards there.

In the unlikely event that a btrfs actually is composed of multiple devices,
then in that case perhaps return something nonsensical.

Mmm.. don't we already *have* an LVM layer in Linux?

Seems like a rather bad idea to have a new Linux-specific
filesystem re-implement it's own private LVM, and thus
confuse various disk management tools and the like.

Cheers

  reply	other threads:[~2009-08-17 21:59 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
2009-08-17 21:59     ` Mark Lord [this message]
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=4A89D2AC.5080006@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=chris.mason@oracle.com \
    --cc=cjb@laptop.org \
    --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.