Date: Mon, 18 May 2009 13:55:26 +0100 From: Paul Wootton <paul@fletchermoorland.co.uk> To: freebsd-current@freebsd.org Cc: Christof Schulze <christof.schulze@gmx.net> Subject: Re: discrepancies in used space after cpio Message-ID: <4A115ABE.6070904@fletchermoorland.co.uk> In-Reply-To: <200905181412.11460.christof.schulze@gmx.net> References: <4A1123C5.3070507@fletchermoorland.co.uk> <200905181412.11460.christof.schulze@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Christof Schulze wrote: > Am Montag 18 Mai 2009 11:00:53 schrieb Paul Wootton: > >> Hi, >> >> I am currently in the process of moving all my data around, going from a >> single zfs drive (ex-mirror) to a zfs raidz. >> I have used cpio to copy the data to the new pool, but a du shows a big >> difference in the results. >> >> Does anyone have any ideas, or does a "du -h ." not do what I think it >> should? >> > it is a known bug (at least for the solaris folks) that du does not display > disk usage correctly on raidz. > > But of course different compression algorithms come into play as well. > > Regards, > > Christof > In this instance, the du from the raidz pool is actually correct. A zfs list shows less space (incorrect) on the single drive compared to the raidz. Doing a tar on both directories gives 2 1.2G files so the data is actually present on both packs (plus I used CPIO to copy the data from the single to the raidz) Is it possible for data corruption on the single drive to not show the extra space as being used?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A115ABE.6070904>