1) path disks

c0d30166
/virtual-devices@100/channel-devices@200/disk@763a
c0d30167
/virtual-devices@100/channel-devices@200/disk@763b

2) virtual networks

vnet2717002:1: flags=201000843 mtu 1500 index 6
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
vnet2717002:2: flags=201000843 mtu 1500 index 6
zone system

With this it’s clear that we are working on ldom but i would like to know “is anything more clear where i can be 100% sure?”

Today i found on a Solaris 10 system the ldom manifest:

online Dec_01 svc:/ldoms/agents:default

This is the answer to my question

[root@system01 config]# vxtunefs -o read_ahead=2,read_pref_io=128k,write_pref_io=128k,read_nstream=16,write_nstream=16 /ora/01
UX:vxfs vxtunefs: INFO: V-3-22525: Parameters successfully set for /ora/01

After i read some info about parameters from the man page

I even found that vxtunefs accepts as argument a volume!
Running vxtunefs <volume with format i can obtain current parameters

Here i’m reading about install and configure it on Oracle Solaris 11

I hope to play with both soon!!

root@system01 # clnode show-rev
clnode: (C660883) Internal error.

Altough this is not a critical issue i was very curious to understand what did not work.
I tried the legacy scinstall command as follow:

system01 # scinstall -p
touch: cannot change times on /var/cluster/run/scinstall/scinstall.tmp.28601: Bad address

scinstall: scinstall did NOT complete successfully!

well , from scinstall i had more info about the issue.
I tried to use touch for make a new file:

root@system01 # cd /var/cluster/run/scinstall/
root@system01 # touch 1
touch: cannot change times on 1: Bad address
root@system01 # touch 1
root@system01 #

the first time it does not work , the second it works, mmm.
Let’s try again:

root@ssb40015 # pwd
/sun-temp
root@system01 # touch 1
touch: cannot change times on 1: Bad address
root@system01 # touch 2
touch: cannot change times on 2: Bad address
root@system01 # touch 3
touch: cannot change times on 3: Bad address

Well , after these experiments i was able to identify the follow conditions:

1) The issue happens when i try to make a new file for the first time
2) The issue does not happens when i try to make a new file for the second time
3) The issue is not due to pathname ( in my opinion ) because i tried it from /var and /sun-temp ( then no permissions issue )
4) Even i got that error the file was maked by touch command but it’s empty.
5) The scinstall comand does not complete , because every time it makes a new file with touch where the name of the file is scinstall.tmp.pid

I used truss for compare both cases output ( when it works and when not ).
The difference is here:
( when it does not work )

4846: stat64(“pippo”, 0xFFBFF968) Err#2 ENOENT
4846: creat64(“pippo”, 0666) = 3
4846: futimens(3, 0×00000000) Err#14 EFAULT
4846: fstat64(2, 0xFFBFE818) = 0
touch4846: write(2, ” t o u c h”, 5) = 5
: cannot change times on 4846: write(2, ” : c a n n o t c h a”.., 25) = 25
pippo4846: write(2, ” p i p p o”, 5) = 5
: 4846: write(2, ” : “, 2) = 2
Bad address4846: write(2, ” B a d a d d r e s s”, 11) = 11

4846: write(2, “\n”, 1) = 1
4846: close(3) = 0
4846: _exit(1)

( when it works )

5868: stat64(“pippo”, 0xFFBFF968) = 0
5868: utimensat(-3041965, “pippo”, 0×00000000, 0) = 0
5868: _exit(0)

It seems that the issue comes from futimens syscall.
I read the manpage but i was not able to find the “Err#14 EFAULT” error.
Looking on the web i found something similar on Solaris 11 , it seems a bug where EFAULT stands for “times pointed to an invalid address; or, dirfd was AT_FDCWD, and pathname is NULL or an invalid address.”

I hope to understand more about this issue!

Following the output:

68G backup_rman
65G imsbackup-26.backup
64G imsbackup-25.backup
11G backup_VAR
1.6G SunOS_sparc
931M Identity_Synchronization_for_Windows
831M Comms-solaris_sparc.zip
98M 110919.tar.gz
1.7M apab.ldif
1.0M serverdb.ldif
757K Legal_Folder
208K pkg
53K backup.log
26K README
8K lost+found
4K COPYRIGHT.txt
3K README.txt

y0!

Mismatch between the Failback policies for the resource group system-rg (True) and global service system-dg (False) detected.

After a conference call the customer asked me to set the resource group failback to False.

Reading the rg_properties manpage i found:

Failback (boolean)
A Boolean value that indicates whether to recalculate
the set of nodes where the group is online when the
cluster membership changes. A recalculation can cause
the RGM to bring the group offline on less preferred
nodes and online on more preferred nodes.

Default
False

Tunable
Any time

ok. Any time means that i can modify this property without offline the resource group.

I tried the command:

root@system1 # scrgadm -c -g system-rg -y Failback=False
system1 – Mismatch between the Failback policies for the resource group system-rg (True) and global service system1-dg (False) detected.

VALIDATE on resource system1-storage, resource group system1-rg, exited with non-zero exit status.
Validation of resource system1-storage in resource group system1-rg on node system1 failed.

mmm….

After some test i finally changed it , doing in order:

1) setting diskgroup failback policy to True ( in this moment both rg and dg had True value )
2) setting resource group failback policy to False ( in this moment rg had False and dg True )
3) setting diskgroup failback policy to False ( in this moment both rg and dg had False value )

I checked what i did with scrgadm/scconf commands:

root@system1 # scrgadm -pvv -g system1-rg | head | grep Failback
(system1-rg) Res Group Failback: False

root@system1 # scconf -pv | grep system1-dg | grep failback
(system1-dg) Device group failback enabled: no

Nice!

More details here

Enjoy the #1 enterprise OS

i tried with the command:

# pnmset -c nafo1 -o create qfe3
nafo1: Must have exactly one configured adapter for the group

mmm

After few checks i saw that qfe3 interface was plumbed and configured but it had not the “UP” flag from ifconfig output.
In this case i did:

# ifconfig qfe3 up
# pnmset -c nafo1 -o create qfe3

# pnmstat -l
group adapters status fo_time act_adp
nafo0 qfe0:qfe2 OK NEVER qfe0
nafo1 qfe3 OK NEVER qfe3

bash-3.00# prtdiag -v | head -3
System Configuration: VMware, Inc. VMware Virtual Platform
BIOS Configuration: Phoenix Technologies LTD 6.00 10/13/2009

bash-3.00# modinfo | grep -i vm
148 fffffffff7e71000 3b38 244 1 vmxnet3s (VMware EtherAdapter v3 b341836)
205 fffffffff78e7000 21b0 230 1 vmmemctl (VMware Memory Control b341836)

very easy