ondjultomte
Contributor
- Joined
- Aug 10, 2015
- Messages
- 117
I added a l2arc to see if I could reduce the bussy time on the drivers. My FreeNAS is a seedbox.
kristoffer@freenas:~ % zpool status tank
pool: tank
state: ONLINE
scan: scrub repaired 0 in 9h49m with 0 errors on Sun Jan 17 09:49:07 2016
config:
NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
gptid/68cf78ef-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/6b4ac5c1-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/6dbfbdba-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/7040d2ea-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/72c9b0f2-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/754e37fa-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
cache
gptid/6fe8f9ce-c6f1-11e5-adf2-000c2975a9ee ONLINE 0 0 0
errors: No known data errors
kristoffer@freenas:~ % arcstat.py -f l2size
l2size
622G
kristoffer@freenas:~ %
how come the arc is reported as 622 GB?!
kristoffer@freenas:~ % gpart show | grep da1
=> 34 188743613 da1 GPT (90G)
da1 at mpt0 bus 0 scbus2 target 1 lun 0
da1: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device
da1: Serial Number 6000c29eccfe5afbe8219d62e5256d4c
da1: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit)
da1: Command Queueing enabled
da1: 92160MB (188743680 512 byte sectors: 255H 63S/T 11748C)
da1: quirks=0x40<RETRY_BUSY>
What have I done? :)
kristoffer@freenas:~ % zpool status tank
pool: tank
state: ONLINE
scan: scrub repaired 0 in 9h49m with 0 errors on Sun Jan 17 09:49:07 2016
config:
NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
gptid/68cf78ef-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/6b4ac5c1-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/6dbfbdba-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/7040d2ea-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/72c9b0f2-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
gptid/754e37fa-8016-11e5-ac06-000c2975a9ee ONLINE 0 0 0
cache
gptid/6fe8f9ce-c6f1-11e5-adf2-000c2975a9ee ONLINE 0 0 0
errors: No known data errors
kristoffer@freenas:~ % arcstat.py -f l2size
l2size
622G
kristoffer@freenas:~ %
how come the arc is reported as 622 GB?!
kristoffer@freenas:~ % gpart show | grep da1
=> 34 188743613 da1 GPT (90G)
da1 at mpt0 bus 0 scbus2 target 1 lun 0
da1: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device
da1: Serial Number 6000c29eccfe5afbe8219d62e5256d4c
da1: 320.000MB/s transfers (160.000MHz DT, offset 127, 16bit)
da1: Command Queueing enabled
da1: 92160MB (188743680 512 byte sectors: 255H 63S/T 11748C)
da1: quirks=0x40<RETRY_BUSY>
What have I done? :)
Attachments
Last edited: