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.

[SOLVED] Cache drive doesn't seem to be used

Featured Replies

Hi -

 

I just dropped a 120 GB cache drive into my 5.0-rc16c unraid server. The server picked it up and formatted it, but it doesn't seem to be used. I have it set to "use cache disk: yes". The min free space is the default, 20GB, I believe.

 

when I copy some files over the network to "//tower/Movies", i can immediately find them in "/mnt/disk1/Movies" or "/mnt/disk2/Movies". The cache drives always appears to have exactly zero files or folders on it.

 

Here is the syslog of the cache drive, if it's helpful. I feel like there must be something silly that I've missed.

 

Thanks

matt

 

Aug 18 16:54:49 Tower kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Aug 18 16:54:49 Tower kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Aug 18 16:54:49 Tower kernel: Mount-cache hash table entries: 512
Aug 18 16:54:49 Tower kernel: PCI: pci_cache_line_size set to 64 bytes
Aug 18 16:54:49 Tower kernel: ehci-pci 0000:00:1d.7: cache line size of 32 is not supported
Aug 18 16:54:49 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through (Drive related)
Aug 18 16:54:49 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through (Drive related)
Aug 18 16:54:49 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through (Drive related)
Aug 18 16:54:49 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Aug 18 16:54:49 Tower kernel: scsi5 : ata_piix (Drive related)
Aug 18 16:54:49 Tower kernel: ata5: SATA max UDMA/133 cmd 0xc080 ctl 0xc000 bmdma 0xb800 irq 19 (Drive related)
Aug 18 16:54:49 Tower kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Aug 18 16:54:49 Tower kernel: ata5.01: ATA-9: Samsung SSD 840 Series, S19HNSAD628137X, DXT08B0Q, max UDMA/133 (Drive related)
Aug 18 16:54:49 Tower kernel: ata5.01: 234441648 sectors, multi 16: LBA48 NCQ (depth 0/32) (Drive related)
Aug 18 16:54:49 Tower kernel: ata5.01: configured for UDMA/133 (Drive related)
Aug 18 16:54:49 Tower kernel: scsi 5:0:1:0: Direct-Access     ATA      Samsung SSD 840  DXT0 PQ: 0 ANSI: 5 (Drive related)
Aug 18 16:54:49 Tower kernel: sd 5:0:1:0: [sdf] 234441648 512-byte logical blocks: (120 GB/111 GiB) (Drive related)
Aug 18 16:54:49 Tower kernel: sd 5:0:1:0: [sdf] Write Protect is off (Drive related)
Aug 18 16:54:49 Tower kernel: sd 5:0:1:0: [sdf] Mode Sense: 00 3a 00 00 (Drive related)
Aug 18 16:54:49 Tower kernel: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Aug 18 16:54:49 Tower kernel: sd 5:0:1:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Aug 18 16:54:49 Tower kernel: sd 6:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Aug 18 16:54:49 Tower kernel: sd 6:0:1:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Aug 18 16:54:49 Tower kernel: sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA (Drive related)
Aug 18 16:54:49 Tower kernel:  sdf: sdf1 (Drive related)
Aug 18 16:54:49 Tower kernel: sd 5:0:1:0: [sdf] Attached SCSI disk (Drive related)
Aug 18 16:54:49 Tower emhttp: Samsung_SSD_840_Series_S19HNSAD628137X (sdf) 117220824 (Drive related)
Aug 18 16:54:49 Tower emhttp: shcmd (14): /usr/local/sbin/set_ncq sdf 1 $stuff$> /dev/null (Drive related)
Aug 18 16:54:49 Tower emhttp: shcmd (15): /usr/sbin/hdparm -S0 /dev/sdf $stuff$> /dev/null (Drive related)
Aug 18 16:54:50 Tower emhttp: shcmd (31): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/sdf1 /mnt/cache |$stuff$ logger (Drive related)
Aug 18 16:54:50 Tower kernel: REISERFS (device sdf1): found reiserfs format "3.6" with standard journal (Routine)
Aug 18 16:54:50 Tower kernel: REISERFS (device sdf1): using ordered data mode (Routine)
Aug 18 16:54:50 Tower kernel: REISERFS (device sdf1): journal params: device sdf1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine)
Aug 18 16:54:50 Tower kernel: REISERFS (device sdf1): checking transaction log (sdf1) (Drive related)
Aug 18 16:54:50 Tower kernel: REISERFS (device sdf1): Using r5 hash to sort names (Routine)
Aug 18 16:54:50 Tower emhttp: shcmd (32): chmod 777 '/mnt/cache' (Other emhttp)
Aug 18 16:54:50 Tower emhttp: shcmd (33): chown nobody:users '/mnt/cache' (Other emhttp)
Aug 18 17:58:11 Tower emhttp: shcmd (44): /usr/sbin/hdparm -y /dev/sdf $stuff$> /dev/null (Drive related)
Aug 18 18:06:44 Tower unmenu[1120]: Processing section "[cache]"

You must also enable "Use cache disk" for each unRaid Share you want to have use it.

  • Author

Yup, that was it. New files are correctly appearing in mnt/cache and not mnt/diskx.

 

Now, we'll have to see if the default mover cron job works well.

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.