Hi I am running 6.12.8.  

 

I ran into the following two problems today after doing some troubleshooting:

 

Quote

 

Dec 10 22:16:00 nas root: Fix Common Problems: Warning: Share isos set to cache-only, but files / folders exist on the array

Dec 10 22:16:00 nas root: Fix Common Problems: Warning: Share system set to cache-only, but files / folders exist on the array

 

 

Googling around and common problems, it seemed pretty straightforward.  Set secondary storage to array and mover action to go from array -> cache (called docker_vm).   Then run mover.  

 

This mostly fixed it.  But im left with a single file, the docker.img file (screenshot), which is present in both the cache pool (docker_vm) and the array itself (disc1).  How does the system know which one to use?  My docker setting is pointed to 

/mnt/user/system/docker/docker.img

 

But more importantly, how do I fix it?  Is it just a matter of stopping docker and simply deleting the file from disk1 using dynamix file manager (is deleting straight from the disk level ok?).  

 

 

Edited December 11, 20241 yr by oliver

Did you disable the docker service before running mover?   It would keep the docker.img file open and prevent it being moved.   However if it exists in both locations then it would be ignored by mover.

 

Are you sure you have the file in both locations?    Your screen shot suggests it might be only on disk1.   Normally the /mnt/user location would use the copy on a pool in preference to one on the array.   

check your share tab.
?did you add secod storage optinon?

check your docker setting for the file path your using.

 

delete and setup the pathing

14 minutes ago, itimpi said:

Did you disable the docker service before running mover?   It would keep the docker.img file open and prevent it being moved.   However if it exists in both locations then it would be ignored by mover.

 

Are you sure you have the file in both locations?    Your screen shot suggests it might be only on disk1.   Normally the /mnt/user location would use the copy on a pool in preference to one on the array.   

 

 

yeah i had the docker and vm services turned off before running mover.  everything else moved out.  this was the only file that existed in both locations but that makes sense why mover didn't do anything.  im honestly not sure how i even ended up in this state with docker.img duplicated, i had some array issues and had to do disable docker, but it didn't disable properly.  the containers are all running properly now though i'd just like to do some cleanup.  

 

i've confirmed docker.img is in both locations:

/mnt/docker_vm/system/docker

/mnt/disk1/system/docker

 

They have different checksums but the filesize is the same.  I'm guessing just bite the bullet and delete the one on disk1?  Is it safe for parity/disk operations to delete a file directly from disk?

Edited December 11, 20241 yr by oliver

delete the one that is not shown in your docker settings as a disk path

Just now, bmartino1 said:

delete the one that is not shown in your docker settings as a disk path

 

the problem is the one in my path is technically both of them - it's the user share path:

 

/mnt/user/system/docker/docker.img

 

sounds like per @itimpi in this scenario, it should be picking the docker_vm one but im not sure how to validate this

ok. then I would recomend setting docker off

delete vdisk

check both location and delete teh file is it exisit.

then go bakc to settings > docker and make a new docker vdisk set at a disk share per your user script? perhaps.

then under the docker tab go to add container and apply to bring back all your docker no data loss and back to 1 docker img file.

You could delete the one that has the oldest modification date as that would be the one not currently being used.

2 hours ago, itimpi said:

You could delete the one that has the oldest modification date as that would be the one not currently being used.

oh wow i didnt even notice that before, the one on the array is last modified way back in august!  

 

is it safe to remove a file from /mnt/disk1 directly, no issues with disk level file changes?  

27 minutes ago, oliver said:

is it safe to remove a file from /mnt/disk1 directly, no issues with disk level file changes?

Yes.

7 minutes ago, itimpi said:

Yes.

thanks, deleted it and everything is all set now