I am facing a problem in disk space, when I say df -h on my server, it
is giving the following results:-
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s2a 9.6G 8.5G 337M 96% /
/dev/ad2s1e 55G 39G 11G 77% /data
/dev/ad0s1e 9.6G 2.0K 8.8G 0% /data2
/dev/ad0s3e 26G 1.0G 23G 4% /data3
/dev/ad0s2e 9.6G 1.9G 6.9G 22% /usr
procfs 4.0K 4.0K 0B 100% /proc
I went into / and measured all the folders it is coming around 2GB as usable
space.
What might be the problem???
Plz give me solution as early as possible.
Suresh
To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
--
____________________________________________________
Message scanned for viruses and dangerous content by
<http://www.newnet.co.uk/av/> and believed to be clean
This would probably be better on questions@ but it is possible that you
have files on the root partition under /usr that are being hidden by the
/usr partition (or any of your other partitions). Check there's nothing
`under' your mounts.
Jamie's comment about the reserved margin is also correct, but it doesn't
account for 2GB.
Ian
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s2a 9.6G 1.0G 7.8G 12% /
/dev/ad2s1e 55G 39G 11G 77% /data
/dev/ad0s1e 9.6G 2.0K 8.8G 0% /data2
/dev/ad0s3e 26G 1.0G 23G 4% /data3
/dev/ad0s2e 9.6G 1.9G 6.9G 22% /usr
procfs 4.0K 4.0K 0B 100% /proc
What might be the problem??? In future how can I overcome this type of
problems without restarting the service.
Suresh
----- Original Message -----
From: "Maxim Konovalov" <ma...@FreeBSD.org>
To: "Naga Suresh B" <torv...@addr.com>
Sent: Thursday, October 10, 2002 3:21 PM
Subject: Re: disk running out of space
>
> Try killall -HUP syslogd
>
> On 13:49+0400, Oct 10, 2002, Naga Suresh B wrote:
>
> > Hai,
> >
> > I am facing a problem in disk space, when I say df -h on my
server, it
> > is giving the following results:-
> >
> > Filesystem Size Used Avail Capacity Mounted on
> > /dev/ad0s2a 9.6G 8.5G 337M 96% /
> > /dev/ad2s1e 55G 39G 11G 77% /data
> > /dev/ad0s1e 9.6G 2.0K 8.8G 0% /data2
> > /dev/ad0s3e 26G 1.0G 23G 4% /data3
> > /dev/ad0s2e 9.6G 1.9G 6.9G 22% /usr
> > procfs 4.0K 4.0K 0B 100% /proc
> >
> > I went into / and measured all the folders it is coming around 2GB as
usable
> > space.
> >
> > What might be the problem???
> >
> > Plz give me solution as early as possible.
> >
> > Suresh
> >
> >
> > To Unsubscribe: send mail to majo...@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
> >
>
> --
> Maxim Konovalov, ma...@FreeBSD.org
btw, why would sending syslogd a SIGHUP help just out or curiosity?
----- Original Message -----
From: "Naga Suresh B" <torv...@addr.com>
--
____________________________________________________
Message scanned for viruses and dangerous content by
<http://www.newnet.co.uk/av/> and believed to be clean
Sounds like you moved/rotated/deleted your Apache log file but Apache
still had it open and continued logging to it. The space on disk will not
be freed until everything has closed the file. Check out the rotatelogs(8)
man page that comes with Apache for information about how to properly
rotate its logs.
Ian
"When a program is using a file, and you delete the file, the file is
not really removed from the filesystem until the program stops using
it."
SIGHUP tells syslogd to reopen logfiles, apachectl restart does the
same for apache.
It's really belongs to -questions.
On 14:12+0400, Oct 10, 2002, Jamie Heckford wrote:
> hmmmm - could possibly be your log files if there going into /var
> ..... could only be explained if apache is cleaning the logs on a
> restart somehow.
>
> btw, why would sending syslogd a SIGHUP help just out or curiosity?
>
> ----- Original Message -----
> From: "Naga Suresh B" <torv...@addr.com>
> To: "Maxim Konovalov" <ma...@FreeBSD.ORG>
> Cc: <freebsd...@FreeBSD.ORG>; <freebsd...@FreeBSD.ORG>
> Sent: Thursday, October 10, 2002 11:04 AM
> Subject: Re: disk running out of space
>
>
> > Thank you for your suggestion I restarted apache on my server my df -h is
> > giving
> >
> > Filesystem Size Used Avail Capacity Mounted on
> > /dev/ad0s2a 9.6G 1.0G 7.8G 12% /
> > /dev/ad2s1e 55G 39G 11G 77% /data
> > /dev/ad0s1e 9.6G 2.0K 8.8G 0% /data2
> > /dev/ad0s3e 26G 1.0G 23G 4% /data3
> > /dev/ad0s2e 9.6G 1.9G 6.9G 22% /usr
> > procfs 4.0K 4.0K 0B 100% /proc
> >
> > What might be the problem??? In future how can I overcome this type of
> > problems without restarting the service.
> >
> > Suresh
[...]
I love picking up the simple things after I've been using FreeBSD for about 4 years :P
--
____________________________________________________
Message scanned for viruses and dangerous content by
<http://www.newnet.co.uk/av/> and believed to be clean
oh well, here, we stop all apache around 23h45, then rotate the logs (moving them into
an other directory log/cold/<IP>/) before restarting.. It take approximately 3 seconds
to stop, move and restart.. Your users shouldn't notice the stop/start..
hope this helps..
fifi..
>
> Suresh
--
Guezou Philippe philipp...@videotron.net
FreeBSD, The power to serve.
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
- Scott
Guezou Philippe(fi...@infinit.com)@2002.10.10 10:05:10 +0000:
--
Scott Nolde
GPG Key 0xD869AB48
Yep, and there's also the rotatelogs(8) utility that comes with apache,
e.g. to rotate once a week:
CustomLog "| rotatelogs /path/to/log/fileprefix 604800" combined
David