From: Szabolcs Szakacsits Subject: Re: bdar: efficiently backup allocated bytes in file systems Date: Thu, 20 Mar 2008 02:26:59 +0200 (MET DST) Message-ID: References: <47DF1737.2050700@zabbo.net> <20080318213543.GC155407@sgi.com> <47E03CE3.3080903@zabbo.net> <20080318235201.GE155407@sgi.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Zach Brown , linux-fsdevel@vger.kernel.org To: David Chinner Return-path: Received: from emh06.mail.saunalahti.fi ([62.142.5.116]:44500 "EHLO emh06.mail.saunalahti.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936765AbYCTAZk (ORCPT ); Wed, 19 Mar 2008 20:25:40 -0400 In-Reply-To: <20080318235201.GE155407@sgi.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 19 Mar 2008, David Chinner wrote: > Yup - the use of a sparse file avoids the need for an internal map. > But that does't really work for piping the output, though. > xfs_metadump is probably more similar to bdar in that respect, but it > doesn't copy data.... Ntfsclone also efficiently copies data or metadata to dense, mountable sparse or a device file since 2003. It was an important factor to get reliable NTFS write support sooner because NTFS is slightly bigger than the other file systems (the size of the Microsoft NTFS driver is almost like the sum of the 60 Linux file systems altogether) and we needed to handle the heavily used (meta)data images efficiently during development and quality assurance. Szaka -- NTFS-3G: http://ntfs-3g.org