'nodump' on directories: new contents still dumped

Bram Schoenmakers bramschoenmakers at xs4all.nl
Thu Mar 15 18:53:41 UTC 2007

Op donderdag 15 maart 2007, schreef John Nielsen:


> On Thursday 15 March 2007 13:57, Bram Schoenmakers wrote:
> > I'm using dump(8) for backing up a FreeBSD 4.10 server. In order to
> > decrease the resulting file size, I flagged some directories like
> > /usr/ports and /usr/src with 'nodump'. I adjusted the dump level 0 script
> > to have -h 0, so that worked fine. The other scripts for dumps >0 do not
> > have a -h flag set, because -h 1 is default.
> >
> > The problem is that new files appearing in the /usr/ports tree (daily
> > portsnap cron) do not have the 'nodump' flag set. But despite the
> > 'nodump' flag on the /usr/ports directory, the new files in the tree are
> > still dumped.
> >
> > I understood that dump does not enter directories with 'nodump' flag set,
> > so it shouldn't see the new files inside, right? Or is this behavior
> > implemented in a newer version than FreeBSD 4.10? I have scanned the CVS
> > logs for dump, but couldn't find anything relevant.
> Read the dump manpage more carefully, and pay particular attention to the
> -h flag. You probably want '-h0'.

-h 0 just works fine, that is not the problem.

I may have forgotten one detail in case that was not clear. The level 0 backup 
does not contain any folder marked with 'nodump' (so it's all OK, despite 
the -h0 you mentioned). New contents (which have no flags set) in these 
folders emerge in higher level dumps.

The problem is that dump(8) enters directories with 'nodump' flags set while 
it shouldn't.

Kind regards,

Bram Schoenmakers

What is mind? No matter. What is matter? Never mind.
(Punch, 1855)

More information about the freebsd-questions mailing list