Re: Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-21 Thread Cyril Brulebois
Control: reassign -1 rootskel Control: affects -1 debian-installer Steven Chamberlain ste...@pyro.eu.org (2014-08-21): The simple patch for this issue is as follows. It has been tested now on kfreebsd-amd64 and kfreebsd-i386 with varying amounts of available RAM. * On kfreebsd, use

Processed: Re: Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-21 Thread Debian Bug Tracking System
Processing control commands: reassign -1 rootskel Bug #757985 [debian-installer] kfreebsd: hang with ENOSPC after a few components are loaded Bug reassigned from package 'debian-installer' to 'rootskel'. No longer marked as found in versions debian-installer/20140802. Ignoring request to alter

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-21 Thread Steven Chamberlain
On 21/08/14 19:53, Cyril Brulebois wrote: Out of curiosity: maybe this could have been done for wheezy in order to avoid having to tweak the initrd size several times? At the time of the freeze, the tmpfs code in wheezy kernels contained a warning that it might not be stable yet, but is removed

Re: Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-20 Thread Bastian Blank
On Wed, Aug 20, 2014 at 01:19:52AM +0100, Steven Chamberlain wrote: On 14/08/14 18:15, Cyril Brulebois wrote: [...] If a single extra udeb (or udeb size increase, which happens from time to time) is going to break kfreebsd-*, it seems to me that their status is far too brittle. The

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-20 Thread Steven Chamberlain
Control: tags -1 + patch Hi, The simple patch for this issue is as follows. It has been tested now on kfreebsd-amd64 and kfreebsd-i386 with varying amounts of available RAM. * On kfreebsd, use dynamically-sized tmpfs for: - /var/cache/anna - /var/lib/cdebconf to avoid running out

Processed: Re: Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-20 Thread Debian Bug Tracking System
Processing control commands: tags -1 + patch Bug #757985 [debian-installer] kfreebsd: hang with ENOSPC after a few components are loaded Added tag(s) patch. -- 757985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757985 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-19 Thread Steven Chamberlain
On 14/08/14 18:15, Cyril Brulebois wrote: [...] If a single extra udeb (or udeb size increase, which happens from time to time) is going to break kfreebsd-*, it seems to me that their status is far too brittle. The fixed-size d-i initrds had to be carefully sized for kfreebsd wheezy. We

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-19 Thread Cyril Brulebois
Steven Chamberlain ste...@pyro.eu.org (2014-08-20): On 14/08/14 18:15, Cyril Brulebois wrote: [...] If a single extra udeb (or udeb size increase, which happens from time to time) is going to break kfreebsd-*, it seems to me that their status is far too brittle. The fixed-size d-i

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-19 Thread Steven Chamberlain
On 20/08/14 01:49, Cyril Brulebois wrote: If you're trying to insinuate I/we deliberately broke kfreebsd-* by introducing partman-iscsi, [...] No, I was not insinuating that. But I am still asking: how is it that partman-iscsi is being installed into a kfreebsd d-i image (by APT I believe)?

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-19 Thread Cyril Brulebois
Steven Chamberlain ste...@pyro.eu.org (2014-08-20): On 20/08/14 01:49, Cyril Brulebois wrote: If you're trying to insinuate I/we deliberately broke kfreebsd-* by introducing partman-iscsi, [...] No, I was not insinuating that. But I am still asking: how is it that partman-iscsi is

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-19 Thread Steven Chamberlain
Steven Chamberlain ste...@pyro.eu.org (2014-08-20): But I am still asking: how is it that partman-iscsi is being installed into a kfreebsd d-i image (by APT I believe)? I'd expect it to be uninstallable due to missing dependencies. Could that be a bug, or is it a known limitation? Thanks.

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-19 Thread Cyril Brulebois
Steven Chamberlain ste...@pyro.eu.org (2014-08-20): But it *is* also relevant here. Each udeb in our image takes up space for the extracted files, but also I suspect _considerable_ space in cdebconf data. Addressing this may already fix the ENOSPC error, and if we can keep the anna excludes

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-19 Thread Steven Chamberlain
I've finished testing these hypotheses: On 20/08/14 03:14, Steven Chamberlain wrote: I think all we need to do is add the expected-uninstallable packages to /var/cache/anna/exclude That works. I think on each architecture, any uninstallable udeb (according to

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-14 Thread Cyril Brulebois
Steven Chamberlain ste...@pyro.eu.org (2014-08-13): On 13/08/14 02:55, Cyril Brulebois wrote: (Looking at syslog when I can, it seems anna is the tool running into a full partition, which isn't surprising.) Some new installer components have appeared since wheezy, such as partman-iscsi,

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-13 Thread Steven Chamberlain
On 13/08/14 02:55, Cyril Brulebois wrote: (Looking at syslog when I can, it seems anna is the tool running into a full partition, which isn't surprising.) Some new installer components have appeared since wheezy, such as partman-iscsi, which is arch: all. It is of no use without

Bug#757985: kfreebsd: hang with ENOSPC after a few components are loaded

2014-08-12 Thread Cyril Brulebois
Package: debian-installer Version: 20140802 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd Hi, with a wheezy/amd64/kvm-based setup (hda is ~5GB, RAM is 1GB), the following images don't work at all, with the following message on vt1: | /: write failed, filesystem is full