Date: Thu, 22 Jul 2004 09:55:25 -0400 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: Daniel Lang <dl@leo.org> Subject: Re: NEW TAR Message-ID: <20040722135525.GA19550@electra.cse.Buffalo.EDU> In-Reply-To: <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu> References: <40F963D8.6010201@freebsd.org> <20040719060730.GA87697@nagual.pp.ru> <20040720081051.GB3001@cirb503493.alcatel.com.au> <B82A97D5-DA91-11D8-B0C4-000A95C893E4@lassitu.de> <Pine.GSO.4.61.0407211440210.28037@mail.ilrt.bris.ac.uk> <20040721151427.GC54664@atrbg11.informatik.tu-muenchen.de> <200407211622.i6LGMZrm040478@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 21, 2004 at 12:22:35PM -0400, Garrett Wollman wrote:
> <<On Wed, 21 Jul 2004 17:14:27 +0200, Daniel Lang <dl@leo.org> said:
>
> > I do not see, why it is important if the original file was sparse
> > at all or maybe in different places.
>
> You've never run out of disk space as a result of a sparse file
> becoming non-sparse?
>
They also effect user quotas. The quota reflects actual disk block
allocation, not file size. I've had users' home directories get
copied and suddenly they're over quota (or the copy fails...) because
of a few core files that became non-sparse...
--
Ken Smith
- From there to here, from here to | kensmith@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040722135525.GA19550>