Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Share uses cache despite setting

Featured Replies

  • Community Expert

So I'm in the midst of setting up another unRAID system and I have a share called movies which every time I move something in there gets put on the cache drive, despite the setting "use cache disk" set to No. I'm moving from a share temp (cache only) on an SSD to a share on the array. So a manual move from:

 

/mnt/user/temp (use cache disk: only) 

to

/mnt/user/movies (use cache disk: no) 

becomes

/mnt/cache/movies/...

 

None of my dockers reference /mnt/cache...

 

Not sure what going here or how to get back the normal behaviour, using 6.5.

Screen Shot 2018-03-19 at 2.30.06 PM.png

Screen Shot 2018-03-19 at 2.30.21 PM.png

Edited by joelones

1 minute ago, joelones said:

/mnt/user/temp (use cache disk: only) 

to

/mnt/user/movies (use cache disk: no) 

becomes

/mnt/cache/movies/...

 

When using the command line, some of the use cache settings become either strange or convoluted.

 

In your case, you're moving from /mnt/user/temp to /mnt/user/movies.  Linux (actually  every OS in existence) is smart enough to realize that the mount point for both the temp and movies is /mnt/user, so it does a simple rename operation.  Net result is that your file winds up on the cache drive in apparent violation of the rules.

 

Two ways around this normal behavior

 

copy from /mnt/user/temp to /mnt/user/movies

 

Or,

 

move from /mnt/cache/temp to /mnt/user/movies.  Very important here though is since you mixing disk shares and user shares to make 100% that the share name (in this case, temp and movies) is NOT identical.  Otherwise you will corrupt your files.

 

  • Author
  • Community Expert
4 minutes ago, Squid said:

 

When using the command line, some of the use cache settings become either strange or convoluted.

 

In your case, you're moving from /mnt/user/temp to /mnt/user/movies.  Linux (actually  every OS in existence) is smart enough to realize that the mount point for both the temp and movies is /mnt/user, so it does a simple rename operation.  Net result is that your file winds up on the cache drive in apparent violation of the rules.

 

Two ways around this normal behavior

 

copy from /mnt/user/temp to /mnt/user/movies

 

Or,

 

move from /mnt/cache/temp to /mnt/user/movies.  Very important here though is since you mixing disk shares and user shares to make 100% that the share name (in this case, temp and movies) is NOT identical.  Otherwise you will corrupt your files.

 

 

Makes sense. Thanks.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.