[gpfsug-discuss] GPFS, LTFS/EE and data-in-inode?

Jonathan Buzzard jonathan at buzzard.me.uk
Tue Jul 25 10:02:14 BST 2017


On Mon, 2017-07-24 at 11:49 -0400, valdis.kletnieks at vt.edu wrote:
> On Mon, 24 Jul 2017 12:43:10 +0100, Jonathan Buzzard said:
> 
> > 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.
> 
> After having dealt with users who fill up disk storage for almost 4 decades
> now, I'm fully aware of those advantages. :)
> 
> ( /me ponders when an IBM 2314 disk pack with 27M of space was "a lot" in 1978,
> and when we moved 2 IBM mainframes in 1989, 400G took 2,500+ square feet, and
> now 8T drives are all over the place...)
> 
> On the flip side, my current project is migrating 5 petabytes of data from our
> old archive system that didn't have such rules (mostly due to politics and the
> fact that the underlying XFS filesystem uses a 4K blocksize so it wasn't as big
> an issue), so I'm stuck with what people put in there years ago.

I would be tempted to zip up the directories and move them ziped ;-)

JAB.

-- 
Jonathan A. Buzzard                 Email: jonathan (at) buzzard.me.uk
Fife, United Kingdom.




More information about the gpfsug-discuss mailing list