Bjørn Øyvind Halvorsen

  • Posts

  • Joined

  • Last visited

Posts posted by Bjørn Øyvind Halvorsen

  1. It's an unraid to unraid backup yes. zfs filesystem on both servers. 


    The permissions i was talking about is something I see that LuckyBackup/rsync is doing. not something i am doing.

    just the flow of how a backup is performed. 

    1. folder structure copied from source to destination. All permissions is set to root.

    2. Files copied

    3. When files are done copying from destination to source, the permissions on the folders on Destination is changed to "nobody" so that anyone can access them..


    I have tried both Synchronizing and backup mode in luckybackup. I have followed the tutorial here to get SSH to work. Basically the exact same thing as here ->


    One thing I have forgotten to say is that the folders with the strange characters is not visible in Samba when viewing them from my windows computer. Also i cannot access them in the termial, unless i change the name of the folder that has the correct spelling (that i can se in Samba). When i have renamed it, i can navigate to it, but only if i write the first part of the name, and then use tab to finish the foldername. Basically what i have done then is gone through and found all of these folders, renamed the folder with the proper naming, and deleted the one with the strange characters. Now i'm trying to run luckybackup again, to an empty folder to see if everything works ok. 


    I know it's a strange error... don't know what to tell you :) - I have a good feeling about it now though... 

    Hope nobody else gets this problem... 

    • Upvote 1
  2. I have cleaned up source, so that there is no more of those magic folders now, and started a new fresh backup to Destination. If this works, something else must have created the folders in the first place, and LuckyBackup (rsync) must have done something clever with them, moving them back and forth. 


    I am certain that LuckyBackup has moved these magic folders and content from the original folders back and forth somewhat, but I'm inclined to say that these folders were not created by LuckyBack (rsync).... 


    I did some tests with just the correct folders, and that seemed to work fine. I'm more worried about the drwx------- folders that's owned by root... I think those are the sinners :)


    I forgot to answer to the filesystem question. Sorry. It's from Unraid to Unraid. So that would mean XFS on both.

    It's copying from SSH to th elocal disk via the Docker..

  3. Ok... so.


    There's two unraid servers. Destination and Source. All the files were initially on Source. Luckybackup runs in a docker on Destination. 

    We connect through SSH. 


    My theory:


    The first time it copies, it moves all files from Source to Destination, and it gets confused by æøåéçã and so on. Because of this confusion it creates folders like the once you have seen on the screenshots. The next time it syncs these new folders back to Destination (which I don't understand, because I thouht it was a oneway backup). Then when it's doing it's second run, it sees the folders it created and tries to copy the content, but instead of going into the strangely named folders, it goes into the folder with the correct letters, and moves these files into the folder on destination, that has the strange characters :| Then there's double. Files in Destination then has two sets of the files. One with the correctly named, and one with the one it created itself...


    Yes. Crazy confusing. 


    Needless to say, I'm getting afraid of LuckyBackup, and think I'll stay away from it for now.... 

  4. Snapshots are not enabled.


    Screenshot from source:





    At first i did not think that these folders were in destination, and so I blamed LuckyBackup. I will try to remove these folders in destination too, and run luckybackup again.... 


    I realize that I don't know how these files are created though, but when they are, LuckyBackup keeps copying from them, over and over again, without any changes. I will updated you when I have tried removing all of these files and run the backup again


    • Thanks 1
  5. Hi!


    LuckyBackup seems awesome, and I tried using it, but it creates some strange folders in the source folder where the data is to be copied from. 



    These folders come up as folders with no name in Unraid web ui:


    And I can't navigate into them in the terminal. 


    When LuckyBackup has made these folders, it keeps copying from them everytime I run the backup. 


    Anyone know why this happens? - Needless to say, I can't really use it until I figure this out...

  6. The three drives are OCZ-VERTEX3 drives. I have tried running all the SMART self tests, but either it returns nothing or pretends it's not started or somesuch. 

    When i download the SMART report it gives me a text document with the following features of interest inside:


    SMART support is: Available - device has SMART capability.
    SMART support is: Disabled


    SMART Disabled. Use option -s with argument 'on' to enable it.
    (override with '-T permissive' option)


    Can I in some manner enable the SMART feature on these disks? What command, and how? I'm not sure what to do with the -s argument with 'on' maybe with a -T permissive option. Any hints, tips or tricks? :) 

  7. I have got almost same setup as you, and your posts has helped me a lot. However, when I restart the vm, the sound card does not want to restart, and the vm hangs... I have to reboot the whole unraid for it to work. Now. I don't really need the hdmi sound card, because I got another one, but I am not able to start the machine without the hdmi soundcard.


    Have you had this issue? And maybe found a solution to it? 

  8. I see.. So still across all drives then. 


    This suggestion went from something to benefit all, to maybe a few to now, maybe just me and especially interested, so here we go. 


    Would using hybrid disks/SSD's (one part ssd one part spin disk) as parity drives increase speed of the array drastically? Since this would likely not care where it writes to in the spinner part of the disk.. 

  9. Hmm.. I hear you. 


    It is possible to have two parity disks tho. Are they copies of each other, or half & half, that is; If there are four disks in the array, and two disks as parity, would two disks have one parity each, or would all four disks have the same two parities?


    If one could set up the parities, one to each half of the array, you could at least double the write speed? or no?

  10. I understand that the cache drives are currently used with a mover script. 


    What if we did something like this instead?

    1. Files gets moved to cache drive (which is fast, preferrably SSD drive, should be twice or three times as fast as to one of the drives in the array, if they are spin disks)

    2. First file lands on Cache (SSD) drive, and Unraid moves the file to one of the drives in the array (while the second file is landing on the SSD drive).

    3. The second file lands on the SSD drive, and Unraid moves this to one of the other drives, which is currently not active.


    This repeats, untill Unraid is moving one file to each drive in the array, reaching the speed of the Cache drive. 


    I understand that you would be moving files to and from the Cache drive at quite the rapid speed, and that this might be a problem for the Cache drive (especially if it's a spin disk drive) 


    An alternative to running this at the same time, is to wait untill there is no operation on the Cache drive, and then move it to the spin drives, one file to each drive, for increased speed.


    The reduced time the data would be on the cache disk, would be a security improvement, and the idea of writing to all drives, at the same time, from the cache drive, seems to me like quite the boost in performance. - Even if it did not happen at the exact same time as the transfer is happening to the cache drive.


    The whole idea is to spread the load of the file transfers to more disks. I suppose this could be done with the Cache drives too. Load a file into the memory of Unraid, then save it on one of the Cache drives, the next file, from memory to the next Cache drive and so on. This would increase the write performance of Unraid quite a lot i would imagine. You could configure how much data you'd want Unraid to keep in memory for incoming filetransfers.

  11. Got the same problem here... Just used my whole day getting set up with all my disks, USB card and Graphic card passthrough it all seemed to work really well, and suddenly GPU is going up to 100% usage. 


    It's System, Client Server Runtime Process and Desktop Window Manager that fights for the resources of the Graphics card..


    There is no other programs open on my desktop.


    GPU Engine said GPU 0 - Copy whatever that should mean.