Date: Mon, 28 Feb 2011 12:26:14 +0000 From: Chris Rees <utisoft@gmail.com> To: Robert Bonomi <bonomi@mail.r-bonomi.com> Cc: freebsd-questions@freebsd.org, nr1c0re@gmail.com Subject: Re: / file system is full, but du does not show that it's full Message-ID: <AANLkTin6En%2BFhQvqxK6E6YkObvAS%2BKzC_xoD3DzfJ_wc@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
On 28 Feb 2011 12:12, "Robert Bonomi" <bonomi@mail.r-bonomi.com> wrote: > > > From owner-freebsd-questions@freebsd.org Mon 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 Size Used Avail Capacity Mounted on > > >> /dev/ad0s1a 496M 466M -9.8M 102% / > > >> > > >> So it's full. > > >> > > >> But by du it's not appeared to be full > > >> > > >> > > >> # du -hxd 1 / > > >> 2.0K /.snap > > >> 512B /dev > > >> 2.0K /tmp > > >> 2.0K /usr > > >> 2.0K /var > > >> 1.9M /etc > > >> 2.0K /cdrom > > >> 2.0K /dist > > >> 1.0M /bin > > >> 131M /boot > > >> 10M /lib > > >> 356K /libexec > > >> 2.0K /media > > >> 12K /mnt > > >> 2.0K /proc > > >> 7.2M /rescue > > >> 296K /root > > >> 4.7M /sbin > > >> 4.0K /lost+found > > >> 157M / > > >> > > > > > > Do you have partitions mounted at /tmp, /usr, /var etc? Does 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) lives > > > 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. Mounting the partition over them makes those > > > files inaccessible, but they still take up space on the drive. > > > > > > Cheers, > > > > > > Matthew > > > > > > -- > > > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > > > Flat 3 > > > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: > > > matthew@infracaninophile.co.uk 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. Stopping any daemons that were using "/var/spooll", and then > umount(1)-ing it would have done the trick from multi-user mode. > > > umount / ??? Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin6En%2BFhQvqxK6E6YkObvAS%2BKzC_xoD3DzfJ_wc>