xxxxx@xxxxx.com 2002-03-07
forced umount case: stop using ufs forced umount
lockfs -h/umount case (aka. cluster failover):
If you've actually suffered from this, you could change
the cluster script "/opt/SUNWcluster/bin/scnfs" to
use the vxfs unmount logic for UFS FS as well,
as vxfs does't have a forced umount (till 3.4)
and hence all procs accessing the FS will be killed before
the unmount of the vxfs FS will take place.
xxxxx@xxxxx.com 2002-03-14
As coredumping procs are the most common trigger of this panic
during forced umounts/failovers, another possible workaround would be
to disable application coredumps via limit(1) in vulnerable
environments.
xxxxx@xxxxx.com 2003-08-28
or easier disable user process coredumps via coreadm(1M) systemwide
"coreadm -d process"
xxxxx@xxxxx.com 2003-12-04
or instead umount(1M) -f use lockfs(1M) -h /filesystem to hard lock the
filesystem, then wait 60sec and the umount(1M) the filesystem.
the 60 sec grace period should enable ongoing VOP's to finish.