mergerfs.balance -p0

[simonmcnair]

Should this work please ? I tried running it and I wouldn't really expect it to work as it's unlikely you could get the same amount of free space on every disk but it did come up with weird results ? (it was yesterday but I think, iirc, it seemed to hang when it was trying to figure out what to move). I wonder if -p should have a minimum value of 1 ?

[simonmcnair]

Actually now I recall I think it just kept moving the last file from disk to disk because it couldn't make them all the same.

[Orski174]

Thanks, I thought it was a flag in mergerfs, should've checked the readme first.

I was copying files from my old drives to these ones so I can add them to mergerfs after a wipe and initialization, which is why i remade all the directories, empty of course in the other drives.

[trapexit]

Why not just put your drives in the pool? Why spend all the time copying data around?

At he very least... why not just set the policy to mfs or whatever you want and rsync into the pool?

[Orski174]

They were a windows ldm array, and I didnt want to keep it as so, now that I'm on a Linux system.

And I did just that, also does mfs affect read speeds? Nvm, another process was running so $du was really slow.

[simonmcnair]

Mfs means minimum free space. It is the policy used to choose where to write data. Mergerfs should have very minimal impact on write speed, if any.

[trapexit]

The create policy has nothing to do with reads or writes.