Messages in this thread | | | From | (H. Peter Anvin) | Subject | Re: Ext2fs and hashed table. | Date | 15 Jun 1997 07:51:31 GMT |
| |
Followup to: <m2afkt4o28.fsf@forest.nuthouse.au> By author: Peter Moulder <reiter@netspace.net.au> In newsgroup: linux.dev.kernel > > Harald Koenig <koenig@tat.physik.uni-tuebingen.de> writes: > > > I'd say "tries to handle"... gnu-tar can't distinguish between > allocated blocks all zero > and sparse holes. in case where it's > important that some areas are really allocated, > gnu-tar may break > your files. might not be a common problem but tar just can't > deal > with sparse files perfectly; dump/restore can... >
Why would that matter?
I would argue that dump can't deal with *ANY* file perfectly, since it (in the typical configuration) is committing the utter no-no of reading a non-quiescent r/w mounted filesystem from the raw block device.
-hpa -- PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74 See http://www.zytor.com/~hpa/ for web page and full PGP public key Always looking for a few good BOsFH. ** Linux - the OS of global cooperation I am Baha'i -- ask me about it or see http://www.bahai.org/
| |