Not that this is probably your problem, but I notice that even after I clear off hd
space, often it takes a while for it to register that fact. Umounting or rebooting
(doing the same thing) generally seems to clear it up. I just chalked it up to the
large degree that Linux caches HD changes.
On Wed, 27 Nov 2002 22:58:49 -0600
RBE [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 27 November 2002 12:29 pm, Alan Jackson wrote:
You know, I've been using Unix and/or Linux for 14 years, and I just
learned something. Thank you guys!!
After
On Tue, Nov 26, 2002 at 08:56:26PM -0600, Alan Jackson wrote:
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had cleared space a few days ago, and then it filled up
again, when I found and killed the gvim zombie. I get quite different
answers
On Wed, 27 Nov 2002 [EMAIL PROTECTED] wrote:
On Tue, Nov 26, 2002 at 08:56:26PM -0600, Alan Jackson wrote:
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had cleared space a few days ago, and then it filled up
again, when I found and killed
No. I guess I could
On Wed, 27 Nov 2002 01:04:48 -0600
RBE [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have you tried umount /dev/hdb1 and running fsck on it?
On Tuesday 26 November 2002 10:21 pm, Alan Jackson wrote:
I did. (I'm the only user). But that's
On Wed, 27 Nov 2002 09:48:46 -0500 (EST)
Net Llama! [EMAIL PROTECTED] wrote:
On Wed, 27 Nov 2002 [EMAIL PROTECTED] wrote:
On Tue, Nov 26, 2002 at 08:56:26PM -0600, Alan Jackson wrote:
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had
You know, I've been using Unix and/or Linux for 14 years, and I just learned
something. Thank you guys!!
After reading everything, I decided I probably needed to fsck at minimum, so
I just rebooted. Turned out the fsck ran automatically, the disk was corrupted,
and now, instead of 100% full at 36
On Wed, Nov 27, 2002 at 12:29:22PM -0600, Alan Jackson wrote:
You know, I've been using Unix and/or Linux for 14 years, and I just learned
something. Thank you guys!!
After reading everything, I decided I probably needed to fsck at minimum, so
I just rebooted. Turned out the fsck ran
On 11/27/02 10:29, Alan Jackson wrote:
You know, I've been using Unix and/or Linux for 14 years, and I just learned
something. Thank you guys!!
After reading everything, I decided I probably needed to fsck at minimum, so
I just rebooted. Turned out the fsck ran automatically, the disk was
Well, I think uptime is over rated as a system quality measure in
any event.
We run a slew of Solaris servers and rebooting seems to clean up
a lot of little annoyances. I'm of the opinion that most systems
regardless of OS should be restarted on a regular basis, say
monthly. Of course some of
Care to elaborate on what kinds of annoyances get cleared up by rebooting?
On 11/27/02 18:08, Jack Berger wrote:
Well, I think uptime is over rated as a system quality measure in
any event.
We run a slew of Solaris servers and rebooting seems to clean up
a lot of little annoyances. I'm of the
On Wed, Nov 27, 2002 at 06:22:02PM -0800, Net Llama! wrote:
Care to elaborate on what kinds of annoyances get cleared up by rebooting?
Memory leaks.
Kurt
--
Here at the Phone Company, we serve all kinds of people; from
Presidents and Kings to the scum of the earth ...
It also cleans various cache areas. Removes orphaned processes.
Cleans up lost files (large and small) which may be left over
from killed processes. Fixes stale NFS mounts (probably related
to cache area problems),
Nothing serious or show stoppers, but it does tend to tidy things
up and make
Simpler than doing it by itself. That and in case the offending process
was still hanging out - which it may have been. The system had trouble
unmounting /home as it was. It probably cleaned up a few stray zombies
and other trash as well.
On Wed, 27 Nov 2002 16:52:20 -0800
Net Llama! [EMAIL
On Wed, 27 Nov 2002 21:26:24 -0500 [EMAIL PROTECTED] wrote:
On Wed, Nov 27, 2002 at 06:22:02PM -0800, Net Llama! wrote:
Care to elaborate on what kinds of annoyances get cleared up by
rebooting?
Memory leaks.
Stale file handles for NFS appear to be the biggest requirement for
reboot on
And a host of other niggling little things users and applications
do to an otherwise pristine system. ;)
From: [EMAIL PROTECTED]
On Wed, Nov 27, 2002 at 06:22:02PM -0800, Net Llama! wrote:
Care to elaborate on what kinds of annoyances get cleared up by rebooting?
Memory leaks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 27 November 2002 12:29 pm, Alan Jackson wrote:
You know, I've been using Unix and/or Linux for 14 years, and I just
learned something. Thank you guys!!
After reading everything, I decided I probably needed to fsck at
minimum, so I
On 11/27/02 20:58, RBE wrote:
On Wednesday 27 November 2002 12:29 pm, Alan Jackson wrote:
You know, I've been using Unix and/or Linux for 14 years, and I just
learned something. Thank you guys!!
After reading everything, I decided I probably needed to fsck at
minimum, so I just rebooted.
That's the most reliable, and in some cases the only method of
resolving these. If anyone has a better way, I'd be glad to hear
it.
Sometimes stopping/starting rpc, nfs client and server, cachefs,
and automounter clears it. But a reboot is the surest solution.
-jhb-
From: Collins [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 27 November 2002 11:16 pm, Net Llama! wrote:
On 11/27/02 20:58, RBE wrote:
On Wednesday 27 November 2002 12:29 pm, Alan Jackson wrote:
You know, I've been using Unix and/or Linux for 14 years, and I
just learned something. Thank you
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had cleared space a few days ago, and then it filled up
again, when I found and killed the gvim zombie. I get quite different
answers from different tools as well :
df tells me I've used 36 Gbytes,
Well, i'd assume that it filled up the diskspace of the user $HOME that
was running it. So, why not run 'du -m' on that user's $HOME?
On 11/26/02 18:56, Alan Jackson wrote:
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had cleared space a few
I did. (I'm the only user). But that's where I can't find where the space went. I even
ran a
find . -type f -ls
and summed up the numbers in perl. Still only get 6 Gbytes of files on a full 36 Gbyte
disk...
On Tue, 26 Nov 2002 19:04:53 -0800
Net Llama! [EMAIL PROTECTED] wrote:
Well, i'd
I had a very similar problem to yours. Here is my problem and solution
from some months ago.
===Old Problem letter===
My / partition is filled, but the amount of data in it is minimal, to wit:
/dev/hda1 3.7G 3.6G 0 100% /
/dev/hda3
On 11/26/02 18:56, Alan Jackson wrote:
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had cleared space a few days ago, and then it filled up
again, when I found and killed the gvim zombie. I get quite different
answers from different tools as
On Tue, Nov 26, 2002 at 08:56:26PM -0600, Alan Jackson wrote:
I'm at my wit's end. A runaway vim process filled up my disk, and I can't
figure out *where*. I had cleared space a few days ago, and then it filled up
again, when I found and killed the gvim zombie. I get quite different
answers from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have you tried umount /dev/hdb1 and running fsck on it?
On Tuesday 26 November 2002 10:21 pm, Alan Jackson wrote:
I did. (I'm the only user). But that's where I can't find where the
space went. I even ran a find . -type f -ls
and summed up the
27 matches
Mail list logo
