|
Description
|
When you use a vdev for a pool that is a UFS file (i.e. mkfile -n 7g /export/home1/zfsclonefile; zpool create zone /export/home1/zfsclonefile), FM will report that the 'The pool data is unavailable'.
I think the reason for this is the /export/home1 file system is not mounted at the time FM is checking zfs vdevs. When the system comes up, all is good, and the 'zpool status -x' says all is OK too. here is what is reported:
xxxxx W-MSG-ID: ZFS-8000-CS, TYPE: Fault, VER: 1, SEVERITY: Major
EVENT-TIME: Fri Mar 17 11:17:36 PST 2006
PLATFORM: W1100z/2100z, CSN: 0502EM400E, HOSTNAME: ts-w1100z-3
SOURCE: zfs-diagnosis, REV: 1.0
EVENT-ID: aa8a5864-f150-c4a6-d136-b9d96a8096a7
DESC: A ZFS pool failed to open. Refer to http://sun.com/msg/ZFS-8000-CS for more information.
AUTO-RESPONSE: No automated response will occur.
IMPACT: The pool data is unavailable
REC-ACTION: Run 'zpool status -x' and either attach the missing device or
restore from backup.
This is actually one case of a more general problem. The ZFS DE
should not be solving cases which apply to a resource that is no
longer valid on the current system. In addition, for ZFS in
particular, it should also check that the vdev/pool is still in
some unusable state.
|
