aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Crash when not enough free disk space for .aMule  (Read 3233 times)

ecforum

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 105
Crash when not enough free disk space for .aMule
« on: May 26, 2007, 08:57:44 AM »

Hello,

Amule crashes when there is no more free space on the disk containing the .aMule directory (config files directory).

Regards.
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Crash when not enough free disk space for .aMule
« Reply #1 on: May 27, 2007, 03:19:31 AM »

Backtrace and aMule version? I have many times ended with no left space, and aMule has never crashed on me. It will simply stop all the downloads.

Regards.
Logged

ecforum

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 105
Re: Crash when not enough free disk space for .aMule
« Reply #2 on: May 27, 2007, 02:31:35 PM »

Hello,

It is amule 2.1.3. And I have no backtrace.

The .aMule directory is on my /home partition.
The downloads (finished or not finished) are on a data partition.

When there is no more space on the data partition, the downloads stop.
But when there is no more space to save files in the .aMule directory aMule crashes (it runs and then crashes some times later).


Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Crash when not enough free disk space for .aMule
« Reply #3 on: May 27, 2007, 05:13:52 PM »

Maybe that has been fixed in the current development versions, since I use them.

Regards.
Logged

ecforum

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 105
Re: Crash when not enough free disk space for .aMule
« Reply #4 on: November 24, 2008, 08:16:46 PM »

Hello,

I had the same problem with amule 2.2.2 last week end.
I was in release... There is no backtrace : only a segmentation fault message in the xterm...

Regards.
Logged