Failed disk showing up as online

[freenascod]

Hey guys, I apologize if this issue has been covered before, but I think I've found a bug in FreeNAS 8.3.0. I'm setting up a new box and have configured 5 drives in a RAIDz1 (full disclosure, the underlying hardware is a PERC6/i with each disk in an individual RAID0. I know this is not the recommended config, but the PERC6/i card has no JBOD mode). I dumped a bunch of data on it (which went well), and am testing out disaster recovery. I pulled the 5th drive in the array and the following things happened:

1.) Volume stayed online.
2.) The console logged the following messages:

Dec 20 06:50:57 freenas kernel: mfi0: 5616 (409301454s/0x0002/WARN) - Removed: PD 04(e0x20/s4)
Dec 20 06:50:59 freenas kernel: mfi0: 5617 (409301454s/0x0002/info) - Removed: PD 04(e0x20/s4) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=1221000004000000,0000000000000000
Dec 20 06:50:59 freenas kernel: mfi0: 5618 (409301454s/0x0002/info) - State change on PD 04(e0x20/s4) from ONLINE(18) to FAILED(11)
Dec 20 06:50:59 freenas kernel: mfi0: 5619 (409301454s/0x0001/info) - State change on VD 04/4 from OPTIMAL(3) to OFFLINE(0)
Dec 20 06:50:59 freenas kernel: mfid4: detached
Dec 20 06:50:59 freenas kernel: mfi0: 5620 (409301454s/0x0001/FATAL) - VD 04/4 is now OFFLINE
Dec 20 06:50:59 freenas kernel: mfi0: 5621 (409301454s/0x0002/info) - State change on PD 04(e0x20/s4) from FAILED(11) to UNCONFIGURED_BAD(1)
Dec 20 06:50:59 freenas kernel: mfi0: 5622 (409301455s/0x0041/info) - Deleted VD 04/4

3.) The GUI displayed an amber light in the top right corner with the following message:

WARNING: The volume BigPool (ZFS) status is UNKNOWN: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'.

So far, so good, right? But when I click on the pool in the GUI it says that the status is healthy. Then when I click on the status button, every disk shows as online. So in a production scenario, assuming I missed the console messages, I'd have no way of knowing which disk was dead. Did I hit a bug here, or am I missing something? Thanks very much for any assistance you can offer!

 

[William Grzybowski]

It is a well-known bug in freeBSD ZFS, it wont take the device as UNAVAIL until a lot of reads/writes occur in the pool.

 

[freenascod]

Thanks very much for the answer, William. I'll keep my fingers crossed that maybe it gets fixed in a future release. In the meantime I am going to see what other ways I can force this to alert me. Thanks!