Jump to content
jbrodriguez

[Plug-In] unBALANCE

1085 posts in this topic Last Reply

Recommended Posts

Update: I used rsync instead to move over my files back:

rsync -av --progress --remove-source-files /mnt/diskX/ /mnt/diskY

No point in using remove-source-files if you are planning on formatting the disk anyway. Copying vs moving is much faster.

 

I have:

Parity

Disk1 - XFS

Disk2 - RFS

Disk3 - RFS

Disk4 - RFS

Disk5 - XFS (New drive, no user shares)

 

I've just done Disk1, my plan is to use Disk 5 as a placeholder while I empty RFS drives followed by reformatting. So I'm using unBalance to move files from the RFS disk to my placeholder. Then I reformat it to XFS. Since there are no user shares on the placeholder, I can't use unBalance. I have a specific requirement for having a certain type of file/shares on certain disks, otherwise I wouldn't be moving them back. Should I use the diskmv script

diskmv -f "" disk1 disk2

instead or maybe just mv

mv /mnt/disk1/ /mnt/disk2

?

 

Hi CRD,

 

If you're copying disk to disk, which means you have available space on the target disk, I would suggest doing a straight rsync copy .... there's a thread somewhere in the forums about this same topic (rfs to xfs transfer) :)

Share this post


Link to post

I tried to use this to empty a disk so I could format it. It should have finished overnight, but didn't. It stopped at 120 gigs. So this morning I set it to run again, and it stopped at 116 gigs, but ~120 gigs disappeared from my array. I checked my disk shares, and sure enough, the drive that was supposed to be emptied had copies of files that were also on other disks. So now I'm paranoid that I have a bunch of copies of files on various disks.

 

Is that something that the built in unraid mover would ultimately fix? Or am I doomed to have to compare files over my 4 disks for a while?

 

hi smashingtool,

 

Do you see anything out of the ordinary in either unraid's or unbalance's logs ?

 

The heart of the operation is an rsync command, any error it might come up with should be written to the log.

 

But rsync can also slow down/pause with a failing disk.

 

Let me know if you find any other evidence of what might have happened.

Share this post


Link to post

You may find the unRAIDFindDuplicates.sh script I wrote some time ago to be of use.  It can very quickly find duplicates based on filenames and timestamps, and also has the option to do (much slower) binary compares.  I regularly use it after moving files around just to check there are no duplicates left behind on different disks.

 

Thanks, It's great that you made that, I'll give it a shot.

 

My only other question now is whether it's possible to pause or stop unBALANCE after you start it.

 

You can't stop it right now, except for killing the unbalance process and the rsync processes from the command line.

 

unBALANCE will go down gracefully as soon as it is interrupted, but rsync will go down hard.

 

Having said that, I think it's possible to add stopping the plugin in the middle of a move operation.

 

I need to look at some scenarios to see how it might work.

 

I don't know if the stock mover can be stopped as well ... it would help to check out how they did it, if they did ;)

Share this post


Link to post

Thanks for this, seems to work great.

 

One suggestion.

 

In my case, when I tried to open unBALANCE from the plugins page, I clicked "Open webUI 1.30" and it took me to "tower:6237" which didn't load.

 

Unfortunately on OS X, to access my server over the network you need to type in tower.local, not just tower. Would it be easy for you to change this link to access via the unRAID IP address instead of via hostname? That way regardless of hostname it will just load the IP:port and should work on any OS.

 

Thanks for the comments lishpy !

 

I'll take a look at the link opening code, to see if I can use ip address rather than hostname (probably, that's what's happening to huladaddy too).

 

I'm a bit tied up until the end of next week, but I'll look into it.

no idea what the webUI page is, but if you just have it as another .page file, then reference it as Settings/webUI and dynamix will handle everything for you...  (turn on help, and look at the link for CA's manual, and look at caHelp.page

 

Squid, in the settings page, when the app is started, there's a link to the app's user interface ... it's opens a new window/tab with the server's hostname, rather than ip address, I'm not sure if there's an env variable that holds the ip address :)

