Hello together,
currently I am formatting the drives with ext4 and no reserved space, therefore -m 0.
But there would also be an option to activate 64-bit file system:
Would it be a good idea to turn on 64-bit?
There is also an option to increase the available space on the disk by formatting as largefile4, but this shouldn’t be an option for STORJ or? Because STORJ should be having lower file sizes.
Thanks in advance and kind regards,
I’m personally running nodes on ext4 with the 64bit option set, as most of changes it makes to data structures should not have measurable impact. However, as I’m also running with inode size set to minimum possible (128 bytes), there’s no space for 64-bit checksums specifically for inodes. I believe that the reliability expected from storage nodes can be achieved without 64-bit checksums.
I’ve done some experiments on tuning the number of inodes (and some other parameters) here: On tuning ext4 for storage nodes I hope you will find these notes useful. largefile4 is too large for Storj.
Do not do this as you get a limited number of inodes and your node will die before 2TB is filled
But what about the 64-bit file system? Is it recommended to be anabled?
“Enables the file system to be larger than 2^32 blocks. This feature is set automatically, as needed, but it can be useful to specify this feature explicitly if the file system might need to be resized larger than 2^32 blocks, even if it was smaller than that threshold when it was originally created. Note that some older kernels and older versions of e2fsprogs will not support file systems with this ext4 feature enabled.”
No, if you are not planning on resizing it >16TiB, which probably isn’t useful for STORJ in the foreseeable future anyways.
It won’t give you any performance benefit, might even be the opposite. Besides you’re losing compatibility with software that might not be that up-to-date. Since it’s a quite recent feature, it might even contain some bugs, that are being discovered over time, etc.
Eh, quite useful.ᅟᅟᅟᅟ
