bouis
Members
-
Joined
-
Last visited
-
I have the same issue (apparently) but it's a pool and can't be accessed (as far as I know) without mounting the array.
-
I guess I should have been more clear---it didn't delete the old files after moving, so I ended up with duplicates. Sorry for the lack of clarity; it was late and I was busy.
-
I have two SSDs in btrfs raid0. I've been fiddling around with my box lately, and I guess the cables were loose on one my drives, because the drive dropped while the mover was running. It came back after reboot and no data was lost, but there were some very preventable corruption issues. Bug #1: After one disk dropped, the files on the raid0 cache remained visible to the UI (but not readable through the UI). Good, I guess. But the mover kept on going and wrote corrupted files to the array disks which had the appearances of being functional files. I was able to clean them up because the files remained on the cache (presumably it went read only). But the mover should not do this! Bug #2: Unraid refuses to mount the cache if one drive in btrfs raid0 is not available after reboot. Good. And the drives sync after being reconnected and the system rebooted. Good. But even though it works and the data is good, unraid shows the dropped drive as unassigned, not as part of the cache pool. I can't see any way to add it back without moving everything off and wiping it. This is very inconvenient.
-
Bug report: it seems that unbalance won't move files with ` (that's that upper-left key) in the name.
-
I've just discovered this plugin. It really seems to scratch an itch with the mover, so thanks a bunch. I do have a feature request, though: I have a large cache drive (4tb SSD), and it would be helpful if I could use set it up so, during a scheduled move, turbo write is used only if the cache drive is filled to a certain percent. That way small scheduled moves would happen without turbo write, but big ones that need to write faster to clear the cache would spin up all the drives. Also, and maybe it's asking for too much, but it'd be great if we could: A) stop the mover manually; and B) automatically stop scheduled moves if they haven't finished by a certain time. My need for those last two may be abrogated by being able to set the mover priority lower / cancel it during parity scans, but I haven' had a chance to test the low priority much. Anyway, thanks again!