Why psrset is not working

Sometime have you came across a situation where you want to create psrset but it doesn't works.

Please check if pool facility is active or not. If its active then you won't be able to create psrset.

svcs -a | egrep pool.

Disable pool and create psrset again.

Comments

Post a Comment

Popular posts from this blog

Linux LVM with EMC powerpath

How you plan to use Linux LVM with a multipathing software like EMc powerpath? The trick is to mask out the non emcpower devices from LVM view. This is to ensure any path failure is handled by the multipathing software rather than LVM itself. The underlying path management complexity is offloaded to multipathing software. When the command pvscan, is issued you see only the emcpower devices. You will have to enable the filter for accepting the emcpower devices and reject all the non emcpower devices inside /etc/lvm/lvm.conf file filter =[ "a|/dev/emcpower.*|", "r|/dev/sd*|", "r|/dev/cdrom|" ] Ensure only one filter is enabled.
Read more

zpool and power path partial compatibility

Is power path fully supported with zpools, no. It's partial. You can have the pseudo devices assigned to a pool but it uses the native ctd disk only. Recently I lost 2 paths from the vnx array to m9000 server running Solaris 11.1. When I ran the zpool status -x command some of the pools were online while some of them were un available. Power path was reporting 2 paths only but it was active. So ideally the zpools should be online. But it's not. I enabled the remaining 2 paths and all became online. Internally the pools were pointing to one of the ctd devices that belonged to dead path and it was not coming online. Also few of the emcpower devices were renamed, so I had to do zpool import -d with the alternate disk. It seems power path is not completely supported now but may become in future.
Read more

Solaris 10 patching best practices

We have a mammoth task every quarter to patch all our Unix servers, and every month if the servers are in DMZ. With time we have formulated a couple of steps that makes life easier during patching of Sun servers. 1. We apply the same patch cluster on every Sun server for a particular quarter, no matter when we patch the server during a particular quarter . 2. Once the patch is downloaded at the centralized location, it is distributed to every server on the / directory. This may sound a little off track as the patch cluster consumes a good 1GB of space and the patching process might fail if we do not have sufficient disk space on our / and /var file system, but we had faced some NFS issues before where we had a lot of trouble bringing up the system after the nfs server crash in middle of the patching process. 3. We inform the database team before hand (1 week) about the patch cluster release and also share with the them release notes, for them to identify any issues with the database a...
Read more