On Fri, 2017-07-21 at 17:13 -0400, [email protected] wrote: > So we're running GPFS 4.2.2.3 and LTFS/EE 1.2.3 to use as an archive service. > Inode size is 4K, and we had a requirement to encrypt-at-rest, so encryption > is in play as well. Data is replicated 2x and fragment size is 32K. >
For an archive service how about only accepting files in actual "archive" formats and then severely restricting the number of files a user can have? By archive files I am thinking like a .zip, tar.gz, tar.bz or similar. Has a number of effects. Firstly it makes the files "big" so they move to tape efficiently. It also makes it less likely the end user will try and use it as an general purpose file server. As it's an archive there should be no problem for the user to bundle all the files into a .zip file or similar. Noting that Windows Vista and up handle ZIP64 files getting around the older 4GB and 65k files limit. JAB. -- Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk Fife, United Kingdom. _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
