dump reads more than restore writes?
Ulrich Spoerlein
uspoerlein at gmail.com
Mon Jan 8 09:05:31 UTC 2007
On 1/8/07, Oliver Fromme <olli at 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
More information about the freebsd-hackers
mailing list