From: Sean Bartell <wingedtachikoma@gmail.com>
To: wks1986 <wks1986@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: A device dedicated for metadata?
Date: Wed, 28 Jul 2010 13:49:43 -0400 [thread overview]
Message-ID: <20100728174943.GA6259@flcl.lan> (raw)
In-Reply-To: <AANLkTi=XBx11aj=_OLpQkAwOzuG4-nENPKvDqdwYA0rT@mail.gmail.com>
In response to your original questions, btrfs currently gives no control
over the allocation of data or metadata. I'm sure someone will implement
more control eventually.
On Wed, Jul 28, 2010 at 11:49:33PM +0800, wks1986 wrote:
> Another issue is the speed of fsck. There will always be times when
> the operating system is brought down abnormally and fsck is necessary.
> In order to make the downtime as short as possible, fsck should be
> fast. In this case, when metadata are stored in a fast device, fsck
> will be significantly faster. The "hot data tracking" patch is based
> on the statistics of ONLINE accesses. Some data may suddenly become
> hot when the filesystem goes offline for fsck.
Actually, because of copy-on-write and other aspects of btrfs' design,
there's no need for the typical use of fsck after a crash. Even once a
proper fsck is finished, it will only be necessary when important
information is corrupted. So it generally doesn't make sense to worry
about fsck speed.
prev parent reply other threads:[~2010-07-28 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 9:32 A device dedicated for metadata? wks1986
2010-07-28 13:14 ` Wengang Wang
2010-07-28 15:49 ` wks1986
2010-07-28 17:49 ` Sean Bartell [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=20100728174943.GA6259@flcl.lan \
--to=wingedtachikoma@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wks1986@gmail.com \
/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).