From: Goffredo Baroncelli <kreijack@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID-10 arrays built with btrfs & md report 2x difference in available size?
Date: Sat, 30 Jan 2010 14:29:46 +0100 [thread overview]
Message-ID: <201001301429.46634.kreijack@libero.it> (raw)
In-Reply-To: <201001301424.25481.kreijack@libero.it>
On Saturday 30 January 2010, Goffredo Baroncelli wrote:
> On Saturday 30 January 2010, 0bo0 wrote:
>
> > Is the goal NOT to accurately represent the actual available space?
> > Seems rather odd that users are simply to know/accept that "available
> > space" in btrfs RAID-10 != "available space" in md RIAD-10 ...
>
> As reported more time in this ML, btrfs is able to store the data in
> striping/raid1 mode per-file-basis.
>
> The space on the disk is grouped in chunk. The raid mode is set per-chunk-
> basis [1]. So a file stored in a chunk may be written two times (in one or
two
> different disk), and another file stored in another chunk may be written
with
> a different policy.
Sorry, I forgot the reference:
[1] http://btrfs.wiki.kernel.org/index.php/Multiple_Device_Support
>
> In fact the btrfs store the data in "raid0" mode, and the metadata in raid1
> mode, even with only one disk. Even tough the words "raid1/0" are incorrect
> with only one disk.
>
> So key points are:
> - it is incorrect to say that the btrfs filesystem is configured in raidX
mode
> - it is correct that the file xyz is stored in raidX mode
> - is quite simple to evaluate the space available. It is more complex to
> evaluate before the file creation how many of the space available a file of
a
> certain size consumes.
> - unfortunately, today are not available tools that permits to manage the
raid
> mode of a file
>
> BR
> G.Baroncelli
>
>
>
> --
> gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack inwind
it>
> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next prev parent reply other threads:[~2010-01-30 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 21:57 RAID-10 arrays built with btrfs & md report 2x difference in available size? Thomas Kupper
2010-01-29 22:13 ` 0bo0
2010-01-29 22:38 ` RK
2010-01-29 23:46 ` jim owens
2010-01-29 23:53 ` 0bo0
2010-01-30 13:24 ` Goffredo Baroncelli
2010-01-30 13:29 ` Goffredo Baroncelli [this message]
2010-01-30 15:36 ` jim owens
2010-02-08 3:52 ` 0bo0
2010-02-08 3:54 ` 0bo0
2010-02-08 14:33 ` jim owens
-- strict thread matches above, loose matches on Subject: below --
2010-01-24 5:31 0bo0
2010-01-24 12:01 ` RK
2010-01-24 17:18 ` 0bo0
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=201001301429.46634.kreijack@libero.it \
--to=kreijack@gmail.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