Menu="Main:2"
Title="Cache Devices"
Tag="bullseye"
Cond="($var['fsState']=='Stopped' || $var['cacheSbNumDisks'])"
---
| _(Device)_ | _(Identification)_ | _(Temp)_. | _(Reads)_ | _(Writes)_ | _(Errors)_ | _(FS)_ | _(Size)_ | _(Used)_ | _(Free)_ | _(View)_ |
foreach ($disks as $disk):
if ($disk['type']=='Cache') echo "| |
";
endforeach;
?>
:help3
> **Colored Status Indicator** the significance of the color indicator at the beginning of each line in *Cache Devices* is as follows:
>
> Normal operation, device is active.
>
> Device is in standby mode (spun-down).
>
> New device.
>
> No device present, position is empty.
>
> **Cache** is a device, or device pool, *outside* the Unraid array. It may be exported for network access just
> like an Array device. Being outside the Unraid array results in significantly faster write access.
>
> There are two ways to configure the Cache:
>
> 1. As a single device, or
> 2. As a multi-device pool.
>
> When configured as a single device you may format the device using any supported file system (btrfs, reiserfs,
> or xfs). This configuration offers the highest performance, but at the cost of no data protection - if the
> single Cache device fails all data contained on it may be lost.
>
> When configured as a multi-device pool, Unraid OS will automatically select *btrfs-raid1* format (for both data
> and meta-data). btrfs permits any number of devices to be added to the pool and each copy of data is guaranteed
> to be written to two different devices. Hence the pool can withstand a single-disk failure without losing data.
>
> When [User Shares](/Settings/ShareSettings) are enabled, user shares may be configured to
> automatically make use of the Cache in order to
> speed up writes. A special background process called the *mover* can be scheduled to run
> periodically to move user share files off the Cache and onto the Array.
:end
:help4
> **Slots** select the number of device slots in your server designated for Cache devices.
:end