Excerpts from Russ Allbery's message of Thu Mar 31 22:03:38 +0200 2011: > Michal Suchanek <michal.sucha...@ruk.cuni.cz> writes: > > Excerpts from Russ Allbery's message of Thu Mar 31 18:18:25 +0200 2011: > > >> That's not consistent with the error message that you got. The error > >> message is from an echo, which is certainly writing a small amount of > >> data. It's also happening inside the dkms shell wrapper, not in the > >> OpenAFS build. > > > But it's not consistent with the disk space shown by df either, there is > > disk space available. > > Okay, I went and looked at this some more, and tried to figure out what > part of DKMS is producing an error. The line referenced in the error > message is DKMS attempting to store the build logs (the standard output > from the build process), or one of the other commands that it runs (like > mkinitrd). It's hard to tell exactly which without knowing more context > for when in the process the error occurred, but either way, we're not > talking about a lot of data. > > It does look like it was storing things in /tmp (unless you had TMPDIR set > to something else), so it's the 1MB of space in /tmp that's presumably the > issue, rather than the space on the root file system, so you're correct, > the root file system issue was a red herring. Sorry about that; I should > have looked closer right away.
Looking more into this I see the odd line in df output: overflow 1.0M - - - /tmp For df to show this there must be very little space on /tmp. It is still odd it shows - instead of 0 or some other sensible value but that's an issue with df. The code at line 28 stores some stuff in $TMPDIR and if I fill up $TMPDIR completely I get the bogus behaviour. The dkms modules package does not finish configuring. It neither succeeds nor fails in a reasonable amount of time. I guess there are two things that can be done here: 1) add a code at line 28 which prints the path to the temporary file which could not be written to ease diagnosis of this issue 2) make the dkms based packages set TMPDIR to some directory inside the build directory. This should prevent pollution of /tmp with dkms files which are left behind and improve resilience against similar errors. While the error is outside of the package itself its install scripts should deal with it one way or another, not cause dpkg to loop. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
