On 01/10/15 23:14, Nikos Chantziaras wrote:
ncdu also makes it easier to find where the space is consumed. "ncdu /"
will scan and sort by size.
Sorry, should have been:
ncdu -x /
This will exclude mounted filesystems.
, consider using emerge
--unmerge on it if you don't need it.
On Thu, Oct 1, 2015 at 1:15 PM, Nikos Chantziaras wrote:
> On 01/10/15 23:14, Nikos Chantziaras wrote:
>
>> ncdu also makes it easier to find where the space is consumed. "ncdu /"
>> will scan and s
u can maintain that with "eclean-dist -d". Also check portage/packages
for old binary packages.
ncdu also makes it easier to find where the space is consumed. "ncdu /"
will scan and sort by size.
googled a bit and I deleted all the /usr/share/doc/ and
this left me with 2.5 gb of space (wow).
So the questions are ... in cases like this, what should be done? what
is storing this much space? logs?
Install sys-fs/ncdu and run it as root with "ncdu -x /". It's gonna
take a bit
2009/6/10 Justin
> Alexander Pilipovsky schrieb:
>
>
> You have something big in /var. Check /var/tmp/portage or /var/log.
>
> Alos test sys-fs/ncdu or similar tools.
>
>
Thanks, it's was /var/log/messages that had 11 GB and was not opened by any
editor.
started 'ncdu -x /' which scans all dirs
on the / partition and then I can browse through my FS hieararchy, showing the
disk usage of every directory. Now I ran the same ncdu command again in
another screen, so I can compare it with the first one.
The folders themselves have 0.1
ackage 115 out of 174
> right now, and df shows a mere 389k blocks remaining.
>
> Also before I began the emerge run, I started 'ncdu -x /' which scans all dirs
> on the / partition and then I can browse through my FS hieararchy, showing the
> disk usage of every directory. Now
hould never parse ls' output:
http://mywiki.wooledge.org/ParsingLs
You can use ncdu or xdiskusage (both available in portage) to get more
useful output. Both will allow you to track down large folders, not
just single files (for example cache folders tend to hold a large
amount of tiny files, which may c
nd then looked at df /, it showed 1022
>> blocks, hence about 1 GB of free disk space. I am at package 115 out of 174
>> right now, and df shows a mere 389k blocks remaining.
>>
>> Also before I began the emerge run, I started 'ncdu -x /' which scans all
>> d
On Wed, Jun 10, 2009 at 1:24 PM, Alexander
Pilipovsky wrote:
>
>
> 2009/6/10 Justin
>>
>> Alexander Pilipovsky schrieb:
>>
>>
>> You have something big in /var. Check /var/tmp/portage or /var/log.
>>
>> Alos test sys-fs/ncdu or similar to
gt; > I've already removed all the files from /usr/portage/distfiles .
>
> 'du' is your friend : it has lots of options, so read the 'man'.
> that will tell you what's using so much space, then you can delete stuff.
I highly recommend sys-fs/ncdu, an ncurs
Paul Hartman написав(ла):
> On Wed, Jun 10, 2009 at 1:24 PM, Alexander
> Pilipovsky wrote:
>
>> 2009/6/10 Justin
>>
>>> Alexander Pilipovsky schrieb:
>>>
>>>
>>> You have something big in /var. Check /var/tmp/portage or
a look here regarding why you should never parse ls' output:
http://mywiki.wooledge.org/ParsingLs
You can use ncdu or xdiskusage (both available in portage) to get more
useful output. Both will allow you to track down large folders, not
just single files (for example cache folders tend to hol
re any to do this faster?
> >
> > Thank you very much in advance for any help!
> > Best regards,
> > Meino
>
>man du
>
> Dave F
Here's a couple of nice ones:
< du -sh /* | sort -rh >
< du -axk / | awk '$1 > 2^20 {print}' | sort -rn | head -20 >
You could also check out the application ncdu for a curses-based
du command analyzer.
d: find / -type f -size +2k -exec ls -lh {} \; | awk
>>> '{ print $8 ": " $5 }'
>>
>>Take a look here regarding why you should never parse ls' output:
>>http://mywiki.wooledge.org/ParsingLs
>>
>>You can use ncdu or xdiskusage (both available
# du -hs /etc
> 11M /etc
> sh-3.2# du -hs /lib
> 35M /lib
> sh-3.2# du -hs /mnt
> 0 /mnt
> sh-3.2# du -hs /sbin
> 5,9M /sbin
> sh-3.2# du -hs /sys
> 0 /sys
> The last install is Qt Creator with Qt SDK.
> How to clean partition?
>
> Thanks!
>
> --
> A
ime
> consuming).
A bit late to the game, but here is my way for this.
For a one-off thing, I use the already-mentioned excellent ncdu, which
provides vi-style navigation and even offers interactive deletion.
du is a viable option for quick use on smaller lists. But when it comes down
to actual c
/usr/share/doc, and you will see
what takes big space. Add a '| sort -n' to get sorted output. Or better
use sys-fs/ncdu which is interactive.
If you prefer something graphical, there are many alternatives:
Baobab in gnome-extra/gnome-utils
kde-base/filelight
k4dirstat in kde-misc/kdi
sk (containing that tree) -- most efficiently (least time
>> consuming).
> A bit late to the game, but here is my way for this.
> For a one-off thing, I use the already-mentioned excellent ncdu, which
> provides vi-style navigation and even offers interactive deletion.
>
> du is a via
> >> consuming).
> > A bit late to the game, but here is my way for this.
> > For a one-off thing, I use the already-mentioned excellent ncdu, which
> > provides vi-style navigation and even offers interactive deletion.
> >
> > du is a viable option fo
sc/whois
sys-apps/dstat
sys-apps/hdparm
sys-apps/hwinfo
sys-apps/less
sys-apps/lshw
sys-apps/microcode-ctl
sys-apps/mlocate
sys-apps/portage
sys-apps/smartmontools
sys-boot/grub-static
sys-fs/dosfstools
sys-fs/fuse
sys-fs/mdadm
sys-fs/ncdu
sys-fs/sysfsutils
sys-kernel/gentoo-sources
sys-kernel/gentoo-so
21 matches
Mail list logo