From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Why does stat() return invalid st_dev field for btrfs ??
Date: Tue, 18 Aug 2009 12:40:54 +1000 [thread overview]
Message-ID: <200908181240.58480.chris@csamuel.org> (raw)
In-Reply-To: <4A8A0B76.1030800@rtr.ca>
[-- Attachment #1: Type: Text/Plain, Size: 949 bytes --]
On Tue, 18 Aug 2009 12:01:26 pm Mark Lord wrote:
> But really, it should be using DM/LVM when there are multiple devices.
Chris Mason addressed a number of these points in this January 2008 comment on
LWN - http://lwn.net/Articles/265533/ - especially:
# This is something LVM cannot provide because it cannot maintain
# consistent checksums for the FS.
and
# When multiple devices are present, Btrfs will want to know it is
# mirroring on different physical spindles. This is a challenge
# with LVM since the locations of physical extents can change without
# the FS knowing about it. Even if there were hooks so the FS could
# know the current extent mappings, it would end up duplicating a copy
# of the mappings internally.
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2009-08-18 2:40 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
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 [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=200908181240.58480.chris@csamuel.org \
--to=chris@csamuel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox