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.

Is this even a good idea? Bypassing fuse writing to cache locations

Featured Replies

Came across this video the other day.

 

 

I'm wondering if this is even a good idea or not. Would this have any effect on share marked for cache that 'should' be moved to the array? Are they still moved or not?

  • Community Expert
2 minutes ago, aglyons said:

Came across this video the other day.

 

 

I'm wondering if this is even a good idea or not. Would this have any effect on share marked for cache that 'should' be moved to the array? Are they still moved or not?

this is being added in 6.12 as exclusive shares. They cannot have a secondary location.

  • Author

would be nice if there was the best of both worlds. Write a DL to the cache but have the mover put it on the array.

 

But, still bypass fuse for the write.

1 hour ago, aglyons said:

would be nice if there was the best of both worlds. Write a DL to the cache but have the mover put it on the array.

 

But, still bypass fuse for the write.

You can't bypass fuse for the write if there's a chance the file already exists on the array

1 hour ago, aglyons said:

Would this have any effect on share marked for cache that 'should' be moved to the array? Are they still moved or not?

The problem with mapping a docker container directly to a cache drive is that when the mover runs, any files will disappear from the container's perspective.

 

That may be major, minor, or non-issue depending on the container and what type of file is disappearing.

 

Seems safe for shares that are cache-only

Edited by veri745

  • Author
46 minutes ago, veri745 said:

The problem with mapping a docker container directly to a cache drive is that when the mover runs, any files will disappear from the container's perspective.

 

That may be major, minor, or non-issue depending on the container and what type of file is disappearing.

 

Seems safe for shares that are cache-only

Ok, there's a gotcha!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.