From: pubny <pubny@xs4all.nl>
To: dave@jikos.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: checkums when converting from ext[234] to Btrfs
Date: Thu, 05 Jan 2012 20:48:33 +0100 [thread overview]
Message-ID: <1325792913.11943.1.camel@lupus.example.com> (raw)
In-Reply-To: <20120105154541.GN7322@twin.jikos.cz>
Thanks David. That's very helpful.
Regards,
G=C3=A1bor
-----Original Message-----
=46rom: David Sterba <dave@jikos.cz>
Reply-to: dave@jikos.cz
To: pubny <pubny@xs4all.nl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: checkums when converting from ext[234] to Btrfs
Date: Thu, 5 Jan 2012 16:45:41 +0100
Mailer: Mutt/1.4.2.2i
On Wed, Jan 04, 2012 at 03:22:11PM +0100, pubny wrote:
> Could someone help me with a clarification whether the btrfs-convert
> tool creates checksums on blocks of the existing ext[234] filesystem?
yes, it does checksum by default and you can switch it off with the '-d=
'
option.
> Any experiences how the size and the filesystem utilization (used vs.
> total diskspace) impacts the time of conversion?
I don't have numbers but it needs to go through extX metadata, read and
checksum data blocks, then write btrfs metadata. Nothing where a
significant time could be saved (except switching off the checksums).
david
--
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
prev parent reply other threads:[~2012-01-05 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1325157169.28566.21.camel@lupus>
2012-01-04 14:22 ` checkums when converting from ext[234] to Btrfs pubny
2012-01-05 15:45 ` David Sterba
2012-01-05 19:48 ` pubny [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=1325792913.11943.1.camel@lupus.example.com \
--to=pubny@xs4all.nl \
--cc=dave@jikos.cz \
--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).