From mboxrd@z Thu Jan 1 00:00:00 1970 From: pubny Subject: Re: checkums when converting from ext[234] to Btrfs Date: Thu, 05 Jan 2012 20:48:33 +0100 Message-ID: <1325792913.11943.1.camel@lupus.example.com> References: <1325157169.28566.21.camel@lupus> <1325686931.2127.112.camel@lupus> <20120105154541.GN7322@twin.jikos.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: linux-btrfs@vger.kernel.org To: dave@jikos.cz Return-path: In-Reply-To: <20120105154541.GN7322@twin.jikos.cz> List-ID: Thanks David. That's very helpful. Regards, G=C3=A1bor -----Original Message----- =46rom: David Sterba Reply-to: dave@jikos.cz To: pubny 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