Hot answers tagged


If you look at the kernel's inode source code, you can see that the ihash_entries is set at the kernel level only. There is no user or process level considerations at all. Adding those could drastically decrease performance which would be counter productive. It would also imply keeping track of all processes that used the cached entries, therefore ...


File size is limited by filesystem type not by OS. Typically, OS supports several filesystems, so there is no such thing like "OS file size limit". There are limits for well-known filesystems: FAT32 - 4Gib NTFS - 16Eib ext2/3 - 16Gib - 2Tib (depends from block size) ext4 - 16Gib - 16Tib XFS - 9Eib ZFS - 16Eib


Since more than a decade, 32 bit Linux applications are able to access files larger than 2 TiB (2^31) thanks to the implementation of large file support. The current OS limitation is 8 EiB (2^63) which shouldn't hit the common of us before a while... You would need a file system that makes no lower limit on file size too.


It turned out to be a small config mistake by myself. After 8 hours of brain-pain and fulle rebuilding the config file the fault turned out to be in the TransferLimit line where also the group was specified. (which is not needed because we use class definitian). TransferRate APPE,RETR,STOR,STOU 1000 group speedlimit should have been: TransferRate ...

Only top voted, non community-wiki answers of a minimum length are eligible