Debian Bug report logs - #620014
openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Tue, 29 Mar 2011 12:20:21 +0200

Package: openafs-modules-dkms
Version: 1.6.0~pre3-1
Severity: normal


When overflow tmp is mounted the package locks up during configure.

# dpkg --pending --configure
Setting up openafs-modules-dkms (1.6.0~pre3-1) ...
Removing old openafs-1.6.0pre3 DKMS files...

------------------------------
Deleting module version: 1.6.0pre3
completely from the DKMS tree.
------------------------------
Done.
Loading new openafs-1.6.0pre3 DKMS files...
Building only for 2.6.38-1-amd64
Building initial module for 2.6.38-1-amd64
/usr/sbin/dkms: line 28: echo: write error: No space left on device

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda3             9.7G  9.4G     0 100% /
tmpfs                 1.9G     0  1.9G   0% /lib/init/rw
udev                  1.9G  264K  1.9G   1% /dev
tmpfs                 1.9G     0  1.9G   0% /dev/shm
/dev/sda1             9.7G  8.8G  912M  91% /home
/dev/sda4             208G  159G   39G  81% /scratch
overflow              1.0M     -     -   -  /tmp



-- System Information:
Debian Release: 6.0.1
  APT prefers stable
  APT policy: (900, 'stable'), (700, 'oldstable'), (510, 'unstable'), (500, 'testing'), (200, 'experimental'), (111, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openafs-modules-dkms depends on:
ii  dkms                          2.1.1.2-5  Dynamic Kernel Module Support Fram
ii  libc6-dev                     2.11.2-10  Embedded GNU C Library: Developmen
ii  perl                          5.10.1-17  Larry Wall's Practical Extraction 

Versions of packages openafs-modules-dkms recommends:
pn  openafs-client                <none>     (no description available)

openafs-modules-dkms suggests no packages.

-- no debconf information

Message #10 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Russ Allbery <rra@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: 620014@bugs.debian.org

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Tue, 29 Mar 2011 10:18:09 -0700

Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:

> When overflow tmp is mounted the package locks up during configure.

I'm not familiar with "overflow tmp", but it looks rather like configure
locked up because your root partition ran out of space.

> # dpkg --pending --configure
> Setting up openafs-modules-dkms (1.6.0~pre3-1) ...
> Removing old openafs-1.6.0pre3 DKMS files...

> ------------------------------
> Deleting module version: 1.6.0pre3
> completely from the DKMS tree.
> ------------------------------
> Done.
> Loading new openafs-1.6.0pre3 DKMS files...
> Building only for 2.6.38-1-amd64
> Building initial module for 2.6.38-1-amd64
> /usr/sbin/dkms: line 28: echo: write error: No space left on device

> Filesystem            Size  Used Avail Use% Mounted on
> /dev/sda3             9.7G  9.4G     0 100% /

I don't think there's anything the package can do about that.  You have to
have enough space on your root partition to build the modules.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Message #15 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Russ Allbery <rra@debian.org>

Cc: "620014@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Wed, 30 Mar 2011 09:23:57 +0200

Excerpts from Russ Allbery's message of Tue Mar 29 19:18:09 +0200 2011:
> Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:
> 
> > When overflow tmp is mounted the package locks up during configure.
> 
> I'm not familiar with "overflow tmp", but it looks rather like configure
> locked up because your root partition ran out of space.

No, it did not.

There is 300M space.

Thanks

Michal

Message #20 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Russ Allbery <rra@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "620014\@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Wed, 30 Mar 2011 11:15:13 -0700

Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:
> Excerpts from Russ Allbery's message of Tue Mar 29 19:18:09 +0200 2011:
>> Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:

>>> When overflow tmp is mounted the package locks up during configure.

>> I'm not familiar with "overflow tmp", but it looks rather like
>> configure locked up because your root partition ran out of space.

> No, it did not.

> There is 300M space.

Well, the error message you got says pretty clearly that it ran out of
space:

/usr/sbin/dkms: line 28: echo: write error: No space left on device

I don't know why your df has a difference between the size and used column
of 300MB, but the available space is 0, which means that nothing is going
to be able to write to the file system.

/dev/sda3             9.7G  9.4G     0 100% /

This definitely isn't something that can be addressed in
openafs-modules-dkms, which just asks dkms to build the module.  dkms
itself failed when trying to write a file (probably into /var).  And it
doesn't really do any good to transfer the bug to dkms either, since the
dkms maintainer is just going to point out that dkms got an out of space
error from the file system.

I can reassign your bug to the Linux kernel package if you really want
someone to look at the reported df discrepency, but I'm not sure they're
going to be able to do anything for you either.  Your file system is
showing every sign of being completely out of space and refusing to write
files, despite the odd 300MB discrepency.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Message #25 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Russ Allbery <rra@debian.org>

Cc: "620014@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Thu, 31 Mar 2011 09:47:51 +0200

Excerpts from Russ Allbery's message of Wed Mar 30 20:15:13 +0200 2011:
> Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:
> > Excerpts from Russ Allbery's message of Tue Mar 29 19:18:09 +0200 2011:
> >> Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:
> 
> >>> When overflow tmp is mounted the package locks up during configure.
> 
> >> I'm not familiar with "overflow tmp", but it looks rather like
> >> configure locked up because your root partition ran out of space.
> 
> > No, it did not.
> 
> > There is 300M space.
> 
> Well, the error message you got says pretty clearly that it ran out of
> space:
> 
> /usr/sbin/dkms: line 28: echo: write error: No space left on device
> 
> I don't know why your df has a difference between the size and used column
> of 300MB, but the available space is 0, which means that nothing is going
> to be able to write to the file system.
> 
> /dev/sda3             9.7G  9.4G     0 100% /
> 
> This definitely isn't something that can be addressed in
> openafs-modules-dkms, which just asks dkms to build the module.  dkms
> itself failed when trying to write a file (probably into /var).  And it
> doesn't really do any good to transfer the bug to dkms either, since the
> dkms maintainer is just going to point out that dkms got an out of space
> error from the file system.
> 
> I can reassign your bug to the Linux kernel package if you really want
> someone to look at the reported df discrepency, but I'm not sure they're
> going to be able to do anything for you either.  Your file system is
> showing every sign of being completely out of space and refusing to write
> files, despite the odd 300MB discrepency.
> 

It is not a discrepancy. It means that only processes running as root
can use the remaining space.

What is a problem that in this case /tmp is mounted as tmpfs with 1M
space by the initscripts and openafs apparently needs more than 1M space
to build. The workaround would be to use the -pipe gcc option I guess.

Another solution would be to mount reasonable amount of space as
overflow tmp in the initscripts.

Thanks

Michal

Message #30 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Russ Allbery <rra@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "620014\@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Thu, 31 Mar 2011 09:18:25 -0700

Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:
> Excerpts from Russ Allbery's message of Wed Mar 30 20:15:13 +0200 2011:

>> Well, the error message you got says pretty clearly that it ran out of
>> space:

>> /usr/sbin/dkms: line 28: echo: write error: No space left on device

[...]

> What is a problem that in this case /tmp is mounted as tmpfs with 1M
> space by the initscripts and openafs apparently needs more than 1M space
> to build. The workaround would be to use the -pipe gcc option I guess.

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.

> Another solution would be to mount reasonable amount of space as
> overflow tmp in the initscripts.

This is definitely not something I can do in the openafs packages; that
sort of decision Debian always leaves entirely to the local administrator.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Message #35 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Russ Allbery <rra@debian.org>

Cc: "620014@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Thu, 31 Mar 2011 21:27:01 +0200

Excerpts from Russ Allbery's message of Thu Mar 31 18:18:25 +0200 2011:
> Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:
> > Excerpts from Russ Allbery's message of Wed Mar 30 20:15:13 +0200 2011:
> 
> >> Well, the error message you got says pretty clearly that it ran out of
> >> space:
> 
> >> /usr/sbin/dkms: line 28: echo: write error: No space left on device
> 
> [...]
> 
> > What is a problem that in this case /tmp is mounted as tmpfs with 1M
> > space by the initscripts and openafs apparently needs more than 1M space
> > to build. The workaround would be to use the -pipe gcc option I guess.
> 
> 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.

> 
> > Another solution would be to mount reasonable amount of space as
> > overflow tmp in the initscripts.
> 
> This is definitely not something I can do in the openafs packages; that
> sort of decision Debian always leaves entirely to the local administrator.
> 

By hardcoding it in the initscript?

Thanks

Michal

Message #40 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Russ Allbery <rra@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: "620014\@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Thu, 31 Mar 2011 13:03:38 -0700

Michal Suchanek <michal.suchanek@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.

I'm not sure what part of the build process is using /tmp.  It may be, as
you say, gcc while doing the build, although if that's the case that's
controlled by the Linux kernel makefiles, not by OpenAFS.  (As with most
modules, it uses kbuild to do the actual builds.)  I'm not sure if the
Linux build system by default uses -pipe or not.  There is some code in
DKMS to do things like unpack the module source itself into /tmp, which
will definitely not work since the OpenAFS module source is 7MB by itself,
but I don't think any of that triggers for just a regular module build.

Does the build work if you set TMPDIR to some directory in another file
system that has more space?  I just want to make sure that it's really the
/tmp part and not the root file system part that's having trouble.

>> This is definitely not something I can do in the openafs packages; that
>> sort of decision Debian always leaves entirely to the local
>> administrator.

> By hardcoding it in the initscript?

The openafs-client init script?  That doesn't make sense to me;
openafs-modules-dkms doesn't even depend on openafs-client, plus packages
really shouldn't make assumptions about how disk utilization or file
systems should be handled on the local system.  There's way too high of a
risk of tromping on something the local administrator is trying to do.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Message #45 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Russ Allbery <rra@debian.org>

Cc: "620014@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Mon, 04 Apr 2011 16:05:40 +0200

Excerpts from Russ Allbery's message of Thu Mar 31 22:03:38 +0200 2011:
> Michal Suchanek <michal.suchanek@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.
> 
> I'm not sure what part of the build process is using /tmp.  It may be, as
> you say, gcc while doing the build, although if that's the case that's
> controlled by the Linux kernel makefiles, not by OpenAFS.  (As with most
> modules, it uses kbuild to do the actual builds.)  I'm not sure if the
> Linux build system by default uses -pipe or not.  There is some code in
> DKMS to do things like unpack the module source itself into /tmp, which
> will definitely not work since the OpenAFS module source is 7MB by itself,
> but I don't think any of that triggers for just a regular module build.
> 
> Does the build work if you set TMPDIR to some directory in another file
> system that has more space?  I just want to make sure that it's really the
> /tmp part and not the root file system part that's having trouble.

I tried on another system and there the module builds fine.

Maybe that's because it's a test system with nothing running and thus nothing taking up space in /tmp.

Or perhaps the log got shorter between rc3 and rc4.

The error message does not give much insight into the part which fails
so I have no idea why it happens on one system but not on other:
Preparing to replace openafs-modules-dkms 1.6.0~pre4-1 (using .../openafs-modules-dkms_1.6.0~pre4-1_all.deb) ...

-------- Uninstall Beginning --------
Module:  openafs
Version: 1.6.0pre4
Kernel:  2.6.38-2-amd64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

openafs.ko:
 - Uninstallation
   - Deleting from: /lib/modules/2.6.38-2-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod........

DKMS: uninstall Completed.

------------------------------
Deleting module version: 1.6.0pre4
completely from the DKMS tree.
------------------------------
Done.
Unpacking replacement openafs-modules-dkms ...
Setting up openafs-modules-dkms (1.6.0~pre4-1) ...
Loading new openafs-1.6.0pre4 DKMS files...
Building only for 2.6.38-2-amd64
Building initial module for 2.6.38-2-amd64
Done.

openafs.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.38-2-amd64/updates/dkms/

depmod.......

DKMS: install Completed.
                                         
root@testbox:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2             5.1G  4.8G     0 100% /
tmpfs                 502M     0  502M   0% /lib/init/rw
udev                  496M  120K  496M   1% /dev
tmpfs                 502M  4.0K  502M   1% /dev/shm
overflow              1.0M     0  1.0M   0% /tmp
/dev/sda3             177G  2.5G  166G   2% /scratch


> 
> >> This is definitely not something I can do in the openafs packages; that
> >> sort of decision Debian always leaves entirely to the local
> >> administrator.
> 
> > By hardcoding it in the initscript?
> 
> The openafs-client init script?  That doesn't make sense to me;
> openafs-modules-dkms doesn't even depend on openafs-client, plus packages
> really shouldn't make assumptions about how disk utilization or file
> systems should be handled on the local system.  There's way too high of a
> risk of tromping on something the local administrator is trying to do.
> 

It's hardcoded in initscripts:

# dpkg -S /etc/init.d/mountoverflowtmp
initscripts: /etc/init.d/mountoverflowtmp

# grep -Fe "-t tmpfs" /etc/init.d/mountoverflowtmp
		mount -t tmpfs -o size=1048576,mode=1777 overflow /tmp



Thanks

Michal

Message #50 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Russ Allbery <rra@debian.org>

Cc: "620014@bugs.debian.org" <620014@bugs.debian.org>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Wed, 06 Apr 2011 17:50:35 +0200

Excerpts from Russ Allbery's message of Thu Mar 31 22:03:38 +0200 2011:
> Michal Suchanek <michal.suchanek@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

Message #57 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Russ Allbery <rra@debian.org>

To: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

Cc: 620014@bugs.debian.org, Thorsten Alteholz <debian@alteholz.de>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Wed, 06 Mar 2013 00:33:16 -0800

Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:

> When overflow tmp is mounted the package locks up during configure.

> # dpkg --pending --configure
> Setting up openafs-modules-dkms (1.6.0~pre3-1) ...
> Removing old openafs-1.6.0pre3 DKMS files...

> ------------------------------
> Deleting module version: 1.6.0pre3
> completely from the DKMS tree.
> ------------------------------
> Done.
> Loading new openafs-1.6.0pre3 DKMS files...
> Building only for 2.6.38-1-amd64
> Building initial module for 2.6.38-1-amd64
> /usr/sbin/dkms: line 28: echo: write error: No space left on device

I know it's been nearly two years, but I wanted to let you know that
Thorsten Alteholz, who has been doing great work helping with the OpenAFS
packages, tracked down this problem to a bug in dkms.  See:

    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702018

for the details of what's going on.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>

Message #62 received at 620014@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <michal.suchanek@ruk.cuni.cz>

To: Russ Allbery <rra@debian.org>

Cc: "620014@bugs.debian.org" <620014@bugs.debian.org>, Thorsten Alteholz <debian@alteholz.de>

Subject: Re: Bug#620014: openafs-modules-dkms: cannot install openafs with overflow tmp mounted - no space

Date: Fri, 08 Mar 2013 17:57:51 +0100

Excerpts from Russ Allbery's message of Wed Mar 06 09:33:16 +0100 2013:
> Michal Suchanek <michal.suchanek@ruk.cuni.cz> writes:
> 
> > When overflow tmp is mounted the package locks up during configure.
> 
> > # dpkg --pending --configure
> > Setting up openafs-modules-dkms (1.6.0~pre3-1) ...
> > Removing old openafs-1.6.0pre3 DKMS files...
> 
> > ------------------------------
> > Deleting module version: 1.6.0pre3
> > completely from the DKMS tree.
> > ------------------------------
> > Done.
> > Loading new openafs-1.6.0pre3 DKMS files...
> > Building only for 2.6.38-1-amd64
> > Building initial module for 2.6.38-1-amd64
> > /usr/sbin/dkms: line 28: echo: write error: No space left on device
> 
> I know it's been nearly two years, but I wanted to let you know that
> Thorsten Alteholz, who has been doing great work helping with the OpenAFS
> packages, tracked down this problem to a bug in dkms.  See:
> 
>     http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702018
> 
> for the details of what's going on.
> 

Thanks for looking into this.

I have the impression that the overflow tmp is now not ridiculously
small anymore so this should be less of an issue.

I can't find the place in initscripts where it is mounted, though.

Michal

Send a report that this bug log contains spam.