From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Reducing disk usage
Date: Fri, 27 Apr 2007 10:00:38 +0800 [thread overview]
Message-ID: <1177639238.28386.49.camel@localhost> (raw)
In-Reply-To: <200704261738.16205.volker.armin.hemmann@tu-clausthal.de>
Watch this one!
I ended up with a seriously broken system after running localepurge -
make sure you have your locale sorted out first! But it can save quite
a lot of space - pity the system was dead in the water ...
reiserfs is more space efficient than other filesystems like ext2/3
(depending on a lot of things ... YMMV)
-O3 - saves peanuts overall
rm -rf /usr/src/linux* - dangerous, lokk in there first and only remove
what you are not using (i.e., leave your current kernel, plus one other
"good" version as a backup - the number of times Ive had to roll
back ... :)
rm -rfv /usr/portage/distfiles - after thinking about if you need to
keep these versions, consider if redownloading them wont be a problem
(or write them out to DVD/CD etc. There are also a couple of distfile
cleaner programs - see the forums. If you have another machine, look
into http-replicator - highly recommended.
rm -rfv /var/tmp/portage - this can all go - often cruft like crashed OO
builds end up here - can be huge.
run `du /|sort -rn|less` and see where your biggest files/directories
are and see if they can go.
In real tight situations, NFS can help by
putting /usr/portage/distfiles, /var/tmp/portage, etc on other machines
with more diskspace. I have found this to be very flakey at times
depending on kernel versions, system loads, etc. Huge builds like OO
rarely finished without a crash or two in the build process :)
Use the -doc useflag and rebuild - this can save over a GB on a large
systems
there have been a number of threads over the years on saving space -
search the forums.
BillK
BillK
On Thu, 2007-04-26 at 17:38 +0200, Hemmann, Volker Armin wrote:
> On Donnerstag, 26. April 2007, Grant wrote:
> > I've found myself with a full hard disk and no obvious choices for
> > reducing usage. Are there any not-so-obvious ways to free up hard
> > disk space?
> >
> > - Grant
>
> localepurge
>
> rm -rf /var/tmp/
>
> using reiserfs
>
> stop using -O3
>
> rm -rf /usr/src/linux*
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-04-27 2:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 14:59 [gentoo-user] Reducing disk usage Grant
2007-04-26 15:16 ` Uwe Thiem
2007-04-26 15:16 ` Nelson, David J
2007-04-26 15:38 ` Hemmann, Volker Armin
2007-04-27 2:00 ` W.Kenworthy [this message]
[not found] ` <200704271212.49816.volker.armin.hemmann@tu-clausthal.de>
2007-04-28 1:09 ` William Kenworthy
2007-04-27 21:52 ` Grant
2007-04-26 17:45 ` fire-eyes
2007-04-26 18:36 ` Neil Bothwick
2007-04-26 21:57 ` [gentoo-user] " Alexander Skwar
2007-04-26 22:58 ` Hemmann, Volker Armin
2007-05-03 20:17 ` Csányi András
2007-05-03 20:37 ` Pongracz Istvan
2007-05-04 2:02 ` waltdnes
2007-05-04 7:15 ` Alan McKinnon
2007-05-05 2:41 ` waltdnes
2007-05-07 9:52 ` Alan McKinnon
[not found] ` <20070428095901.GA3742@ark.in-berlin.de>
2007-04-28 10:40 ` Neil Bothwick
2007-04-28 15:41 ` [gentoo-user] " Alexander Skwar
2007-05-04 7:52 ` [gentoo-user] " Florian Philipp
2007-05-08 2:18 ` Troy Curtis Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1177639238.28386.49.camel@localhost \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox