Hi,

I created a Linux system tar ball without using the --sparse switch.
The .tar.bzip2 tar ball is only of 1.5G in size. However, restoring such
tar ball into a 10G partition would fail:

Cannot write: No space left on device

It fails even if I've used the --sparse switch when restoring. 10G is
more than 6 times bigger than 1.5G. Does it really require that much of
space, or I'm doing something wrong.

Thanks

--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: i7dpjd$op2$1@dough.gmane.org">http://lists.debian.org/i7dpjd$op2$1@dough.gmane.org

On 2010-09-22 22:40 +0200, T o n g wrote:

> I created a Linux system tar ball without using the --sparse switch.
> The .tar.bzip2 tar ball is only of 1.5G in size. However, restoring such
> tar ball into a 10G partition would fail:
>
> Cannot write: No space left on device
>
> It fails even if I've used the --sparse switch when restoring. 10G is
> more than 6 times bigger than 1.5G. Does it really require that much of
> space, or I'm doing something wrong.

The GNU tar documentation says this about the --sparse option:

This option is meaningful only when creating or updating archives.
It has no effect on extraction.

HTH,
Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87k4mdlcjp.fsf@turtle.gmx.de">http://lists.debian.org/87k4mdlcjp.fsf@turtle.gmx.de

What is the actual size of the original file/directory before tarring?On the source side, trydu -ms <file or directory> to find out the actual size on disk. *That should be less than 10GB.


On Thu, Sep 23, 2010 at 02:29, Sven Joachim <svenjoac@gmx.de> wrote:

On 2010-09-22 22:40 +0200, T o n g wrote:



> I created a Linux system tar ball without using the --sparse switch.

> The .tar.bzip2 tar ball is only of 1.5G in size. However, restoring such

> tar ball into a 10G partition would fail:

>

> *Cannot write: No space left on device

>

> It fails even if I've used the --sparse switch when restoring. 10G is

> more than 6 times bigger than 1.5G. Does it really require that much of

> space, or I'm doing something wrong.



The GNU tar documentation says this about the --sparse option:



* * This option is meaningful only when creating or updating archives.

* * It has no effect on extraction.



HTH,

* *Sven





--

To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org

with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: http://lists.debian.org/87k4mdlcjp.fsf@turtle.gmx.de

On Wed, 22 Sep 2010 20:40:13 +0000, T o n g wrote:

> I created a Linux system tar ball without using the --sparse switch. The
> .tar.bzip2 tar ball is only of 1.5G in size. However, restoring such tar
> ball into a 10G partition would fail:
>
> Cannot write: No space left on device

(...)

Maybe a "tmpfs" limit related issue?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.09.23.08.53.28@gmail.com">http://lists.debian.org/pan.2010.09.23.08.53.28@gmail.com

Hi,

Thanks you all for the comments, which make it obligatory for me to
explain more. First, why I asked:

$ man tar | grep -i sparse
-S, --sparse
handle sparse files efficiently
--sparse-version=MAJOR[.MINOR]
set version of the sparse format to use (implies --sparse)

On Wed, 22 Sep 2010 22:59:38 +0200, Sven Joachim wrote:

>> I created a Linux system tar ball without using the --sparse switch.
>> The .tar.bzip2 tar ball is only of 1.5G in size. However, restoring
>> such tar ball into a 10G partition would fail:
>>
>> Cannot write: No space left on device
>>
>> . . .
>
> The GNU tar documentation says this about the --sparse option:
>
> This option is meaningful only when creating or updating archives.
> It has no effect on extraction.

I think this explains well.

IIRC, the source is only around 3G, at most 5G, according to du output.
But it turns out I need over 15G of space to expand this 1.5G tar ball.
Sparse files are the reason.

cheers

--
Tong (remove underscore(s) to reply)
http://xpt.sourceforge.net/techdocs/
http://xpt.sourceforge.net/tools/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: i7gu49$hmq$2@dough.gmane.org">http://lists.debian.org/i7gu49$hmq$2@dough.gmane.org