Why do I have a mirrored directory on cache and share?

[fortytwo]

I'm trying to change my cache drive and, as part of that, I've been working on finally moving all my application config to a user share so I don't have to worry about losing it if the cache drive fails.  What's weird is that I've noticed that both /mnt/cache/appdata and /mnt/user/appdata point to the same directory (as in, create a file in one of those dirs and the other will see it).  Neither directory is a symlink.  `stat` on each shows:

 

root@Tower:/mnt/cache# stat /mnt/cache/appdata/
  File: /mnt/cache/appdata/
  Size: 168             Blocks: 0          IO Block: 4096   directory
Device: 881h/2177d      Inode: 249006      Links: 5
Access: (0777/drwxrwxrwx)  Uid: (   99/  nobody)   Gid: (  100/   users)
Access: 2017-05-31 15:18:39.000000000 -0700
Modify: 2019-03-03 13:45:15.000000000 -0800
Change: 2019-03-03 13:45:15.000000000 -0800
 Birth: -
root@Tower:/mnt/cache# stat /mnt/user/appdata/
  File: /mnt/user/appdata/
  Size: 168             Blocks: 0          IO Block: 4096   directory
Device: 1fh/31d Inode: 10          Links: 1
Access: (0777/drwxrwxrwx)  Uid: (   99/  nobody)   Gid: (  100/   users)
Access: 2017-05-31 15:18:39.000000000 -0700
Modify: 2019-03-03 13:45:15.000000000 -0800
Change: 2019-03-03 13:45:15.000000000 -0800
 Birth: -

 

I just want to know if this mirroring is intentionally done by something in unraid before I go blasting things away?

[BRiT]

Thats how it always worked.

 

/mnt/user/foo includes everything from /mnt/cache/foo

/mnt/user0/foo does not.

[cpshoemake]

It's normal. The /mnt/user/appdata/ mount is the conglomeration of /mnt/cache/appdata/, /mnt/disk1/appdata/, /mnt/disk2/appdata/, etc.

 

Here is the step-by-step for replacing a cache drive: https://wiki.unraid.net/Replace_A_Cache_Drive

 

To store appdata on the array, just set "Use cache disk:" to "No" from the Shares page.

[fortytwo]

Gotcha, thanks.  So how can I "convert" it at this point?  How can I create /mnt/user/appdata such that the directory doesn't live on the cache?  I set "use cache disk" to no, but nothing seemed to change.

[itimpi]

1 minute ago, fortytwo said:

Gotcha, thanks.  So how can I "convert" it at this point?  How can I create /mnt/user/appdata such that the directory doesn't live on the cache?  I set "use cache disk" to no, but nothing seemed to change.

Turning on the Help in the GUI might help to see how the settings interact with placement of new files and what mover then does (if anything).    You first need to set Use Cache=Yes; turn off the docker and VM services (if you are using them); and then manually run mover.   When that completes you can change the setting to Use Cache=No and (if needed) re-enable the docker and VM services.

[BRiT]

Let me ask a question first … What do you have in your AppData directory that needs to be parity protected? The only items I have there are docker configurations which are backed up using the plugin "CA Backup AppData".

[fortytwo]

 

4 minutes ago, itimpi said:

Turning on the Help in the GUI might help to see how the settings interact with placement of new files and what mover then does (if anything).    You first need to set Use Cache=Yes; turn off the docker and VM services (if you are using them); and then manually run mover.   When that completes you can change the setting to Use Cache=No and (if needed) re-enable the docker and VM services.

Thanks, I'll take a look at that.

 

3 minutes ago, BRiT said:

Let me ask a question first … What do you have in your AppData directory that needs to be parity protected? The only items I have there are docker configurations which are backed up using the plugin "CA Backup AppData".

 

I don't have that installed, so guess I'll have to look into that as well.

 

 

 

Edited March 3, 2019 by fortytwo

[trurl]

Why do you want your appdata on the array, where your applications will be impacted by the slower parity writes, and your applications will keep parity and array disks spinning?

 

There are reasons (I just mentioned them😉 ) why appdata defaults to being on cache.