Re: /var/mail fills up

From: Hokan (hokan_at_hokan.org)
Date: 01/03/05


Date: 03 Jan 2005 19:22:23 GMT

On Mon, 03 Jan 2005 18:35:05 GMT, Bill Vermillion <bv@wjv.com> wrote:
> In article <slrncth1sa.2r0j.hokan@hokan.org>, Hokan <hokan@hokan.org> wrote:
>>Every few months /var/mail fills up.
>
>>Oddly, there are no files to account for this filling. df reports
>>all of my 32GB drive is full, du reports that only 16BG are used.
>
>>The only things that can update this drive are the mail servers,
>>sendmail, imap-uw, and qpopper (though it is NFS exported
>>read-only). When this problem occurs, I shut down all mail
>>services.
>
>>fstat and lsoft both tell me no files are open on that file system.
>
>>After reboot the file system is back to normal: du and df agree
>>on space used.
>
>>What is happening? How can I debug this issue?
>
> You don't have some programming removing log files that are open do
> you? If so those files will remain until everything that uses
> them closes. There will be no directory entries but the space will
> still be used.
>
> Have you tried an 'fsck' on the partition. Running fsck in a
> mounted system will not change the file system, but it might give
> you some hints.
>
> You might unmount /var and then run fsck.
>
> You really should never have to reboot a Unix system, if all your
> programs behave themselves and you don't do something that is
> not prudent.

This isn't /var, but /var/mail on a separate file system on a
separate drive. No log files, nothing but inboxes (and those
dot files that qpopper creates).

I have not tried fsck. The next time this happens I will do that.

I cannot unmount /var/mail, the system claims it's in use.
By what? I donno.

I agree I shouldn't have to reboot this thing, but couldn't otherwise
fix the problem.



Relevant Pages

  • Re: Printer not working after a short circuit
    ... > system will reboot when you leave the shell. ... Give root password for maintenance or type Control-D to ... Run fsck manually. ... > entire file system and prompted me as to whether or not to continue. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Printer not working after a short circuit
    ... > the system will reboot when you leave the shell. ... > I typed Control-D and the system went to reboot, ... Run fsck manually. ... > entire file system and prompted me as to whether or not to continue. ...
    (microsoft.public.windowsxp.hardware)
  • Re: HELP! Linux 911... (fsck/HDD failure)
    ... It means you have a bad boo boo and need to fix your owie. ... | /dev/hda3 contains file system with errors, ... UNEXPECTED INCONSISTENCY; Run fsck MANUALLY. ... Please repair manually and reboot. ...
    (alt.os.linux.suse)
  • Re: HELP! Linux 911... (fsck/HDD failure)
    ... It means you have a bad boo boo and need to fix your owie. ... | /dev/hda3 contains file system with errors, ... UNEXPECTED INCONSISTENCY; Run fsck MANUALLY. ... Please repair manually and reboot. ...
    (alt.linux)
  • RE: serioup problem after running fsck
    ... I'm not an expert in recovery and I'm not sure you could recover at ... > The easiest and first thing is to run fsck again (although I ... Running it once is no guarantee that the file system ... > shutdown command from the command line or the shutdown menu ...
    (RedHat)