Zfs kstats changed in Solaris 11 - breaks arcstat

I maintain the arcstat tool here:
[https://github.com/mharsch/arcstat]
I've identified some changes in zfs kstats that have broken this tool for Solaris 11 users. My analysis of the issue is here:
[https://github.com/mharsch/arcstat/issues/4]
Would someone from the ZFS team be willing to work with me to reconcile the kstat changes so users of the arcstat tool can get running on Solaris 11?
The easiest engagement would be in the form of a github pull request, but I'll take anything I can get.
Mike Harsch

Similar Messages

ANY SY-INDEX REFLECT CHANGES WHEN CONTROL BREAK STATEMENT PROCESS

Dear Guru's,
                 I have a requirement where i have to move the values to variable when control break (AT END OF) process. So i want to move the values according to the end of Vendor so for that i want to know is there any sy-index available which reflects changes when Control break (AT end of) process.
LIKE Sy-subrc = 0 when select statement fetches record or sy-tabix is like counter for loop.
Hope to get reply soon.
Regards,
Himanshu Rangappa

Hi,
There is no system Fields for it.
But your requirement can be done with 'AT NEW' and 'AT END' statement.
Refer this sample example,
loop at otab.
    at new module.
      move otab-module to otab2-module.
    ENDAT.
      at END OF effort.
      sum.               "Do your calculations here
      move otab-count to otab2-count.
      append otab2.
    endat.
endloop.

Changes in Solaris 10 Patch Access Policy

Solaris 10 x86 User Community
As of November 29th, Sun will be changing its Solaris 10 patch access policy. Now that Solaris 10 is freely available, support services require the purchase of a Sun Service Plan.
Under this new policy, access to patches is restricted. Security fixes and hardware driver updates are publicly available for free, but access to all other patches requires a Sun Service Plan.
Please see http://www.sun.com/service/sunconnection/solaris10patches.html for available access options.
Please send any questions to [email protected]

hi,
As a technical specialist I can understand everyone needs revenues to keep on going. But $120 for a min. level service plan it's really foolish on the policy makers. This would result in severe dent for the Solaris initiative itself in the long run. There should be reasonable pricing model, especially when Sun is projecting Solaris as an alternative to Linux! I do strongly suggest as a loyal Sun developer since 1996 to re-consider the service plan rates.
thanks,
Su37

How to change the page break in adobe forms

Does anyone know how to change the page break on an adobe form? I'm hoping it will be the same way you change the page view in excel.
Can anyone help?
Thank you in advance,
Priscilla

HI
 YOU CAN USE THE FOLLOWING SYSTEM FIELDS OF SMARTFORMS FOR THE MENTIONED PURPOSE
&SFSY-PAGE& 
 Inserts the number of the current print page into the text. You determine the format of the page number (for example, Arabic, numeric) in the page node.
&SFSY-FORMPAGES&
 Displays the total number of pages for the currently processed form. This allows you to include texts such as'Page x of y' into your output
&SFSY-JOBPAGES& 
 Contains the total page number of all forms in the currently processed print request.
REGARDS
ANOOP

Networking changes between Solaris 10 x86 10/08 (u6) and previous versions?

Solaris Community:
We have a J2SE CORBA-based application (that uses the default Sun ORB) that has run without problems on Solaris 8, 9, and 10 on both SPARC and, more recently, X86 platforms. Upgrading our client side machine (X4100 M2 Opteron platform) from Solaris 10 x86 5/08 (u5) to Solaris 10 x86 10/08 (u6) has resulted in threading or socket contention issues that we have not experienced previously. Using Live Upgrade, we can quickly go back to the u5 install on the client machine .... and the problems go away .... going back to u6, however, and the problems begin to show almost immediately. Our Java code base is identical as is the version of the JDK (1.5.0_16), so it would appear that there must be an underlying change to socket, networking, or threading behavior between these two versions of Solaris.
Thus far, I've not been unable to find details of changes either in the networking support or the threading model that might explain this .... or course, I don't have great expertise in these areas.
I've tried to use 'ndd /dev/tcp SOME_PARAMETER' for all of the /dev/tcp parameters returned by 'ndd /dev/tcp \?' to try to see if there are underlying changes in the /dev/tcp parameters .... but have not found any differences between Solaris 10 u5 and u6.
Can anyone point me to resources that would discuss changes between Solaris 10 u5 or u6 that might explain the problems that we've encountered? Or, alternatively, other system parameters that I could check that might explain changes in either TCP socket or threading behavior?
Thanks for your input,
John

I have a vague memory of someone reporting something similar which turned out to be due to a solaris feature called tcp_fusion.
To check whether thats your problem or not try the following.
Add following line in the /etc/system file.
set ip:do_tcp_fusion = 0
Once the /etc/system file is updated, it will be necessary to restart the system before the workaround will take effect.

Netmask Changes in Solaris 10

Hi Team,
We tried to change the netmask and broadcast address in solaris 10 by below steps
ifconfig ipge0 down
ifconfig ipge0 <ipaddress> netmask <subnet mask> broadcast <address
ifconfig ipge0 up
But interface is not up. The command (ifconfig ipge0 up) is hanged for long time without giving any error.
So, we changed the new netmask in the /etc/inet/netmasks and rebooted the server. The new changes got affect only after reboot.
Could you please confirm the Solaris 10 requres reboot for changes in netmask.
Regards,
R. Rajesh Kannan.

No, it doesn't need a reboot.
In fact, you don't even have to take the interface down....
I would edit /etc/netmasks so that the correct setting was in there for the next time I booted. Then:
'ifconfig <interface> netmask + broadcast +' (Yes, with the '+' symbols).
That should do it. No need to down or up.
Darren

Can Host ID be changed on Solaris 10

Recently upgraded an Ultra 10 from Solaris 2.6 to Solaris 10.
Problem:
We use an application that is no longer supported by the manufacturer. The application ran on the Ultra when it had Solaris 2.6. It required a specific host ID because it was originally licensed on a much older system. We cannot get a new license authorization for the application because the company is no longer in business.
To get around this, we used a program called "hid2" to change the host ID of the system. This temporarily changed the host ID on the Ultra and allowed the application to run.
After installing Solaris 10, I run the command "hid2 newhostid", and I get an error "cannot read namelist out of /dev/ksyms". The command to change the host ID is "hid2 newhostid" where newhostid is the ID required by the application.
Is this something with Solaris 10? It worked with the same hardware when the OS was Solaris 2.6.
I need an excutable program like hid2 because I'm not knowledgeable enough to compile C programs. There are several available on other websites but those that are excutabiles didn't work..
Does anyone know what to do? Do I need to install an older version of the OS? I've used 10 a little on a x86 system and like it. I'd like to upgrade this Ultra to 10.
Thank you.
jdw

Jonathan,
Keep in mind that the hints given in that Squirrel.Com link work for OBP 3.x systems, only.
When the time comes that you migrate to the next, newer system, it'll likely have an OBP design of 4.x or 5.x or 6.x, and the procedure will NOT work. The mkpl functions were deliberately removed by Sun.
So... it may now be the time to start a budget line item to save up to replace that software. Perhaps find a program that can take advantage of 21st Century computing, with 64bit and CMT architecture. <img src="images/smiley_icons/icon_smile.gif" border=0 alt="Smile">

Cannot run zpool (zfs feature) command in Solaris 10 6/06

Hi, I couldnt run ZPOOL command in Solaris 10 6/06. It said command not found.
May I know what should I do? My Solaris 10 version provide Solaris zoning features, but no ZFS feature provided.
How?

check your PATH- the zpool command is in the /usr/sbin directory.
Also, double check you have the zfs packages-
#pkginfo | grep zfs
system SUNWzfskr ZFS Kernel (Root)
system SUNWzfsr ZFS (Root)
system SUNWzfsu ZFS (Usr)

Find/Change Inserting paragraph break

Hello
I am trying to insert a paragraph mark between two lines of text using find/change
The first line has a heading style and I want to insert an empty line (Paragraph) after it and before the next line (without changing any formatting)
I am able to use enter the correct parameters in find but can't figure out what parameter to use in 'Change to"
Forced line break doesn't produce what I want. Neither does standard carriage return (not sure what that is)
I have tried both Text and Grep dialogs without success. Yes I read the help files.
This will be simple for you guys but is stumping me.
Any ideas oh brilliant ones?
As usual Thanks much in advance

Err, a paragraph mark? You mean a paragraph break?
Anyhow, if you insist on Doing it Wrong, you can use ^p ("End of Paragraph") in the change field. So you might
change ^p to ^p^p to insert a blank paragraph between each paragraph. For instance. But again, it is the wrong answer.
Yes-a paragraph break.' Sorry for the imperfect terminology
The first line is a heading style which I was advised in this forum to make into a 'list style' due to TOC issues
The 'doing it wrong' paragraph is going to be used to anchor a graphic and then converted to a very small paragraph mark (nearly invisible) as advised in another article
I did use the
change ^p to ^p^p
but it creating another list style as the paragraph break. Its ok. I went ahead and did it anyway and then manually changed all of those entries into a regular paragraph 'break'
With 300 graphics I would like to automate this but.....
Thanks for your reply

Zfs core dumps in Solaris Zones after patchcluster installation

Hi
I've installed the recommended patch cluster for Solaris 10 (SPARC) on my T2000 Server.
Now after the reboot all the Solaris Zones (got about 10 of them) instantly do zfs core dumps when their booted.
Some Output:
Dec 15 15:34:43 XXXXX genunix: NOTICE: core_log: zfs[1711] core dumped: /var/core/core_XXXXXX_zfs_0_0_1292423682_1711
bash-3.00# svcs
STATE STIME FMRI
online 13:58:50 svc:/system/svc/restarter:default
online 13:58:51 svc:/system/filesystem/root:default
online 13:58:51 svc:/network/loopback:default
online 13:58:53 svc:/network/pfil:default
online 13:58:54 svc:/system/installupdates:default
online 13:58:55 svc:/system/boot-archive:default
online 13:58:56 svc:/network/physical:default
online 13:58:57 svc:/system/filesystem/usr:default
online 13:58:57 svc:/system/identity:node
online 13:58:58 svc:/system/device/local:default
online 13:58:58 svc:/system/keymap:default
online 13:58:58 svc:/milestone/devices:default
online 13:58:58 svc:/system/filesystem/minimal:default
online 13:58:58 svc:/system/rmtmpfiles:default
online 13:58:58 svc:/system/cryptosvc:default
online 13:58:59 svc:/system/identity:domain
online 13:58:59 svc:/system/name-service-cache:default
online 13:58:59 svc:/system/coreadm:default
online 13:58:59 svc:/network/ipsec/ipsecalgs:default
online 13:58:59 svc:/application/print/ppd-cache-update:default
online 13:58:59 svc:/network/ipsec/policy:default
online 13:59:00 svc:/milestone/network:default
online 13:59:00 svc:/network/initial:default
online 13:59:00 svc:/system/manifest-import:default
online 13:59:00 svc:/network/service:default
online 13:59:00 svc:/milestone/single-user:default
online 13:59:00 svc:/network/dns/client:default
online 13:59:00 svc:/network/routing-setup:default
online 13:59:00 svc:/milestone/name-services:default
online 13:59:03 svc:/milestone/sysconfig:default
online 13:59:03 svc:/system/utmp:default
online 13:59:03 svc:/system/console-login:default
offline 13:58:51 svc:/system/sysidtool:net
offline 13:58:51 svc:/network/rpc/bind:default
offline 13:58:51 svc:/system/sysidtool:system
offline 13:58:52 svc:/network/nfs/status:default
offline 13:58:52 svc:/network/nfs/nlockmgr:default
offline 13:58:52 svc:/network/nfs/cbd:default
offline 13:58:52 svc:/network/nfs/mapid:default
offline 13:58:52 svc:/network/inetd:default
offline 13:58:52 svc:/network/nfs/client:default
offline 13:58:52 svc:/system/filesystem/autofs:default
offline 13:58:53 svc:/system/system-log:default
offline 13:58:53 svc:/network/smtp:sendmail
offline 13:58:53 svc:/system/cron:default
offline 13:58:53 svc:/milestone/multi-user:default
offline 13:58:54 svc:/application/management/snmpdx:default
offline 13:58:54 svc:/application/management/dmi:default
offline 13:58:54 svc:/application/management/seaport:default
offline 13:58:54 svc:/network/ssh:default
offline 13:58:54 svc:/milestone/multi-user-server:default
offline 13:58:54 svc:/application/font/fc-cache:default
offline 13:58:55 svc:/application/management/sma:default
offline 13:58:58 svc:/system/sac:default
offline 13:59:00 svc:/network/shares/group:default
offline 13:59:00 svc:/system/boot-archive-update:default
maintenance 15:34:43 svc:/system/filesystem/local:default
uninitialized 13:58:52 svc:/network/rpc/gss:default
uninitialized 13:58:54 svc:/application/font/stfsloader:default
uninitialized 13:58:55 svc:/network/rpc/rstat:default
uninitialized 13:58:55 svc:/application/print/rfc1179:default
uninitialized 13:58:55 svc:/application/x11/xfs:default
uninitialized 13:58:55 svc:/network/finger:default
uninitialized 13:58:55 svc:/network/ftp:default
uninitialized 13:58:56 svc:/network/login:rlogin
uninitialized 13:58:56 svc:/network/nfs/rquota:default
uninitialized 13:58:56 svc:/network/rpc/rusers:default
uninitialized 13:58:56 svc:/network/rpc/smserver:default
uninitialized 13:58:57 svc:/network/security/ktkt_warn:default
uninitialized 13:58:57 svc:/network/shell:default
uninitialized 13:58:57 svc:/network/telnet:default
uninitialized 13:58:58 svc:/network/rpc-100235_1/rpc_ticotsord:default
uninitialized 13:58:58 svc:/network/rpc/cde-calendar-manager:default
uninitialized 13:58:59 svc:/network/rpc/cde-ttdbserver:tcp
bash-3.00# svcs -x
svc:/system/filesystem/local:default (local file system mounts)
State: maintenance since Wed Dec 15 15:34:43 2010
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/system-filesystem-local:default.log
Impact: 24 dependent services are not running. (Use -v for list.)
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Wed Dec 15 13:58:52 2010
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: gssd(1M)
Impact: 11 dependent services are not running. (Use -v for list.)
svc:/network/rpc/rstat:default (kernel statistics server)
State: uninitialized since Wed Dec 15 13:58:55 2010
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: rpc.rstatd(1M)
See: rstatd(1M)
Impact: 1 dependent service is not running. (Use -v for list.)
bash-3.00# cat /var/svc/log/system-filesystem-local:default.log
[ Jul 10 03:41:35 Enabled. ]
[ Jul 10 03:43:45 Rereading configuration. ]
[ Jul 10 03:44:17 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 03:44:18 Method "start" exited with status 0 ]
[ Jul 10 12:44:36 Enabled. ]
[ Jul 10 12:44:45 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 12:44:45 Method "start" exited with status 0 ]
[ Jul 10 12:45:03 Enabled. ]
[ Jul 10 12:45:09 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 12:45:09 Method "start" exited with status 0 ]
[ Jul 10 13:54:39 Enabled. ]
[ Jul 10 13:54:46 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 10 13:54:46 Method "start" exited with status 0 ]
[ Jul 18 12:34:19 Enabled. ]
[ Jul 18 12:34:27 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 18 12:34:27 Method "start" exited with status 0 ]
[ Jul 18 17:29:08 Enabled. ]
[ Jul 18 17:29:15 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 18 17:29:15 Method "start" exited with status 0 ]
[ Jul 19 11:13:34 Enabled. ]
[ Jul 19 11:13:42 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:13:42 Method "start" exited with status 0 ]
[ Jul 19 11:32:23 Enabled. ]
[ Jul 19 11:32:30 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:32:31 Method "start" exited with status 0 ]
[ Jul 19 11:57:06 Enabled. ]
[ Jul 19 11:57:13 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 11:57:13 Method "start" exited with status 0 ]
[ Jul 19 12:40:05 Enabled. ]
[ Jul 19 12:40:12 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 19 12:40:12 Method "start" exited with status 0 ]
[ Jul 20 15:51:46 Enabled. ]
[ Jul 20 15:51:54 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 20 15:51:54 Method "start" exited with status 0 ]
[ Jul 24 11:42:17 Enabled. ]
[ Jul 24 11:42:25 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 24 11:42:25 Method "start" exited with status 0 ]
[ Jul 27 12:05:06 Stopping because service disabled. ]
[ Jul 27 12:05:07 Executing stop method (null) ]
[ Jul 27 12:13:10 Enabled. ]
[ Jul 27 12:13:17 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 27 12:13:17 Method "start" exited with status 0 ]
[ Jul 27 13:10:26 Stopping because service disabled. ]
[ Jul 27 13:10:26 Executing stop method (null) ]
[ Jul 27 13:18:19 Enabled. ]
[ Jul 27 13:18:26 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 27 13:18:26 Method "start" exited with status 0 ]
[ Jul 31 10:12:31 Enabled. ]
[ Jul 31 10:12:38 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jul 31 10:12:39 Method "start" exited with status 0 ]
[ Aug 7 10:08:52 Stopping because service disabled. ]
[ Aug 7 10:08:52 Executing stop method (null) ]
[ Aug 7 10:34:50 Enabled. ]
[ Aug 7 10:34:57 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 7 10:34:58 Method "start" exited with status 0 ]
[ Aug 9 09:14:50 Stopping because service disabled. ]
[ Aug 9 09:14:50 Executing stop method (null) ]
[ Aug 9 09:55:03 Enabled. ]
[ Aug 9 09:55:10 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 9 09:55:11 Method "start" exited with status 0 ]
[ Aug 16 10:46:43 Enabled. ]
[ Aug 16 10:46:50 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 10:46:50 Method "start" exited with status 0 ]
[ Aug 16 12:06:56 Enabled. ]
[ Aug 16 12:07:02 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 12:07:02 Method "start" exited with status 0 ]
[ Aug 16 13:45:10 Enabled. ]
[ Aug 16 13:45:16 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 13:45:16 Method "start" exited with status 0 ]
[ Aug 16 14:36:59 Enabled. ]
[ Aug 16 14:37:07 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 14:37:07 Method "start" exited with status 0 ]
[ Aug 16 15:00:40 Enabled. ]
[ Aug 16 15:00:47 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 16 15:00:47 Method "start" exited with status 0 ]
[ Aug 22 16:00:13 Enabled. ]
[ Aug 22 16:00:21 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 22 16:00:21 Method "start" exited with status 0 ]
[ Aug 23 09:49:04 Enabled. ]
[ Aug 23 09:49:10 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 09:49:11 Method "start" exited with status 0 ]
[ Aug 23 09:49:23 Stopping because service disabled. ]
[ Aug 23 09:49:23 Executing stop method (null) ]
[ Aug 23 10:04:13 Enabled. ]
[ Aug 23 10:04:20 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 10:04:20 Method "start" exited with status 0 ]
[ Aug 23 10:06:57 Enabled. ]
[ Aug 23 10:07:04 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 23 10:07:05 Method "start" exited with status 0 ]
[ Oct 23 08:43:05 Enabled. ]
[ Oct 23 08:43:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Oct 23 08:43:14 Method "start" exited with status 0 ]
[ Nov 21 14:51:50 Enabled. ]
[ Nov 21 14:51:58 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Nov 21 14:51:59 Method "start" exited with status 0 ]
[ Nov 29 15:33:19 Enabled. ]
[ Nov 29 15:33:26 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Nov 29 15:33:27 Method "start" exited with status 0 ]
[ Dec 18 13:37:35 Enabled. ]
[ Dec 18 13:37:42 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 18 13:37:42 Method "start" exited with status 0 ]
[ Dec 19 08:48:07 Enabled. ]
[ Dec 19 08:48:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:48:14 Method "start" exited with status 0 ]
[ Dec 19 08:56:07 Enabled. ]
[ Dec 19 08:56:14 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:56:14 Method "start" exited with status 0 ]
[ Dec 19 08:57:41 Enabled. ]
[ Dec 19 08:57:48 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Dec 19 08:57:48 Method "start" exited with status 0 ]
[ Feb 1 10:39:48 Enabled. ]
[ Feb 1 10:39:55 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 1 10:39:56 Method "start" exited with status 0 ]
[ Feb 8 11:12:50 Enabled. ]
[ Feb 8 11:12:57 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 8 11:12:57 Method "start" exited with status 0 ]
[ Jun 6 10:08:34 Enabled. ]
[ Jun 6 10:08:44 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Jun 6 10:08:46 Method "start" exited with status 0 ]
[ Aug 8 09:45:48 Enabled. ]
[ Aug 8 09:46:35 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 8 09:46:36 Method "start" exited with status 0 ]
[ Aug 14 17:53:59 Enabled. ]
[ Aug 14 17:54:06 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 14 17:54:06 Method "start" exited with status 0 ]
[ Aug 14 17:55:20 Enabled. ]
[ Aug 14 17:55:27 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 14 17:55:27 Method "start" exited with status 0 ]
[ Aug 18 15:19:17 Enabled. ]
[ Aug 18 15:19:24 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 18 15:19:24 Method "start" exited with status 0 ]
[ Aug 29 12:56:48 Enabled. ]
[ Aug 29 12:56:55 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 29 12:56:55 Method "start" exited with status 0 ]
[ Oct 13 11:59:43 Enabled. ]
[ Oct 13 11:59:50 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Oct 13 11:59:51 Method "start" exited with status 0 ]
[ Feb 26 16:47:00 Enabled. ]
[ Feb 26 16:47:07 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Feb 26 16:47:07 Method "start" exited with status 0 ]
[ Apr 14 15:54:17 Enabled. ]
[ Apr 14 15:54:24 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Apr 14 15:54:25 Method "start" exited with status 0 ]
[ Aug 28 08:49:58 Stopping because service disabled. ]
[ Aug 28 08:49:58 Executing stop method (null) ]
[ Aug 28 08:52:54 Enabled. ]
[ Aug 28 08:53:01 Executing start method ("/lib/svc/method/fs-local") ]
bootadm: this operation is not supported on sparc
[ Aug 28 08:53:01 Method "start" exited with status 0 ]
[ Aug 28 09:08:20 Stopping because service disabled. ]
[ Aug 28 09:08:20 Executing stop method (null) ]
[ Sep 1 16:05:36 Enabled. ]
[ Sep 1 16:06:05 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 16:06:05 Method "start" exited with status 0 ]
[ Sep 1 19:29:19 Enabled. ]
[ Sep 1 19:29:27 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 19:29:27 Method "start" exited with status 0 ]
[ Sep 1 23:04:00 Enabled. ]
[ Sep 1 23:04:08 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 1 23:04:08 Method "start" exited with status 0 ]
[ Sep 2 00:23:41 Stopping because service disabled. ]
[ Sep 2 00:23:42 Executing stop method (null) ]
[ Sep 2 00:46:46 Enabled. ]
[ Sep 2 00:46:53 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 2 00:46:54 Method "start" exited with status 0 ]
[ Sep 26 12:04:34 Enabled. ]
[ Sep 26 12:04:41 Executing start method ("/lib/svc/method/fs-local") ]
[ Sep 26 12:04:42 Method "start" exited with status 0 ]
[ Oct 20 13:05:09 Stopping because service disabled. ]
[ Oct 20 13:05:10 Executing stop method (null) ]
[ Oct 20 13:24:01 Enabled. ]
[ Oct 20 13:24:08 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 20 13:24:09 Method "start" exited with status 0 ]
[ Oct 21 16:30:59 Enabled. ]
[ Oct 21 16:31:09 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 16:31:09 Method "start" exited with status 0 ]
[ Oct 21 16:32:42 Stopping because service disabled. ]
[ Oct 21 16:32:42 Executing stop method (null) ]
[ Oct 21 16:42:05 Enabled. ]
[ Oct 21 16:42:15 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 16:42:15 Method "start" exited with status 0 ]
[ Oct 21 17:27:37 Enabled. ]
[ Oct 21 17:27:47 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 21 17:27:47 Method "start" exited with status 0 ]
[ Oct 22 11:08:34 Enabled. ]
[ Oct 22 11:08:43 Executing start method ("/lib/svc/method/fs-local") ]
[ Oct 22 11:08:43 Method "start" exited with status 0 ]
[ Dec 9 09:17:33 Stopping because service disabled. ]
[ Dec 9 09:17:33 Executing stop method (null) ]
[ Dec 10 11:47:14 Enabled. ]
[ Dec 10 11:47:24 Executing start method ("/lib/svc/method/fs-local") ]
[ Dec 10 11:47:25 Method "start" exited with status 0 ]
[ Dec 15 10:52:25 Stopping because service disabled. ]
[ Dec 15 10:52:25 Executing stop method (null) ]
[ Dec 15 12:42:16 Enabled. ]
[ Dec 15 12:42:26 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 12:42:28 Method "start" exited with status 95 ]
[ Dec 15 13:13:19 Enabled. ]
[ Dec 15 13:13:28 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 13:13:30 Method "start" exited with status 95 ]
[ Dec 15 13:58:51 Enabled. ]
[ Dec 15 13:59:00 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 13:59:03 Method "start" exited with status 95 ]
[ Dec 15 15:34:41 Leaving maintenance because clear requested. ]
[ Dec 15 15:34:41 Enabled. ]
[ Dec 15 15:34:41 Executing start method ("/lib/svc/method/fs-local") ]
Abort - core dumped
WARNING: /usr/sbin/zfs mount -a failed: exit status 134
[ Dec 15 15:34:43 Method "start" exited with status 95 ]
bash-3.00# /usr/sbin/zfs mount -a
internal error: Unknown error
Abort (core dumped)
Before that I've installed the patch cluster with halted solaris zones which produced following output:
Application of patches finished : 2010.12.15 12:08:43
Following patches were applied :
119254-77 119812-10 125719-31 140159-03 142911-01
141588-04 119900-11 125731-05 142292-01 142933-02
142251-02 119906-16 126206-05 141444-09 142909-17
118666-28 120460-17 126363-08 141500-07 143140-04
118667-28 121012-03 126365-16 141502-02 143502-01
118777-16 121308-20 126868-04 141506-09 143506-01
140860-02 122212-40 127724-02 141514-02 143615-02
119059-56 122261-03 136998-09 141518-12 143731-01
119213-23 122675-05 137000-07 141552-03 143733-01
124628-10 123003-04 137080-05 141558-01 143977-01
119252-29 123590-12 137147-06 141586-01 144053-04
119280-23 123893-22 138195-04 141590-02 144106-01
124188-03 124393-11 138822-07 141874-09 144254-01
120199-15 124457-02 138826-07 141876-07 144488-04
119534-19 124630-42 138880-02 142084-04 144492-01
120272-28 125215-03 139099-04 142397-01 145124-01
119757-18 125388-03 139620-01 142529-01 145796-01
119783-15 125555-07
Following patches were skipped :
Patches already applied
120900-04 119063-01 119810-05 123005-07 137093-01
121133-02 119081-25 119986-03 124444-01 138866-03
119317-01 119130-33 120061-02 124939-03 137137-09
121296-01 123611-04 120201-05 124943-01 137871-02
138215-01 140899-01 120292-02 124997-01 138181-01
127884-01 122640-05 120329-02 125279-05 138361-01
118712-23 126897-02 121975-01 125539-06 138373-02
118918-24 127755-01 120719-02 125891-01 138647-01
138217-01 125503-02 120830-06 126440-01 141016-01
119578-30 125547-02 121095-02 126540-02 139555-08
121453-02 140796-01 121606-04 127127-11 139967-01
121453-02 120011-14 124171-07 136882-02 140455-01
121118-16 139520-02 123630-03 137032-01 140563-01
118833-36 119764-06
Patches obsoleted by one or more patches already applied
118731-01 124204-04 122660-10
Patches not applicable to packages on the system
121181-03 120410-33 121211-02 125533-15 143317-03
119115-35 120412-11 122259-03 125541-06 143510-01
119117-52 120414-27 122470-03 125952-20 143725-01
119315-19 120543-21 122911-24 137004-08 143727-01
119548-14 120739-06 122958-06 138387-01 143739-01
119903-02 120811-09 123938-02 138824-07 144325-01
120094-30 120849-04 125136-24 138876-01 145006-02
120185-21 121104-11 125137-24 139986-01 145080-01
119368-04 121136-02 125332-14 142244-02 145200-01
120286-03
Installation of patch set complete. PLEASE REBOOT THE SYSTEM.
when i tried to reboot the system by init 6 the service iscsi hanged and produced syslog errors about a unkown iocall -> killed the process. System rebooted w/o errors.
Does anyone have got an idea how to find out which patch or whatever do produce these errors?

Hi,
I'm having the same issue of diskmon core dumps after upgrading grid and database from 11.2.0.1 to 11.2.0.2 on Solaris 10 x86-64. Following this thread, I'm trying to deinstall the Oracle 11.2.0.1 grid home.
I answered the following questions asked by the grid deinstall tool:
1. ASM configuration was not detected in this Oracle home. Was ASM configured in this Oracle home (y|n): y
2. Specify the ASM Diagnostic Destination: /db01/app/oracle/diag/asm/+ASM
3. Specify the diskgroups that are managed by this ASM instance: DATA FRA
4. De-configuring ASM will drop all the diskgroups at cleanup time. Do you want deconfig tool to drop the diskgroups:
If I answer no to question 1, the tool exits with error.
How do I answer question #4? (confused about this question of dropping diskgroups, it's already been upgraded)
Deinstall of Oracle db Home 11.2.0.1 was successful.
The +ASM instance has been upgraded and is running fine under 11.2.0.2 except for the excessive diskmon core dumps.
Thanks,
Lisa
Edited by: user12018917 on Apr 19, 2011 10:21 AM

IP address change in Solaris 10

Hello Friends
while installing solaris I gave some ip address to computer say 192.168.100.x .. , now after installation I have been asked to change the Ip address to some other series say 172.168.100.x , and this IP address should reflect even if reboots the computer. - i used "ifconfig" to change ip but when i m restarting the system its showing the prevoius one ( 192.168.100.x)
what do i do to solve the thing.
regards
Kinshuk

ifconfig only changes the running config.
When you reboot it will be lost.
The easy way is to run sys-unconfig.
Then reboot and it will ask for IP address etc again.
If you know what you are doing, you can edit the files.
Look in the sys-unconfig man page for the list of files it modifies.
The files in question are roughly
/etc/hosts
/etc/inet/ipnodes
/etc/defaultrouter
/etc/netmasks.
if you are changing the hostname as well as the IP then there are more files to change.

Confused about ZFS filesystems created with Solaris 11 Zone

Hello.
Installing a blank Zone in Solaris *10* with "zonepath=/export/zones/TESTvm01" just creates one zfs filesystem:
+"zfs list+
+...+
+rzpool/export/zones/TESTvm01 4.62G 31.3G 4.62G /export/zones/TESTvm01"+
Doing the same steps with Solaris *11* will ?create? more filesystems:
+"zfs list+
+...+
+rpool/export/zones/TESTvm05 335M 156G 32K /export/zones/TESTvm05+
+rpool/export/zones/TESTvm05/rpool 335M 156G 31K /rpool+
+rpool/export/zones/TESTvm05/rpool/ROOT 335M 156G 31K legacy+
+rpool/export/zones/TESTvm05/rpool/ROOT/solaris 335M 156G 310M /export/zones/TESTvm05/root+
+rpool/export/zones/TESTvm05/rpool/ROOT/solaris/var 24.4M 156G 23.5M /export/zones/TESTvm05/root/var+
+rpool/export/zones/TESTvm05/rpool/export 62K 156G 31K /export+
+rpool/export/zones/TESTvm05/rpool/export/home 31K 156G 31K /export/home"+
I dont understand why Solaris 11 is doing that. Just one FS (like in Solaris 10) would be better for my setup. I want to configure all created volumes by myself.
Is it possible to deactivate this automatic "feature"?

There are several reasons that it works like this, all guided by the simple idea "everything in a zone should work exactly like it does in the global zone, unless that is impractical." By having this layout we get:
* The same zfs administrative practices within a zone that are found in the global zone. This allows, for example, compression, encryption, etc. of parts of the zone.
* beadm(1M) and pkg(1) are able to create boot environments within the zone, thus making it easy to keep the global zone software in sync with non-global zone software as the system is updated (equivalent of patching in Solaris 10). Note that when Solaris 11 updates the kernel, core libraries, and perhaps other things, a new boot environment is automatically created (for the global zone and each zone) and the updates are done to the new boot environment(s). Thus, you get the benefits that Live Upgrade offered without the severe headaches that sometimes come with Live Upgrade.
* The ability to have a separate /var file system. This is required by policies at some large customers, such as the US Department of Defense via the DISA STIG.
* The ability to perform a p2v of a global zone into a zone (see solaris(5) for examples) without losing the dataset hierarchy or properties (e.g. compression, etc.) set on datasets in that hierarchy.
When this dataset hierarchy is combined with the fact that the ZFS namespace is virtualized in a zone (a feature called "dataset aliasing"), you see the same hierarchy in the zone that you would see in the global zone. Thus, you don't have confusing output from df saying that / is mounted on / and such.
Because there is integration between pkg, beadm, zones, and zfs, there is no way to disable this behavior. You can remove and optionally replace /export with something else if you wish.
If your goal is to prevent zone administrators from altering the dataset hierarchy, you may be able to accomplish this with immutable zones (see zones admin guide or file-mac-profile in zonecfg(1M)). This will have other effects as well, such as making all or most of the zone unwritable. If needed, you can add fs or dataset resources which will not be subject to file-mac-profile and as such will be writable.

Unable to detect iSCSI LUN size change on Solaris 10

I resized (grew) an OpenFiler iSCSI LUN, but I cannot get Solaris 10 to pick up the change. Using the type -> autoconfigure in format and relabeling the disk ought to do the trick but it does not work. Does anybody know how to overcome this?

Hmm, what filesystem do you have on the disk?
.7/M.

Nslookup output changes between Solaris 8 and 10

I have a customer that has asked why and if the output can be changed to match?
We have noticed a difference on the nslookup reverse lookup with
Solaris 10.
On Solaris 8 we get:
# nslookup x.x.x.x
Server: dnsserver.csd.disa.mil
Address: x.x.x.x
Name: hostname.my.af.mil
Address: x.x.x.x
On Solaris 10 we get:
# nslookup x.x.x.x
Server: x.x.x.x
Address: x.x.x.x#53
x.x.x.x(server ip in reverse).in-addr.arpa name =
hostname.my.af.mil.
Why is the output on Solaris 10 different when doing an nslookup on
the IP
address? The guys who work on the application noticed it and
opened a
ticket. Is there something I can do to get the output to come out
like it
does on Solaris 8.Any and all help would be appreciated....

SPARC doesn't need a split boot loader like BIOS/x86. The OBP can directly load from any slice. So 'boot disk:a' would boot from slice 0 and 'boot disk:g' would boot from slice 6.
Darren

How to change current Solaris version for a program?

Hello,
A program I am trying to run under Solaris 5.10 checks the OS version to be 5.8 or 5.9.
Can I somehow tell Solaris to report 5.9 to the program instead of 5.10?
According to "Solaris Application Guarantee" I should be able to run 5.8/9 programs under Solaris 10 with no problems.
Thakns,
Victor

You can use dtrace to manipulate the OS version on-the-fly.
eg.,
% cat sysrelease.d
#!/usr/sbin/dtrace -Cws
#include <sys/utsname.h>
syscall::uname:entry
this->in = (struct utsname *)arg0;
syscall::uname:return
copyoutstr($$1, (uintptr_t)&this->in->release[0], SYS_NMLN);
}This script accepts an argument, the version of our choice; so as long as the script is running, OS returns our input as output to uname -r. Once the script exits, OS returns the true version.
% uname -a
SunOS sunfire4 5.10.1 snv_10 sun4u sparc SUNW,Sun-Fire-1280R
% ./sysrelease.d 5.9
dtrace: script './sysrelease.d' matched 2 probes
dtrace: allowing destructive actions
.. script waits here doing nothing ..
In another window:
% uname -a
SunOS sunfire4 5.9 snv_10 sun4u sparc SUNW,Sun-Fire-1280RComplete the software installation. Once it is done, go back to the previous window, and stop the script by pressing Ctrl-C

Zfs kstats changed in Solaris 11 - breaks arcstat

Similar Messages

Maybe you are looking for