On Wed, 12 Nov 2008, Ivan Voras wrote:
I don't know for sure, but here's some generic troubleshooting:
a) Are you 100% sure there isn't an application that periodically fills the
drive? This would be easiest to solve - all other problems are worse.
Yes, I'm sure, anyways there is about 40G free space now on that drive and
it's not so easy to suddenly fill it up
b) How is your IO rate at the time you run out of space?
Nothing ususial, except I just noticed that at any time, not just when the
problem arises, the %slo-z value is about 97-99%. May be it has nothing
to do with this problem, but on other similar servers it's not that high.
c) Did you try fsck-ing the file system?
Last time two weeks ago the server was rebooted ungracefully and fsck'd in
foreground (it has background_fsck="NO"). After that, I didn't have a
possibility yet to reboot it in single-user. If I could do it remotely it
would help but there is no KVM or anything there. Honestly I'm a bit
afraid of doing "kill -1 1" or "reboot -qn".
d) Why can't you upgrade to a more recent version of FreeBSD, like 7.1?
The server is in production and there is no other server to substitute it
during the downtime.
----
Alexander Varshavchick, Metrocom Joint Stock Company
Phone: (812)718-3322, 718-3115(fax)
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
