From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: newbie problems (difficulty with mkfs.btrfs and learning how to navigate trees
Date: Tue, 31 Jan 2012 06:12:21 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.01.31.06.12.20@cox.net> (raw)
In-Reply-To: CAHb3AmJWh-0W-f5AjZxstu8xtd+evA2VFidJPu+XecA4_O-t-Q@mail.gmail.com
Rohit Mehta posted on Mon, 30 Jan 2012 11:38:51 -0500 as excerpted:
> Thanks, it does seem to work on larger filesystems. I'll work with 500
> MB virtual disks.
FWIW I'd suggest 512 MiB, just because btrfs seems to like powers of two
as opposed to powers of 10. That might be what you meant anyway, but
it's not what you posted. =:^/
Talking about which, if you want to try 500 vs 512 vs 520 (or 512 plus
whatever the system usage size turns out to be for such a volume, I
assumed 8 MiB here), I'd be quite interested in comparative results. It
may be that getting it exactly right means a far more efficient layout,
less space waste and faster access, or that it really doesn't matter that
much. I don't know, which is why the results of such a test would be so
interesting. =:^)
Of course on real disks as opposed to virtual, speed would depend on the
disk alignment (512 byte vs 4KiB physical sectors and alignment to it,
for spinning media, larger erase chunks, up to 1 or 4 MiB, likely on ssd),
etc, but physical disk layout shouldn't directly affect btrfs' chunk-size
and space utilization efficiency.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2012-01-31 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 3:06 newbie problems (difficulty with mkfs.btrfs and learning how to navigate trees Rohit Mehta
2012-01-30 5:56 ` Duncan
2012-01-30 16:38 ` Rohit Mehta
2012-01-31 6:12 ` Duncan [this message]
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=pan.2012.01.31.06.12.20@cox.net \
--to=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).