FreeBSD 8.2, sec.update -p3, switching between X and console prompt, /var full

2011-10-03 Thread n dhert
Hi, I have FreeBSD amd64, 8.2-RELEASE, I just applied the securtiy update p3 and now have $ uname -r 8.2-RELEASE-p3 I have X running and KDE, My machine is a virtual machine (Vmware) After boot-up I got a graphical login window (as always), I wanted to switch to a console prompt, so hit

Re: FreeBSD 8.2, sec.update -p3, switching between X and console prompt, /var full

2011-10-03 Thread Damien Fleuriot
On 10/3/11 1:54 PM, n dhert wrote: Hi, I have FreeBSD amd64, 8.2-RELEASE, I just applied the securtiy update p3 and now have $ uname -r 8.2-RELEASE-p3 I have X running and KDE, My machine is a virtual machine (Vmware) After boot-up I got a graphical login window (as always), I wanted

Fwd: FreeBSD 8.2, sec.update -p3, switching between X and console prompt, /var full

2011-10-03 Thread n dhert
I tried Ctrl-Alt-Backspace in the graphical login wndow, but as with other key Ctrl-Alt key combinations this does not do anything ... I there a commadn line way to restart X I also tried fsck-ing the /var/ file system, but it chooses NO WRITE nothing is repaired See the last UNREF FILE, it has

Re: Fwd: FreeBSD 8.2, sec.update -p3, switching between X and console prompt, /var full

2011-10-03 Thread Polytropon
On Mon, 3 Oct 2011 15:15:26 +0200, n dhert wrote: I tried Ctrl-Alt-Backspace in the graphical login wndow, but as with other key Ctrl-Alt key combinations this does not do anything ... It is new behaviour that certain default functionalities of X need to be enabled manually. Ctrl+Alt+Backspace

Re: Fwd: FreeBSD 8.2, sec.update -p3, switching between X and console prompt, /var full

2011-10-03 Thread n dhert
I tried # ps -jaxw | grep X root7609 1461 7609 11 S ??0:00.55 /usr/local/bin/X -br -nolisten tcp :0 -auth /var/run/xauth/A:0-9mN8YK ( root7633 3423 7632 33562 S+ 50:00.06 grep X # kill -9 7609 but it creates a new one ... # ps -jawx | grep X root

Re: /var full

2008-06-19 Thread Steve Bertrand
Paul Schmehl wrote: --On June 18, 2008 11:59:49 PM -0400 Sahil Tandon [EMAIL PROTECTED] wrote: Also, what is the output of 'df -i /var'? # df -i /var/ Filesystem 1K-blocksUsed Avail Capacity iusedifree %iused Mounted on /dev/da1s1d 283737842 5397568 255641248 2% 20350

Re: /var full

2008-06-19 Thread Robert Huff
Steve Bertrand writes: I am not in any which way certain changing major revision numbers will affect the file system in any which way. I am also not very knowledgeable in regards to inodes, but I do know that they can run out before disk space does. It is my understanding that

Re: /var full

2008-06-19 Thread Steve Bertrand
Steve Bertrand writes: I am not in any which way certain changing major revision numbers will affect the file system in any which way. I am also not very knowledgeable in regards to inodes, but I do know that they can run out before disk space does. It is my understanding that

Re: /var full

2008-06-19 Thread Paul Schmehl
--On Thursday, June 19, 2008 02:28:31 -0400 Steve Bertrand [EMAIL PROTECTED] wrote: Paul Schmehl wrote: --On June 18, 2008 11:59:49 PM -0400 Sahil Tandon [EMAIL PROTECTED] wrote: Also, what is the output of 'df -i /var'? # df -i /var/ Filesystem 1K-blocksUsed Avail Capacity

Re: /var full

2008-06-19 Thread Jeffrey Goldberg
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 That won't tell us what is in use, but it will

Re: /var full

2008-06-19 Thread Paul Schmehl
--On Thursday, June 19, 2008 11:09:57 -0500 Jeffrey Goldberg [EMAIL PROTECTED] 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

Re: /var full

2008-06-19 Thread Peter Boosten
Paul Schmehl wrote: 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

Re: /var full

