Date: Fri, 27 Apr 2001 14:58:29 -0700 (PDT) From: Nick Sayer <nsayer@quack.kfu.com> To: Cy.Schubert@uumail.gov.bc.ca Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Dump very slow in 4.3-RELEASE? Message-ID: <1545.127.0.0.1.988408709.squirrel@medusa.kfu.com> In-Reply-To: <200104252246.f3PMkQl49426@cwsys.cwsent.com> References: <200104252246.f3PMkQl49426@cwsys.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > There was some discussion about this on this list a couple of weeks ago > shortly after the traverse.c patch was MFC'd. The conclusion at that > time was that this was to be expected. > Then it should be documented in the dump man page, IMHO. I found a workaround. Instead of chflag nodump on the top of a hierarchy, one can do a find . -type f -print0 | xargs -0 chflags nodump but that is imperfect, as you will still dump the (skeleton) directory hierarchy, As long as no directory has nodump, dump speeds through Pass II are normal (that is, fast). If there really is no way for this functionality to not suck, then it should be optional, IMHO. I'd rather go back to having to chflag -R a hierarchy before dump starts. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1545.127.0.0.1.988408709.squirrel>