I removed an external Sun disk (with data on it) from an old 2.6 system and added the disk to another 2.6 system. The new system seems to recognize the system (verified by the format command).
When try to mount I am getting, I got the error:
mount: /dev/dsk/c1t1d0s6 is not this fstype.
I... (3 Replies)
Hi there,
I need to get a Chinese disclaimer attached to an email on a Solaris 2.7 box. The disclaimer we use is in English and stored as a text file although I've been asked to see if we can add the Chinsese one?
Is it simply just a matter of adding the Chinese locale to the OS or is there... (1 Reply)
Hello everbody:
I have Sol9, and I need to check its kernekl parameters, do you know how to list them or in which file they can be found.
Thanks in Advance (3 Replies)
We have a Spark Solaris 10 box running behind a Pix 501 firewall, we are running NAT and I have mapped access to it from the outside world. Anyway, we can receive mail no problem just can't send. I receive this message bounce:
The original message was received at Thu, 10 Jan 2008 17:04:29 -0600... (1 Reply)
Hello
When I login as root - my prompt is # I want to change this and I understand the setting (PS1=) needs to go into a file called .profile, but I don't know where this file is for the root user. The root users home folder is / when I type env.
Should I be creating a home folder for the... (4 Replies)
Good morning all
Once again, I come seeking wisdom :-)
I have a sunfire 6800 with two domains. Both Sc controllers are uncontactabe, probably due to network issues, but as the server is on a different site, Im a little stuck.
So, am trying to use scadm, as I know I can view / configure... (7 Replies)
Hi Gurus,
An Application is not able to create files above 2.14gb in size in my Sol5.9 server. I have checked the file limit of the user running the Application and am attaching the same:
boiadm: ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) ... (4 Replies)
Hello All:
I am trying to configure mail service on Solaris 10 and I am unable to send using mailx. It appears the server may not be listening on port 25:
bash-3.00# mconnect
connecting to host localhost (127.0.0.1), port 25
connect: Connection refused
services is configured to use port... (7 Replies)
Need help with GCC package.
I did downloaded the same from sunfreeware.com for i86, however after doing the unzip I am unable to add the same with pkgadd as I am unable to get the sun standard format as SUNWgcc on my system.
Thanks (4 Replies)
Do I need to reinstall/rerun JASS after upgrading from Sol9 to Sol10?
Just wondered if the upgrade procedure overwrote any of the settings etc? (0 Replies)
Discussion started by: psychocandy
0 Replies
LEARN ABOUT HPUX
cmdisklock
cmdisklock(1m)cmdisklock(1m)NAME
cmdisklock - manage Serviceguard cluster lock devices.
SYNOPSIS
cmdisklock check path
cmdisklock [-f] reset path
DESCRIPTION
cmdisklock is a tool to check the current state of a Serviceguard cluster lock device. It can also be used to reset the state of the clus-
ter lock device. The need to reset the cluster lock device state could arise if the cluster lock device is replaced or becomes corrupt.
A cluster lock device can be either an HP-UX LVM cluster lock or a cluster lock LUN device. HP-UX LVM cluster locks exist only on a disk
in an LVM volume group. Cluster lock LUNs exist only on disks dedicated to cluster lock. cmdisklock is useful for checking either type of
cluster lock and for re-initializing cluster lock LUN devices after a failure or corruption.
NOTE
To restore an HP-UX LVM cluster lock, use vgcfgrestore. cmdisklock will fail until vgcfgrestore is run, and cmdisklock is unnecessary as
long as vgcfgbackup was done after the cluster lock was initialized. See the Managing Serviceguard manual for details.
The syntax of the path option depends on the type of lock. For HP-UX LVM cluster lock disks, the syntax is VG:PV (for example:
/dev/vglock:/dev/dsk/c0t0d2). For cluster lock LUN disks, the path is the disk device path. For example, /dev/sdd1 (on Linux) or
/dev/dsk/c0t1d2 (on HP-UX).
Options
cmdisklock supports the following options:
check Check the current state of the cluster lock device and report the results.
reset Reset (initialize) the state of the cluster lock device. This operation should only be performed on a cluster lock
LUN device. For HP-UX LVM cluster lock, use vgcfgrestore as documented in the Managing Serviceguard manual. After
performing a reset, a check can be used to verify that the lock is cleared.
EXAMPLES
If the cluster lock LUN device becomes corrupted and the cluster is up, messages like the following will appear in syslog.
Mar 15 12:20:41 usb cmdisklockd[17599]: WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is cor-
rected, a single failure could cause all nodes in the cluster to crash.
Mar 15 12:20:41 usb cmdisklockd[17599]: After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset
/dev/dsk/c0t1d2' to repair
Mar 15 12:20:41 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is inaccessible
Once the above messages appear in syslog on all running nodes, the following command will re-initialize the cluster lock LUN:
ucd:/> cmdisklock reset /dev/dsk/c0t1d2
WARNING: Cluster lock LUN /dev/dsk/c0t1d2 is corrupt: bad label. Until this situation is corrected, a single failure could cause all nodes
in the cluster to crash.
After ensuring that all active nodes in the cluster have logged this message, run 'cmdisklock reset /dev/dsk/c0t1d2' to repair
/dev/dsk/c0t1d2 is inaccessible
Resetting cluster lock device /dev/dsk/c0t1d2
Cluster lock reset completed
/dev/dsk/c0t1d2 is accessible
cleared
After the lock is restored, a message like the following appears in syslog:
Mar 15 12:23:11 usb cmdisklockd[17599]: Cluster lock disk /dev/dsk/c0t1d2 is accessible
WARNINGS
CAUTION
For cluster lock LUN, reset is a potentially destructive operation. While cmdisklock checks for known volume manager and file system use
(overridden by -f), it does not validate that the device to be reset is actually used by any cluster. If -f is used on the wrong device
file, loss of data may result.
CAUTION
Care should be taken when doing a reset when the cluster is active as there is a remote possibility that the cluster will partition right
when this command is run and both nodes could end up thinking they have successfully acquired the lock. To avoid this situation, make sure
cmcld has logged a message in syslog on all running nodes saying the device is inaccessble, before performing a reset. Note that it is
safe to run cmdisklock when the cluster is down.
RETURN VALUE
cmdisklock returns the following values:
0 Successful completion.
1 The disk is inaccessible or is not recognized as a cluster lock.
AUTHOR
cmdisklock was developed by HP.
SEE ALSO cmapplyconf(1m), cmviewcl(1m), vgcfgbackup(1m), vgcfgrestore(1m)
Requires Optional Serviceguard Software cmdisklock(1m)