rcrh

I have an SSD that holds my docker image & my appdata fold. Over time the used space on SSD has crept up & I can't figure out why. I've run mover so it isn't files waiting to be moved to the array. If I go to the cache drive through my windows share I see the docker image at about 15 gig and the appdata folder that has about 23gig. Yet in unRaid the Main/Cache Device screen shows 121gig used. Any idea what might be eating up the 83gig?

Oddly, I don't have that directory on my server. I'm running 6.8.2 I'm also not sure what you're suggesting I do.

Oddly, I don't have that directory on my server. I'm running 6.8.2 I'm also not sure what you're suggesting I do.

Is it possible to trigger the mover immediately after CA Backup completes? I have the pluggin creating its data on a share that's set to "use cache=yes" and I'd rather not leave my backup sitting on the cache drive until the scheduled mover. I guess I could create a new share that doesn't use the cache but then the backup will take significantly longer.

I knew "what" the parity drive does but I didn't realize it did this without having an underlying format to the drive. Honestly I hadn't thought it through this deeply. Thanks for the link.

I'm just finishing up the process of migrating my drives from ReiserFX to xFS. I've shuffled data around and slowly reformatted each drive. As I final step I assumed I'd have to reformat my parity drive and rebuild it. However, when I stopped the array and clicked on the drive tab for my parity drive I couldn't find an option for selecting the format of the drive. Did my parity drive automatically move to xFS when I moved from unraid 5.x to 6.x or am I not looking in the right place. Thanks in advance.

That's one of the reasons I wanted to get off of ReiserFS, Thanks,

I'm in the middle of migrating from ReiserFS to xFS by moving data off of each drive, formating it, and then moving data back. So far I've been able to do this within my array (6tb parity, 7x4tb data, 1x6tb data) but I'm not down to my 6tb drive. To get all of the data off of it I'll be leaving only about 100gb on each data drive. Do I run any performance or security risks by filling my array drives this full? I could probably find an external drive somewhere and move the data off of the server but I'd rather not. Thanks in advance.

Doesn't "high water mark" fill one drive until it hits the high water mark and only then does it move onto the next drive? So with 14tb drives you're going to get 7tb on disk1 before anything is written to the next disk in the share.

Yup. Seems I got this all wrong. I'll be back later. *** I think I got confused because even right after the mover completed I still had files in appdata on the array. It didn't occur to me that it would be files that were in use during the mover operation. I shut down all of my dockers and ran Mover again and now everything in appdata has been moved from my array. So now I'll go and study the CA backup plugin like I should have in the first place. Thanks all.

I've just set up an SSD cache drive & I've set up my appdata share as "preferred". My understanding is that each time the mover is run everything syncs between the cache drive & the parity protected array while also ensuring that routine access to the files will be from the cache drive for performance. If this is right I have two questions: 1) Since the mover keeps all of my appdata backed up what is the point of the CA backup plugin? 2) Is there any reason to NOT put the docker image in the appdata share so that is also "moved" to the array and then protected by parity? Thanks.

thanks. That's a lot of reading but I found what I'm looking for.

Still working through the process. I finished my first copy using MC but I'm not sure how to do a verify. Got another hint? Thanks!

Here is what I was looking at. Part way down is a section on "changing file systems" https://wiki.unraid.net/UnRAID_6/Storage_Management#File_System_Management What does the second part of your second point mean? ".. and it's the drive that has a full copy performed"? Finally, copying and verifying makes a lot more sense then moving. Thanks for that point.

My server is old enough that its default file system is still RieserFS. I want to go through a process of upgrading to xFS. I've gone through the wiki and it walks me through the steps of formating a new drive, moving data to create an empty RieserFS drive and then reformating that one. But, I'm wonder when I should change the DEFAULT FS for the system. If I do that at the start of this process will it impact any of the existing drives? I don't want to accidentally trigger a process that wipes out data on existing RieserFS drives. Thanks.

Thanks for that. I'll look at the CA as soon as I get the controller for my SSD.

For those using an ssd cache drive for their docker apps what process do you follow to keep your apps and their data backed up?

the link above was for the 2 mSATA card but I found this one. https://www.amazon.co.uk/SEDNA-Express-mSATA-Adapter-SATA/dp/B00M0R19OC/ref=sr_1_2?keywords=sedna+msata&qid=1574192500&s=computers&sr=1-2 Heck it even has a bonus SATA port on it!

Thanks for the extra steps. I forgot that I needed to turn off the service as well as stop the running dockers. Concerning the mSATA I already have an mSATAT to SATA adapter from IOCrest that I was going to figure out how to mount but maybe I'll look at a dedicated PCIe card for it. I had a quick look at the IOCrest and they do have a card that fits a x1 slot. It only takes one mSATA but that would still leave me a x4 slot for future expansion. The card that takes 2 mSATAs requires at least a x2 slot. Thanks again for all the help.

II currently have it set to: /mnt/disk1/docker.img so my steps should be: 1) shut down all dockers 2) move the image file 3) change docker vDisc location to /mnt/disk3/docker.img 4) restart the dockers. That seems pretty straight forward. But, since I have a256gb mSATA SSD sitting around I might shop for another SATA controller first. I could use it for my docker image, appdata, & a cache. Thanks for the suggestions & pointers.

Do I have any to change anything in the docker settings tab after I move the image file (and before I restart the dockers)?

I'd love to if I had anywhere to attach it. Perhaps you have a suggestions for an inexpensive PCi x4 controller I could add?

I currently have an 7 disc array (plus 1 disc for parity) so my 10 gig docker image is located on my disc1. My Appdata is share is on disc3. I'm trying to minimize my drive activity so I'm thinking about moving my image to disc3, which is my recently upgraded drive. Is this possible? Would it show things down since the docker apps & appdata would be on the same physical disc? Am I worrying too much about disc wear & tear? I see that the general guidance is to put the docker image on a cache drive but I don't have one. Thanks in advance for any suggestions.

I bet I looked at most of those threads But I'll take your advice and assume this is a plex issue and not a container issue. Thanks.

I hope someone else finds that wiki, 'cause I can't find it. Here's what I've done. 1) in \appdata\plex\Library\Application Support\Plex Media Server I created a folder called Profiles 2) found the android.xml profile on my windows instalation of PMS and edited it so that all references to AAC were changed to AC3 and put it in the newly created Profiles folder 3) restarted plex server 4) started a file with DTS audio and I'm still getting stereo transcoding.