You are not logged in.
Pages: 1
I have a 7.6 GB /var partition, which is currently full. What would be safe to delete from it, and should I enlarge it so it doesn't fill up again?
Thanks!
Offline
Check which subdirectory is so big (I guess /var/cache/pacman/pkg). You can free space from there with pacman -Scc (deletes the downloaded arch pkgs).
Offline
I guess it's caused by (a) big log file(s). But of course doing a pacman -Sc or pacman -Scc will give you a lot of space back.
Offline
du -hs /var/*
should tell you which subdirectory is eating up a lot of space. If you have a separate /var it's a smart move to clean out your cache periodically.
Make also sure you rotate your logs and have old ones compressed.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Most of it seems to be /var/lib/pacman and /var/lib/nvidia (and /var/abs). Can I delete anything from those directories?
I'll clear the cache once I can boot, but for now I can't even boot.
e: Is the cache that would be cleared with pacman -Sc /var/cache/pacman/pkg? Would it be safe to delete that manually?
e2: Nevermind, I just chrooted into the install from an Ubuntu install and ran pacman -Sc from there.
Thanks all!
Last edited by Yes (2010-04-10 19:21:18)
Offline
hum...
74M /var/lib/pacman/
60M /var/abs/
1,2G /var/
1,1G /var/cache/
1,1G /var/cache/pacman/pkg/
Are you sure /var/lib/pacman(abs) are realy that big? Nevertheless it is safe to remove old packages from /var/cache/pacman/pkg/. so find some old package, delete it manually. some few mbs should be more than sufficient to boot again.
Offline
The pacman cache will grow and grow if you let it. There is no need to remove stuff manually either. "pacman -Sc(c)" as mentioned above will do the job.
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
Along with cleaning all or uninstall package cache, you might be interested in a log cleaner app such as bleachbit to increase the leftover space.
Offline
There is no need to remove stuff manually either.
...unless you cant even boot, because /var is filled up to the last byte.
Offline
loafer wrote:There is no need to remove stuff manually either.
...unless you cant even boot, because /var is filled up to the last byte.
You can boot even if your system is filled up, since ext* fs allocates some space for root login.
Offline
You can boot even if your system is filled up, since ext* fs allocates some space for root login.
Pacman is generally run as root, so its cache could conceivably fill up the reserved 5%.
Offline
flamelab wrote:You can boot even if your system is filled up, since ext* fs allocates some space for root login.
Pacman is generally run as root, so its cache could conceivably fill up the reserved 5%.
You've confused the term "root" and "ran as root"
Offline
as everyone said, its probably because of the downloaded packages. do a pacman -Sc or pacman -Scc or empty the folder /var/cache/pacman/pkg manually. i dont think anything else can take up that much space.
Offline
i know this is not the place for this kind of discussion, as this problem is probably solved, but tavianator is right. I think pacman filled up the cache dir and the last available bytes were allocated by some log files. (all these files are owned by root.)
Offline
I dont know where these 7 gigs come from - but this is the 2nd such problem in a short time! When oh when will people learn to make a root filesystem that is big enough. With today's disks and prices - why skimp??
Me - I use 20 gigs (but then I dont split it up any - the entire distro is on one single partition (which is great when you are distrohopping!).
For those unfortuneate enough to have such a problem - and it will occur again and again whenever you have large'ish updates - the solution is simple. Just move /var/cache to somewhere else - an otherwise unused partition eg. and then make a symbolic link.
Offline
uwinkelvos wrote:loafer wrote:There is no need to remove stuff manually either.
...unless you cant even boot, because /var is filled up to the last byte.
You can boot even if your system is filled up, since ext* fs allocates some space for root login.
I have had a situation where a /var on the same partition as / would fill up the whole root partition to the brim and would not allow me to boot up any further - so I could not log in. Giving /var a separate partition prevents that. If you keep that in mind, what uwinkelvos said is probably true.
From the tune2fs manual (emphasis mine):
-m reserved-blocks-percentage
Set the percentage of the filesystem which may only be allocated by privileged processes. Reserving some number of filesystem blocks
for use by privileged processes is done to avoid filesystem fragmentation, and to allow system daemons, such as syslogd(8), to continue
to function correctly after non-privileged processes are prevented from writing to the filesystem. Normally, the default percentage of
reserved blocks is 5%.
Perbh, allow me to show you wrong:
/dev/sda5 3,9G 2,7G 1007M 74% /
udev 10M 228K 9,8M 3% /dev
none 1004M 0 1004M 0% /dev/shm
/dev/sda2 92M 14M 73M 16% /boot
/dev/sda6 1,5G 379M 1,1G 26% /var
/dev/sda7 24G 19G 5,5G 78% /home
none 512M 44K 512M 1% /tmp
You don't need a huge /, you do need to know how much you'll be installing (and that's experience and calculation, pacman happily reports installed size for installs). Split out /var and you can trim down even further.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I have a script that'll keep your pacman cache trimmed (and fast), run it just when var gets big or pacman gets too slow:
#!/bin/bash
tar -cjvf /srv/rec/pacman-database.tar.bz2 /var/lib/pacman/local
pacman -Rscn $(pacman -Qtdq)
pacman -Sc
pacman-optimize && sync
You can use whatever compression you like. Don't run it too much. You'll need to run as root. You'll need to make a dir called /srv/rec/ or whatever you like.
Last edited by Anikom15 (2010-04-11 18:15:01)
Personally, I'd rather be back in Hobbiton.
Offline
I have a script that'll keep your pacman cache trimmed (and fast), run it just when var gets big or pacman gets too slow:
#!/bin/bash tar -cjvf /srv/rec/pacman-database.tar.bz2 /var/lib/pacman/local pacman -Rscn $(pacman -Qtdq) pacman -Sc pacman-optimize && sync
You can use whatever compression you like. Don't run it too much. You'll need to run as root. You'll need to make a dir called /srv/rec/ or whatever you like.
That script will break things on many people's systems. I strongly recommend not using it until at least pacman -Qtdq is clear of any output.
Offline
kay, so is there a way I can fix it?
(I'm not a big bash scripter, but I've never had any problems with it.)
Personally, I'd rather be back in Hobbiton.
Offline
Perbh, allow me to show you wrong:
/dev/sda5 3,9G 2,7G 1007M 74% / udev 10M 228K 9,8M 3% /dev none 1004M 0 1004M 0% /dev/shm /dev/sda2 92M 14M 73M 16% /boot /dev/sda6 1,5G 379M 1,1G 26% /var /dev/sda7 24G 19G 5,5G 78% /home none 512M 44K 512M 1% /tmp
You don't need a huge /, you do need to know how much you'll be installing (and that's experience and calculation, pacman happily reports installed size for installs). Split out /var and you can trim down even further.
Yeah - and this is a 'newbie' forum!! How many newbies has the kind of experience neccessary?
As for splitting it all up - that is fine if you have but one distro ... If you use more than one, you'll soon have almost unsurmountable problems keeping them all apart!
I didn't say it was _wrong_ to have small partitions, I just questioned the wisdom to do it for a _newbie_ - at least these days where you can get 1 TB disk for less than 100 bucks.
Offline
This is a newbie *subforum*. Last time I checked this is still the Arch forum, and Arch Linux is not a distro targeted at newbies. You've been around for five years, don't tell me you expect the hand holding certain distros offer, be it for you or for other people, even the new ones? This subforum is intended for new members needing a bit more leniency, but not a free pass at 'hey spell it out for me cuz I dunnoes how 2 google LULZ!'.
As for splitting things up, I must confess I lose track easily already now - with only one distro . While it may be a bit of a hassle at times, it's not like you need to recreate that layout every week. Three or four separate partitions is really not a problem if you stick with a single distro.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
Pages: 1