This may be
not a compatibility issue, but it's worth sharing …
- Code: Select all
[root@freenas] ~# date
Fri Sep 13 18:14:05 BST 2013
[root@freenas] ~# zpool status -v
pool: bingo
state: ONLINE
scan: scrub repaired 0 in 0h29m with 0 errors on Fri Sep 13 07:33:12 2013
config:
NAME STATE READ WRITE CKSUM
bingo ONLINE 0 0 0
gptid/f5e63821-1a55-11e3-8043-0024e80a5517 ONLINE 0 0 0
gptid/5427612b-1b10-11e3-a61c-0024e80a5517 ONLINE 0 0 0
errors: No known data errors
pool: tall
state: ONLINE
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Fri Sep 13 18:09:57 2013
34.9G scanned out of 3.54T at 143M/s, 7h8m to go
91.8M resilvered, 0.96% done
config:
NAME STATE READ WRITE CKSUM
tall ONLINE 0 0 0
gpt/ZFS_ROCKS! ONLINE 0 0 0
gptid/99056308-f5e2-4314-852c-4da04732a2d0 ONLINE 0 0 0 (resilvering)
errors: Permanent errors have been detected in the following files:
… then a few minutes later,
- Code: Select all
[root@freenas] ~# date
Fri Sep 13 18:17:21 BST 2013
[root@freenas] ~# uptime
6:17PM up 9 mins, 1 user, load averages: 0.23, 0.32, 0.25
[root@freenas] ~# zpool status -v
pool: bingo
state: ONLINE
scan: scrub repaired 0 in 0h29m with 0 errors on Fri Sep 13 07:33:12 2013
config:
NAME STATE READ WRITE CKSUM
bingo ONLINE 0 0 0
gptid/f5e63821-1a55-11e3-8043-0024e80a5517 ONLINE 0 0 0
gptid/5427612b-1b10-11e3-a61c-0024e80a5517 ONLINE 0 0 0
errors: No known data errors
pool: tall
state: UNAVAIL
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Fri Sep 13 18:09:57 2013
257G scanned out of 3.54T at 588M/s, 1h37m to go
92.1M resilvered, 7.09% done
config:
NAME STATE READ WRITE CKSUM
tall UNAVAIL 22 4 0
gpt/ZFS_ROCKS! ONLINE 0 0 0
gptid/99056308-f5e2-4314-852c-4da04732a2d0 FAULTED 1 19 0 too many errors (resilvering)
errors: Permanent errors have been detected in the following files:
<metadata>:<0x0>
<metadata>:<0x11b6>
/mnt/tall/com.apple.backupd/gpes3e-gjp4.sparsebundle/bands/82db
/mnt/tall/com.apple.backupd/gpes3e-gjp4.sparsebundle/bands/83db
/mnt/tall/com.apple.backupd/gpes3e-gjp4.sparsebundle/bands/8717
/mnt/tall/com.apple.backupd/gpes3e-gjp4.sparsebundle/bands/83dc
/mnt/tall/com.apple.backupd/gpes3e-gjp4.sparsebundle/bands/82dd
/mnt/tall/com.apple.backupd/gpes3e-gjp4.sparsebundle/bands/8cd3
^C
[root@freenas] ~#
*** FINAL System shutdown message from root@freenas.local ***
System going down IMMEDIATELY
- FAULTED with too many errors whilst the two disks were attached to what appear to be separate controllers
- I don't get that behaviour when the same pool is used on a USB 2.0 hub with ZEVO on a MacBookPro5,2 so I chose to shutdown the NAS.
And so on, repeatedly; FreeNAS on the Dell seemed unable to cope for more than a few minutes with a pool that's otherwise reliable.
I no longer trusted the NAS to attempt the resilver, so I returned the pool to ZEVO where resilver completed without error.
Yesterday I asked a related question in
irc://chat.freenode.net/#freenas … I'll continue to seek advice there.