2008-06-19 Thread Paul Schmehl
--On Thursday, June 19, 2008 20:02:59 +0200 Peter Boosten [EMAIL PROTECTED] wrote: Paul Schmehl wrote: 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

Re: /var full

2008-06-19 Thread Peter Boosten
Paul Schmehl wrote: --On Thursday, June 19, 2008 20:02:59 +0200 Peter Boosten [EMAIL PROTECTED] wrote: Paul Schmehl wrote: 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

/var full

2008-06-18 Thread Paul Schmehl
At 10PM (local time) this evening, a server started reporting that /var was full. When I ssh'd in to the server to investigate, df said /var was at 2% full (5.1G) and dh reported the same (5.1G). /var/log/dmesg.today is full of messages listing multiple entries with the same inode number

Re: /var full

2008-06-18 Thread Sahil Tandon
Paul Schmehl [EMAIL PROTECTED] wrote: At 10PM (local time) this evening, a server started reporting that /var was full. When I ssh'd in to the server to investigate, df said /var was at 2% full (5.1G) and dh reported the same (5.1G). /var/log/dmesg.today is full of messages listing

Re: /var full

2008-06-18 Thread Paul Schmehl
--On June 18, 2008 10:45:57 PM -0500 Paul Schmehl [EMAIL PROTECTED] wrote: Why would toor be running dd? Is it some sort of file recovery routine triggered by filesystem full messages? Sheesh - that's operator, not toor, of course. Paul Schmehl If it isn't already obvious, my opinions are

Re: /var full

2008-06-18 Thread Paul Schmehl
--On June 18, 2008 11:59:49 PM -0400 Sahil Tandon [EMAIL PROTECTED] wrote: Paul Schmehl [EMAIL PROTECTED] wrote: At 10PM (local time) this evening, a server started reporting that /var was full. When I ssh'd in to the server to investigate, df said /var was at 2% full (5.1G) and dh

/var Full

2005-02-07 Thread Warren
im trying to get cacti working, but since im using a small P2 300 machine with a small hdd my /var has suddenly become full and im wodering what is safe and not safe so to speak to del in the /var dir .. the following are the dir's i have. drwxr-xr-x 2 rootwheel 512 Feb 24 2004

Re: /var Full

2005-02-07 Thread albi
Warren wrote: im trying to get cacti working, but since im using a small P2 300 machine with a small hdd my /var has suddenly become full and im wodering what is safe and not safe so to speak to del in the /var dir .. the following are the dir's i have. --- cut drwxr-xr-x 2 rootwheel

Re: /var Full

2005-02-07 Thread Warren
On Mon, 7 Feb 2005 11:20 pm, albi wrote: Warren wrote: im trying to get cacti working, but since im using a small P2 300 machine with a small hdd my /var has suddenly become full and im wodering what is safe and not safe so to speak to del in the /var dir .. the following are the dir's i

Re: /var Full

2005-02-07 Thread albi
Warren wrote: Sadly neither the log dir nor mail had much in it since they where the 1st 2 i also thought of. what about /var/tmp ? also, a du -h /var might help ___ freebsd-questions@freebsd.org mailing list

Re: /var Full

2005-02-07 Thread Warren
On Mon, 7 Feb 2005 11:34 pm, albi wrote: Warren wrote: Sadly neither the log dir nor mail had much in it since they where the 1st 2 i also thought of. what about /var/tmp ? also, a du -h /var might help awesome .. i was wondering about a command to list the stuff inthe individual dir's

Re: /var Full

2005-02-07 Thread Erik Norgaard
Warren wrote: im trying to get cacti working, but since im using a small P2 300 machine with a small hdd my /var has suddenly become full and im wodering what is safe and not safe so to speak to del in the /var dir .. the following are the dir's i have. drwxr-xr-x 2 rootwheel 512 Feb

Re: /var Full

2005-02-07 Thread Warren
On Tue, 8 Feb 2005 12:19 am, Erik Norgaard wrote: Warren wrote: im trying to get cacti working, but since im using a small P2 300 machine with a small hdd my /var has suddenly become full and im wodering what is safe and not safe so to speak to del in the /var dir Although you have now

Re: /var Full

2005-02-07 Thread chip
On Mon, 7 Feb 2005 22:48:41 +1000, Warren [EMAIL PROTECTED] wrote: im trying to get cacti working, but since im using a small P2 300 machine with a small hdd my /var has suddenly become full and im wodering what is safe and not safe so to speak to del in the /var dir .. the following are the

Fwd: /var Full

2005-02-07 Thread Ben Dover
that you can install lsof from /usr/ports/sysutils/lsof In my case it was as easy as killing apache and restarting it and I cleared up hundreds of MB of space. -- Forwarded message -- From: Warren [EMAIL PROTECTED] Date: Tue, 8 Feb 2005 00:24:41 +1000 Subject: Re: /var Full

Re: /var Full

2005-02-07 Thread Luyt
On Monday 07 February 2005 13:48, Warren wrote: i was wondering about a command to list the stuff inthe individual dir's and it seems some old packages that have been de-installed ahev remnets and a lot of them in the /var/db port totalling a significant amount of Meg. Thanks for the help.

Re: /var Full

2005-02-07 Thread Michael C. Shultz
On Monday 07 February 2005 10:16 pm, Luyt wrote: On Monday 07 February 2005 13:48, Warren wrote: i was wondering about a command to list the stuff inthe individual dir's and it seems some old packages that have been de-installed ahev remnets and a lot of them in the /var/db port totalling

/var Full ?

2005-01-29 Thread GRF .
I am running FBSD 5.2.1 and my /var partition is giving me cannot write to disk errors, disk is full. I cleared out what I could and got it down to about 98% but I have some strange findings which I will show below. [/var] df -h FilesystemSize Used Avail Capacity Mounted on

Re: /var Full ?

2005-01-29 Thread Lane
Hi. I don't know if this is going to be of much use, but I encountered the same problem on 5.3-STABLE only 48 hours after upgrading from 4.10. My problem was that KDE was storing more crap than the law should allow on /var/tmp My solution was to create a symbolic link from /var/tmp to

Re: /var Full ?

2005-01-29 Thread Loren M. Lang
On Sat, Jan 29, 2005 at 05:48:26PM -0500, GRF . wrote: I am running FBSD 5.2.1 and my /var partition is giving me cannot write to disk errors, disk is full. I cleared out what I could and got it down to about 98% but I have some strange findings which I will show below. [/var] df -h

Re: Phantom /var full messages

2004-09-11 Thread Paul Schmehl
--On Saturday, September 11, 2004 8:30 AM +0400 Sergey Zaharchenko [EMAIL PROTECTED] wrote: Actually, if the files in question are opened and unlinked, then they have no `name' in the filesystem and find(1) won't help you. Interesting. I did a find /var -inum {inode_num} and got the name of the

Re: Phantom /var full messages

2004-09-10 Thread Paul Schmehl
--On Friday, September 10, 2004 11:58:41 AM +0100 [EMAIL PROTECTED] wrote: I'm running snort 2.1.3 and mysql 3.23.58 on FreeBSD 4.9 RELEASE. All applications are built from ports. Periodically I get /var full messages and everything comes to a grinding halt. The problem is, /var isn't full. df

Re: Phantom /var full messages

2004-09-10 Thread Jerry McAllister
--On Friday, September 10, 2004 11:58:41 AM +0100 [EMAIL PROTECTED] wrote: I'm running snort 2.1.3 and mysql 3.23.58 on FreeBSD 4.9 RELEASE. All applications are built from ports. Periodically I get /var full messages and everything comes to a grinding halt. The problem is, /var

Re: Phantom /var full messages

2004-09-10 Thread Sergey Zaharchenko
On Fri, Sep 10, 2004 at 11:23:11AM -0400, Jerry McAllister probably wrote: No, you are running out of space! DF has nothing to do with it. If one of the processes grabs some file space and then unlinks, it is still holding/using that space and probably needs it, even if one method (df)

Re: Phantom /var full messages

2004-09-10 Thread Robert Huff
Jerry McAllister writes: If you are doing database stuff, then I can't imagine having a /var of less than a few GB, unless you move a lot of stuff out of /var and create links. I'll suggest part of the answer is to move that space off /var - possibly to a dedicated partition or

Re: Phantom /var full messages

2004-09-10 Thread Paul Schmehl
--On Friday, September 10, 2004 11:23:11 AM -0400 Jerry McAllister [EMAIL PROTECTED] wrote: How in the world would that help? (BTW, /var is 31GB) ^^^ Did you miss this? If you are doing database stuff, then I can't imagine having a /var of less than a few GB, unless you move a

Re: Phantom /var full messages

2004-09-10 Thread Sergey Zaharchenko
On Fri, Sep 10, 2004 at 11:57:57AM -0500, Paul Schmehl probably wrote: --On Friday, September 10, 2004 11:23:11 AM -0400 Jerry McAllister [EMAIL PROTECTED] wrote: If you are doing database stuff, then I can't imagine having a /var of less than a few GB, unless you move a lot of stuff out of

Re: Phantom /var full messages

2004-09-10 Thread Paul Schmehl
--On Friday, September 10, 2004 07:43:00 PM +0400 Sergey Zaharchenko [EMAIL PROTECTED] wrote: Correct. du can only show the `named' space (the size of files which are not unlinked-but-open). One of the ways to find out what has the largest files open is # fstat | grep /var | sort -r -n -k 8 |

