nuticles

Thanks for the quick response! I realize Crashplan being slow known, but since I am seeing a very specific issue I want to be sure I am diligent. I know myself and being complacent with known problems has caused me to miss opportunities. Is my specific issue, where Crashplan only utilizes only 1 core (out of 4 assigned) considered part of the known error? The reason I ask is I've seen a lot of posts about "high CPU" however nothing about not utilizing multiple cores properly. Maybe the de-dup or compression process is single threaded? I will check with Crashplan, but if anyone else has ideas or has this problem let me know. I mean its very possible I hosed a configuration somewhere since I'm a n00b

I wanted to toss a question out to the community regarding slow backup times in the Crashplan Pro container. I realize its Crashplan itself, not the container which as been awesome. Unfortunately I just had too much data to migrate, so I needed to start fresh. Before I go on, I want to be sure I show my appreciation for the work on the container. Keep in mind I've already attempted to self serve spending several hours on both Unraid, Crashplan and Docker. Also keep in mind I'm a relative noob. That said, here's a summary: Issue: Despite having 4 cores (2 Real & 2 HyperTHread) assigned Crashplan dances between core to core pinned each one at 100%, but never using more than 1 (effectively only using 25% assigned resources). I assume the majority of processing is dedup, so I figured more efficient processor usage would help, but I am not sure. Background: - Dual 2650 Xeons (32 Cores) / 64 GB Memory. - Verified Cores & HT Partners are correct. - Glances shows 500% processor (odd) but dashboard still shows 100. - Gave Crashplan 10GB of memory (verified its done properly). - Set CPU to 100% on Crashplan Central Console for both both active and idle user. - Average aka "effective bandwidth" = 4 mbits" out of 15 meg up. Thoughts? Thanks in advance!

My bad, I somehow missed that. Thank you!

Unraid Guru's- I am not sure if this is a bug, or self-inflicted but I suspect the later. I recently moved VMs from an old UnRaid box to a new one with refreshed hardware. I moved the VMs by doing a virsh dumpxml and then a define with the .xml on the new box. Moving the vdisk.img by using a simple copy. The good news -- the VM works on the new machine! The bad news.... I didn't notice when this happened, if it was before the move or after, but the VM templates are gone from the VM tab (see below). Thanks in advance for any help!

You are a baller! I always botch hand soldering anything smaller than car stereo wiring. When I was a teen I'd solder to compliment the crimping... I was insane back then. Or when building subwoofer boxes I'd solder to the woofer and the plate which connects to the outside of the box. Anything smaller I'd make a mess.... amps, circuit boards, etc.. nope... ruined

I love it! I remember when my father bought a "Trash 80" for his small business. That's when I first discovered the text-based game "Planetfall," among others. Poor little Floyd

Please don't apologize, anyone who takes the time out of their busy lives to contribute to someone else's learning and or problem solving is great. That said, is there any way I can thank you and other members who responded? I see there is reputation, how can I add to yours and the other folks who contributed? Ok, now on to the whole User0 thing. Some background on me first of all, as much as I have been in IT for years between a childhood hobby. This is the part I should deny, my first PC was an Apple //e. Yes I dated myself. There are several factors here which is why I became obsessed with User0: This one is huge -- it was 3 AM! - I was tired and went with the "fire, aim, ready" order. All typical diligence was put aside, stupid, I know. Typically with any change I follow the carpenter's method "measure twice cut once." I didn't read (aka measure) one lick on user0, I just nuked it (aka cut). I am a linux n00b -- I did not realize it was a logical file system, I thought I created some bizarre data duplication. Once I make a mistake, I tend to examine the crap out of it. In my mind the true mistake is not learning from it! I am slightly IT OCD. I like to think of things being "Clean" or "Lean." This is probably too many years of running Windows because its so damn bloated over time. In hindsight, this mistake was one of the best unRaid learning experiences. That said, I hope I don't screw up this bad again! TLDR: Thanks for the help. How do I add forum reputation to those what helped? When I screw up I need to examine why thoroughly!

Hey all, I have a small issue I wanted to bring up the community. I am a bit of a n00b, so its possible that its something simple or stupid I am doing. However, doing a few hours of research has still left me stumped. Before I go on, I have to say thanks for putting together this Crashplan Pro docker. I realize hours and hours of effort go into developing things like this. I've had great success with Home and was happy to be able to migrate over to Pro since CP Home is bailing out on us. My issue: I tried a test restore of a few dockers in "appdata" and found that Crashplan Pro failed with a super ambiguous error message "- Uknown problem for /storage/appdata/" All files and directories fail, so I just see this message over and over again (sample attached). A few notes: 1- I did delete the teamspeak3 directory from appdata, so there were no file conflicts. 2- When I did the restore, I selected the files from /storage/appdata/ and clicked the teamspeak3 directory 3- I've tried this with different folders in /appdata all with the same results 4- I did not see a permissions issue, but I am a noob so I can miss things - right now appdata is set 777 with nobody / users. 5- When I restored from Crashplan Pro GUI - I selected to restore to the "Original Location" for destination / "Overwrite" for file conflicts / "Original" for file permissions. It does work if I restore to /config - which is the default setting in CP Pro! Any ideas? I mean I can restore to /config and copy over, but I was wondering if I was doing something wrong. I'd rather be able to restore to an original directory to restore. Thanks in advance!

