Discussion:
/ was overflows
三輪晋( Miwa Susumu )
2014-04-28 14:18:41 UTC
Permalink
hi.

/ (root) was overflows.
How do I get to find out, consuming capacity?


question
========
I ran the sysbuild build. And it was in error.

/ was full for a long time. or impact of sysbuild. I do not know it.
As it, Where is / overflowing? I should I examine how?


environment
========
% uname -msr
NetBSD 6.1.2 i386


sysbuild error
========
% sysbuild build

:
# compile libpuffs/callcontext.ln
CC=/root/sysbuild/i386/tools/bin/i486--netbsdelf-gcc
/root/sysbuild/i386/tools/bin/i486--netbsdelf-lint -chapbxzFS -S -w -d
/root/sysbuild/i386/destdir/usr/include -D_FORTIFY_SOURCE=2 -i
/usr/src/lib/libpuffs/callcontext.c

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full

/: write failed, file system is full
/usr/src/lib/libpuffs/callcontext.c:49:0: fatal error: when writing
output to : No space left on device

/: write failed, file system is full
compilation terminated.
*** [callcontext.ln] Error code 1
nbmake: stopped in /usr/src/lib/libpuffs
1 error
nbmake: stopped in /usr/src/lib/libpuffs
*** [dependall] Error code 2
nbmake: stopped in /usr/src/lib/libpuffs
1 error
nbmake: stopped in /usr/src/lib/libpuffs
*** [dependall-libpuffs] Error code 2
nbmake: stopped in /usr/src/lib
1 error
nbmake: stopped in /usr/src/lib
*** [do-lib] Error code 2

nbmake: stopped in /usr/src
1 error

nbmake: stopped in /usr/src
*** [build] Error code 2
nbmake: stopped in /usr/src
1 error

nbmake: stopped in /usr/src
*** [distribution] Error code 2
nbmake: stopped in /usr/src
1 error

nbmake: stopped in /usr/src
*** [release] Error code 2

nbmake: stopped in /usr/src
1 error

nbmake: stopped in /usr/src

ERROR: Failed to make release
*** BUILD ABORTED ***
sysbuild: W: Command failed with code 1


survey
========
% df -h
Filesystem Size Used Avail %Cap Mounted on
/dev/wd0a 528M 527M -25M 105% /
/dev/wd0f 9.8G 153M 9.2G 1% /var
/dev/wd0e 20G 12G 7.1G 61% /usr
/dev/wd0g 19G 8.5G 9.6G 47% /home
kernfs 1.0K 1.0K 0B 100% /kern
ptyfs 1.0K 1.0K 0B 100% /dev/pts
procfs 4.0K 4.0K 0B 100% /proc


Looking at the / , only uses 13MB.


% ls -lh /
total 13M
drwxr-xr-x 2 root wheel 512 Nov 28 20:30 altroot/
drwxr-xr-x 2 root wheel 1.0K Nov 28 22:12 bin/
-r--r--r-- 1 root wheel 59K Jul 24 2011 boot
-rw-r--r-- 1 root wheel 319 Dec 7 2012 boot.cfg
drwxr-xr-x 2 root wheel 512 Jul 24 2011 cdrom/
drwxr-xr-x 5 root wheel 34K Nov 28 22:18 dev/
drwxr-xr-x 2 root wheel 512 Dec 29 16:48 emul/
drwxr-xr-x 26 root wheel 2.0K Apr 28 18:51 etc/
drwxr-xr-x 3 root wheel 512 May 25 2012 home/
dr-xr-xr-x 2 root wheel 512 Apr 28 18:53 kern/
drwxr-xr-x 2 root wheel 2.5K Nov 28 22:12 lib/
drwxr-xr-x 3 root wheel 512 Nov 28 20:30 libdata/
drwxr-xr-x 5 root wheel 512 Nov 28 22:12 libexec/
drwxr-xr-x 2 root wheel 512 Jan 24 20:20 media/
drwxr-xr-x 2 root wheel 512 Nov 28 20:30 mnt/
-rwxr-xr-x 1 root wheel 13M Nov 29 12:22 netbsd*
dr-xr-xr-x 1 root wheel 512 Apr 28 18:53 proc/
drwxr-xr-x 2 root wheel 3.0K Nov 28 22:17 rescue/
drwxr-xr-x 13 root wheel 512 Apr 27 17:39 root/
drwxr-xr-x 2 root wheel 3.0K Nov 28 22:14 sbin/
drwxr-xr-x 3 root wheel 512 Nov 28 21:21 stand/
drwxrwxrwt 3 root wheel 512 Apr 28 18:51 tmp/
drwxr-xr-x 23 root wheel 512 Apr 27 16:45 usr/
drwxr-xr-x 27 root wheel 512 Dec 10 20:51 var/


output of du. Is / consumed?


% du -m / | sort -nr -T ~/ | head -30
21401 /
11845 /usr
8722 /home
7696 /home/rin
4362 /usr/pkg
3437 /home/rin/work
2755 /home/rin/work/lang
2447 /home/rin/work/lang/c
2178 /usr/pkg/lib
2118 /usr/src.6.1.2
1576 /usr/src
1230 /usr/obj
1228 /usr/src.6.1.2/external
1081 /usr/pkg/lib/ruby
1047 /usr/pkg/share
1040 /usr/pkg/lib/ruby/gems
861 /usr/src/external
837 /usr/pkg/lib/ruby/gems/1.9.3
781 /home/rin/.hg
780 /home/rin/.hg/store
775 /usr/xsrc
726 /home/rin/mail
706 /usr/src.6.1.2/external/gpl3
693 /home/rin/public_html
690 /home/rin/.hg/store/data
685 /usr/pkgsrc
635 /home/rin/usr
635 /home/rin/usr/local
603 /usr/src/external/gpl3
598 /home/rin/public_html/images
--
miwarin
Ottavio Caruso
2014-04-28 14:23:30 UTC
Permalink
Post by 三輪晋( Miwa Susumu )
Looking at the / , only uses 13MB.
You're looking at the wrong entry.

% df -h
Filesystem Size Used Avail %Cap Mounted on
/dev/wd0a 528M 527M -25M 105% /

You have 528M on the first partition and you've used it all.
--
Ottavio
三輪晋( Miwa Susumu )
2014-04-28 15:13:11 UTC
Permalink
hi.
Post by Ottavio Caruso
Post by 三輪晋( Miwa Susumu )
Looking at the / , only uses 13MB.
You're looking at the wrong entry.
% df -h
Filesystem Size Used Avail %Cap Mounted on
/dev/wd0a 528M 527M -25M 105% /
You have 528M on the first partition and you've used it all.
I understanding of the mount seems to have missing.

thanks.
--
miwarin
Niels Dettenbach (Syndicat IT&Internet)
2014-04-28 14:37:34 UTC
Permalink
Post by 三輪晋( Miwa Susumu )
/ (root) was overflows.
How do I get to find out, consuming capacity?
i use the following or similiar for that job:

mkdir /mnt/root
mount /dev/volume-of-root /mnt/root
df -h /mnt/root/*

then if you found the file(s) which are so big, use i.e.:

lsof

or similiar tools to check who is writing/accessing that file.


hth
cheerioh,


Niels.
--
Niels Dettenbach
Syndicat IT&Internet
http://www.syndicat.com
三輪晋( Miwa Susumu )
2014-04-28 15:11:03 UTC
Permalink
hi.

2014-04-28 23:37 GMT+09:00 Niels Dettenbach (Syndicat IT&Internet)
Post by Niels Dettenbach (Syndicat IT&Internet)
Post by 三輪晋( Miwa Susumu )
/ (root) was overflows.
How do I get to find out, consuming capacity?
mkdir /mnt/root
mount /dev/volume-of-root /mnt/root
df -h /mnt/root/*
lsof
or similiar tools to check who is writing/accessing that file.
It is by dividing the mount point, and that isolate the problem.
In addition, I try to time it happens now.

thanks.
--
miwarin
三輪晋( Miwa Susumu )
2014-04-28 15:07:43 UTC
Permalink
hi.
thanks.
Post by 三輪晋( Miwa Susumu )
/ (root) was overflows.
How do I get to find out, consuming capacity?
<snip>
Post by 三輪晋( Miwa Susumu )
% du -m / | sort -nr -T ~/ | head -30
You need the -x flag to prevent du crossing mounts. What gives
du -m -x / | sort ...
I did not know -x options.

% du -m -x / | sort -nr -T ~/ | head -10
527 /
456 /root
357 /root/sysbuild
357 /root/sysbuild/i386
246 /root/sysbuild/i386/obj
246 /root/sysbuild/i386/obj/usr
246 /root/sysbuild/i386/obj/usr/src
187 /root/sysbuild/i386/obj/usr/src/tools
124 /root/sysbuild/i386/obj/usr/src/tools/gcc
124 /root/sysbuild/i386/obj/usr/src/tools/gcc/build


oh...
impact of sysbuild.
--
miwarin
David Lord
2014-04-28 23:46:44 UTC
Permalink
Post by 三輪晋( Miwa Susumu )
hi.
/ (root) was overflows.
How do I get to find out, consuming capacity?
question
========
I ran the sysbuild build. And it was in error.
/ was full for a long time. or impact of sysbuild. I do not know it.
As it, Where is / overflowing? I should I examine how?
environment
========
% uname -msr
NetBSD 6.1.2 i386
sysbuild error
========
% sysbuild build
# compile libpuffs/callcontext.ln
CC=/root/sysbuild/i386/tools/bin/i486--netbsdelf-gcc
/root/sysbuild/i386/tools/bin/i486--netbsdelf-lint -chapbxzFS -S -w -d
/root/sysbuild/i386/destdir/usr/include -D_FORTIFY_SOURCE=2 -i
/usr/src/lib/libpuffs/callcontext.c
/: write failed, file system is full
Hi

I've been using sysbuild twice a week as from Oct 5, 2013. You
might find both memory and disk usage is more than you expected.

Build pc, 3 GB ram, disk usage:
13G /home/sysbuild/nbsd-6_i386/i386
1.1G /home/sysbuild/nbsd-6_i386/release
1.5G /home/sysbuild/nbsd-6_i386/src
plus logs etc.

Trying to run a conf with 4 x ver + arch ran out of memory and
swap. Build of a single ver + arch doesn't touch swap.


David

Loading...