can't you just do <a href="/settings/Unbalance.page" target="_blank"> and have unraid figure it out for itself?  IIRC the browser will correctly go to either the IP or to the hostname depending upon how the originating page was loaded.  I'll look tonight.

Share this post


Link to post

Thanks for this, seems to work great.

 

One suggestion.

 

In my case, when I tried to open unBALANCE from the plugins page, I clicked "Open webUI 1.30" and it took me to "tower:6237" which didn't load.

 

Unfortunately on OS X, to access my server over the network you need to type in tower.local, not just tower. Would it be easy for you to change this link to access via the unRAID IP address instead of via hostname? That way regardless of hostname it will just load the IP:port and should work on any OS.

 

Thanks for the comments lishpy !

 

I'll take a look at the link opening code, to see if I can use ip address rather than hostname (probably, that's what's happening to huladaddy too).

 

I'm a bit tied up until the end of next week, but I'll look into it.

no idea what the webUI page is, but if you just have it as another .page file, then reference it as Settings/webUI and dynamix will handle everything for you...  (turn on help, and look at the link for CA's manual, and look at caHelp.page

 

Squid, in the settings page, when the app is started, there's a link to the app's user interface ... it's opens a new window/tab with the server's hostname, rather than ip address, I'm not sure if there's an env variable that holds the ip address :)

can't you just do <a href="/settings/Unbalance.page" target="_blank"> and have unraid figure it out for itself?  IIRC the browser will correctly go to either the IP or to the hostname depending upon how the originating page was loaded.  I'll look tonight.

 

don't remember why I was trying env variables, but your suggestion seems saner, will check it too :)

Share this post


Link to post

Update: I used rsync instead to move over my files back:

rsync -av --progress --remove-source-files /mnt/diskX/ /mnt/diskY

No point in using remove-source-files if you are planning on formatting the disk anyway. Copying vs moving is much faster.

 

I have:

Parity

Disk1 - XFS

Disk2 - RFS

Disk3 - RFS

Disk4 - RFS

Disk5 - XFS (New drive, no user shares)

 

I've just done Disk1, my plan is to use Disk 5 as a placeholder while I empty RFS drives followed by reformatting. So I'm using unBalance to move files from the RFS disk to my placeholder. Then I reformat it to XFS. Since there are no user shares on the placeholder, I can't use unBalance. I have a specific requirement for having a certain type of file/shares on certain disks, otherwise I wouldn't be moving them back. Should I use the diskmv script

diskmv -f "" disk1 disk2

instead or maybe just mv

mv /mnt/disk1/ /mnt/disk2

?

 

Hi CRD,

 

If you're copying disk to disk, which means you have available space on the target disk, I would suggest doing a straight rsync copy .... there's a thread somewhere in the forums about this same topic (rfs to xfs transfer) :)

 

Thank you, I've re-read many posts from that thread, I've got one final disk left! *phew* Thank you so much, I'm using your plugin to do 1 part of the move and it has worked well for me. Thank you again.

Share this post


Link to post

Thanks for this, seems to work great.

 

One suggestion.

 

In my case, when I tried to open unBALANCE from the plugins page, I clicked "Open webUI 1.30" and it took me to "tower:6237" which didn't load.

 

Unfortunately on OS X, to access my server over the network you need to type in tower.local, not just tower. Would it be easy for you to change this link to access via the unRAID IP address instead of via hostname? That way regardless of hostname it will just load the IP:port and should work on any OS.

 

Thanks for the comments lishpy !

 

I'll take a look at the link opening code, to see if I can use ip address rather than hostname (probably, that's what's happening to huladaddy too).

 

I'm a bit tied up until the end of next week, but I'll look into it.