Interesting... maybe I'll run a test and confirm. Although after this nightmare I may not want to monkey around. Thanks for the support!

Thanks! Not that I'll ever monkey with it again, but if you decide against cache and turn it back off is there a way to remove user0? I'm asking more because I am curious how I went wrong.... its really not super relevant, as I have the most important answers!

User0 was not there from the beginning, only after cache was turned on. Unless its hidden and I somehow missed it. Either I did something wrong or something triggered it. Unfortunately I am more nervous now! What did I do....? "Tower-New" (below) is the box I had issues with and since started from scratch. As you can see, there is no user0 and I do have a "server" user share created myself. "Tower" (below) which is the old box I have been using for years with user shares also shows no user0. Also with the same "server" user share I created. Is this what you are referring to? The fact that you cannot copy between disk and user shares or risk data loss? Thats scary, fortunately I almost exclusively use user shares.... I am glad I know this now. Phew.... https://lime-technology.com/forums/topic/60961-is-there-a-simple-way-to-clean-up-user-shares/?tab=comments#comment-598522

Thank you for confirming my hunch about user versus user0. I've read it explained a lot of ways, and so far yours was the best and easiest for me to understand. Once I thought about it as two different views in a "logical filesystem" versus the actual files themselves it really clicked. Dropping the FUSE breadcrumb helped as well, this will give me something more to while the data moves back over the next 3 days!! I am too paranoid not to have multiple data backups. I did go the XFS route. I'm not sure why, but in cases of mass file loss I do not have a ton of confidence in undelete so despite it being much faster than a restore, I typically go to backup. Yes thank God for backups! I love the 3, 2, 1 philosophy. It will also take me 30 to 60 days after finalizing the new box before I am willing to tear down the old. For me it was worth buying another license to run these in parallel for a while. Even after the 60 or so days, I may strip the old box down to 1 drive and use it as a "dev" or "QA" box. So one or two more questions on this issue: - What triggers the creation of the user0? You need an "AND" condition. You need a cache drive configured AND a share set to a cache favorable setting (yes, prefer, only). But if only cache is installed OR a share is set cache favorable it will not. - If for some reason you tried cache but didn't like it, how do you get rid of user0 and ensure mover (or whatever process) will not create user0 again? I doubt I'll go backwards from cache, but I am more curios where I went wrong. Thanks a ton for the support!

First of all I want to thank the community a ton. I have found every answer I have needed for the past year on the forums without needing to post once! Until now.... A little background for everyone, I have successfully migrated from old hardware (i5 3570 / 16 GB / 5 x 2 TB HGST drives) on to my new box (2x Xeon 2650s, 64 GB 5 x 8 TB HGST Drives). I was able to move my appdata, get all of my dockers over to the new box as well as migrate from Crashplan Home to Pro. I credit these forums for everything from build, docker migration and finally data migration all being flawless. The good news, I have multiple copies of my data 3...2...1... backup scheme including an up-to-date synch between the old (i5) and new (xeon) boxes. So all is not lost. The bad news. I somehow nailed all of my data. A big part of the problem is I get addicted to these projects and stay up way too late and am not fresh, regardless. Here is what I did: 1. Installed SSD Cache. 2. Did not realize appdata share was set to "cache prefer" be default. 3. Noticed the yellow triangle before the appdata share and data copied on the cache drive. 4. Stopped array, turned appdata share to "cache no". 5. Reformatted SSD. 6. Started Array. 7. Eventually noticed "User0" which had never been there before. 8. Get irritated thinking I have duplicate data. 9. rm -rd /mnt/user0 -- before reading, or doing anything smart -- mind you its 2:00 AM at this point. 10. Watch all of my Shares slowly disappear from the GUI. 11. Rebuild new box from scratch. 12. Start data migration from old back to new. 13. Post here. So with all of that jargon out of the way (and I hope its not too long). Can someone help me understand the relationship between cache, mover and user0? I'm now very afraid to put cache back on once the data is migrated TLDR: - How does mover work with user0? If I understand properly, user0 represent files which are not in cache or to be moved to cache. - Any idea why mover created user0 after appdata was set to "cache no"? All other shares were "cache no." I assume once I turned on cache I started the process and was simply too late. - Why did the shares and data under user vaporize? Is it because I wiped user0, thus the files on user were cleaned as they were assumed to have been moved to cache? Thanks a ton in advance. I really want to move appdata and dockers to SSD in order to improve performance, specifically on plex. The library is growing and the tumbs can sometimes load kinda slow. Thank you!