Re: var Filesystem Full Help
Derek Ragona wrote: I would reboot and run fsck in single user mode. The reboot will clear any old open files that may be causing the drive full problem. -Derek At 11:59 AM 4/3/2007, Sean Murphy wrote: Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Purge some old log files to start with. However according to your df above you should have plenty of room I have deleted logs and lost+found but the same messages still show up. Check df -i as you may have run out of inodes rather than out of file space. Looks as though I have plenty of inodes muse2# df -i Filesystem1K-blocksUsed Avail Capacity iusedifree %iused Mounted on /dev/amrd0s1a 1012974 57694874244 6%1520 139790 1% / devfs 1 1 0 100% 00 100% /dev /dev/amrd0s1e 1012974 33192898746 4% 11141 130169 8% /tmp /dev/amrd0s1f 9938894 4368142 477564248% 279371 1015987 22% /usr /dev/amrd0s1g 257098734 9794488 226736348 4% 113153 33118717 0% /usr/home /dev/amrd0s1d 2026030 510498 135345027% 866 281756 0% /var muse2# Have you rebooted since the problem showed up? I have not rebooted yet can I fun fsck on a live filesystem or do I have to drop into single usermode? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. I ran the # fstat -f /var and compared it to the # find /var -inum n -print command. I found mysqld httpd mimedefang syslogd all had processes open but not written the files to /var. I ended up rebooting into single user mode and running fsck -f -y /var twice just to make sure it was clean. There were many errors on /var reported and fixed by fsck. here is my new output of df -h muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 23M888M 2%/tmp /dev/amrd0s1f9.5G4.2G4.5G48%/usr /dev/amrd0s1g245G9.3G216G 4%/usr/home /dev/amrd0s1d1.9G357M1.4G20%/var muse2# /var is smaller now it was /dev/amrd0s1d1.9G526M1.3G29%/var also the current inode count muse2# df -i Filesystem1K-blocksUsed Avail Capacity iusedifree %iused Mounted on /dev/amrd0s1a 1012974 57762874176 6%1524 1397861% / devfs 1 1 0 100% 00 100% /dev /dev/amrd0s1e 1012974 23064908874 2% 11481 129829 8% /tmp /dev/amrd0s1f 9938894 4376480 476730448% 279523 1015835 22% /usr /dev/amrd0s1g 257098734 9763632 226767204 4% 114302 33117568 0% /usr/home /dev/amrd0s1d 2026030 365632 149831620% 12198 270424 4% /var muse2# it was /dev/amrd0s1d 2026030 510498 135345027% 866 281756 0% /var the 0% is interesting why would it report 0% when it was having problems? Thanks for all your help and advice. The system seems stable now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
var Filesystem Full Help
I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
Run fsck on /var also check that /var doesn't exist elseware like from a symbolic link. -Derek At 11:18 AM 4/3/2007, Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
On Apr 3, 2007, at 12:18 PM, Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? ___ Purge some old log files to start with. However according to your df above you should have plenty of room. Cheers, m ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. Check df -i as you may have run out of inodes rather than out of file space. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
On Tue, Apr 03, 2007 at 09:18:29AM -0700, Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? The first thing that comes to mind is that some process created some huge file[s] and then unlinked it[them], but has not actually ended and released the space. But, that is an awfully lot of space to be held on to that way. Have you rebooted since the problem showed up? jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
lsof is your friend Alex Zbyslaw wrote: Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. Check df -i as you may have run out of inodes rather than out of file space. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
Alex Zbyslaw wrote: Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. Check df -i as you may have run out of inodes rather than out of file space. Also, try working with fstat(1) to see if the offending superbig file is active but not yet written (and therefore visible to df(1)) and try du(1), because it may also show you the offending file. Kevin Kinsey -- Baruch's Observation: If all you have is a hammer, everything looks like a nail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Purge some old log files to start with. However according to your df above you should have plenty of room I have deleted logs and lost+found but the same messages still show up. Check df -i as you may have run out of inodes rather than out of file space. Looks as though I have plenty of inodes muse2# df -i Filesystem1K-blocksUsed Avail Capacity iusedifree %iused Mounted on /dev/amrd0s1a 1012974 57694874244 6%1520 1397901% / devfs 1 1 0 100% 00 100% /dev /dev/amrd0s1e 1012974 33192898746 4% 11141 130169 8% /tmp /dev/amrd0s1f 9938894 4368142 477564248% 279371 1015987 22% /usr /dev/amrd0s1g 257098734 9794488 226736348 4% 113153 33118717 0% /usr/home /dev/amrd0s1d 2026030 510498 135345027% 866 281756 0% /var muse2# Have you rebooted since the problem showed up? I have not rebooted yet can I fun fsck on a live filesystem or do I have to drop into single usermode? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
On Tuesday 03 April 2007 09:18:29 Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? take a look at /tmp my guess is you havea number of ancient large files you need to either delete or transfer to somewhere else. David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? There are two reasons why a filesystem may give 'out of space' errors when df(1) still shows plenty of space available. i) Out of inodes. You can tell this by running 'df -i'. You're unlikely to run into this unless either you used non-standard settings when you newfs'd the partition or else the partition is full of a very large number of very files. If this is the case, then apart from rampantly deleting lots of stuff the only solution is to backup the filesystem somewhere, recreate the filesystem by running newfs with a more realistic set of parameters (bytes-per-inode should be smaller) and then recover the data from backup. ii) Open file descriptor on an unlinked file. This is much more likely to be the problem with the /var partition, seeing as it's a favourite place for log files. What can happen is this: a process has a file open (ie. it has an open file descriptor on the data) but a second process comes along and unlinks the original file. That means that the file name and other meta data are removed from the directory contents, but since another process has the file open, the space taken up by the files' data is not returned to the generally available pool. Sounds daft at first, but that's the way Unix has worked since the epoch and if you think about it, it makes sense really. Doing that deliberately can be exceedingly useful -- a program can reserve itself some scratch space that can't be accessed or altered by anything else[*] What tends to happen in /var is a side effect of not rotating log files correctly. newsyslog(8) and pals will move aside and compress an existing log file very happily, then they will send a signal to the program generating the log file (by default assumed to be syslogd) to tell it to close and reopen any files it is logging to -- it's a common behaviour for Unix daemons to understand a SIGHUP to mean 'reinitialise yourself and reopen any files you're using' If newsyslog(8) signals the wrong process, or doesn't signal any process at all, or the process doesn't grok the SIGHUP, then you'll find you get exactly the sort of orphaned file with an open descriptor on it as described above. The way to debug this is to list all of the processes that have open descriptors on the partition: # fstat -f /var then it's a case of doing some detective work to try and identify which out of the many processes listed is the culprit. Unfortunately fstat(1) doesn't tell you file names -- instead you get the files inode number as column 6 of the output. There is no generic method of mapping from inode number to filename (indeed, orphaned files like we've been discussing have an inode number, but *no* filename); other than by doing exhaustive searches using eg. find(1): # find /var -inum n -print In this case you're looking for the ones that don't return an answer. Cheers, Matthew [*] Well, not without rootly powers, ample clue and a reasonable expenditure of effort. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: var Filesystem Full Help
Noah wrote: Alex Zbyslaw wrote: Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. Check df -i as you may have run out of inodes rather than out of file space. lsof is your friend First of all, please don't top-post. Second of all, I'm not the original poster so sending the email To: me isn't that helpful. Third of all, and most important, open files are irrelevant. The OP was using df. df counts free blocks in the file system. Files which are open and then deleted do not free their blocks and do not show up as free blocks in df. If the original command had been du, which traverses the file system to count usage and therefore can't count a file which has been deleted but is still open, then lsof might be useful. In this case it is not. A simple experiment to see this: 1) df /var Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad10s1e 5077038 116682 4554194 2%/var 2) Create a big file dd if=/dev/zero of=/var/tmp/HUGE bs=1m count=100 df /var Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad10s1e 5077038 219162 4451714 5%/var 3) Hold the file open; delete it; repeat df perl -e 'open(X, /var/tmp/HUGE); sleep 30;' rm /var/tmp/HUGE remove /var/tmp/HUGE? y df /var Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad10s1e 5077038 219162 4451714 5%/var 4) Wait for open process to finish; repeat df [1]Done perl -e open(X, /var/tmp/HUGE); sleep 30; df /var Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad10s1e 5077038 116682 4554194 2%/var The available disk space start at 4554194, drops to 4451714 when the file is created, and *remains like that* until the process holding the file open exits, thus freeing the last reference and allowing the blocks to be freed. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
Sean Murphy wrote: Check df -i as you may have run out of inodes rather than out of file space. Looks as though I have plenty of inodes muse2# df -i Filesystem1K-blocksUsed Avail Capacity iusedifree %iused Mounted on /dev/amrd0s1a 1012974 57694874244 6%1520 139790 1% / devfs 1 1 0 100% 00 100% /dev /dev/amrd0s1e 1012974 33192898746 4% 11141 130169 8% /tmp /dev/amrd0s1f 9938894 4368142 477564248% 279371 1015987 22% /usr /dev/amrd0s1g 257098734 9794488 226736348 4% 113153 33118717 0% /usr/home /dev/amrd0s1d 2026030 510498 135345027% 866 281756 0% /var muse2# [...] Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full I've no idea what mimedefang does. Is it possible it is trying to create a file which is larger than your available disk space? If it did that then deleted the offending file, then df would look normal except at the point where mimedefang was creating the enormous file. If it happens frequently, then you could just run df in a loop and read back through for tcsh while (1) df -h echo sleep 1 end Hit ^C when you've seen enough. You could redirect df and echo e.g. /tmp/DF to put output in a file or even | tee -a /tmp/DF to put to a file and see on screen. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: var Filesystem Full Help
--On Tuesday, April 03, 2007 18:12:09 +0100 Alex Zbyslaw [EMAIL PROTECTED] wrote: The available disk space start at 4554194, drops to 4451714 when the file is created, and *remains like that* until the process holding the file open exits, thus freeing the last reference and allowing the blocks to be freed. When I read the OP's post, I was going to respond. Then I read Matthew's and Alex' responses, and I knew the answer had been properly given. It's guys like Matthew and Alex that make this list invaluable, and I want to thank both of you for your thorough and accurate answers. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: var Filesystem Full Help
I would reboot and run fsck in single user mode. The reboot will clear any old open files that may be causing the drive full problem. -Derek At 11:59 AM 4/3/2007, Sean Murphy wrote: Sean Murphy wrote: I am getting these errors on my var filesystem but df -h shows there is plenty of space available. I am running FreeBSD 5.4 muse2# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/amrd0s1a989M 56M854M 6%/ devfs1.0K1.0K 0B 100%/dev /dev/amrd0s1e989M 32M878M 4%/tmp /dev/amrd0s1f9.5G4.2G4.6G48%/usr /dev/amrd0s1g245G9.4G216G 4%/usr/home /dev/amrd0s1d1.9G526M1.3G29%/var muse2# tail /var/log/messages Apr 3 09:00:44 muse2 kernel: pid 537 (mimedefang), uid 26 inumber 126291 on /var: filesystem full Apr 3 09:09:55 muse2 kernel: pid 52000 (httpd), uid 80 inumber 170037 on /var: filesystem full Apr 3 09:12:59 muse2 kernel: pid 34758 (mimedefang), uid 26 inumber 127701 on /var: filesystem full I have restarted the mimdefang process but I get the same messages. What can I do? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Purge some old log files to start with. However according to your df above you should have plenty of room I have deleted logs and lost+found but the same messages still show up. Check df -i as you may have run out of inodes rather than out of file space. Looks as though I have plenty of inodes muse2# df -i Filesystem1K-blocksUsed Avail Capacity iusedifree %iused Mounted on /dev/amrd0s1a 1012974 57694874244 6%1520 1397901% / devfs 1 1 0 100% 00 100% /dev /dev/amrd0s1e 1012974 33192898746 4% 11141 130169 8% /tmp /dev/amrd0s1f 9938894 4368142 477564248% 279371 1015987 22% /usr /dev/amrd0s1g 257098734 9794488 226736348 4% 113153 33118717 0% /usr/home /dev/amrd0s1d 2026030 510498 135345027% 866 281756 0% /var muse2# Have you rebooted since the problem showed up? I have not rebooted yet can I fun fsck on a live filesystem or do I have to drop into single usermode? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
