From owner-freebsd-questions Tue Jan 15 18:49: 3 2002 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-31-201-166.mmcable.com [65.31.201.166]) by hub.freebsd.org (Postfix) with SMTP id 5C8AA37B404 for ; Tue, 15 Jan 2002 18:49:00 -0800 (PST) Received: (qmail 19767 invoked by uid 100); 16 Jan 2002 02:48:53 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15428.59925.443917.666351@guru.mired.org> Date: Tue, 15 Jan 2002 20:48:53 -0600 To: Brian T.Schellenberger Cc: questions@FreeBSD.ORG Subject: Re: HOWTO -- backup onto CDRs? In-Reply-To: <0a2d11623021012FE4@mail4.nc.rr.com> References: <15426.33499.296182.78699@guru.mired.org> <200201152209.g0FM9eI00811@i8k.babbleon.org> <15428.54969.119254.138926@guru.mired.org> <0a2d11623021012FE4@mail4.nc.rr.com> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.4-STABLE-i386) 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 Brian T. Schellenberger types: > On Tuesday 15 January 2002 08:26 pm, Mike Meyer wrote: > > There's one other type of screwy file: sparse files. These have > > "holes" where there are no blocks on disk. You can create one > > trivially: > > Are these at all common? For the matter, are they preserved by cp? They > seem like a hyphothetical concern more than a practical one and a nuisance > more than a benefit. But maybe that's just me. Various implementations of db use them. The original implementation of UniCOS didn't provide them, and when we plugged in the db'ified version of the pwd routines and tried to make the password db, it ran root out of space. I'm not sure what else uses them, but the source for tar turn up a test for sparseness that ought to work on all Unix systems: if the stat structure's st_blocks times the file blocksize is less than the same structure's st_size. No, they aren't preserved by cp. Neither are flags, set*id bits, and a number of other things that one would rather not lose. If the cp crosses file systems, it also loses hard links. > Regardless, if you do a compressed backup they should compress real nicely > (though not as efficiently as the sparse files), though they will spring to > full space on a restore if the backup/restore program isn't clueful about > them. Springing back to full space can easily mean they don't fit on the restore media, even though it's bigger than the file system you are restoring. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message