If the described issue occurs, the system may exhibit a panic with a stack trace similar to the following:
panic[cpu1]/thread=300026a3820: mutex_enter: bad mutex, lp=6001999c270 owner=300026a3820 thread=300026a3820
zfs:dsl_dataset_disown+c (6001999c140, 136dfb0, 0, 6001999c270, 6001999c140, 16)
zfs:zvol_set_volsize+224 (6001fdf5680, 136dc00, 18e4000, 16, 2a102711010, 2a102711008)
zfs:zfs_prop_set_special+22c (6001be0c000, 2a4, 600179aa9b8, 0, 8, 8)
zfs:zfs_set_prop_nvlist+104 (6001be0c000, 8, 600364a14b8, 2a102711828, 0, 600179aa9b8)
zfs:zfs_ioc_set_prop+f8 (6001be0c000, 2, 0, 0, 8, 1128)
zfs:zfsdev_ioctl+19c (16, 2, ffbfdc60, 0, 18cfb10, 1400)
genunix:fop_ioctl+20 (60015a9b880, 5a16, ffbfdc60, 100003, 600104220e8, 12a6a54)
genunix:ioctl+184 (3, 6001be79930, ffbfdc60, 0, 0, 5a16)
syncing file systems... done
The panic has been seen during Live Upgrade operations and whilst modifying ZFS filesystem properties relating to filesystem size and quota where insufficient space exists within the zpool.
Cause
Due to bug 15734114 (previously referenced as bug 7076775), this issue can occur in the following releases:
SPARC Platform
Solaris 10 without patch 147440-11 or later
Solaris 11 11/11 with SRU3 or earlier
Solaris 11 Express
x86 Platform
Solaris 10 without patch 147441-11 or later
Solaris 11 11/11 with SRU3 or earlier
Solaris 11 Express
Solution
This issue is addressed in the following releases:
SPARC Platform
Solaris 10 with patch 147440-11 or later
Solaris 11 11/11 with SRU4 or later
x86 Platform
Solaris 10 with patch 147441-11 or later
Solaris 11 11/11 with SRU4 or later
Note: A solution is not available for Solaris 11 Express. Systems running this OS version should be upgraded to Solaris 11 11/11 SRU4 or later.
panic[cpu1]/thread=300026a3820: mutex_enter: bad mutex, lp=6001999c270 owner=300026a3820 thread=300026a3820
zfs:dsl_dataset_disown+c (6001999c140, 136dfb0, 0, 6001999c270, 6001999c140, 16)
zfs:zvol_set_volsize+224 (6001fdf5680, 136dc00, 18e4000, 16, 2a102711010, 2a102711008)
zfs:zfs_prop_set_special+22c (6001be0c000, 2a4, 600179aa9b8, 0, 8, 8)
zfs:zfs_set_prop_nvlist+104 (6001be0c000, 8, 600364a14b8, 2a102711828, 0, 600179aa9b8)
zfs:zfs_ioc_set_prop+f8 (6001be0c000, 2, 0, 0, 8, 1128)
zfs:zfsdev_ioctl+19c (16, 2, ffbfdc60, 0, 18cfb10, 1400)
genunix:fop_ioctl+20 (60015a9b880, 5a16, ffbfdc60, 100003, 600104220e8, 12a6a54)
genunix:ioctl+184 (3, 6001be79930, ffbfdc60, 0, 0, 5a16)
syncing file systems... done
The panic has been seen during Live Upgrade operations and whilst modifying ZFS filesystem properties relating to filesystem size and quota where insufficient space exists within the zpool.
Cause
Due to bug 15734114 (previously referenced as bug 7076775), this issue can occur in the following releases:
SPARC Platform
Solaris 10 without patch 147440-11 or later
Solaris 11 11/11 with SRU3 or earlier
Solaris 11 Express
x86 Platform
Solaris 10 without patch 147441-11 or later
Solaris 11 11/11 with SRU3 or earlier
Solaris 11 Express
Solution
This issue is addressed in the following releases:
SPARC Platform
Solaris 10 with patch 147440-11 or later
Solaris 11 11/11 with SRU4 or later
x86 Platform
Solaris 10 with patch 147441-11 or later
Solaris 11 11/11 with SRU4 or later
Note: A solution is not available for Solaris 11 Express. Systems running this OS version should be upgraded to Solaris 11 11/11 SRU4 or later.
No comments:
Post a Comment