Date: Mon, 28 Feb 2011 16:26:59 +0300 From: c0re <nr1c0re@gmail.com> To: Robert Bonomi <bonomi@mail.r-bonomi.com> Cc: freebsd-questions@freebsd.org Subject: Re: / file system is full, but du does not show that it's full Message-ID: <AANLkTimQU6sTJT%2BT_FqOWvBDT06FnUziG8DLq316ErL=@mail.gmail.com> In-Reply-To: <201102281218.p1SCIR87034416@mail.r-bonomi.com> References: <AANLkTikyiZD%2BO6BKCighmuyppo5j2NinzoJE04zW8sXB@mail.gmail.com> <201102281218.p1SCIR87034416@mail.r-bonomi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2011/2/28 Robert Bonomi <bonomi@mail.r-bonomi.com>: >> From owner-freebsd-questions@freebsd.org =A0Mon Feb 28 05:31:46 2011 >> Date: Mon, 28 Feb 2011 14:24:30 +0300 >> From: c0re <nr1c0re@gmail.com> >> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> >> Cc: FreeBSD <freebsd-questions@freebsd.org> >> Subject: Re: / file system is full, but du does not show that it's full >> >> 2011/1/6 Matthew Seaman <m.seaman@infracaninophile.co.uk>: >> > On 06/01/2011 11:26, c0re wrote: >> >> # df -h >> >> Filesystem =A0 =A0 Size =A0 =A0Used =A0 Avail Capacity =A0Mounted on >> >> /dev/ad0s1a =A0 =A0496M =A0 =A0466M =A0 -9.8M =A0 102% =A0 =A0/ >> >> >> >> So it's full. >> >> >> >> But by du it's not appeared to be full >> >> >> >> >> >> # du -hxd 1 / >> >> 2.0K =A0 =A0/.snap >> >> 512B =A0 =A0/dev >> >> 2.0K =A0 =A0/tmp >> >> 2.0K =A0 =A0/usr >> >> 2.0K =A0 =A0/var >> >> 1.9M =A0 =A0/etc >> >> 2.0K =A0 =A0/cdrom >> >> 2.0K =A0 =A0/dist >> >> 1.0M =A0 =A0/bin >> >> 131M =A0 =A0/boot >> >> =A010M =A0 =A0/lib >> >> 356K =A0 =A0/libexec >> >> 2.0K =A0 =A0/media >> >> =A012K =A0 =A0/mnt >> >> 2.0K =A0 =A0/proc >> >> 7.2M =A0 =A0/rescue >> >> 296K =A0 =A0/root >> >> 4.7M =A0 =A0/sbin >> >> 4.0K =A0 =A0/lost+found >> >> 157M =A0 =A0/ >> >> >> > >> > Do you have partitions mounted at /tmp, /usr, /var etc? =A0Does the >> > output of your du command change if you unmount those partitions? (It >> > might be an idea to boot into a livefs CD or DVD given that du(1) live= s >> > in /usr/bin, so a bit tricky to unmount /usr and then run du) >> > >> > My guess is that you've at one time created files beneath what is >> > usually a mount point. =A0Mounting the partition over them makes those >> > files inaccessible, but they still take up space on the drive. >> > >> > =A0 =A0 =A0 =A0Cheers, >> > >> > =A0 =A0 =A0 =A0Matthew >> > >> > -- >> > Dr Matthew J Seaman MA, D.Phil. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 7 = Priory Courtyard >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Flat 3 >> > PGP: http://www.infracaninophile.co.uk/pgpkey =A0 =A0 Ramsgate JID: >> > matthew@infracaninophile.co.uk =A0 =A0 =A0 =A0 =A0 =A0 =A0 Kent, CT11 = 9PW >> > >> > >> >> At last I found time to check it. Booted with frenzy life cd, mounted >> only / partition and saw trash >> /var/spool. Deleted it and it solved problem. >> But later was and idea to mount device of / (/dev/da0s1a) as /mnt/root >> and just delete those files without need of livecd. It works in Linux. >> But in freebsd i got >> >> # mount /dev/da0s1a /mnt/root/ >> mount: /dev/da0s1a : Operation not permitted >> >> So only single user mode or live cd could solve it. > > *NOT* true. =A0Stopping any daemons that were using "/var/spooll", and th= en > umount(1)-ing it would have done the trick from multi-user mode. > Yeah, not true. Checked with lsof /var and it was used by these daemons: devd syslogd rpcbind snmpd mysqld httpd sendmail cron Yes, I can stop them all, but was not sure about stopping devd...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimQU6sTJT%2BT_FqOWvBDT06FnUziG8DLq316ErL=>