no idea what the webUI page is, but if you just have it as another .page file, then reference it as Settings/webUI and dynamix will handle everything for you...  (turn on help, and look at the link for CA's manual, and look at caHelp.page

 

Squid, in the settings page, when the app is started, there's a link to the app's user interface ... it's opens a new window/tab with the server's hostname, rather than ip address, I'm not sure if there's an env variable that holds the ip address :)

can't you just do <a href="/settings/Unbalance.page" target="_blank"> and have unraid figure it out for itself?  IIRC the browser will correctly go to either the IP or to the hostname depending upon how the originating page was loaded.  I'll look tonight.

 

don't remember why I was trying env variables, but your suggestion seems saner, will check it too :)

ca uses href="Settings/caHelp", and unRaid adds either the hostname or the IP appropriately.  However, caHelp is actually caHelp.page.  If its not a .page file, then a reference like that isn't going to work.

 

Since you're odds on not going to a .page file, my best suggestion would be to go to the IP address instead of the hostname since that should always work.  You can get the IP from /var/local/emhttp/var.ini

Share this post


Link to post

I tried to use this to empty a disk so I could format it. It should have finished overnight, but didn't. It stopped at 120 gigs. So this morning I set it to run again, and it stopped at 116 gigs, but ~120 gigs disappeared from my array. I checked my disk shares, and sure enough, the drive that was supposed to be emptied had copies of files that were also on other disks. So now I'm paranoid that I have a bunch of copies of files on various disks.

 

Is that something that the built in unraid mover would ultimately fix? Or am I doomed to have to compare files over my 4 disks for a while?

 

hi smashingtool,

 

Do you see anything out of the ordinary in either unraid's or unbalance's logs ?

 

The heart of the operation is an rsync command, any error it might come up with should be written to the log.

 

But rsync can also slow down/pause with a failing disk.

 

Let me know if you find any other evidence of what might have happened.

 

I dont see any evidence of a failing disk. Otherwise, here's the main error i found in unBALANCE's logs:

 

I: 2016/02/10 07:50:52 core.go:651: diskmv finished
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: Cannot stat file /proc/32071/fd/70: No such file or directory
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]
I: 2016/02/10 07:50:52 core.go:651: rsync: failed to set times on "/mnt/disk1/Video/Movies/Primary": Operation not permitted (1)
I: 2016/02/10 07:50:52 core.go:651: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.0]

Share this post


Link to post

Thanks for this, seems to work great.

 

One suggestion.

 

In my case, when I tried to open unBALANCE from the plugins page, I clicked "Open webUI 1.30" and it took me to "tower:6237" which didn't load.

 

Unfortunately on OS X, to access my server over the network you need to type in tower.local, not just tower. Would it be easy for you to change this link to access via the unRAID IP address instead of via hostname? That way regardless of hostname it will just load the IP:port and should work on any OS.

As a temporary work around for this you might consider using the Hosts system prefs pane on your mac. It will set the mac so that servername:6237 will resolve to IP:6237. Very simple to use. Also free.

Share this post


Link to post

Is there any way to keep the script running even if the page is closed and re opened like a parity sync?

Share this post


Link to post

Is there any way to keep the script running even if the page is closed and re opened like a parity sync?

It does already. Are you having a problem?

Share this post


Link to post

If I start the plugin and leave the page it dies. I have to keep the page open. It only works on edge. Internet explorer is no good neither is Safari and I don't have Crome or fire fox. .

 

I almost emptied a drive and by mistake closed the window and then went back and it remembers nothing..... Didn't see open.... Checked disk activities and no more writing..... Weird

Share this post


Link to post

By no good I can send screen shots if you are interested..... I installed the plugin yesterday and running on newest 6.

Share this post


Link to post

If you open your browser and load the page again you won't see anything until another file is displayed in the log so if you are moving large files it might take a while to see the next file.

Share this post


Link to post

If you open your browser and load the page again you won't see anything until another file is displayed in the log so if you are moving large files it might take a while to see the next file.

 

