[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Disk out of space in /var while installing Terminal Server profile



Hi Petter,

[re-odering your quotes in my reply...]

As debian-edu-fsautoresizetab takes care of this in the background,
we probably should teach APT to ignore its own disk space
calculations.

As LVM now hangs when debian-edu-fsautoresizetab try to run in the
background during the installation, it had to be disabled. :( So this
isn't the case any more.


Ah, ok. Then increasing the disk space in the VM does not help. It actually did not help. I re-installed the LTSP server via PXE overnight and it failed again with the same message.

On Fr 20 Sep 2013 01:58:02 CEST Petter Reinholdtsen wrote:

[Mike Gabriel]
What happens is that APT checks what would be installed (many
packages are listed) and what it needs to download for that (I used
the PXE based installation method for the installation) and that it
then thinks /var(/cache/apt/archive) is too small for all those .deb
files to be downloaded.

How much space was needed?  The minumum requirement sent to partman
should be adjusted.


Ok, so at the stage where the installation fails, I have:

/dev/mapper/vg_system-opt 10.8G(size) 1.4G(used) 8.8G(avail) 14% /target/opt
/dev/mapper/vg_system-var 3.6G(size) 3.2G(used) 236.4M(avail) 93% /target/var

APT says that 800 more megabytes have to be downloaded (to /var/cache/apt/archives) and 5.607 more MB of storage will be used after the installation (LTSP chroot in /opt).

So, I would add some more 1.6gb or so to /var (to have some reserves). I will reinstall the LTSP server now and do a lvextend/resizefs manually after the partitions have been created, so I will report back if the plus of 1.6gb is sufficient.

What is not clear to me: do the packages that get installed into the LTSP chroot get cached in /target/var/cache/apt/archives rather than /target/opt/ltsp/i386/var/cache/apt/archives?

As an additional info: the LTSP server is an amd64 installation, whereas the LTSP chroot is (of course) an i386. So, the D(E)-I has to download all arch:any packages twice (amd64, i386) which might probably cause this failure only on systems with this architecture combination.

Greets,
Mike



--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

Attachment: pgp9mbqbwLBzK.pgp
Description: Digitale PGP-Unterschrift


Reply to: