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 the Cache Drive Not Always Used

Featured Replies

Sometimes when I do a file copy to a share, the file is written directly to the share and data disk, bypassing the cache drive.  This seems to happen only on fairly small files - say 30 MB or less.  The cache drive does spin up, but so does the correct data disk.  The cache drive shows the directory where the files should be, but the directory is empty.  The data disk then shows the copied file already on the disk.

 

Is there some sort of logic that bypasses the cache drive or moves files immediately on files of a certain size?

 

 

Ehm. No.

 

Cache drive is not used when writing directly to a disk share though, only when writing to a user share.

 

Also when you copy on the server itself (thru console) it is not used.

  • Author

Man, I swear this is happening!  LOL.  I must be going crazy.  I backed up a file to a share (done this several times to prove I am not crazy), both the cache and the actual physical disk spin up, the file on the physical disk shows the current date and time, the cache disk is empty.  This only happens on pretty small files.

 

OK, well, on to better things - just driving me nuts!

If the file exists already on the data disk then the cache is not used.

  • Author

If the file exists already on the data disk then the cache is not used.

 

Good to know. So if the file is just an updated/modified version of an existing file it gets written immediately?  I did not know that, and maybe I wasn't crazy!  ;D

It would appear that it magically appears in the user share because that's the magic of the cache drive, then later it will actually move the file and the user is none the wiser.

 

However if you check the Disk Share it shouldn't be there until its moved.

Sometimes when I do a file copy to a share, the file is written directly to the share and data disk, bypassing the cache drive.  This seems to happen only on fairly small files - say 30 MB or less.  The cache drive does spin up, but so does the correct data disk.  The cache drive shows the directory where the files should be, but the directory is empty.  The data disk then shows the copied file already on the disk.

 

Is there some sort of logic that bypasses the cache drive or moves files immediately on files of a certain size?

 

You also have to make sure you have the cache drive enabled for the share. See the screenshot :) (I assume you have this done, but better safe than sorry).

Cache_Drive_No.PNG.b516870e77a67912af3e2c59fcf79fe0.PNG

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.