Last updated on MARCH 08, 2017
Applies to:Solaris Operating System - Version 10 11/06 U3 and later
Solaris x64/x86 Operating System - Version 10 11/06 U3 and later
Information in this document applies to any platform.
Explorer (that does the same "zpool import") as part of it's run can cause the similar panic on these hosts
The system would panic with:
panic string: assertion failed: P2PHASE(size, sizeof (uint64_t)) == 0, file: ../../common/fs/zfs/space_map.c, line: 344
panic string: assertion failed: sm->sm_space == space (0x5200 == 0xa40000), file: ../../common/fs/zfs/space_map.c, line: 337
It's likely to be difficult to tell if this is an same issue by just looking at the panic strings due to nature of the underlined problem.
This will most likely be seen on Control Domains (and/or hosts) where "Shadow Copy" / "LUN Copy" / "Storage Level Block Copy" was used to replicate existing zpool into another pool. Such zpool will end up having same GUID as the original zpool.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms