[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cp command - problem with sparse
From: |
Andreas Schwab |
Subject: |
Re: cp command - problem with sparse |
Date: |
Wed, 02 Feb 2005 15:40:10 +0100 |
User-agent: |
Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) |
Jim Meyering <address@hidden> writes:
> Is this just theoretical, or do you know of a file system type
> that'd cause trouble (that doesn't support sparse files, yet for
> which meta data can take up extra space)?
It's just a guess, I don't know of any example. It might well be that
going from 64K to 128K on hfs could result in enough meta data to be
allocated so that the total size rounds up to 129 (assuming that such meta
data is actually accounted for in the stat data).
Andreas.
--
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- cp command - problem with sparse, RE, 2005/02/01
- Re: cp command - problem with sparse, James Youngman, 2005/02/01
- Re: cp command - problem with sparse, Eric Blake, 2005/02/02
- Re: cp command - problem with sparse, Jim Meyering, 2005/02/02
- Re: cp command - problem with sparse, Andreas Schwab, 2005/02/02
- Re: cp command - problem with sparse, Jim Meyering, 2005/02/02
- Re: cp command - problem with sparse, Andreas Schwab, 2005/02/02
- Re: cp command - problem with sparse, Jim Meyering, 2005/02/02
- Re: cp command - problem with sparse,
Andreas Schwab <=
- AW: cp command - problem with sparse, RE, 2005/02/02
- Re: AW: cp command - problem with sparse, Eric Blake, 2005/02/02
Re: cp command - problem with sparse, Eric Blake, 2005/02/03