Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!nrl-cmf!cmcl2!brl-adm!umd5!decuac!felix!zemon
From: richl@penguin.USS.TEK.COM (Rick Lindsley)
Newsgroups: comp.unix.ultrix
Subject: Re: problem with dump/restore across filesystems
Message-ID: <24042@felix.UUCP>
Date: 5 Mar 88 00:38:34 GMT
References: <22152@felix.UUCP>
Sender: zemon@felix.UUCP
Reply-To: richl@penguin.USS.TEK.COM (Rick Lindsley)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 24
Approved: zemon@felix.UUCP
Reply-Path:



In article <22152@felix.UUCP> gordon@prls.UUCP (Gordon Vickers) writes:
    
        For some reason, my backup filesystems are about 10Mbytes larger
     than the originals.  Prior to doing the backup, I used 'newfs' and
     then 'df' to verify that the new filesystem was empty (except for
     an empty lost+found directory).
    
The du output and ls -l's are very telling ... could you have dumped
from a file system with a small block size, like 1024, and restored to
one with a much larger size, like 4096 or 8192?

If you did this, then small files (or directories) might be using
more of the disk than before, due to larger "basic building blocks".

Try both "dumpfs /dev/ra0d" and "dumpfs /dev/ra1h" and look for "bsize"
and "fsize" in the output. If they aren't the same, then perhaps that
is the problem. Some of the problem may result from your doing dumps on
an active system -- a lot of file system information may not have been
written out to disk when you did your dump. A growth of 10 Mb, though,
seems unreasonable for both scenarios, so I can't believe this is the
only answer. (Of course, if /usr/spool/news is on /usr, you WILL find
lots of small files there ....)

Rick