In my particular case, and I'm sure for many other people, files that
are stored never change again until they deleted. I hinted that there
could be a command line switch to turn this functionality on, as it may
not be perfect for everyone's use cases.
If nobody likes this still, I would appreciate some hints on how to mark
files as no-defrag from within fsr itself given that I only have the
file descriptor ... A hack like looking up the descriptor in
/proc/self/fd should work, but is linux specific and is too hackish in
my opinion. I'd like to at least have a nice simple patch for my own uses.
Eric Sandeen wrote:
Just Marc wrote:
2. Files for which 'No improvement will be made' should also be marked
as no-defrag, this will avoid a ton of extra work in the future.
But... that file could drastically change in the future, no? Just
because it can't be improved now doesn't necessarily mean that it should
never be revisited on subsequent runs, does it?