Question: I'm moving data from an unassigned device which is a bare HD in a USB 3.0 connected dock.

 

The data is coming across at 60-70MB/s but even though I have the share set to use the cache (yes) drive but it seems to not being used at all.

 

The data is going direct to the 8TB share without going through the 250GB cache and then MOVEed. 

 

Any help would really be appreciated. Thanks in advance!

The screenshot seems to indicate cache was written and has contents.

 

You are building parity so that might slow things down, though I wouldn't expect it to make much difference with cache writes.

 

1 hour ago, JCristina said:

The data is going direct to the 8TB share without going through the 250GB cache

Not sure what you mean by the 8TB share. Disk1 is 8TB, but that is not the size of the user share.

 

It would actually make more sense to talk about how much space is used by the user share (total files on array + cache), or how much free space the user share has (total free space of included array disks + free space on cache).

 

So having said all that, I have to wonder if you don't mean you are actually sharing disk1 and are writing directly to that. Are you writing directly to the array disk, or are you actually writing to a cache-yes user share?

 

Are you writing files that might already exist on an array drive? If so, then those overwrites would happen on the array drive.

 

Any more details you can provide? Diagnostics?

 

Thanks so much.. Really appreciate you taking the time. I think I didn't do a great job explaining. 

 

Yes, The parity drive is being rebuilt which will take like 7 days at 10MB/s  

 

As for the move, I used Krusader and basically selected all the directories I needed from the USB 3.0 attached drive (around 2.5TB or so) and dragged them into my /video/business/2019  folder which lives on the VIDEO share. I'm not writing to a specific drive,, (disk1 disk2, etc) simply to the array share set to high-water and use cache (YES) not NO or PREFERRED.

 

What I'm noticing is the data on the Cache Drive is not changing as the files are being copied over which I thought was strange. I thought the cache drive would fill and then a MOVE would be initiated to move the data from the cache (SSD) over to the array.

 

The share /video/business/2019 is located in the /media/user0/video/business/2019 to be specific. <-- is this correct or should it be /media/user/video/business/2019  ?

 

Thanks again. Hope this information helped a bit.  As you can tell, I'm new to this and want to make sure I don't screw it up while also making sure the array is working as it should be.

 

I added another screen shot so we can see that the cache has not changed but the other increased by 700+ GB out of the 2.5TB that is being moved.

Edited August 1, 20196 yr by JCristina

3 hours ago, JCristina said:

Yes, The parity drive is being rebuilt which will take like 7 days at 10MB/s

If you try to copy data to the array while a parity check/build is running they will SEVERELY affect each other's performance.   How fast does  the parity check run if you are not doing anything else on the array - I would expect it to be something like 10 times faster than the speed you quote!   If it is not then you should be looking into why as 10MB/s is extremely slow for a parity check running at full speed.   You would almost certainly be much better of timewise to let the parity check finish before doing any significand amount of data copying.

 

3 hours ago, JCristina said:

The share /video/business/2019 is located in the /media/user0/video/business/2019 to be specific. <-- is this correct or should it be /media/user/video/business/2019  ?

The question is what have you mapped /media to at the Unraid level?   If it is /mnt then that would explain your symptoms.   At the Unraid level /mnt/user is where User Shares are located.   /mnt/user0 is a special location that only includes the array parts of the User Share and specifically excludes the cache disk.   It is also deprecated so could well no longer be available in a future Unraid release.

 

Note that mapping /media to /mnt is potentially dangerous.   This is because if you ever try to copy a /mnt/diskX location to/from a /mnt/user location in the same copy or move command you are liable to end up with data loss   You may be better of mapping /media in Krusader to /mnt/user in Unraid which avoids the possibility of doing this.

 

9 hours ago, JCristina said:

Yes, The parity drive is being rebuilt which will take like 7 days at 10MB/s

This is not normal. Writing to an array disk while building parity will slow it down considerably so that might be what is going on with that. I usually estimate 2-3 hours per TB of parity, so 8TB should complete in about 1 day.

 

I suggest you quit doing anything at all until parity is built.

 

9 hours ago, JCristina said:

I thought the cache drive would fill and then a MOVE would be initiated to move the data from the cache (SSD) over to the array.

Normally the move happens on a schedule, which you can set. The default is once per day in the middle of the night. There is also a plugin that will let you specify moves based on cache free space.

 

9 hours ago, JCristina said:

The share /video/business/2019 is located in the /media/user0/video/business/2019 to be specific. <-- is this correct or should it be /media/user/video/business/2019  ?

It is still unclear, to me at least, what you are doing. The fact that you even mention user0 makes me suspect you have excluded cache as itimpi mentioned.

 

Post the docker run command you have for krusader, as explained in the very first link in the Docker FAQ:

 

https://forums.unraid.net/topic/57181-real-docker-faq/

 

That will clarify some things for us.

 

Also, post your diagnostics so we can take a look and see if there is something else going on with your very slow parity build. Tools - Diagnostics. Attach complete diagnostics zip file to your next post.

110% correct. Once the file transfers were complete the Parity sync speed popped from 10MB/s to 115-120MB/s.  Here's a screen shot!