Hello SuSE'ers. Last night my 8.1 sys was running fine w/o any noticable problems. This morning the KDE desktop is littered with msgs saying "Cannot write XXX" and there is one from KDiskfree saying "dev /dev/hda3 is dangerously full" hda3 is my main ide 80GB WD drive. Last night it had 32GB FREE, but now it shows 99% full. Most things running have stopped on errors, KMail has lost it's indexes but shutdown -restart worked. Upon reboot the system reports 32GB free and after some repairs seems to be OK. /var/log/messages shows nothing ou of the ordinary. Upon reboot there was an entry: Reiserfs replayed 86 transactions in 5 seconds Using reiserfs SuSE 8.1 up to date via YOU KDE 3.0.5 SuSE 2.4.19 SMP kernel Has this happened to anyone else? Anyone able to explain this weird problem? PeterB -- -- Proud to be a SuSE Linux User since 5.2 --
On Sat, 1 Mar 2003 11:53:31 -0600
Peter B Van Campen
Hello SuSE'ers.
Last night my 8.1 sys was running fine w/o any noticable problems. This morning the KDE desktop is littered with msgs saying "Cannot write XXX" and there is one from KDiskfree saying "dev /dev/hda3 is dangerously full" hda3 is my main ide 80GB WD drive. Last night it had 32GB FREE, but now it shows 99% full. Most things running have stopped on errors, KMail has lost it's indexes but shutdown -restart worked.
Upon reboot the system reports 32GB free and after some repairs seems to be OK. /var/log/messages shows nothing ou of the ordinary. Upon reboot there was an entry: Reiserfs replayed 86 transactions in 5 seconds
Using reiserfs SuSE 8.1 up to date via YOU KDE 3.0.5 SuSE 2.4.19 SMP kernel Has this happened to anyone else?
Anyone able to explain this weird problem?
No, but it's easy enough to do. Alot of people create files by using dd if=/dev/zero of=sometemp.file and renaming the file according to some incrementing naming scheme to get by the 2 gig file limit. This then fills the disk up to 100%. Of course, they delete the files when done. They do this to "wipe" the freespace on the harddrive, by the overwriting with zeros. So you might want to watch your apps everynow and then, with "top" and sort for memory using "M". See if and what is getting big, check your /tmp directories too. -- use Perl; #powerful programmable prestidigitation
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 01 March 2003 01:53 pm, Peter B Van Campen wrote:
Last night my 8.1 sys was running fine w/o any noticable problems. This morning the KDE desktop is littered with msgs saying "Cannot write XXX" and there is one from KDiskfree saying "dev /dev/hda3 is dangerously full" hda3 is my main ide 80GB WD drive. Last night it had 32GB FREE, but now it shows 99% full. Most things running have stopped on errors, KMail has lost it's indexes but shutdown -restart worked.
I had the same problem last week. It turned out that Kopete went crazy spewing messages which ended up in $HOME/.xsession-errors. Deleting the file has no effect, because the file is still open. The only way to fix it is to log out and log in again. - -- James Oakley Engineering - SolutionInc Ltd. joakley@solutioninc.com http://www.solutioninc.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Y2kD+FOexA3koIgRArobAJ0ZHlSYhQLNcz6zZez3vLkj9bYsrwCePgPj FLvx4MqATUA4dxNmGbN9a7Q= =lzVW -----END PGP SIGNATURE-----
On Mon, Mar 03, 2003 at 10:38:59AM -0400, joakley@solutioninc.com wrote:
I had the same problem last week. It turned out that Kopete went crazy spewing messages which ended up in $HOME/.xsession-errors. Deleting the file has no effect, because the file is still open.
The only way to fix it is to log out and log in again.
Or: cat /dev/null > $HOME/.xsession-errors -- David Smith | Tel: +44 (0)1454 462380 Home: +44 (0)1454 616963 STMicroelectronics | Fax: +44 (0)1454 617910 Mobile: +44 (0)7932 642724 1000 Aztec West | TINA: 065 2380 GPG Key: 0xF13192F2 Almondsbury | Work Email: Dave.Smith@st.com BRISTOL, BS32 4SQ | Home Email: David.Smith@ds-electronics.co.uk
Hi, Looks like the beta of the new SLIMP3 server perl script 3.1b2 caused the problem. I am talking to the developer. PeterB On Monday 03 March 2003 09:24 am, Dave Smith wrote:
On Mon, Mar 03, 2003 at 10:38:59AM -0400, joakley@solutioninc.com wrote:
I had the same problem last week. It turned out that Kopete went crazy spewing messages which ended up in $HOME/.xsession-errors. Deleting the file has no effect, because the file is still open.
The only way to fix it is to log out and log in again.
Or: cat /dev/null > $HOME/.xsession-errors
-- -- Proud to be a SuSE Linux User since 5.2 --
On Monday 03 March 2003 10:46 am, Peter B Van Campen wrote:
Hi,
Looks like the beta of the new SLIMP3 server perl script 3.1b2 caused the problem. I am talking to the developer.
PeterB
On Monday 03 March 2003 09:24 am, Dave Smith wrote:
On Mon, Mar 03, 2003 at 10:38:59AM -0400, joakley@solutioninc.com wrote:
I had the same problem last week. It turned out that Kopete went crazy spewing messages which ended up in $HOME/.xsession-errors. Deleting the file has no effect, because the file is still open.
The only way to fix it is to log out and log in again.
Or: cat /dev/null > $HOME/.xsession-errors
-- #------------------------ #Eric Bambach #Eric@CISU.net #------------------------
participants (5)
-
Dave Smith -
Eric -
James Oakley -
Peter B Van Campen -
zentara