cannot use apt-get on kFreeBSD; 'no space left on device'

AnalBeard · 07-29-2012, 05:23 PM

Ok, so i'm not sure this is the best forum to post this in, although kFreeBSD is BSD-based, it still runs the same GNU userland as Debian 6.

My problem is this: i'm trying to upgrade samba, but I hit the same problem every time. Probably best if I just quote the error:

Code:

Setting up samba-common (2:3.6.6-2) ...
cp: writing `/var/run/samba/upgrades/smb.conf': No space left on device
dpkg: error processing samba-common (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
                                      dpkg: dependency problems prevent configuration of samba:
 samba depends on samba-common (= 2:3.6.6-2); however:
  Package samba-common is not configured yet.
dpkg: error processing samba (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      Errors were encountered while processing:
 samba-common
 samba
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have plenty of space on the drive in question, so can anyone shed any light on this?

Distro:

GNU/kFreeBSD s8.1-1-amd64

evo2 · 07-29-2012, 07:29 PM

Hi,

Quote:

Originally Posted by AnalBeard

I have plenty of space on the drive in question, so can anyone shed any light on this?

well the post install script thinks you don't. Are you sure there is space on the partition where /var is located? What happens if you try to write a file there?

Evo2.

AnalBeard · 07-30-2012, 02:14 AM

Ok, so this is what i have space-wise:

Code:

simon@sepulveda:/var/run$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/ad6s1            3.5G  1.4G  1.8G  45% /
devfs                 1.0K  1.0K     0 100% /dev
linprocfs             4.0K  4.0K     0 100% /proc
/sys                  4.0K  4.0K     0 100% /sys
fdescfs               1.0K  1.0K     0 100% /dev/fd
tmpfs                 556K  556K     0 100% /run
sepulveda.tank        5.4T  1.6T  3.9T  29% /mnt/sepulveda.tank
linprocfs             4.0K  4.0K     0 100% /proc

I tried copying a 3mb file to /var/run/ and received 'no space left on device'

evo2 · 07-30-2012, 02:20 AM

Hi,

well on my system (w/ Linux kernel) /var/run is just a symlink to /run. Your /run is reporting 100% full.

Evo2.

AnalBeard · 07-30-2012, 03:56 AM

Ah that would make sense. How would I go about increasing the size of the partition? Or should it not be full in the first place?

fatmac · 07-30-2012, 04:27 AM

tmpfs are usually ram based, how much ram in your system; if only 1gb, then more ram wanted.

AnalBeard · 07-30-2012, 04:47 AM

I have 2gb, should that not be enough?

Code:

mon@sepulveda:~$ free -mt
             total       used       free     shared    buffers     cached
Mem:          1967        560       1407         15          0         42
-/+ buffers/cache:        517       1450
Swap:            0          0          0
Total:        1967        560       1407

fatmac · 07-30-2012, 08:28 AM

2gb ram should certainly be enough, I queried it because to my knowledge tmpfs uses half of the available ram; however, it doesn't seem to be in your case.

I've just tried surfing for specifics pertaining to kfreebsd & your problem with no success, so I'm afraid I can't help you.

widget · 07-30-2012, 10:51 AM

Having all those tiny partitions is kind of silly. This is what it leads to.

Making them bigger will make them not read as full. This will help. Better to leave them in your / partition in the first place. Having a partition for /var would make sense but only if large enough.

My /run (in /) is only 76.9KB. /var (also in /) is 2.3GB.

Remember that most recommendations for a / partition are in the range of 10GB. Var is a large part of that making it a good candidate for a separate partition. I think /usr is too for that matter.

I stick with a / and /home (sometimes a /boot). I make my / partition no smaller than 10GB and it is 30GB on this (production OS) install. It is about half full at this point.

The file system in partitions will become fragmented under Linux when you get above 80% full. Give the buggers room to breath. This is easier, to me anyway, by sticking to a simple partition table for each install.

We have no idea how much space you have on your drive but having partitions that read as full is not a good thing at all. You can resize them using gparted.

You probably have to move some of them to some free space so that you have room to enlarge them. This can be done with gparted too.

Do not attempt to do this from any install on the drive you are working on. The best way is using an install on another drive if you have one. If not use a live CD (any distro should do) and do it from the live session.

AnalBeard · 07-30-2012, 11:15 AM

Ok, so obviously I need to do some shuffling around, I have a liveUSB lined up to do this with. Am I not right in thinking that as /run is mounted as tmpfs, it's not actually part of the partition table for the root drive? The root drive is 4gb by the way.

widget · 08-01-2012, 06:30 PM

/run is a directory. On mine which has a lot of stuff happening it is all of 106.1KB.

It does take up room, not a lot but it is there.

With a / drive the size you have you need to keep it as small as you can. Don't make a bunch of partitions. Just go with /.

Make sure that you are not keeping anything in the /var/cache/apt/archive directory except the "lock" file. I would keep the "/partial" directory in there too, just make sure it is empty. "apt=get clean" should clear it out for you. I don't use it usually as I like to keep a bunch of back packages in case I need to go to an older version (Debian testing - it happens - not often).

fatmac · 08-02-2012, 03:03 AM

That's apt-get clean. :-)

widget · 08-03-2012, 11:28 AM

Quote:

Originally Posted by fatmac

That's apt-get clean. :-)

I keep threatening to learn how to type. Obviously have not done it yet.