|
|
Sponsored Content
Operating Systems
Solaris
what is going on with SUNW.HAStoragePlus?!!!!!
Post 302268694 by samar on Tuesday 16th of December 2008 06:09:26 AM
12-16-2008
what is going on with SUNW.HAStoragePlus?!!!!!
Hi all,
really interesting thing I have encountered . So :
root@host4 # uname -a
SunOS host4 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-880
root@host4 # scinstall -p
3.2
latest recommended patches applied ..all SUN cluster patches applied.
SUN cluster software installed without any issue.
all needed resource types installed:
root@host4 # clrt list
SUNW.LogicalHostname:2
SUNW.SharedAddress:2
SUNW.gds:6
SUNW.HAStoragePlus:4
so I created simply one resource group ..
root@host4 # clrg create data-rg
and then created logicalhostname:
root@host4 # clrslh create -g data-rg -h datalh datalh-rs
and simply created SUNW.HAStorkagePlus:
root@host4 # clrs create -g data-rg -t SUNW.HAStoragePlus -p AffinityOn=TRUE -p FilesystemMountPoints=/data1,/data2 hasp-rs
then simply tried enable resource group with it's resources ..
Everything fine .. it started up .. got logicalhostname .. and then mounted /data1 and /data2 ..
here I create directory in /data1
root@host4 # mkdir /data1/test
root@host4 # cd /data1/test
root@host4 # mkfile 5m file1
root@host4 # mkfile 10m file2
root@host4 #chown -R mysql:mysql /data1/test
I gave all included files owner as mysql ..
then I'm testing it .. failed it over to second node .. it started on second node succesfully .. but here the problem is .. I look in /data1 and so that permissions of that directory "test" and files that I ceated changed ..
root@host3 # cd /data1
root@host3 # ls -al test
total 30756
drwxr-xr-x 2 60003 mysql 512 Dec 16 14:58 .
drwxr-xr-x 4 root root 512 Dec 16 14:58 ..
-rw------T 1 60003 mysql 5242880 Dec 16 14:58 file1
-rw------T 1 60003 mysql 10485760 Dec 16 14:58 file2
.. from where does it take "60003" ?!!!!!
If I fail it over again to forst node it is ok with it's permissions:
root@host4 # ls -al
total 30756
drwxr-xr-x 2 mysql mysql 512 Dec 16 13:49 .
drwxr-xr-x 5 root root 512 Dec 16 13:47 ..
-rw------T 1 mysql mysql 5242880 Dec 16 13:49 file1
-rw------T 1 mysql mysql 10485760 Dec 16 13:49 file2
...
really interesting thing I have encountered . So :
root@host4 # uname -a
SunOS host4 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-880
root@host4 # scinstall -p
3.2
latest recommended patches applied ..all SUN cluster patches applied.
SUN cluster software installed without any issue.
all needed resource types installed:
root@host4 # clrt list
SUNW.LogicalHostname:2
SUNW.SharedAddress:2
SUNW.gds:6
SUNW.HAStoragePlus:4
so I created simply one resource group ..
root@host4 # clrg create data-rg
and then created logicalhostname:
root@host4 # clrslh create -g data-rg -h datalh datalh-rs
and simply created SUNW.HAStorkagePlus:
root@host4 # clrs create -g data-rg -t SUNW.HAStoragePlus -p AffinityOn=TRUE -p FilesystemMountPoints=/data1,/data2 hasp-rs
then simply tried enable resource group with it's resources ..
Everything fine .. it started up .. got logicalhostname .. and then mounted /data1 and /data2 ..
here I create directory in /data1
root@host4 # mkdir /data1/test
root@host4 # cd /data1/test
root@host4 # mkfile 5m file1
root@host4 # mkfile 10m file2
root@host4 #chown -R mysql:mysql /data1/test
I gave all included files owner as mysql ..
then I'm testing it .. failed it over to second node .. it started on second node succesfully .. but here the problem is .. I look in /data1 and so that permissions of that directory "test" and files that I ceated changed ..
root@host3 # cd /data1
root@host3 # ls -al test
total 30756
drwxr-xr-x 2 60003 mysql 512 Dec 16 14:58 .
drwxr-xr-x 4 root root 512 Dec 16 14:58 ..
-rw------T 1 60003 mysql 5242880 Dec 16 14:58 file1
-rw------T 1 60003 mysql 10485760 Dec 16 14:58 file2
.. from where does it take "60003" ?!!!!!
If I fail it over again to forst node it is ok with it's permissions:
root@host4 # ls -al
total 30756
drwxr-xr-x 2 mysql mysql 512 Dec 16 13:49 .
drwxr-xr-x 5 root root 512 Dec 16 13:47 ..
-rw------T 1 mysql mysql 5242880 Dec 16 13:49 file1
-rw------T 1 mysql mysql 10485760 Dec 16 13:49 file2
...
|
|
We Also Found This Discussion For You
1. Solaris
Ultra E150 Solaris 2.5.1 Oracle server. was working fine, then started losing network connection. I can see in messages file that it was complaining about another device using its ip address. Though not any longer, though I wonder if that was a red herring. My IT guys have now re-reserved its ip... (29 Replies)
Discussion started by: AlSmith1964
29 Replies
LEARN ABOUT CENTOS
pmdamysql
PMDAMYSQL(1) Performance Co-Pilot PMDAMYSQL(1) NAME
pmdamysql - MySQL database PMDA DESCRIPTION
pmdamysql is a Performance Co-Pilot PMDA which extracts live performance data from a running MySQL database. INSTALLATION
pmdamysql uses a configuration file from (in this order): o /etc/pcpdbi.conf o $PCP_PMDAS_DIR/mysql/mysql.conf This file can contain overridden values (Perl code) for the settings listed at the start of pmdamysql.pl, namely: o database name (see DBI(3) for details) o database user name o database pass word Once this is setup, you can access the names and values for the mysql performance metrics by doing the following as root: # cd $PCP_PMDAS_DIR/mysql # ./Install If you want to undo the installation, do the following as root: # cd $PCP_PMDAS_DIR/mysql # ./Remove pmdamysql is launched by pmcd(1) and should never be executed directly. The Install and Remove scripts notify pmcd(1) when the agent is installed or removed. Binary Status values in text Some of the status values are in the form of YES/NO or ON/OFF. Since these cannot be intepreted by tools like PMIE, they have been duplicated with a _num extension and the values of 1 (YES/ON) or 0 (NO/OFF). Eg: o mysql.slave_status.slave_io_running o mysql.slave_status.slave_io_running_num FILES
/etc/pcpdbi.conf configuration file for all PCP database monitors $PCP_PMDAS_DIR/mysql/mysql.conf configuration file for pmdamysql $PCP_PMDAS_DIR/mysql/Install installation script for the pmdamysql agent $PCP_PMDAS_DIR/mysql/Remove undo installation script for the pmdamysql agent $PCP_LOG_DIR/pmcd/mysql.log default log file for error messages from pmdamysql SEE ALSO
pmcd(1), pmdadbping.pl(1) and DBI(3). # vi: sw=4 ts=4 et: 3.8.10 Performance Co-Pilot PMDAMYSQL(1)