Wo ist die maximale Filegröße denn eigentlich bei aktuellen amule Versionen?
Ich wollte ein großes File hashen aber das ging nicht wegen Größe.
Das File ist 349 GB groß.
Gibt es vom ED2K System systembedingte Grenzen?
EDIT: 2015-12-19 14:45:11: Hasher: Warning, file is larger than supported size, skipping: /media/sda6/DATA/ABCDEFG/blablabla.abc
Hmmm I don't know what language it is but i'm guessing its Dutch from the name. But anyways by reading the error message you posted I can guess your trying to hash file 349GB in size. As it failed your now your asking about max file size supported by ~Mule?
Back in the early days ED2K had max file size of 4GB, as storage grew so did file size count. So when it became more common with bigger file size it was revised by eMule to support larger file and made default standard to support 256GB in early 2006, thus aMule adopted as well. As this is the current hard max file limit handled by standard ~Mule clients. But can be changed to 512GB but to increase more than that major protocol changes would be needed. So its kept to maintain backward compatibility for older clients that are still connected via KAD/ED2K.
./amule/src/include/protocol/ed2k/Constants.h
// (4294967295/PARTSIZE)*PARTSIZE = ~4GB
#define OLD_MAX_FILE_SIZE 4290048000ull
// = 2^38 = 256GB
#define MAX_FILE_SIZE 0x4000000000ull
const uint64 PARTSIZE = 9728000ull;
const uint32 BLOCKSIZE = 184320u;
const uint32 EMBLOCKSIZE = 184320u;
Keep in mind this has nothing to do with 32/64bit OS user is running. But currently some ~Mule mods does allow 512GB allocation thus theoretically clients can transfer it, as it has been the case for many years now. But its between mod client to mod client where normal standard client would have problem addressing the sheer number of chunks as serious optimization would be needed. As it would have to be addressed due to over 56k chunks for 512GB, where standard chunk size are 9.28MB.