From owner-freebsd-questions Sat May 19 15:45:30 2001 Delivered-To: freebsd-questions@freebsd.org Received: from rhymer.cogsci.ed.ac.uk (rhymer.cogsci.ed.ac.uk [129.215.144.8]) by hub.freebsd.org (Postfix) with ESMTP id 75E3E37B422 for ; Sat, 19 May 2001 15:45:27 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: from banks.cogsci.ed.ac.uk (banks [129.215.144.55]) by rhymer.cogsci.ed.ac.uk (8.9.3/8.9.3) with ESMTP id XAA06328 for ; Sat, 19 May 2001 23:45:25 +0100 (BST) Received: (from richard@localhost) by banks.cogsci.ed.ac.uk (8.9.3+Sun/8.9.3) id XAA08007 for freebsd-questions@freebsd.org; Sat, 19 May 2001 23:45:24 +0100 (BST) Date: Sat, 19 May 2001 23:45:24 +0100 (BST) Message-Id: <200105192245.XAA08007@banks.cogsci.ed.ac.uk> From: Richard Tobin Subject: nodump flag To: freebsd-questions@freebsd.org Organization: just say no Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the hope of being able to dump a large filesystem in CD-size pieces, I tried setting the nodump flag on most of the top-level directories. The resulting dump file was much larger than I expected - about 600MB when du shows 400MB (the whole filesystem is about 9GB). So I tried marking all but an *empty* directory as nodump. The resulting dump file was 200MB! restore -i shows only the expected empty directory. restore -r produces zillions of messages like expected next file 2539521, got 1390370 What is dump doing? Is it writing something for every inode even though it's only dumping part of the filesystem? -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message