Re: / file system is full, but du does not show that it's full
2011/2/28 Robert Bonomi : >> From owner-freebsd-questi...@freebsd.org Mon Feb 28 05:31:46 2011 >> Date: Mon, 28 Feb 2011 14:24:30 +0300 >> From: c0re >> To: Matthew Seaman >> Cc: FreeBSD >> Subject: Re: / file system is full, but du does not show that it's full >> >> 2011/1/6 Matthew Seaman : >> > 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: >> > matt...@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. > 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... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On 02/28/11 12:47, Polytropon wrote: On Mon, 28 Feb 2011 13:29:59 +0100, Damien Fleuriot wrote: Slice a (as in: da0s1a) is very likely his / /var is usually slice f Terminology: Slices are with numbers, partitions are with letters. :-) E. g. da0s1 is the FreeBSD slice, its partition a = da0s1a is /, while /var corresponds to partition da0s1f. Unless you've got GPT disks where there are usually only partitions and they're numbered: arthur@fileserver> gpart show ada5 => 34 976773101 ada5 GPT (466G) 34 6- free - (3.0K) 40 64 1 freebsd-boot (32K) 1042097152 2 freebsd-ufs (1.0G) 20972562097152 3 freebsd-ufs (1.0G) 41944088388608 4 freebsd-swap (4.0G) 12583016 964190119 5 freebsd-ufs (460G) arthur@fileserver> ls /dev/ada5* /dev/ada5 /dev/ada5p1 /dev/ada5p2 /dev/ada5p3 /dev/ada5p4 /dev/ada5p5 Personally I prefer labelling everything, which GPT makes easier. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On Mon, 28 Feb 2011 13:29:59 +0100, Damien Fleuriot wrote: > Slice a (as in: da0s1a) is very likely his / > > /var is usually slice f Terminology: Slices are with numbers, partitions are with letters. :-) E. g. da0s1 is the FreeBSD slice, its partition a = da0s1a is /, while /var corresponds to partition da0s1f. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On 28 February 2011 12:29, Damien Fleuriot wrote: > On 2/28/11 1:27 PM, Chris Rees wrote: >> On 28 February 2011 12:26, Chris Rees wrote: > > # 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 >> >> Er, caffeine overdose. >> >> I guess you meant: >> >> # umount /var > Slice a (as in: da0s1a) is very likely his / > > /var is usually slice f Yeah, that's why I sent the first email. However, it's now clear to me that c0re wanted to remount his / on a different partition to delete a file hidden by /var. Hence the suggestion from Robert to umount /var. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On 2/28/11 1:27 PM, Chris Rees wrote: > On 28 February 2011 12:26, Chris Rees wrote: # 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 > > Er, caffeine overdose. > > I guess you meant: > > # umount /var > > > > I'll hide now. > > Chris Slice a (as in: da0s1a) is very likely his / /var is usually slice f ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On 28 February 2011 12:26, Chris Rees wrote: >> > >> > # 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 Er, caffeine overdose. I guess you meant: # umount /var I'll hide now. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On 2/28/11 12:24 PM, c0re wrote: > 2011/1/6 Matthew Seaman : >> On 06/01/2011 11:26, c0re wrote: >>> # df -h >>> Filesystem SizeUsed Avail Capacity Mounted on >>> /dev/ad0s1a496M466M -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: matt...@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. > > Thanks Matthew for an idea! You're not really trying to umount / on a running system are you ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On 28 Feb 2011 12:12, "Robert Bonomi" wrote: > > > From owner-freebsd-questi...@freebsd.org Mon Feb 28 05:31:46 2011 > > Date: Mon, 28 Feb 2011 14:24:30 +0300 > > From: c0re > > To: Matthew Seaman > > Cc: FreeBSD > > Subject: Re: / file system is full, but du does not show that it's full > > > > 2011/1/6 Matthew Seaman : > > > On 06/01/2011 11:26, c0re wrote: > > >> # df -h > > >> Filesystem SizeUsed Avail Capacity Mounted on > > >> /dev/ad0s1a496M466M -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: > > > matt...@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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
> From owner-freebsd-questi...@freebsd.org Mon Feb 28 05:31:46 2011 > Date: Mon, 28 Feb 2011 14:24:30 +0300 > From: c0re > To: Matthew Seaman > Cc: FreeBSD > Subject: Re: / file system is full, but du does not show that it's full > > 2011/1/6 Matthew Seaman : > > On 06/01/2011 11:26, c0re wrote: > >> # df -h > >> Filesystem SizeUsed Avail Capacity Mounted on > >> /dev/ad0s1a496M466M -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: > > matt...@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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
2011/1/6 Matthew Seaman : > 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: matt...@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. Thanks Matthew for an idea! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
Concrete jungle, oh freebsd-questions, you've got to do your best... 2011/01/06 17:19:05 +0300 c0re => To FreeBSD : cr> > Another place to look for wasted space is filesystem snapshots, if any. They cr> > can be created implicitly, e. g., by fsck. cr> Yeah, I checked /.snap - nothing there. snapshot is represented as a file of a special type that can be located anywhere oin a file system, not only the /.snap/. Try snainfo -a. 73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
On 06.01.2011 15:19, c0re wrote: >> why not to restart your httpd and mysqld? >> This may release your unused filehandles. > As I said I've restarted whole server, so nothing there to release at all. > >> Another place to look for wasted space is filesystem snapshots, if any. They >> can be created implicitly, e. g., by fsck. > Yeah, I checked /.snap - nothing there. Reboot into single user mode, and check with du -hs /* before the system mounts other FS'es than / //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: / file system is full, but du does not show that it's full
> why not to restart your httpd and mysqld? > This may release your unused filehandles. As I said I've restarted whole server, so nothing there to release at all. > Another place to look for wasted space is filesystem snapshots, if any. They > can be created implicitly, e. g., by fsck. Yeah, I checked /.snap - nothing there. > And... why lsof and not fstat(1)? As I mentioned - fstat does not show full path including filename like lsof does. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
Server has been rebooted before to try this. Chris Sorry for top-posting, Android won't let me quote, but K-9 can't yet do threading. On 6 Jan 2011 14:06, "Peter Vereshagin" wrote: > Concrete jungle, oh freebsd-questions, you've got to do your best... > 2011/01/06 16:57:34 +0300 Peter Vereshagin => To freebsd-questions@freebsd.org : > PV> This may release your unused filehandles. > > used but unlinked, really, oops. > > 73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) > -- > http://vereshagin.org > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
Concrete jungle, oh freebsd-questions, you've got to do your best... 2011/01/06 16:57:34 +0300 Peter Vereshagin => To freebsd-questions@freebsd.org : PV> This may release your unused filehandles. used but unlinked, really, oops. 73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
Concrete jungle, oh freebsd-questions, you've got to do your best... 2011/01/06 15:06:18 +0300 c0re => To FreeBSD : cr> # lsof / why not to restart your httpd and mysqld? This may release your unused filehandles. Another place to look for wasted space is filesystem snapshots, if any. They can be created implicitly, e. g., by fsck. And... why lsof and not fstat(1)? 73! Peter pgp: A0E26627 (4A42 6841 2871 5EA7 52AB 12F8 0CE1 4AAC A0E2 6627) -- http://vereshagin.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
2011/1/6 Matthew Seaman : > 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: matt...@infracaninophile.co.uk Kent, CT11 9PW > > Nice idea! But I can't check it now - server is may hundred km away and no KVM aviable. Will check it 1 or 2 weeks later. Checked only /tmp - it was ok, no files there after unmount. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: / file system is full, but du does not show that it's full
2011/1/6 Ryan Coleman : > What about filehandlers? > > On Jan 6, 2011, at 5:26 AM, 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 / >> >> >> I know that something (like running process) can hold file so it's >> actually are not deleted. I rebooted server. But this not helped, so >> it's not a process holding file. >> >> Checked with fsck >> >> # fsck / >> ** /dev/ad0s1a (NO WRITE) >> ** Last Mounted on / >> ** Root file system >> ** Phase 1 - Check Blocks and Sizes >> ** Phase 2 - Check Pathnames >> ** Phase 3 - Check Connectivity >> ** Phase 4 - Check Reference Counts >> ** Phase 5 - Check Cyl groups >> 47268 files, 238539 used, 15276 free (6684 frags, 1074 blocks, 2.6% >> fragmentation) >> >> No problems here. >> >> >> # uname -a >> FreeBSD host.domain.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #0: Tue >> Dec 28 13:55:47 MSK 2010 >> r...@host.domain.com:/usr/obj/usr/src/sys/MYKERNEL i386 >> >> What's the problem here? Why df says that filesystem is full? Other >> command may also say that can't write because file system is full. >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > fstat does not show full filepath so I uses lsof from ports lsof does not show anything criminal # lsof / COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME init 1 root cwd VDIR 0,81 512 2 / init 1 root rtd VDIR 0,81 512 2 / init 1 root txt VREG 0,81 632348 33074 /sbin/init firmware 5 root cwd VDIR 0,81 512 2 / firmware 5 root rtd VDIR 0,81 512 2 / adjkerntz 145 root cwd VDIR 0,81 512 2 / adjkerntz 145 root rtd VDIR 0,81 512 2 / adjkerntz 145 root txt VREG 0,81 7448 16481 /sbin/adjkerntz adjkerntz 145 root txt VREG 0,81 189172 50770 /libexec/ld-elf.so.1 adjkerntz 145 root txt VREG 0,81 1067248 50739 /lib/libc.so.7 devd 487 root cwd VDIR 0,81 512 2 / devd 487 root rtd VDIR 0,81 512 2 / devd 487 root txt VREG 0,81 369684 32969 /sbin/devd syslogd564 root cwd VDIR 0,81 512 2 / syslogd564 root rtd VDIR 0,81 512 2 / syslogd564 root txt VREG 0,81 189172 50770 /libexec/ld-elf.so.1 syslogd564 root txt VREG 0,8155240 50747 /lib/libutil.so.7 syslogd564 root txt VREG 0,81 1067248 50739 /lib/libc.so.7 rpcbind650 root cwd VDIR 0,81 512 2 / rpcbind650 root rtd VDIR 0,81 512 2 / rpcbind650 root txt VREG 0,81 189172 50770 /libexec/ld-elf.so.1 rpcbind650 root txt VREG 0,8155240 50747 /lib/libutil.so.7 rpcbind650 root txt VREG 0,81 1067248 50739 /lib/libc.so.7 snmpd 690 root cwd VDIR 0,81 512 2 / snmpd 690 root rtd VDIR 0,81 512 2 / snmpd 690 root txt VREG 0,81 189172 50770 /libexec/ld-elf.so.1 snmpd 690 root txt VREG 0,8132024 50740 /lib/libcrypt.so.4 snmpd 690 root txt VREG 0,8155240 50747 /lib/libutil.so.7 snmpd 690 root txt VREG 0,8192720 50743 /lib/libm.so.5 snmpd 690 root txt VREG 0,8129916 50741 /lib/libkvm.so.4 snmpd 690 root txt VREG 0,8118788 50761 /lib/libdevstat.so.6 snmpd 690 root txt VREG 0,81 1417668 50595 /lib/libcrypto.so.5 snmpd 690 root txt VREG 0,81 1067248 50739 /lib/libc.so.7 sh 751 mysql cwd VDIR 0,81 512 2 / sh 751 mysql rtd VDIR 0,81 512 2 / sh 751 mysql txt VREG 0,81 115388 33069 /bin/sh sh 751 mysql txt VREG 0,81 189172 50770 /libexec/ld-elf.so.1 sh 751 mysql txt VREG 0,8188492 50751 /lib/libedit.so.6 sh 751 mysql txt VREG 0,81 261484 50738 /lib/libncurses.so.7 sh 751 mysql txt VREG 0,81 1067248 50739 /lib/libc.so.7 mysqld 800 mysql rtd VDIR 0,81 512 2 / mysqld 800 mysql txt VREG 0,81 189172 50770 /libexec/ld-elf.so.1 mysqld 800 mysql txt VREG 0,8164300 49385 /lib/libz.so.3 mysqld 800 mysql txt VREG 0,8128768 58494 /lib/libcrypt.so.3 mysqld 800 mysql txt VREG 0,8195120 49378 /lib
Re: / file system is full, but du does not show that it's full
On 06/01/2011 11:26, c0re wrote: > # df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ad0s1a496M466M -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: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: / file system is full, but du does not show that it's full
What about filehandlers? On Jan 6, 2011, at 5:26 AM, c0re wrote: > # df -h > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ad0s1a496M466M -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/ > > > I know that something (like running process) can hold file so it's > actually are not deleted. I rebooted server. But this not helped, so > it's not a process holding file. > > Checked with fsck > > # fsck / > ** /dev/ad0s1a (NO WRITE) > ** Last Mounted on / > ** Root file system > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 47268 files, 238539 used, 15276 free (6684 frags, 1074 blocks, 2.6% > fragmentation) > > No problems here. > > > # uname -a > FreeBSD host.domain.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #0: Tue > Dec 28 13:55:47 MSK 2010 > r...@host.domain.com:/usr/obj/usr/src/sys/MYKERNEL i386 > > What's the problem here? Why df says that filesystem is full? Other > command may also say that can't write because file system is full. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
/ file system is full, but du does not show that it's full
# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M466M -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/ I know that something (like running process) can hold file so it's actually are not deleted. I rebooted server. But this not helped, so it's not a process holding file. Checked with fsck # fsck / ** /dev/ad0s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 47268 files, 238539 used, 15276 free (6684 frags, 1074 blocks, 2.6% fragmentation) No problems here. # uname -a FreeBSD host.domain.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #0: Tue Dec 28 13:55:47 MSK 2010 r...@host.domain.com:/usr/obj/usr/src/sys/MYKERNEL i386 What's the problem here? Why df says that filesystem is full? Other command may also say that can't write because file system is full. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
