|
|
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 OPENSOLARIS
sunw.sctelemetry
SUNW.SCTelemetry(5) Sun Cluster Miscellaneous SUNW.SCTelemetry(5) NAME
SUNW.SCTelemetry, SCTelemetry - resource type for collecting data on system resource usage DESCRIPTION
SUNW.SCTelemetry is the resource type that enables you to collect data on the usage of system resources. SUNW.SCTelemetry stores system resource usage data in a Java DB database for seven days. The resource of type SUNW.SCTelemetry has a dependency on the resource of type SUNW.derby. For more information, see the SUNW.derby(5) man page. The extension properties associated with the SUNW.SCTelemetry resource type are as follows: Extended_accounting_cleanup(boolean) Specifies whether the extended accounting log file is cleaned up, that is whether historical data is deleted. Possible values for Extended_accounting_cleanup are TRUE and FALSE. Category Optional Default TRUE Tunable Anytime Monitor_retry_count(integer) Controls fault-monitor restarts. The property indicates the number of times that the process monitor facility restarts the fault moni- tor. The property corresponds to the -n option passed to the pmfadm(1M) command. The Resource Group Manager (RGM) counts the number of restarts in a specified time window. See the Monitor_retry_interval property for more information. Note that Monitor_retry_count refers to the restarts of the fault monitor itself, not to the resource of type SUNW.SCTelemetry. Category Optional Default 2 Tunable Anytime Monitor_retry_interval(integer) Indicates the time window in minutes during which the RGM counts fault-monitor failures. The property corresponds to the -t option passed to the pmfadm(1M) command. If the number of times the fault monitor fails exceeds the value of the Monitor_retry_count prop- erty, the process monitor facility does not restart the fault monitor. Category Optional Default 2 minutes Tunable Anytime Probe_timeout(integer) Specifies the timeout value, in seconds, for the probe. Category Optional Default 30 seconds Tunable Anytime Sampling_interval(integer) Specifies how often monitoring data is collected. The Telemetry_sampling_interval property must have a value of between 30 and 3600. Category Mandatory Default 60 Tunable Anytime SEE ALSO
pmfadm(1M), SUNW.derby(5) Sun Cluster 3.2 12 Jul 2005 SUNW.SCTelemetry(5)