Re: Phantom /var full messages

2004-09-10 Thread Robert Huff
Paul Schmehl writes: How do you convert the filenames from numbers to names? man find Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To

Re: Phantom /var full messages

2004-09-10 Thread Sergey Zaharchenko
On Fri, Sep 10, 2004 at 01:55:03PM -0400, Robert Huff probably wrote: Paul Schmehl writes: How do you convert the filenames from numbers to names? man find Actually, if the files in question are opened and unlinked, then they have no `name' in the filesystem and find(1) won't

Phantom /var full messages

2004-09-09 Thread Paul Schmehl
I'm running snort 2.1.3 and mysql 3.23.58 on FreeBSD 4.9 RELEASE. All applications are built from ports. Periodically I get /var full messages and everything comes to a grinding halt. The problem is, /var isn't full. df -h will show /var at 104%, but du -h /var shows /var at 40

Re: Phantom /var full messages

2004-09-09 Thread Bill Moran
Paul Schmehl [EMAIL PROTECTED] wrote: I'm running snort 2.1.3 and mysql 3.23.58 on FreeBSD 4.9 RELEASE. All applications are built from ports. Periodically I get /var full messages and everything comes to a grinding halt. The problem is, /var isn't full. df -h will show /var at 104

Re: Phantom /var full messages

2004-09-09 Thread cpghost
On Thu, Sep 09, 2004 at 11:50:36AM -0500, Paul Schmehl wrote: I'm running snort 2.1.3 and mysql 3.23.58 on FreeBSD 4.9 RELEASE. All applications are built from ports. Periodically I get /var full messages and everything comes to a grinding halt. The problem is, /var isn't full. df -h

Re: Phantom /var full messages

2004-09-09 Thread Bart Silverstrim
On Sep 9, 2004, at 1:03 PM, Bill Moran wrote: Paul Schmehl [EMAIL PROTECTED] wrote: snip I suspect this is some sort of filehandle not being released issue, but I'm not sure how to track it down. I've got lsof installed, but I'm not an expert on it yet. Any hints would be welcomed. What's

Re: Phantom /var full messages

2004-09-09 Thread Paul Schmehl
--On Thursday, September 09, 2004 05:54:16 PM +0100 Martin Hepworth [EMAIL PROTECTED] wrote: Paul who are you running du as? du will only report file sizes that it has access to. So if you don't run du as root you can get odd results... Sorry, I should have mentioned that. I'm running both df

Re: Phantom /var full messages

2004-09-09 Thread Paul Schmehl
--On Thursday, September 09, 2004 01:03:33 PM -0400 Bill Moran [EMAIL PROTECTED] wrote: Any hints would be welcomed. What's the best way to troubleshoot this problem? First, if you could isolate it to just snort or just MySQL. Typically, folks have this problem because they try to rotate log

Re: Phantom /var full messages

2004-09-09 Thread Bill Moran
Paul Schmehl [EMAIL PROTECTED] wrote: --On Thursday, September 09, 2004 01:03:33 PM -0400 Bill Moran [EMAIL PROTECTED] wrote: Any hints would be welcomed. What's the best way to troubleshoot this problem? First, if you could isolate it to just snort or just MySQL. Typically,