aMule Forum
English => aMule Help => Topic started by: ender2431 on May 21, 2004, 09:14:51 AM
-
Greetings,
I just switched over from M$ windows to linux on my main tower and with that I had to convert from emule, specifically emule-plus, to amule. I have been pretty pleased with it, and the conversion went very smoothly. I did not loose any dowloaded parts or files that I am trying to download, so thanks.
I am having a problem with trying to move files into paused mode from stopped mode. While downloading I keep about 20 files actively downloading and then I like to have some files paused so that when a file finishes, another starts up. To acomplish this, I keep trying to move files from being stopped into paused mode. However after a couple minutes, all the files that I have moved to paused change back to being stopped. Is this a feature, bug or do I have something configured wrong?
Also another weird note, I have 4 files that have been in the "completing" status for the past four hours? Should I just continue to wait?
I am running Gentoo 2004.1, amule version 2.0.0rc3 and 2.6 kernel.
-
check your disc space plz ;)
greets
-
300 GB LV and 100 GB free. I can expand the LVM further if needed to 0.75 TB. Disk space is not an issue.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda3 11G 7.2G 3.8G 66% /
/dev/vg/media 300G 218G 82G 73% /usr/media
none 252M 0 252M 0% /dev/shm
-
I have no clue how logical volumes work, but amule's errors may be due to that LV. Is it formatted with any filesystem? (sorry if that's a stupid question)
Citroklar
-
Just think of it as a large disk. That is how the LVM layer is supposed to work. The programs are not supposed to be aware of it.
For instance, normally you have:
1) Physical Hard Drives ( hda, hdb, ... )
2) Partitions (hda1, hda2, .... )
3) File system format (ext, xfs, jfs, .... )
Amule should not even be aware of the file system that it is on or the partition type like most programs (Except for high performance databases that sometimes use there own filesystem formate so they operate at level 2). That is the beauty of linux and the file system. It should just say output to so and so file and then the kernel or other programs handle the traslation to the disk data.
LVM adds a layer into that mix:
1) Physical Hard Drives ( hda, hdb, ... )
2) Volume Groups ( /dev/vg, /dev/vg1, ... ) - Think of these as virtual hard disks
3) Logical Volume ( /dev/vg/usr, /dev/vg/whatever, .... ) - Think of these as partitions
4) File system format (ext, xfs, jfs, .... )
The advantage of LVM is that it is all dynamic now. You can resize partitions and volume groups on the fly to meet whatever your demands are. I hope this was not over the top, but the quick answer is since amule can operate on any file system that Linux supports because it is not aware of the file system. It should not matter that it is on a LVM2 group. Otherwise you would have to have a different version of amule for each filesystem type and would destroy portability :)
PS - Love the sig
-
Update: Looks like the files just needed awhile to complete the processing. They have changed status from completing to completed. The other problem still exists. Oh well, I am still very happy with this release and platform.
:D
-
your temp & incoming are on /dev/vg/media ?
-
Yep:
$ ll ~/.aMule/
lrwxrwxrwx 1 hurt users 26 May 18 16:17 Incoming -> /usr/media/eMule/Incoming/
lrwxrwxrwx 1 hurt users 21 May 18 16:17 Temp -> /usr/media/eMule/Temp/
They are symbolic links.
*** Update ***
Thanks, it seems that amule will resume the stopped files when a file finishes downloading. So that is fine. Not exactly the behaviour that I was looking for, but it works, cheers.