Re: [OpenIndiana-discuss] oracle removes 32bit x86 cpu support for solaris 11 will OI do same?
On Wed, Jun 22, 2011 at 4:05 AM, Jonathan Adams wrote: > One that strikes me as odd on that list is under "OpenWindows Libraries" > > "... However, if required, the applications that use OpenWindows > Libraries can be run in Oracle Solaris 10 Zones" > > I thought that the renumbering of zones was just that and not a > rebranding with libraries ... in fact I was pretty certain that that > was advised against. "Oracle Solaris 10 Zones" are branded zones that run on Oracle Solaris 11 Express 2010.11 and the notice you cite implies will continue to run on Solaris 11. This is analogous to the Solaris 8 Containers and Solaris 9 Containers products that used branded zones to run Solaris 8 and Solaris 9 userland bits on Solaris 10. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ECC question
On Sun, Feb 20, 2011 at 9:09 AM, taemun wrote: > Note that ZFS isn't intrinsically any more likely to die from a bad bit in > RAM than any given file system, but it is going to be able to *tell you when > it occurs*. Actually, zfs is far more likely to have problems due to a bad bit. Most file systems blindly pass bad data from disk to the application. ZFS verifies the integrity of what it reads before sending it to the application. It does this by comparing the checksum (cryptographic hash, actually) of a block with the checksum that was stored on disk when the block was written to disk. If it detects corrupt data (via a checksum mismatch) it will look to see if there are other copies of the data and try to self correct. This is great. However, suppose that before writing the data, there was a single bit error in the memory holding the checksum while or after computing the checksum. This will cause an invalid checksum to be written along with the data. Next time this data and checksum are read from disk (e.g. after the next reboot), the checksum will not match the checksum that is computed from the data that is on disk. It will not be able to correct it either. The same problem could occur if there are any errors in the memory holding file data - so long as that corruption happens after the checksum is computed but before the data is sent to disk. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ZFS single drive CKSUM errors
On Sat, Jan 22, 2011 at 4:08 PM, Michelle Knight wrote: > Hi Folks, > > Something I don't understand. > > A single drive with a ZFS partition on it. No mirror, no raid, no nothing. > > I copied a load of files to it and did a scrub. > > It encountered six checksum errors and was able to recover from them ... > without having any mirror or other redundant reference ... it didn't lose a > single file. > > Now ... am I mad, or does this mean I've got corruption somewhere, or how did > ZFS manage to recover from cksum errors that it detected on a single drive? > > I haven't managed to read anything yet which goes to the depth of explaining > this. > > Can someone help me on this please? Perhaps you have bad RAM. I'd suggest booting from a CD that contains memtest86 to see what it says. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] inetadm and svcadm
On Fri, Jan 14, 2011 at 1:18 PM, ann kok wrote: > I can ps -ef|grep nagios > > But I can't see how to start the nagios in it > > svcs -a list | grep nagios <== nothing > > How does it start? If it was started by an SMF service and it has not abandoned the contract, you should be able to find the pid in the output of "svcs -p" -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] man pages to solaris cmds
On Sun, Dec 19, 2010 at 8:46 PM, Harry Putnam wrote: > I couldn't make heads or tails of that. . sorry. Perhaps the kinder, gentler heads up message will make more sense. http://hub.opensolaris.org/bin/view/Community+Group+on/2008051501 -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] man pages to solaris cmds
On Sat, Dec 18, 2010 at 7:08 PM, Calum Mackay wrote: > hi Harry, > >> What is the MANPATH to the solaris cmds that there are also gnu >> versions of. > > man -M /usr/share/man ls > > is what you're after :) > > Assuming your MANPATH is by default: > > /usr/gnu/share/man:/usr/share/man:/usr/X11/share/man > > so you get the GNU man pages first... And if you don't set your MANPATH, it will man will give you the man page that is appropriate for your path. For most users, having MANPATH set is more likely to do harm than good. http://arc.opensolaris.org/caselog/PSARC/2007/688/20071212_mike.gerdts -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] samba keeps dumping core on oi_147
On Tue, Oct 26, 2010 at 10:25 PM, Christopher Chan wrote: > Ah, so that's where I can tell SMF to leave things alone. I concur. Running > smbd unmanaged has resulted in zero samba downtime. As for the core dumps... > > In the logs: smbd[22213] setid process, core not dumped: > > coreadm > global core file pattern: /var/cores/%d/%f.%p.%n This directory needs to exist. That is, /var/cores/smbd needs to exist with this pattern. If the directory doesn't exist, you should be getting messages in /var/adm/messages (depending on syslog setup) that says that the core dump failed because the directory doesn't exist. I tend to avoid using / in the pattern after the first %. That is, I'd be more inclined to use /var/cores/%d.%f.%p.%n. If you are aware of what you are doing, the pattern than you use can be effective for selectively getting core dumps from only certain processes. I commonly use this technique (core file pattern puts core files in /var/cores, but /var/cores doesn't usually exist) to get a log entry in /var/adm/messages saying that something tried to dump core without filling /var. This has helped me many times when application admins come to me to tell me that somebody is killing their processes. If I care to capture some core files, I'll create the /var/cores directory until I get however many I am looking for. > global core file content: all > init core file pattern: core > init core file content: default > global core dumps: enabled > per-process core dumps: enabled > global setid core dumps: enabled > per-process setid core dumps: enabled > global core dump logging: enabled > > What am I missing? > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] samba keeps dumping core on oi_147
On Tue, Oct 26, 2010 at 9:43 PM, Albert Lee wrote: > On Mon, Oct 25, 2010 at 11:53 PM, Christopher Chan > wrote: >> So I ran truss on the master smbd process... >> >> It appears that something fired a SIGTERM arrow at it and then tried to >> cancel it with a SIGCONT arrow or something? > > Not sure about the cause of the crash, but the truss output appears to > be Samba trying to perform an orderly shutdown after it gets the first > SIGTERM from the SMF stop method. This is likely a result of SMF detecting that something in the service is sick (dumped core) and as such is performing a restart. The default configuration of the apache22 service is smart enough to delegate this work to httpd, which already knows how to deal with children that core dump. From /lib/svc/manifest/network/http-apache22.xml: Perhaps the samba smf service requires a similar configuration. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] UFS supported?
On Sun, Sep 26, 2010 at 9:00 PM, Yi Zhang wrote: > 2010/9/26 Ignacio Marambio Catán : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 9/26/2010 10:49 PM, Yi Zhang wrote: >> >> supported for what purpose? you will not be able to use UFS as your root >> filesystem, IPS which is openindiana's package manager relies on ZFS. >> what would you want UFS for anyway? > I don't need UFS for the root FS, just for an application which relies > on some UFS features (e.g., direct I/O). > I would fully expect to see UFS live on for quite a few years for non-root file systems. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
