Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Jun 2008 12:53:46 -0500
From:      Paul Schmehl <pschmehl_lists@tx.rr.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: /var full
Message-ID:  <421A1EE3E8C305AD72BBA2BE@utd65257.utdallas.edu>
In-Reply-To: <A42873E7-6DCB-4F55-AC79-C14353880E7D@goldmark.org>
References:  <EA09BDBE04BB7B81413DB590@Macintosh.local> <20080619035949.GB8205@shepherd>	<DB82314EA03D57CB11849EA5@Macintosh.local> <4859FC8F.5020308@ibctech.ca>	<BBBB9169909ADCA813DB44EE@utd65257.utdallas.edu> <A42873E7-6DCB-4F55-AC79-C14353880E7D@goldmark.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--On Thursday, June 19, 2008 11:09:57 -0500 Jeffrey Goldberg 
<jeffrey@goldmark.org> wrote:

> On Jun 19, 2008, at 9:40 AM, Paul Schmehl wrote:
>
>> As you can see from the df -i I posted (to which you responded),
>> inode exhaustion is not an issue.
>
> You are probably right about that, but could you also post the result of
>
>   sudo tunefs -p /var

# tunefs -p /var
tunefs: ACLs: (-a)                                         disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: gjournal: (-J)                                     disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  2048
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             8%
tunefs: optimization preference: (-o)                      time
tunefs: volume label: (-L)

>
> That won't tell us what is in use, but it will confirm whether /var was set
> up with funky parameters or not.  Also, the last time I ran out of inodes,
> the error messages made it clear that that was what was happening instead of
> merely giving a disk full error.
>
>>  I'm leaning toward some sort of bug in mysql version 5.0.51 which
>> creates a temporary file (in the wrong place) and then doesn't
>> release it until it exhausts the space on the drive.  In any case,
>> I'm going to report it to the mysql folks as such and hope they can
>> figure out what the cause is.
>
> That would be my guess.  I haven't seen a mention of that of the mysql lists,
> but I don't follow the lists closely.   (For the most part, I just go and
> clean out the mail folder they collect in every week or so.)
>

I looked all over their website and didn't see a place or an email address to 
submit bug reports unless you're an enterprise customer.

-- 
Paul Schmehl
As if it wasn't already obvious,
my opinions are my own and not
those of my employer.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?421A1EE3E8C305AD72BBA2BE>