Tip 1: You can’t have too big a volume for Hammer.
Tip 2: Snapshots are the easiest way to track historical data.
One Reply to “Hammer tips”
Comments are closed.
A running description of activity related to DragonFly BSD.
A running description of activity related to DragonFly BSD.
Tip 1: You can’t have too big a volume for Hammer.
Tip 2: Snapshots are the easiest way to track historical data.
Comments are closed.
Re tip 1: The size of HAMMER volumes isn’t the issue,
the sum of all volumes, i.e. the size of the whole HAMMER filesystem is.
But HAMMER likes lots of space, but then access to all the historical data
will give users a whole new dimension of what a file system constitutes, I think.
With the big disks these days HAMMER could be a hit for both desktop and server
users, if it gets ported to the systems they use; but it should get more ‘self managed’,
so users won’t have to implement retension policy themselves.