Well i just started a run.... waited 30 seconds closed the window and all writing on the server stopped....... if i leave the window open writing doesn't stop..... ? i did a dry run an then you are correct nothing stops and docent forget but normal run for me is not acting that way.

 

 

 

 

 

 

ok sorry so it looks like it is still running but the website can't tell so it allows you to run it again?? can the header be made to reflect if it is truly running? and lock out the start like a parity check? sorry for the trouble but i am guessing that i must have started it 3 times now on top of each other prior to knotting that it was running.

Share this post


Link to post

It won't let you click the button if it is already running.

Share this post


Link to post

If you open your browser and load the page again you won't see anything until another file is displayed in the log so if you are moving large files it might take a while to see the next file.

 

You're right, I've seen that too. I need to fix it.

Share this post


Link to post

If you open your browser and load the page again you won't see anything until another file is displayed in the log so if you are moving large files it might take a while to see the next file.

...

ok sorry so it looks like it is still running but the website can't tell so it allows you to run it again?? can the header be made to reflect if it is truly running? and lock out the start like a parity check? sorry for the trouble but i am guessing that i must have started it 3 times now on top of each other prior to knotting that it was running.

 

Like trurl mentioned, it won't let you click on the button if it's already running, do you see something different ?

Share this post


Link to post

I've published v1.3.1, with the following changes:

 

- Use ip address instead of hostname when opening app window

- Improve UI feedback when an operation is in progress (browser is being reopened)

- Set a 1000 lines buffer for the console (older messages will be removed)

 

Let me know if you find any issues.

 

I have to think some more about stopping the operation.

 

With regards to the copy functionality, I'm about 95% sure I won't do it  :o

Share this post


Link to post

Updated...won't even calculate now. Just sits there at "CALCULATE: Operation started"

Share this post


Link to post

I had a similar issue where the calculate stops, I've had to force the plugin to terminate when it does this. It only happened though when I was calculating a location with a lot of small files, ie. my Plex App folder (I used unBalance to move files around to convert all my files to XFS). But, it had no issues when actually running it. On different shares, ie. Movies, music, TV Shows, etc, calculating was instantaneous and also had no problems moving files over.

Share this post


Link to post

Updated...won't even calculate now. Just sits there at "CALCULATE: Operation started"

 

Like CRD mentioned, it can take a while if there's lot of small files.

 

But, it's showing the progress bar, next to the 'started' label right ?

Share this post


Link to post

Actually, there was a bug with progress messages, I've fixed it in 1.3.2  :)

 

aha! That fixed it....I knew something wasn't quite right. Thank you!

Share this post


Link to post

I've published v1.3.4, which adds progress stats when moving folders.

 

It has a folder level granularity (not file level), so increments should be in big chunks, and spaced in time between them.

 

But it gives a ball park estimate of where the operation is sitting at.

 

I also took a look at what smashingtool reported, with the app stopping and all.

 

It's very difficult to replicate, what I've read is that sometimes rsync hangs, but there are no specific reasons.

 

If someone comes across this issue (app stopping/rsync hanging), please provide me with the output of the following commands

 

$ ls -l /proc/$(pidof rsync)/fd/*

$ ps aux | grep diskmv

$ ps aux | grep find

 

Additionally, to move on with the process, I'd do the following:

 

1 - Get the last diskmv command that's being executed

$ ps aux | grep diskmv

 

It should output something like

... /bin/bash /usr/local/emhttp/plugins/unbalance/diskmv -f films/bluray/Movie/ /mnt/disk1 /mnt/disk2

 

2 - Stop unBALANCE from the plugin settings page

 

3 - Execute the diskmv command manually (minus the /bin/bash)

$ /usr/local/emhttp/plugins/unbalance/diskmv -f films/bluray/Movie/ /mnt/disk1 /mnt/disk2

 

This should sync the folder and the data should be in a reasonable state.

 

4 - Start unBALANCE again, calculate, move :)

 

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now