Date: Mon, 8 Jan 2007 09:37:31 +0100 From: "Ulrich Spoerlein" <uspoerlein@gmail.com> To: freebsd-hackers@freebsd.org, dgilbert@dclg.ca, perryh@pluto.rain.com Subject: Re: dump reads more than restore writes? Message-ID: <7ad7ddd90701080037p3ade4c12tca3163d3de1aeef7@mail.gmail.com> In-Reply-To: <200701080823.l088Nfqe082552@lurza.secnetix.de> References: <45a1c260./gHVPL2TJkCotGTS%perryh@pluto.rain.com> <200701080823.l088Nfqe082552@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/8/07, Oliver Fromme <olli@lurza.secnetix.de> wrote: > However, I think that there must be a bug in gstat when it > displays 600 GB read to copy a 200 GB file system. dump(8) > is inefficient, but not _that_ inefficient. When doing the dump|restore dance to copy filesystems, I make it a habit to have iostat(1) running. It is _always_ displaying a read rate twice as high as the write rate. And since the iostat/gstat numbers usually match up, eg., dd(1) numbers, I heavily doubt that it's a reporting/statistics glitch. It has to be dump(8). Uli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7ad7ddd90701080037p3ade4c12tca3163d3de1aeef7>