From bluethundr at gmail.com  Fri Jun  1 15:11:44 2012
From: bluethundr at gmail.com (Tim Dunphy)
Date: Fri, 1 Jun 2012 11:11:44 -0400
Subject: [OpenIndiana-discuss] chicken and egg file sharing problem
Message-ID: <CAOZy0en4vLDby5W9K6V=f4LRWSYE0FKEaoB8P0LorizMKMRcEA@mail.gmail.com>

Hey list,

I'm attempting to use a centos 6 iso mounted on loopback on my
openindiana box so that I can install centos on another machine via
nfs. Problem is that if I mount the disk on the oi box via lofiadm
then I can't share it via NFS because the directory I'm attempting to
share has files in it -

[root at openindiana:~] #lofiadm -a /tank/iso/CentOS-6.2-i386-bin-DVD1.iso
/dev/lofi/1

[root at openindiana:~] #mount -F hsfs -o ro /dev/lofi/1 /tank/iso/centos

[root at openindiana:~] #df -h /tank/iso/centos
Filesystem             size   used  avail capacity  Mounted on
/dev/lofi/1            3.6G   3.6G     0K   100%    /tank/iso/centos

[root at openindiana:~] # zfs set sharenfs=rw=@192.168.1.0/24,anon=0
tank/iso/centos
cannot mount '/tank/iso/centos': directory is not empty
property may be set but unable to remount filesystem


Basically I'm just looking for a way to accomplish the goal of sharing
this disk so that I can install it on another machine. Does anyone
have any suggestions?

Thanks!
Tim
-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B


From ko at research.att.com  Fri Jun  1 15:12:42 2012
From: ko at research.att.com (Kostas Oikonomou)
Date: Fri, 01 Jun 2012 11:12:42 -0400
Subject: [OpenIndiana-discuss] libmtsk.so and Solaris Studio 12.3 with
	libsunperf
Message-ID: <4FC8DBEA.1090800@research.att.com>

Is there any chance of updating the /lib/libmtsk.so.1 and 
/lib/amd64/libmtsko.so.1 that come with OI 151a3 to
version SUNWprivate_1.5?

This version is required by Solaris (Oracle) Studio 12.3's 
libsunperf.  Without this update, libsunperf is apparently 
not usable.
You cannot get programs to compile because of

Undefined            first referenced
  symbol                  in file
__mt_static_for_loop                
/opt/solstudio/lib/amd64/libsunperf.so


                 Kostas


From carlsonj at workingcode.com  Fri Jun  1 16:06:04 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Fri, 01 Jun 2012 12:06:04 -0400
Subject: [OpenIndiana-discuss] chicken and egg file sharing problem
In-Reply-To: <CAOZy0en4vLDby5W9K6V=f4LRWSYE0FKEaoB8P0LorizMKMRcEA@mail.gmail.com>
References: <CAOZy0en4vLDby5W9K6V=f4LRWSYE0FKEaoB8P0LorizMKMRcEA@mail.gmail.com>
Message-ID: <4FC8E86C.80904@workingcode.com>

Tim Dunphy wrote:
> [root at openindiana:~] #mount -F hsfs -o ro /dev/lofi/1 /tank/iso/centos

At this point you have a CD/DVD image mounted on /tank/iso/centos.
It'll be read-only.

> [root at openindiana:~] # zfs set sharenfs=rw=@192.168.1.0/24,anon=0
> tank/iso/centos
> cannot mount '/tank/iso/centos': directory is not empty
> property may be set but unable to remount filesystem

That command doesn't quite make sense.  The data you want to share is in
the CD/DVD image, not ZFS, so why ask ZFS to share anything?  And the
thing you're sharing is read-only, so how is a read-write share going to
work?

I think there's a fundamental misunderstanding here.  Once you've got a
file system mounted, you can just share it:

share -o anon=0 /tank/iso/centos

But maybe that's not quite what you want.  If you really want a writable
file system, mount up the CD/DVD image and copy it over to a ZFS file
system, then share the copied ZFS file system as you wish.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From milan.jurik at xylab.cz  Fri Jun  1 16:22:16 2012
From: milan.jurik at xylab.cz (Milan Jurik)
Date: Fri, 01 Jun 2012 18:22:16 +0200
Subject: [OpenIndiana-discuss] libmtsk.so and Solaris Studio 12.3 with
 libsunperf
In-Reply-To: <4FC8DBEA.1090800@research.att.com>
References: <4FC8DBEA.1090800@research.att.com>
Message-ID: <1338567736.1313.18.camel@xylabone>

Hi,

no. It looks like Oracle moved libmtsk to system/library/openmp package
with something called openmp.license. From the license only one header
file is under BSD like license, the rest is owned by Oracle and not
redistributable. So there is no legal way to publish newer libmtsk in
OpenIndiana, only if somebody reimplements libmtsk :-(

Best regards,

Milan

Kostas Oikonomou p??e v p? 01. 06. 2012 v 11:12 -0400:
> Is there any chance of updating the /lib/libmtsk.so.1 and 
> /lib/amd64/libmtsko.so.1 that come with OI 151a3 to
> version SUNWprivate_1.5?
> 
> This version is required by Solaris (Oracle) Studio 12.3's 
> libsunperf.  Without this update, libsunperf is apparently 
> not usable.
> You cannot get programs to compile because of
> 
> Undefined            first referenced
>   symbol                  in file
> __mt_static_for_loop                
> /opt/solstudio/lib/amd64/libsunperf.so
> 
> 
>                  Kostas
> 




From rlhamil at smart.net  Sat Jun  2 05:45:05 2012
From: rlhamil at smart.net (Richard L. Hamilton)
Date: Sat, 2 Jun 2012 01:45:05 -0400
Subject: [OpenIndiana-discuss] zfs question - when can _rewriting_ a block
	of a file fail on out-of-space?
Message-ID: <BE8B4A3E-0E10-48C5-9A46-81BA2BA51B22@smart.net>

In a non-COW filesystem, one would expect that rewriting an already allocated block would never fail for out-of-space (ENOSPC).

But I would expect that it could on ZFS - definitely if there was a snapshot around, as it would create a divergence from that snapshot (because both blocks would be kept).  Or if deduplication was in effect, and the new block contents were unique when the old contents hadn't been unique.

Could rewriting a block _ever_ fail with ENOSPC if there _wasn't_ a snapshot present, or is the replace old block with new somehow guaranteed to succeed, so as to avoid introducing unexpected semantics?  (say maybe there's a reserved amount of free space just for rewrites to avoid that sort of problem, or some other magic)

I would think DBMS developers allowing databases to be stored on ZFS, as well as folks using mmap(), might particularly want to be aware of the cases in which an errno not anticipated from experience with other filesystems might arise.



From k.nuyt at zonnet.nl  Sat Jun  2 07:36:56 2012
From: k.nuyt at zonnet.nl (Kees Nuyt)
Date: Sat, 02 Jun 2012 09:36:56 +0200
Subject: [OpenIndiana-discuss] zfs question - when can _rewriting_ a
	block of a file fail on out-of-space?
In-Reply-To: <BE8B4A3E-0E10-48C5-9A46-81BA2BA51B22@smart.net>
References: <BE8B4A3E-0E10-48C5-9A46-81BA2BA51B22@smart.net>
Message-ID: <vofjs7d29tnnofaaio3bqraqqgignqqsse@dim53.demon.nl>

On Sat, 2 Jun 2012 01:45:05 -0400, you wrote:

> In a non-COW filesystem, one would expect that rewriting 
> an already allocated block would never fail for 
> out-of-space (ENOSPC).
>
> But I would expect that it could on ZFS - definitely if 
> there was a snapshot around, as it would create a 
> divergence from that snapshot (because both blocks would 
> be kept). Or if deduplication was in effect, and the new 
> block contents were unique when the old contents hadn't 
> been unique.

Not only then. Every block written obeys COW, the previous version is
always retained. The new version of the block is always a new
allocation. The previous version is released over time, when nothing
refers to it anymore.

> Could rewriting a block _ever_ fail with ENOSPC if there 
> _wasn't_ a snapshot present, 

Yes.

> or is the replace old block 
> with new somehow guaranteed to succeed, so as to avoid 
> introducing unexpected semantics? (say maybe there's a 
> reserved amount of free space just for rewrites to avoid 
> that sort of problem, or some other magic)

No. You have to monitor the used capacity of the pool, with alert
thresholds of, for example, 80% (warning), 95% (critical) and 98%
(fatal).
 
It might make sense to limit the size per filesystem using quota to
avoid the pool from filling up completely, protecting one zfs against
another zfs.

> I would think DBMS developers allowing databases to be 
> stored on ZFS, as well as folks using mmap(), might 
> particularly want to be aware of the cases in which an 
> errno not anticipated from experience with other 
> filesystems might arise.

http://assets.en.oreilly.com/1/event/21/Optimizing%20MySQL%20Performance%20with%20ZFS%20Presentation.pdf

-- 
Regards,

Kees Nuyt



From stream at willows7.myzen.co.uk  Sat Jun  2 09:27:23 2012
From: stream at willows7.myzen.co.uk (russell)
Date: Sat, 02 Jun 2012 10:27:23 +0100
Subject: [OpenIndiana-discuss] Nvidia Driver 295.53
Message-ID: <4FC9DC7B.7000707@willows7.myzen.co.uk>

Hi,

I noticed after upgrading to Nvidia Driver 295.53 that the driver 
supports a colour depth of 30 giving 1.1 billion colours as an 
experimental feature does the current release of X implemented in 
OI_151.1.4 support the 30 bit colour depth. If the 30 bit colour depth 
is selected it warns about X support and that some applications do not 
support 30bit depth. If the application does not support  30 bit depth 
will it operate at 24 bit depth and still be displayed or will the 
application not display anything or crash?




From lattera at gmail.com  Sat Jun  2 14:59:24 2012
From: lattera at gmail.com (Shawn Webb)
Date: Sat, 2 Jun 2012 08:59:24 -0600
Subject: [OpenIndiana-discuss] zfs send issue
Message-ID: <CADt0fhwgZzX-a6HMRt2j6qVEhhDEEYXvyGudY=zM+xAyN3oDzg@mail.gmail.com>

Hey All,

It looks like `zfs send -rp ...` isn't working on 151a4:

[paste]
shawn at indianapolis:/backup$ uname -a
SunOS indianapolis 5.11 oi_151a4 i86pc i386 i86pc Solaris
shawn at indianapolis:/backup$ pfexec zfs send -r -p tank\@2012-06-02_0847 >
tank\@2012-06-02_0847.zfs
invalid option 'r'
usage:
        send [-DnPpRrv] [-[iI] snapshot] <snapshot>

For the property list, run: zfs set|get

For the delegated permission list, run: zfs allow|unallow
[/paste]

Am I doing it wrong?

Thanks,

Shawn

From lattera at gmail.com  Sat Jun  2 15:01:40 2012
From: lattera at gmail.com (Shawn Webb)
Date: Sat, 2 Jun 2012 09:01:40 -0600
Subject: [OpenIndiana-discuss] zfs send issue
In-Reply-To: <CADt0fhwgZzX-a6HMRt2j6qVEhhDEEYXvyGudY=zM+xAyN3oDzg@mail.gmail.com>
References: <CADt0fhwgZzX-a6HMRt2j6qVEhhDEEYXvyGudY=zM+xAyN3oDzg@mail.gmail.com>
Message-ID: <CADt0fhzAc03wc2G+gMeH5CMn_Ta5ThpzKvzaNo2Ub+E3ByddAw@mail.gmail.com>

Nevermind. -R is the flag I want. But I'm still curious as to why -r didn't
work.

On Sat, Jun 2, 2012 at 8:59 AM, Shawn Webb <lattera at gmail.com> wrote:

> Hey All,
>
> It looks like `zfs send -rp ...` isn't working on 151a4:
>
> [paste]
> shawn at indianapolis:/backup$ uname -a
> SunOS indianapolis 5.11 oi_151a4 i86pc i386 i86pc Solaris
> shawn at indianapolis:/backup$ pfexec zfs send -r -p tank\@2012-06-02_0847 >
> tank\@2012-06-02_0847.zfs
> invalid option 'r'
> usage:
>         send [-DnPpRrv] [-[iI] snapshot] <snapshot>
>
> For the property list, run: zfs set|get
>
> For the delegated permission list, run: zfs allow|unallow
> [/paste]
>
> Am I doing it wrong?
>
> Thanks,
>
> Shawn
>

From jsowoc at gmail.com  Sat Jun  2 15:40:54 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Sat, 2 Jun 2012 09:40:54 -0600
Subject: [OpenIndiana-discuss] Nvidia Driver 295.53
In-Reply-To: <4FC9DC7B.7000707@willows7.myzen.co.uk>
References: <4FC9DC7B.7000707@willows7.myzen.co.uk>
Message-ID: <CADCwuEa8SwX2p24W6j=r_KGExHOSFrHC0OBajsj4BH3+7y39-g@mail.gmail.com>

Hi,

On Sat, Jun 2, 2012 at 3:27 AM, russell <stream at willows7.myzen.co.uk> wrote:
> I noticed after upgrading to Nvidia Driver 295.53 that the driver supports a
> colour depth of 30 giving 1.1 billion colours as an experimental feature
> does the current release of X implemented in OI_151.1.4 support the 30 bit
> colour depth. If the 30 bit colour depth is selected it warns about X
> support and that some applications do not support 30bit depth. If the
> application does not support ?30 bit depth will it operate at 24 bit depth
> and still be displayed or will the application not display anything or
> crash?

I have two pieces of anecdotal evidence.

1) For some time in the 1990s I was using a Matrox card that supported
a 10-bit-per-channel depth, and I didn't run into any programs that
would misbehave (luck?).

2) I currently use a certain image viewing program that requires that
the display be exactly 8 bits (total) or it will crash. To run it, I
need to restart X in 8-bit mode or run something like Xephyr.

I would guess that many programs should be fine, especially the
relatively common ones, but you may run into a specific applications
that don't know what to do if the number of colours doesn't match what
it expects.

Jan


From oi at stephanws.de  Sat Jun  2 15:44:36 2012
From: oi at stephanws.de (=?ISO-8859-15?Q?J=F6rg_Stephan?=)
Date: Sat, 02 Jun 2012 17:44:36 +0200
Subject: [OpenIndiana-discuss] Froscon
Message-ID: <4FCA34E4.5000703@stephanws.de>

  Hi,

will openindiana (or illumos) run a booth at froscon this year?

http://www.froscon.de/en/home/

Regards

J?rg


From bfriesen at simple.dallas.tx.us  Sat Jun  2 16:21:24 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Sat, 2 Jun 2012 11:21:24 -0500 (CDT)
Subject: [OpenIndiana-discuss] Nvidia Driver 295.53
In-Reply-To: <4FC9DC7B.7000707@willows7.myzen.co.uk>
References: <4FC9DC7B.7000707@willows7.myzen.co.uk>
Message-ID: <alpine.GSO.2.01.1206021113320.21691@freddy.simplesystems.org>

On Sat, 2 Jun 2012, russell wrote:

> I noticed after upgrading to Nvidia Driver 295.53 that the driver supports a 
> colour depth of 30 giving 1.1 billion colours as an experimental feature does 
> the current release of X implemented in OI_151.1.4 support the 30 bit colour 
> depth. If the 30 bit colour depth is selected it warns about X support and 
> that some applications do not support 30bit depth. If the application does 
> not support  30 bit depth will it operate at 24 bit depth and still be 
> displayed or will the application not display anything or crash?

I don't see much value to enabling 30-bit color depth unless you have 
a display and path to that display which supports 10-bits/channel. 
There are LCD panels available which support 10-bits/channel via 
DisplayPort.  Many modern TVs will accept 10-bits/channel via HDMI, 
even if they don't internally support all the levels.  Professional 
displays supporting HD-SDI will support 10-bits/channel and Nvidia 
offers boards with an HD-SDI output.

There might be some value offered from 30-bit color depth when using 
OpenGL since the extra depth may improve the quality of calculations, 
even if you can not see a visual improvement to the results.  However, 
OpenGL also supports floating-point types.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From me at cs.Stanford.EDU  Sat Jun  2 19:09:40 2012
From: me at cs.Stanford.EDU (Martin Frost)
Date: Sat, 02 Jun 2012 12:09:40 -0700
Subject: [OpenIndiana-discuss] zfs send issue
In-Reply-To: <CADt0fhzAc03wc2G+gMeH5CMn_Ta5ThpzKvzaNo2Ub+E3ByddAw@mail.gmail.com>
	(message from Shawn Webb on Sat, 2 Jun 2012 09:01:40 -0600)
Message-ID: <E1Sathk-0005e9-Nk@sunburn.Stanford.EDU>

Judging from my (oi_148) man page for zfs, there is simply no -r
option for zfs send:

     zfs send [-DvRp] [-[iI] snapshot] snapshot

Martin

 > Date: Sat, 2 Jun 2012 09:01:40 -0600
 > From: Shawn Webb <lattera at gmail.com>
 > 
 > Nevermind. -R is the flag I want. But I'm still curious as to why -r didn't
 > work.
 > 
 > On Sat, Jun 2, 2012 at 8:59 AM, Shawn Webb <lattera at gmail.com> wrote:
 > 
 > > Hey All,
 > >
 > > It looks like `zfs send -rp ...` isn't working on 151a4:
 > >
 > > [paste]
 > > shawn at indianapolis:/backup$ uname -a
 > > SunOS indianapolis 5.11 oi_151a4 i86pc i386 i86pc Solaris
 > > shawn at indianapolis:/backup$ pfexec zfs send -r -p tank\@2012-06-02_0847 >
 > > tank\@2012-06-02_0847.zfs
 > > invalid option 'r'
 > > usage:
 > >         send [-DnPpRrv] [-[iI] snapshot] <snapshot>
 > >
 > > For the property list, run: zfs set|get
 > >
 > > For the delegated permission list, run: zfs allow|unallow
 > > [/paste]
 > >
 > > Am I doing it wrong?
 > >
 > > Thanks,
 > >
 > > Shawn
 > >
 > _______________________________________________
 > OpenIndiana-discuss mailing list
 > OpenIndiana-discuss at openindiana.org
 > http://openindiana.org/mailman/listinfo/openindiana-discuss
 > 


From lattera at gmail.com  Sat Jun  2 19:12:48 2012
From: lattera at gmail.com (Shawn Webb)
Date: Sat, 2 Jun 2012 13:12:48 -0600
Subject: [OpenIndiana-discuss] zfs send issue
In-Reply-To: <E1Sathk-0005e9-Nk@sunburn.Stanford.EDU>
References: <CADt0fhzAc03wc2G+gMeH5CMn_Ta5ThpzKvzaNo2Ub+E3ByddAw@mail.gmail.com>
	<E1Sathk-0005e9-Nk@sunburn.Stanford.EDU>
Message-ID: <CADt0fhy8sTxtGtZ1OHBYoowh3ZLC7X3=V3_yqKF=-c2pW4O4xg@mail.gmail.com>

On oi_151a4, there is in both the man page and in the usage:

shawn at indianapolis:~$ uname -a
SunOS indianapolis 5.11 oi_151a4 i86pc i386 i86pc Solaris
shawn at indianapolis:~$ zfs send
missing snapshot argument
usage:
        send [-DnPpRrv] [-[iI] snapshot] <snapshot>

For the property list, run: zfs set|get

For the delegated permission list, run: zfs allow|unallow

On Sat, Jun 2, 2012 at 1:09 PM, Martin Frost <me at cs.stanford.edu> wrote:

> Judging from my (oi_148) man page for zfs, there is simply no -r
> option for zfs send:
>
>     zfs send [-DvRp] [-[iI] snapshot] snapshot
>
> Martin
>
>  > Date: Sat, 2 Jun 2012 09:01:40 -0600
>  > From: Shawn Webb <lattera at gmail.com>
>  >
>  > Nevermind. -R is the flag I want. But I'm still curious as to why -r
> didn't
>  > work.
>  >
>  > On Sat, Jun 2, 2012 at 8:59 AM, Shawn Webb <lattera at gmail.com> wrote:
>  >
>  > > Hey All,
>  > >
>  > > It looks like `zfs send -rp ...` isn't working on 151a4:
>  > >
>  > > [paste]
>  > > shawn at indianapolis:/backup$ uname -a
>  > > SunOS indianapolis 5.11 oi_151a4 i86pc i386 i86pc Solaris
>  > > shawn at indianapolis:/backup$ pfexec zfs send -r -p
> tank\@2012-06-02_0847 >
>  > > tank\@2012-06-02_0847.zfs
>  > > invalid option 'r'
>  > > usage:
>  > >         send [-DnPpRrv] [-[iI] snapshot] <snapshot>
>  > >
>  > > For the property list, run: zfs set|get
>  > >
>  > > For the delegated permission list, run: zfs allow|unallow
>  > > [/paste]
>  > >
>  > > Am I doing it wrong?
>  > >
>  > > Thanks,
>  > >
>  > > Shawn
>  > >
>  > _______________________________________________
>  > OpenIndiana-discuss mailing list
>  > OpenIndiana-discuss at openindiana.org
>  > http://openindiana.org/mailman/listinfo/openindiana-discuss
>  >
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>

From realrichardsharpe at gmail.com  Sun Jun  3 03:59:13 2012
From: realrichardsharpe at gmail.com (Richard Sharpe)
Date: Sat, 2 Jun 2012 20:59:13 -0700
Subject: [OpenIndiana-discuss] Getting an OpenIndiana dev VM to fix some
 issues with the Samba master branch on OpenIndiana
Message-ID: <CACyXjPxi_gjyiTz_D=kNrXkFamVcO9gByiDFcwpifYcan-FsbA@mail.gmail.com>

Hi Folks,

I need to track down why some fairly standard make magic I added to
the examples/VFS/Makefile.in does not seem to work on the OpenIndiana
machine in the Samba build farm.

I tried installing oi-dev-151a in a VM, and that seemed to work well.
However, when I tried to use the package manager to install the
development packages it told me that I had a live install and I
couldn't do that.

How do I rectify this? Do I need to re-install? Is there some other
way to transition to something that will allow me to install the
development packages I need?

-- 
Regards,
Richard Sharpe
(??????????--??)


From jay at frelled.us  Sun Jun  3 04:14:32 2012
From: jay at frelled.us (Jay Heyl)
Date: Sat, 2 Jun 2012 21:14:32 -0700
Subject: [OpenIndiana-discuss] ZFS restore from snapshot
Message-ID: <CAACKFonqSuPFpF9dWLJp_6Pd6ZRJTTXQ5vKMxbdc8Ezxs_CYpQ@mail.gmail.com>

I have a file that shows as corrupted in the live file system and two
snapshots. The file gives every indication of being valid in earlier
snapshots. I've tried to restore it from the good snapshot but it doesn't
seem to want to take. After several failed attempts to copy directly from
the snapshot, I copied from the snapshot to my home directory. That copy
appears to be good. (It's an image file and the image comes up fine.) I've
deleted the file from the live directory and it seems to disappear. But
every time I copy the file from my home directory into the target
directory, the target directory copy appears corrupted.

With most other file systems I'd suspect this indicates a problem with the
directory rather than with the actual file, but I don't know enough about
zfs to judge whether this makes sense or not.

Any ideas what might be going on with this file and how I can get it
restored from the good snapshot?

The other odd thing, not directly related to getting it restored, is that
neither the file nor the directory it's in has been purposely changed since
the time of the good snapshot. Obviously something changed or there
wouldn't be any difference between the live version and the snapshot, but
I'm bewildered about how it might have happened.

From mike.laspina at laspina.ca  Sun Jun  3 12:35:05 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Sun, 3 Jun 2012 07:35:05 -0500
Subject: [OpenIndiana-discuss] ZFS restore from snapshot
In-Reply-To: <CAACKFonqSuPFpF9dWLJp_6Pd6ZRJTTXQ5vKMxbdc8Ezxs_CYpQ@mail.gmail.com>
References: <CAACKFonqSuPFpF9dWLJp_6Pd6ZRJTTXQ5vKMxbdc8Ezxs_CYpQ@mail.gmail.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D46D3@MS1.laspina.ca>

I would suggest you run a zpool scrub.

-----Original Message-----
From: Jay Heyl [mailto:jay at frelled.us] 
Sent: Saturday, June 02, 2012 11:15 PM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] ZFS restore from snapshot

I have a file that shows as corrupted in the live file system and two
snapshots. The file gives every indication of being valid in earlier
snapshots. I've tried to restore it from the good snapshot but it
doesn't seem to want to take. After several failed attempts to copy
directly from the snapshot, I copied from the snapshot to my home
directory. That copy appears to be good. (It's an image file and the
image comes up fine.) I've deleted the file from the live directory and
it seems to disappear. But every time I copy the file from my home
directory into the target directory, the target directory copy appears
corrupted.

With most other file systems I'd suspect this indicates a problem with
the directory rather than with the actual file, but I don't know enough
about zfs to judge whether this makes sense or not.

Any ideas what might be going on with this file and how I can get it
restored from the good snapshot?

The other odd thing, not directly related to getting it restored, is
that neither the file nor the directory it's in has been purposely
changed since the time of the good snapshot. Obviously something changed
or there wouldn't be any difference between the live version and the
snapshot, but I'm bewildered about how it might have happened.
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From richard.elling at richardelling.com  Sun Jun  3 13:54:58 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Sun, 3 Jun 2012 06:54:58 -0700
Subject: [OpenIndiana-discuss] zfs question - when can _rewriting_ a
	block of a file fail on out-of-space?
In-Reply-To: <BE8B4A3E-0E10-48C5-9A46-81BA2BA51B22@smart.net>
References: <BE8B4A3E-0E10-48C5-9A46-81BA2BA51B22@smart.net>
Message-ID: <8D642AE9-434A-4CAE-BFDB-81F0A2525533@RichardElling.com>

On Jun 1, 2012, at 10:45 PM, Richard L. Hamilton wrote:

> In a non-COW filesystem, one would expect that rewriting an already allocated block would never fail for out-of-space (ENOSPC).

This seems like a rather broad assumption. It may hold for FAT or UFS, but might not
hold for some of the more modern file systems (eg flash file systems) But I digress...

> But I would expect that it could on ZFS - definitely if there was a snapshot around, as it would create a divergence from that snapshot (because both blocks would be kept).  Or if deduplication was in effect, and the new block contents were unique when the old contents hadn't been unique.
> 
> Could rewriting a block _ever_ fail with ENOSPC if there _wasn't_ a snapshot present, or is the replace old block with new somehow guaranteed to succeed, so as to avoid introducing unexpected semantics?  (say maybe there's a reserved amount of free space just for rewrites to avoid that sort of problem, or some other magic)

There is a reserve at the pool level. It is needed for the ZIL at the very least.

> I would think DBMS developers allowing databases to be stored on ZFS, as well as folks using mmap(), might particularly want to be aware of the cases in which an errno not anticipated from experience with other filesystems might arise.

Those developers have to handle all error conditions anyway.

NB, many important databases are also COW, so the concept is well understood.
 -- richard

--
ZFS Performance and Training
Richard.Elling at RichardElling.com
+1-760-896-4422




From realrichardsharpe at gmail.com  Sun Jun  3 13:55:59 2012
From: realrichardsharpe at gmail.com (Richard Sharpe)
Date: Sun, 3 Jun 2012 06:55:59 -0700
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not gmake) to
	accept the following
Message-ID: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>

Hi folks,

I have figured out part of my problem with the OpenIndiana machine on
the Samba build farm.

It seems that the system goes not have GNU make installed or the
OpenIndiana version of make is first on the path.

We have the following in the Makefile:

.SUFFIXES: .so

.o.so:
        @echo "Linking $<"
        @$(CC) $(LDSHFLAGS) $(LDFLAGS) $*.o -o $*.so

and make is objecting with: Don't know how to make blah.so.

Is there any way to work around this?

-- 
Regards,
Richard Sharpe
(??????????--??)


From josh at sysmgr.org  Sun Jun  3 14:34:23 2012
From: josh at sysmgr.org (Joshua M. Clulow)
Date: Mon, 4 Jun 2012 00:34:23 +1000
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
Message-ID: <CAEwA5nL9R54afbPr1GY1GMoazST0jF0S8DG1Ka46jXFW_oemPA@mail.gmail.com>

On 3 June 2012 23:55, Richard Sharpe <realrichardsharpe at gmail.com> wrote:
> We have the following in the Makefile:
> .SUFFIXES: .so
>
> .o.so:
> ? ? ? ?@echo "Linking $<"
> ? ? ? ?@$(CC) $(LDSHFLAGS) $(LDFLAGS) $*.o -o $*.so
>
> and make is objecting with: Don't know how to make blah.so.
>
> Is there any way to work around this?

You need both suffixes in .SUFFIXES...

i.e.

.SUFFIXES: .down .up
TR= /usr/bin/tr
.down.up:
        @echo "Munging $<"
        $(TR) "[:lower:]" "[:upper:]" < $*.down > $*.up

-- 
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org


From realrichardsharpe at gmail.com  Sun Jun  3 14:59:03 2012
From: realrichardsharpe at gmail.com (Richard Sharpe)
Date: Sun, 3 Jun 2012 07:59:03 -0700
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <CAEwA5nL9R54afbPr1GY1GMoazST0jF0S8DG1Ka46jXFW_oemPA@mail.gmail.com>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
	<CAEwA5nL9R54afbPr1GY1GMoazST0jF0S8DG1Ka46jXFW_oemPA@mail.gmail.com>
Message-ID: <CACyXjPw+cqTXPYXGPwMd5U39t5XGcr-70z_XeGvR2+f=W3=XQg@mail.gmail.com>

On Sun, Jun 3, 2012 at 7:34 AM, Joshua M. Clulow <josh at sysmgr.org> wrote:
> On 3 June 2012 23:55, Richard Sharpe <realrichardsharpe at gmail.com> wrote:
>> We have the following in the Makefile:
>> .SUFFIXES: .so
>>
>> .o.so:
>>        @echo "Linking $<"
>>        @$(CC) $(LDSHFLAGS) $(LDFLAGS) $*.o -o $*.so
>>
>> and make is objecting with: Don't know how to make blah.so.
>>
>> Is there any way to work around this?
>
> You need both suffixes in .SUFFIXES...
>
> i.e.
>
> .SUFFIXES: .down .up
> TR= /usr/bin/tr
> .down.up:
>        @echo "Munging $<"
>        $(TR) "[:lower:]" "[:upper:]" < $*.down > $*.up

OK, thanks for that. Can I assume that .SUFFIXES operate additively
and does not replace any built-in ones?

-- 
Regards,
Richard Sharpe
(??????????--??)


From realrichardsharpe at gmail.com  Sun Jun  3 15:17:43 2012
From: realrichardsharpe at gmail.com (Richard Sharpe)
Date: Sun, 3 Jun 2012 08:17:43 -0700
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <CAEwA5nL9R54afbPr1GY1GMoazST0jF0S8DG1Ka46jXFW_oemPA@mail.gmail.com>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
	<CAEwA5nL9R54afbPr1GY1GMoazST0jF0S8DG1Ka46jXFW_oemPA@mail.gmail.com>
Message-ID: <CACyXjPw0EibWRsxhnVegmW0D8YZ6g0iSjPmiPAZ639knR1mP2A@mail.gmail.com>

On Sun, Jun 3, 2012 at 7:34 AM, Joshua M. Clulow <josh at sysmgr.org> wrote:
> On 3 June 2012 23:55, Richard Sharpe <realrichardsharpe at gmail.com> wrote:
>> We have the following in the Makefile:
>> .SUFFIXES: .so
>>
>> .o.so:
>>        @echo "Linking $<"
>>        @$(CC) $(LDSHFLAGS) $(LDFLAGS) $*.o -o $*.so
>>
>> and make is objecting with: Don't know how to make blah.so.
>>
>> Is there any way to work around this?
>
> You need both suffixes in .SUFFIXES...
>
> i.e.
>
> .SUFFIXES: .down .up
> TR= /usr/bin/tr
> .down.up:
>        @echo "Munging $<"
>        $(TR) "[:lower:]" "[:upper:]" < $*.down > $*.up
>

Hmmm, that does not _seem_ to be the case. Regardless of whether I have

   .SUFFIXES: .o .so

or

   .SUFFIXES: .so .o

I still get the same message indicating that it does not know how to
build a .so from a .o

(The indent above is for exposition purposes, the .SUFFIXES: is hard
up against the left hand column in the Makefile.)

-- 
Regards,
Richard Sharpe
(??????????--??)


From carlsonj at workingcode.com  Sun Jun  3 18:25:27 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Sun, 03 Jun 2012 14:25:27 -0400
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <CACyXjPw0EibWRsxhnVegmW0D8YZ6g0iSjPmiPAZ639knR1mP2A@mail.gmail.com>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
	<CAEwA5nL9R54afbPr1GY1GMoazST0jF0S8DG1Ka46jXFW_oemPA@mail.gmail.com>
	<CACyXjPw0EibWRsxhnVegmW0D8YZ6g0iSjPmiPAZ639knR1mP2A@mail.gmail.com>
Message-ID: <4FCBAC17.8020804@workingcode.com>

On 6/3/2012 11:17 AM, Richard Sharpe wrote:
> Hmmm, that does not _seem_ to be the case. Regardless of whether I have
> 
>    .SUFFIXES: .o .so
> 
> or
> 
>    .SUFFIXES: .so .o
> 
> I still get the same message indicating that it does not know how to
> build a .so from a .o
> 
> (The indent above is for exposition purposes, the .SUFFIXES: is hard
> up against the left hand column in the Makefile.)

That's not quite how the old-style implicit suffix rules work.  They
don't chain together in arbitrary ways, so the match is between suffixes
and dependencies.

Note that this is true of all implementations of 'make' -- not just the
one in OpenIndiana, but also GNU make and BSD make and others.

In other words, if you need foo.so and have only foo.c, then 'make' will
look for an implicit rule of the form ".c.so".  If such a rule exists,
it uses it.  If not, it's done with the implicit rule search.

If you have a ".o.so" rule, then either the "foo.o" file must already
exist for that rule to fire, or you need a dependency from the .so to
the .o file; otherwise, it's ignored.

If you have another dependency to complete the chain, then 'make' will
find the rules you're specifying.  For example, if you have this:

all:	foo.so
foo.so:	foo.o

Then make goes through these steps: first, it wants a target to build,
and it finds "all."  "All" depends on "foo.so", so it needs that.
"foo.so" depends on "foo.o", so, even though "foo.o" doesn't exist, it
goes on to build "foo.o" from the existing "foo.c", then looks for the
".o.so" rule, and finds it.

You can see some of the subtleties of this if you remove the "foo.so:"
dependency rule above and do "make foo.o" then "make".  The first run
will create "foo.o".  The second will create "foo.so" as expected.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From realrichardsharpe at gmail.com  Sun Jun  3 18:50:38 2012
From: realrichardsharpe at gmail.com (Richard Sharpe)
Date: Sun, 3 Jun 2012 11:50:38 -0700
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <4FCBAC17.8020804@workingcode.com>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
	<CAEwA5nL9R54afbPr1GY1GMoazST0jF0S8DG1Ka46jXFW_oemPA@mail.gmail.com>
	<CACyXjPw0EibWRsxhnVegmW0D8YZ6g0iSjPmiPAZ639knR1mP2A@mail.gmail.com>
	<4FCBAC17.8020804@workingcode.com>
Message-ID: <CACyXjPyoqQ8a+7awiP7iAj9CKJ0X84Bw-oMCm+E4ZwRWdtDijg@mail.gmail.com>

On Sun, Jun 3, 2012 at 11:25 AM, James Carlson <carlsonj at workingcode.com> wrote:
> On 6/3/2012 11:17 AM, Richard Sharpe wrote:
>> Hmmm, that does not _seem_ to be the case. Regardless of whether I have
>>
>>    .SUFFIXES: .o .so
>>
>> or
>>
>>    .SUFFIXES: .so .o
>>
>> I still get the same message indicating that it does not know how to
>> build a .so from a .o
>>
>> (The indent above is for exposition purposes, the .SUFFIXES: is hard
>> up against the left hand column in the Makefile.)
>
> That's not quite how the old-style implicit suffix rules work.  They
> don't chain together in arbitrary ways, so the match is between suffixes
> and dependencies.
>
> Note that this is true of all implementations of 'make' -- not just the
> one in OpenIndiana, but also GNU make and BSD make and others.

Well, that may be true, except, the original Makefile snippet has
successfully been used on FreeBSD and Linux (Fedora 14).

Expanding the snippet a bit more, what I currently have that is
working (and, it is always possible that I have accidentally found
something that works for gmake under Linux and the FreeBSD make, but
for reasons that I don't understand :-)

-----------------------------------------------------------
# Change these targets to the names of your modules if building out of tree
MODULES         = skel_opaque.so shadow_copy_test.so \
                skel_transparent.so

all: $(MODULES)

# Pattern rules

.SUFFIXES: .so

.o.so:
        @echo "Linking $<"
        @$(CC) $(LDSHFLAGS) $(LDFLAGS) $*.o -o $*.so

.c.o:
        @echo "Compiling $<"
        @$(CC) $(FLAGS) -c $< -D$*_init=samba_init_module

install: default
        $(INSTALLCMD) -d $(VFS_LIBDIR)
        $(INSTALLCMD) -m 755 *.$(SHLIBEXT) $(VFS_LIBDIR)

# Misc targets
clean:
        rm -rf .libs
        rm -f core *~ *% *.bak *.o *.$(SHLIBEXT)

distclean: clean
        rm -f config.status config.cache Makefile
------------------------------------------------

> In other words, if you need foo.so and have only foo.c, then 'make' will
> look for an implicit rule of the form ".c.so".  If such a rule exists,
> it uses it.  If not, it's done with the implicit rule search.

OK ... but

> If you have a ".o.so" rule, then either the "foo.o" file must already
> exist for that rule to fire, or you need a dependency from the .so to
> the .o file; otherwise, it's ignored.

The above works for Linux and FreeBSD ...

> If you have another dependency to complete the chain, then 'make' will
> find the rules you're specifying.  For example, if you have this:
>
> all:    foo.so
> foo.so: foo.o
>
> Then make goes through these steps: first, it wants a target to build,
> and it finds "all."  "All" depends on "foo.so", so it needs that.
> "foo.so" depends on "foo.o", so, even though "foo.o" doesn't exist, it
> goes on to build "foo.o" from the existing "foo.c", then looks for the
> ".o.so" rule, and finds it.
>
> You can see some of the subtleties of this if you remove the "foo.so:"
> dependency rule above and do "make foo.o" then "make".  The first run
> will create "foo.o".  The second will create "foo.so" as expected.

I will give what you suggest a try ... if it works on all three
platforms then I am happy.

-- 
Regards,
Richard Sharpe
(??????????--??)


From milan.jurik at xylab.cz  Sun Jun  3 19:03:12 2012
From: milan.jurik at xylab.cz (Milan Jurik)
Date: Sun, 03 Jun 2012 21:03:12 +0200
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
Message-ID: <1338750192.1300.7.camel@xylabone>

Hi Richard,

Richard Sharpe p??e v ne 03. 06. 2012 v 06:55 -0700:
> Hi folks,
> 
> I have figured out part of my problem with the OpenIndiana machine on
> the Samba build farm.
> 
> It seems that the system goes not have GNU make installed or the
> OpenIndiana version of make is first on the path.
> 

is gmake not installed? GNU make package with gmake 3.81 is
developer/build/gnu-make

Best regards,

Milan

> We have the following in the Makefile:
> 
> .SUFFIXES: .so
> 
> .o.so:
>         @echo "Linking $<"
>         @$(CC) $(LDSHFLAGS) $(LDFLAGS) $*.o -o $*.so
> 
> and make is objecting with: Don't know how to make blah.so.
> 
> Is there any way to work around this?
> 




From realrichardsharpe at gmail.com  Sun Jun  3 19:08:29 2012
From: realrichardsharpe at gmail.com (Richard Sharpe)
Date: Sun, 3 Jun 2012 12:08:29 -0700
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <1338750192.1300.7.camel@xylabone>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
	<1338750192.1300.7.camel@xylabone>
Message-ID: <CACyXjPwDhRDwBzh363A5nQhgt6dfgCncAFPVW2va5rX6P1MNvQ@mail.gmail.com>

On Sun, Jun 3, 2012 at 12:03 PM, Milan Jurik <milan.jurik at xylab.cz> wrote:
> Hi Richard,
>
> Richard Sharpe p??e v ne 03. 06. 2012 v 06:55 -0700:
>> Hi folks,
>>
>> I have figured out part of my problem with the OpenIndiana machine on
>> the Samba build farm.
>>
>> It seems that the system goes not have GNU make installed or the
>> OpenIndiana version of make is first on the path.
>>
>
> is gmake not installed? GNU make package with gmake 3.81 is
> developer/build/gnu-make

I don't know at this stage. I have to wait for the owner of the system
to respond to me.

However, I would like to find a solution that produces few surprises
for people :-)

So, if they do not have GNU make installed it should still work. I do,
however, need to improve the comments in the existing Makefile.in so
that people have an idea of what to do when things do not work ...

-- 
Regards,
Richard Sharpe
(??????????--??)


From jsowoc at gmail.com  Sun Jun  3 22:20:09 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Sun, 3 Jun 2012 16:20:09 -0600
Subject: [OpenIndiana-discuss] problems with permissions on smb share
Message-ID: <CADCwuEY5YJ-eWW-vmn3SyEYYoCNCdJwawQ3zsb3rZzTURKDrhQ@mail.gmail.com>

Hi,

I've been using OpenIndiana151 for a home file server for several
months now with good success, but am running into a curious problem.
When I copy a file from Windows to the smb share, I can do whatever I
want with it (rename, delete, etc.). However, if I move the file
(using Windows) from one folder on the share to a different folder on
the same share, all permissions disappear (i.e. no one has permission
to do anything until I ssh into the box and run a chmod).

I'm familiar with how ACLs work under GNU/Linux. I read the chapter on
OpenSolaris ACLs in the "Solaris ZFS Administration Guide", but it
merely enumerates all 99 possible options, rather than tell me what I
should have my ACLs set to.

As this is a home NAS, there is one user, and I'd like this user to
have permission to do anything on that particular share (there's an
autosnapshot process that prevents accidents). I'd also like these
permissions to extend to any created/moved/renamed files. Any
suggestions?

Jan


P.S. Additional (maybe useful?) information:

root at openindiana:~# zfs get aclinherit tankz2
NAME    PROPERTY    VALUE          SOURCE
tankz2  aclinherit  restricted     default
root at openindiana:~# /bin/ls -V /tankz2/scratch
total 11314255
drwx------+  2 oi       other          5 Jun  2 14:17 foto-dvdisaster
                user:oi:rwxpdDaARWcCos:-------:allow
       group:2147483648:rwxpdDaARWcCos:-------:allow
[...]


From sardonic.smiles at gmail.com  Sun Jun  3 22:32:10 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Sun, 3 Jun 2012 18:32:10 -0400
Subject: [OpenIndiana-discuss] problems with permissions on smb share
In-Reply-To: <CADCwuEY5YJ-eWW-vmn3SyEYYoCNCdJwawQ3zsb3rZzTURKDrhQ@mail.gmail.com>
References: <CADCwuEY5YJ-eWW-vmn3SyEYYoCNCdJwawQ3zsb3rZzTURKDrhQ@mail.gmail.com>
Message-ID: <CAPVmm=bLfW2hcp-i030oZ-e=VzBR3rTCzXNs8p-52RQJpKU6XA@mail.gmail.com>

What's the aclmode on the pool?

Zfs get aclmode tankz2
On Jun 3, 2012 6:21 PM, "Jan Owoc" <jsowoc at gmail.com> wrote:

> Hi,
>
> I've been using OpenIndiana151 for a home file server for several
> months now with good success, but am running into a curious problem.
> When I copy a file from Windows to the smb share, I can do whatever I
> want with it (rename, delete, etc.). However, if I move the file
> (using Windows) from one folder on the share to a different folder on
> the same share, all permissions disappear (i.e. no one has permission
> to do anything until I ssh into the box and run a chmod).
>
> I'm familiar with how ACLs work under GNU/Linux. I read the chapter on
> OpenSolaris ACLs in the "Solaris ZFS Administration Guide", but it
> merely enumerates all 99 possible options, rather than tell me what I
> should have my ACLs set to.
>
> As this is a home NAS, there is one user, and I'd like this user to
> have permission to do anything on that particular share (there's an
> autosnapshot process that prevents accidents). I'd also like these
> permissions to extend to any created/moved/renamed files. Any
> suggestions?
>
> Jan
>
>
> P.S. Additional (maybe useful?) information:
>
> root at openindiana:~# zfs get aclinherit tankz2
> NAME    PROPERTY    VALUE          SOURCE
> tankz2  aclinherit  restricted     default
> root at openindiana:~# /bin/ls -V /tankz2/scratch
> total 11314255
> drwx------+  2 oi       other          5 Jun  2 14:17 foto-dvdisaster
>                user:oi:rwxpdDaARWcCos:-------:allow
>       group:2147483648:rwxpdDaARWcCos:-------:allow
> [...]
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>

From jsowoc at gmail.com  Sun Jun  3 23:18:47 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Sun, 3 Jun 2012 17:18:47 -0600
Subject: [OpenIndiana-discuss] problems with permissions on smb share
In-Reply-To: <CAPVmm=bLfW2hcp-i030oZ-e=VzBR3rTCzXNs8p-52RQJpKU6XA@mail.gmail.com>
References: <CADCwuEY5YJ-eWW-vmn3SyEYYoCNCdJwawQ3zsb3rZzTURKDrhQ@mail.gmail.com>
	<CAPVmm=bLfW2hcp-i030oZ-e=VzBR3rTCzXNs8p-52RQJpKU6XA@mail.gmail.com>
Message-ID: <CADCwuEZL4T-E9CzuVC0tYM8K5iEX6yYPnQoq6fTPRYaSVH+M3w@mail.gmail.com>

On Sun, Jun 3, 2012 at 4:32 PM, Robbie Crash <sardonic.smiles at gmail.com> wrote:
> What's the aclmode on the pool?
>
> Zfs get aclmode tankz2

root at openindiana:~# zfs get aclmode tankz2 tankz2/scratch
NAME            PROPERTY  VALUE        SOURCE
tankz2          aclmode   discard      default
tankz2/scratch  aclmode   discard      default

"tankz2" is the name of the zpool (and the corresponding zfs). I have
several shares in this pool, one of which is "scratch". They all
exhibit this odd behaviour (copying is ok, moving resets permissions).

Jan


From sardonic.smiles at gmail.com  Mon Jun  4 05:06:35 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Mon, 4 Jun 2012 01:06:35 -0400
Subject: [OpenIndiana-discuss] problems with permissions on smb share
In-Reply-To: <CADCwuEZL4T-E9CzuVC0tYM8K5iEX6yYPnQoq6fTPRYaSVH+M3w@mail.gmail.com>
References: <CADCwuEY5YJ-eWW-vmn3SyEYYoCNCdJwawQ3zsb3rZzTURKDrhQ@mail.gmail.com>
	<CAPVmm=bLfW2hcp-i030oZ-e=VzBR3rTCzXNs8p-52RQJpKU6XA@mail.gmail.com>
	<CADCwuEZL4T-E9CzuVC0tYM8K5iEX6yYPnQoq6fTPRYaSVH+M3w@mail.gmail.com>
Message-ID: <CAPVmm=Y6wVu7DffjmFj+vAcMNEnfjCJ8HRfKb9vWe7a9uymadA@mail.gmail.com>

I see two problems,

The first is that you've got your ACL's set to not propagate to
files/directories:

This:
 user:oi:rwxpdDaARWcCos:-------:allow
Means that the owner has full access to that file, but not to child
directories, or to child files according to the ZFS ACL. In order to get
things to actually pass on to child objects, the directory needs to have
the f bit set for files, and the d bit set for directories:
$ /usr/bin/chmod -R A=owner@:full_set:fd:allow,<GROUP/EVERYONE>
/PATH/YOU/ARE/CHANGING

With the f and d set after the permissions you're granting, either with
full/read_set or with rwxpdDaARWcCos. Although, I don't get why cp is fine,
but mv breaks things. It /should/ be the other way around. mv should always
preserve permissions, where as cp should inherit. So I don't get that.

Second is that your ZFS ACLs are set to be discarded as per the ACLMode, so
you're just using the normal UNIX/POSIX ones. If you're going to use ZFS
ACLs, you need to have ACLmode set to passthrough.

/usr/gnu/ls and /usr/gnu/chmod both only work on the UNIX permissions, and
leave the ZFS ones untouched. If you set your ACLMode to passthrough,
that's supposed to link the ZFS ACL with whatever the UNIX ACL is set to.

How do the permissions show in Windows?

I had a lot of permissions problems with Windows shares initially, lots of
them because of things like this. Initially i disabled the ZFS ACLs, and
just used the normal ones, but that caused issues when setting/modifying
permissions from Windows. What I ended up doing was creating a new pool
from scratch, setting things up with passthrough and inherit turned on, and
then made sure to use /usr/bin/chmod to make any server-side permissions
changes. Since rebuilding, I haven't had any similar issues.


On Sun, Jun 3, 2012 at 7:18 PM, Jan Owoc <jsowoc at gmail.com> wrote:

> On Sun, Jun 3, 2012 at 4:32 PM, Robbie Crash <sardonic.smiles at gmail.com>
> wrote:
> > What's the aclmode on the pool?
> >
> > Zfs get aclmode tankz2
>
> root at openindiana:~# zfs get aclmode tankz2 tankz2/scratch
> NAME            PROPERTY  VALUE        SOURCE
> tankz2          aclmode   discard      default
> tankz2/scratch  aclmode   discard      default
>
> "tankz2" is the name of the zpool (and the corresponding zfs). I have
> several shares in this pool, one of which is "scratch". They all
> exhibit this odd behaviour (copying is ok, moving resets permissions).
>
> Jan
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
Seconds to the drop, but it seems like hours.

http://www.eff.org/
<http://www.eff.org/>http://creativecommons.org/

From dave.koelmeyer at davekoelmeyer.co.nz  Mon Jun  4 05:30:37 2012
From: dave.koelmeyer at davekoelmeyer.co.nz (Dave Koelmeyer)
Date: Mon, 04 Jun 2012 17:30:37 +1200
Subject: [OpenIndiana-discuss] installing oracle 11g
In-Reply-To: <4FBD62C3.1060900@oracle.com>
References: <CAOZy0ek4XK9ACnX5U8NnJVLzzOXBxBv5uKcf1HCuA0m4o1cfnw@mail.gmail.com>
	<E8480657D4AD4183A4715E1F74BEC634@ragnarok>
	<CAOZy0emwDpfSrxoHbmPAGpxp4wexVX86Cx6CmRs1FF2Gdyz=vg@mail.gmail.com>
	<4FBD62C3.1060900@oracle.com>
Message-ID: <4FCC47FD.50501@davekoelmeyer.co.nz>

On 05/24/12 10:20 AM, Alan Coopersmith wrote:
>
> The simplest workaround is to grant the Oracle user permission before you su to
> it:
> 	xhost +si:localuser:oracle
>

Hi Alan/all,

Out of interest, assuming I am granting a local user permission to use X 
in this manner, how do I make this persist across reboots?
The man page implies I create an X0.hosts file at /etc containing 
"+si:localuser:oracle", but this doesn't work. I probably haven't got 
the format right, but any pointers?

Thanks,

-- 
Dave Koelmeyer
http://www.davekoelmeyer.co.nz



From jimklimov at cos.ru  Mon Jun  4 10:13:11 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 04 Jun 2012 14:13:11 +0400
Subject: [OpenIndiana-discuss] installing oracle 11g
In-Reply-To: <4FCC47FD.50501@davekoelmeyer.co.nz>
References: <CAOZy0ek4XK9ACnX5U8NnJVLzzOXBxBv5uKcf1HCuA0m4o1cfnw@mail.gmail.com>
	<E8480657D4AD4183A4715E1F74BEC634@ragnarok>
	<CAOZy0emwDpfSrxoHbmPAGpxp4wexVX86Cx6CmRs1FF2Gdyz=vg@mail.gmail.com>
	<4FBD62C3.1060900@oracle.com> <4FCC47FD.50501@davekoelmeyer.co.nz>
Message-ID: <4FCC8A37.60904@cos.ru>

2012-06-04 9:30, Dave Koelmeyer wrote:
> On 05/24/12 10:20 AM, Alan Coopersmith wrote:
>>
>> The simplest workaround is to grant the Oracle user permission before
>> you su to
>> it:
>> xhost +si:localuser:oracle
>>
>
> Hi Alan/all,
>
> Out of interest, assuming I am granting a local user permission to use X
> in this manner, how do I make this persist across reboots?
> The man page implies I create an X0.hosts file at /etc containing
> "+si:localuser:oracle", but this doesn't work. I probably haven't got
> the format right, but any pointers?

I'd use the profile file for the X11 window manager your
interactive user uses (root or whoever). I don't use X11
interactively (on console) but rather as a TightVNC server -
there such settings can go into ~/.vnc/xstartup script.
Maybe this snippet would help your profile: it permits
the server's local zones and optionally some listed hosts
the right to access the GZ's VNC server for management
(i.e. installing the Oracle with its interactive wizard),
and this is a little breach because the VNC server is
fired up for such tasks and is normally disabled:

##########
# (C) 2008-2012 by Jim Klimov: allow local zones to this X11 server
# Permit the following hosts to use this VNC for display
XHOSTLIST="localhost `hostname`"

if [ -s "/etc/default/vncserver-xhosts" ]; then
     XHOSTLIST="$XHOSTLIST `cat /etc/default/vncserver-xhosts`"
fi

if [ -x "/usr/sbin/zoneadm" ]; then
     # This system contains some Solaris zones
     # We simply presume that zone names are known (resolvable)
     # as IP addresses via hosts file or DNS
     XHOSTLIST="$XHOSTLIST `/usr/sbin/zoneadm list -cp | grep -v global 
| while IFS=: read ZID ZNAME ZSTATE ZPATH; do /bin/echo \" $ZNAME\c\"; 
done`"
fi

echo "XHOSTLIST=$XHOSTLIST" >&2

if [ x"$XHOSTLIST" != x -a x"$XHOSTLIST" != "x " ]; then
     for XHOST in $XHOSTLIST; do
         echo "Adding XHost: $XHOST..." >&2
         xhost + "$XHOST"
     done
fi
##########

I guess it should be trivial to replace or expand this logic
with one needed for local users (i.e. as a list file in the
topmost clause).

HTH,
//Jim Klimov


From jimklimov at cos.ru  Mon Jun  4 10:20:46 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 04 Jun 2012 14:20:46 +0400
Subject: [OpenIndiana-discuss] ZFS restore from snapshot
In-Reply-To: <CAACKFonqSuPFpF9dWLJp_6Pd6ZRJTTXQ5vKMxbdc8Ezxs_CYpQ@mail.gmail.com>
References: <CAACKFonqSuPFpF9dWLJp_6Pd6ZRJTTXQ5vKMxbdc8Ezxs_CYpQ@mail.gmail.com>
Message-ID: <4FCC8BFE.8060201@cos.ru>

2012-06-03 8:14, Jay Heyl wrote:
> I have a file that shows as corrupted in the live file system and two
> snapshots. The file gives every indication of being valid in earlier
> snapshots. I've tried to restore it from the good snapshot but it doesn't
> seem to want to take. After several failed attempts to copy directly from
> the snapshot, I copied from the snapshot to my home directory. That copy
> appears to be good. (It's an image file and the image comes up fine.) I've
> deleted the file from the live directory and it seems to disappear. But
> every time I copy the file from my home directory into the target
> directory, the target directory copy appears corrupted.

Does your filesystem use dedup? If so, I discussed a bug
earlier this year, which would cause similar corruption.

If this is a likely cause, try to disable dedup, restore
(copy) the file, destroy the bad copy (if deduped - check
and fix all instances similarly) and scrub/clear the pool.
If you need the file(s) deduped, you can later enable dedup
and copy the file(s) over again - data would become deduped
upon write.

Anyhow, do the scrub as suggested - this might help (or
in case of the bug I dealt with - it could cause a kernel
panic when the zfs iteration hits the corrupt block and
tries to free it a few times too many; fix was in the
works). Some workarounds were possible for me at that
time with a manually recompiled kernel to allow leaking
the blocks so they don't bother the ZFS block tree as
invalid corruptions ;)

HTH,
//Jim Klimov


From jsowoc at gmail.com  Mon Jun  4 13:37:16 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Mon, 4 Jun 2012 07:37:16 -0600
Subject: [OpenIndiana-discuss] problems with permissions on smb share
In-Reply-To: <CAPVmm=Y6wVu7DffjmFj+vAcMNEnfjCJ8HRfKb9vWe7a9uymadA@mail.gmail.com>
References: <CADCwuEY5YJ-eWW-vmn3SyEYYoCNCdJwawQ3zsb3rZzTURKDrhQ@mail.gmail.com>
	<CAPVmm=bLfW2hcp-i030oZ-e=VzBR3rTCzXNs8p-52RQJpKU6XA@mail.gmail.com>
	<CADCwuEZL4T-E9CzuVC0tYM8K5iEX6yYPnQoq6fTPRYaSVH+M3w@mail.gmail.com>
	<CAPVmm=Y6wVu7DffjmFj+vAcMNEnfjCJ8HRfKb9vWe7a9uymadA@mail.gmail.com>
Message-ID: <CADCwuEbE3dg2TisvcSTsZC-n-JgPoUcBHBbojhGJZPpT23x++w@mail.gmail.com>

On Sun, Jun 3, 2012 at 11:06 PM, Robbie Crash <sardonic.smiles at gmail.com> wrote:
> I see two problems,
>
> The first is that you've got your ACL's set to not propagate to
> files/directories:
>
> This:
> ?user:oi:rwxpdDaARWcCos:-------:allow
> Means that the owner has full access to that file, but not to child
> directories, or to child files according to the ZFS ACL. In order to get
> things to actually pass on to child objects, the directory needs to have
> the f bit set for files, and the d bit set for directories:
> $ /usr/bin/chmod -R A=owner@:full_set:fd:allow,<GROUP/EVERYONE>
> /PATH/YOU/ARE/CHANGING
>
> With the f and d set after the permissions you're granting, either with
> full/read_set or with rwxpdDaARWcCos. Although, I don't get why cp is fine,
> but mv breaks things. It /should/ be the other way around. mv should always
> preserve permissions, where as cp should inherit. So I don't get that.

Yes, there was even additional oddity that I found after sending my
original mail, as Windows XP SP3 would discard the permissions, while
Windows 7 SP1 would properly propagate them.


> Second is that your ZFS ACLs are set to be discarded as per the ACLMode, so
> you're just using the normal UNIX/POSIX ones. If you're going to use ZFS
> ACLs, you need to have ACLmode set to passthrough.

As I have a few shares (each on its own fs), I could play around with
various combinations. It appears that there were two possible
solutions:

1) only changing the "owner@:fullset:fd:allow" permission (without
changing the zfs properties aclinherit or aclpassthrough) was enough
to fix the problem (or at least I can't reproduce this specific
problem when I do this). The trick was the "fd", which I'd missed.


> How do the permissions show in Windows?

2) simply turning off "Use simple file sharing (Recommended)", which I
needed to do to look at the permissions, fixed the problem. It appears
I don't even need the "fd" permissions set.


My problem is solved. Thank you!


> I had a lot of permissions problems with Windows shares initially, lots of
> them because of things like this. Initially i disabled the ZFS ACLs, and
> just used the normal ones, but that caused issues when setting/modifying
> permissions from Windows. What I ended up doing was creating a new pool
> from scratch, setting things up with passthrough and inherit turned on, and
> then made sure to use /usr/bin/chmod to make any server-side permissions
> changes. Since rebuilding, I haven't had any similar issues.

What is the benefit of setting up a new pool if you can do a "chmod
-R"? Or did you have specific needs that could only be addressed this
way?


Jan


From sardonic.smiles at gmail.com  Mon Jun  4 13:44:19 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Mon, 4 Jun 2012 09:44:19 -0400
Subject: [OpenIndiana-discuss] problems with permissions on smb share
In-Reply-To: <CADCwuEbE3dg2TisvcSTsZC-n-JgPoUcBHBbojhGJZPpT23x++w@mail.gmail.com>
References: <CADCwuEY5YJ-eWW-vmn3SyEYYoCNCdJwawQ3zsb3rZzTURKDrhQ@mail.gmail.com>
	<CAPVmm=bLfW2hcp-i030oZ-e=VzBR3rTCzXNs8p-52RQJpKU6XA@mail.gmail.com>
	<CADCwuEZL4T-E9CzuVC0tYM8K5iEX6yYPnQoq6fTPRYaSVH+M3w@mail.gmail.com>
	<CAPVmm=Y6wVu7DffjmFj+vAcMNEnfjCJ8HRfKb9vWe7a9uymadA@mail.gmail.com>
	<CADCwuEbE3dg2TisvcSTsZC-n-JgPoUcBHBbojhGJZPpT23x++w@mail.gmail.com>
Message-ID: <CAPVmm=Zp-Sdc5f7gAZrJgfVUvvJSUZ=+sOBFX+-YoFXRM0JtzA@mail.gmail.com>

I had to set up the new pool, probably solely due to my own inexperience.
After mucking about in the permissions so much while trying to figure
things out, I'm sure I broke things and left them so inconsistent that it
became a constant battle to get things working properly without constantly
fixing permissions.

Glad to hear you got everything working without issues.

Sended from my Android.
On Jun 4, 2012 9:38 AM, "Jan Owoc" <jsowoc at gmail.com> wrote:

> On Sun, Jun 3, 2012 at 11:06 PM, Robbie Crash <sardonic.smiles at gmail.com>
> wrote:
> > I see two problems,
> >
> > The first is that you've got your ACL's set to not propagate to
> > files/directories:
> >
> > This:
> >  user:oi:rwxpdDaARWcCos:-------:allow
> > Means that the owner has full access to that file, but not to child
> > directories, or to child files according to the ZFS ACL. In order to get
> > things to actually pass on to child objects, the directory needs to have
> > the f bit set for files, and the d bit set for directories:
> > $ /usr/bin/chmod -R A=owner@:full_set:fd:allow,<GROUP/EVERYONE>
> > /PATH/YOU/ARE/CHANGING
> >
> > With the f and d set after the permissions you're granting, either with
> > full/read_set or with rwxpdDaARWcCos. Although, I don't get why cp is
> fine,
> > but mv breaks things. It /should/ be the other way around. mv should
> always
> > preserve permissions, where as cp should inherit. So I don't get that.
>
> Yes, there was even additional oddity that I found after sending my
> original mail, as Windows XP SP3 would discard the permissions, while
> Windows 7 SP1 would properly propagate them.
>
>
> > Second is that your ZFS ACLs are set to be discarded as per the ACLMode,
> so
> > you're just using the normal UNIX/POSIX ones. If you're going to use ZFS
> > ACLs, you need to have ACLmode set to passthrough.
>
> As I have a few shares (each on its own fs), I could play around with
> various combinations. It appears that there were two possible
> solutions:
>
> 1) only changing the "owner@:fullset:fd:allow" permission (without
> changing the zfs properties aclinherit or aclpassthrough) was enough
> to fix the problem (or at least I can't reproduce this specific
> problem when I do this). The trick was the "fd", which I'd missed.
>
>
> > How do the permissions show in Windows?
>
> 2) simply turning off "Use simple file sharing (Recommended)", which I
> needed to do to look at the permissions, fixed the problem. It appears
> I don't even need the "fd" permissions set.
>
>
> My problem is solved. Thank you!
>
>
> > I had a lot of permissions problems with Windows shares initially, lots
> of
> > them because of things like this. Initially i disabled the ZFS ACLs, and
> > just used the normal ones, but that caused issues when setting/modifying
> > permissions from Windows. What I ended up doing was creating a new pool
> > from scratch, setting things up with passthrough and inherit turned on,
> and
> > then made sure to use /usr/bin/chmod to make any server-side permissions
> > changes. Since rebuilding, I haven't had any similar issues.
>
> What is the benefit of setting up a new pool if you can do a "chmod
> -R"? Or did you have specific needs that could only be addressed this
> way?
>
>
> Jan
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>

From darknovanick at gmail.com  Mon Jun  4 15:24:41 2012
From: darknovanick at gmail.com (Nick Hall)
Date: Mon, 4 Jun 2012 10:24:41 -0500
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
Message-ID: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>

I'm considering buying a separate SSD drive for my ZIL as I do quite a bit
over NFS and would like the latency to improve. But first I'm trying to
understand exactly how the ZIL works and what happens in case of a problem.
I'll list my understanding here, and I'm hoping someone can correct me if
I'm understanding this incorrectly:

- In normal operation, the ZIL drive would just be written to but never
read from.

- In the case of a power failure, the ZIL will probably contain 5-10
seconds (maybe up to 30 seconds) worth of writes that didn't make it onto
the main hard drives. The next time the system boots, ZFS will use what's
in the ZIL to bring the main hard drives up to date.

- I'm running ZFS version 28 -- in this version, if the ZIL drive were to
die while the system were running, the system would switch back to using
the main pool hard drives to store the ZIL, just as it currently does since
I have no separate ZIL drive right now.


So, now I have a couple of questions:

- If the ZIL drive were to die while the system were running, I'm assuming
no data would be lost? In order for this to work, the system would need to
cache everything in the ZIL in RAM, so if the ZIL were to die, it would
write the transactions that were on the ZIL from RAM to the main pool
drives. Applications would not notice anything from their perspective. Is
this what happens?

- So far, assuming I'm understanding this correctly, none of the above
scenarios involve any data loss. The scenario I can think of that would
involve data loss is if there's a power failure and the ZIL drive at the
same time. It seems likely that this scenario would be caused by
a catastrophic hardware failure, and the main system drives would also die,
but let's pretend that only the ZIL drive is affected. So any transactions
stored in the ZIL are lost. I'm thinking that the system would boot up,
note that the ZIL drive is dead and switch the ZIL back to the main pool
drives, and the last 5-30 seconds or writes would be lost forever. But
would the system be in a consistent state, that is, things would be the
same as if you went back in time 30 seconds before the system died and just
pulled the plug? So there's no corruption, just the loss of those seconds
of data?

- Are there any other scenarios I'm not thinking, specifically any other
scenarios that would cause corruption or loss of data? My use is for a home
server -- I would like higher NFS write performance, but not by making it
more likely I have corrupted or majorly lost data, but for my use, if I
only lost the last few seconds or writes and things were in a consistent
state, it would be of little consequence. I understand that for a
commercial server that would be huge issue, though, as banking transactions
lost or something would be a major problem. Thanks.

From jsowoc at gmail.com  Mon Jun  4 15:48:39 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Mon, 4 Jun 2012 09:48:39 -0600
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
Message-ID: <CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>

On Mon, Jun 4, 2012 at 9:24 AM, Nick Hall <darknovanick at gmail.com> wrote:
> I'm considering buying a separate SSD drive for my ZIL as I do quite a bit
> over NFS and would like the latency to improve. But first I'm trying to
> understand exactly how the ZIL works and what happens in case of a problem.
> I'll list my understanding here, and I'm hoping someone can correct me if
> I'm understanding this incorrectly:

The ZIL fixes latency with synchronous writes. Do you have a workload
that you can benchmark with the ZIL disabled to determine if it's
indeed the ZIL that's slowing you down?
http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disabling_the_ZIL_.28Don.27t.29

(just remember to re-enable the ZIL after you are done benchmarking,
if you care about data integrity)


> - If the ZIL drive were to die while the system were running, I'm assuming
> no data would be lost? In order for this to work, the system would need to
> cache everything in the ZIL in RAM, so if the ZIL were to die, it would
> write the transactions that were on the ZIL from RAM to the main pool
> drives. Applications would not notice anything from their perspective. Is
> this what happens?

The ZIL is sort of like a journal. Your application issues a "sync"
and ZFS isn't supposed to return from the sync until the data actually
makes it onto disk. With platters rotating etc., this can take tens of
miliseconds. A ZIL on NVRAM (or an SSD) would allow this sync'ed data
to hit the fast-write device, and the system call to return
immediately. The data will also, as you'd read, make it to the disk in
5-30 seconds. Yes, a copy stays in the RAM, and it's this copy that is
normally written (and not a copy re-read from the ZIL).



> - So far, assuming I'm understanding this correctly, none of the above
> scenarios involve any data loss. The scenario I can think of that would
> involve data loss is if there's a power failure and the ZIL drive at the
> same time. It seems likely that this scenario would be caused by
> a catastrophic hardware failure, and the main system drives would also die,
> but let's pretend that only the ZIL drive is affected. So any transactions
> stored in the ZIL are lost. I'm thinking that the system would boot up,
> note that the ZIL drive is dead and switch the ZIL back to the main pool
> drives, and the last 5-30 seconds or writes would be lost forever. But
> would the system be in a consistent state, that is, things would be the
> same as if you went back in time 30 seconds before the system died and just
> pulled the plug? So there's no corruption, just the loss of those seconds
> of data?

I don't have first-hand experience with this case, so maybe someone
can correct me if I'm wrong.

The data on the main pool is always consistent in that a certain
operation either made it to the disk or it didn't. However, if your
application depends on the fact that writes make it out to disk in a
specific order (that's why it's sync'ing, right?), then it's the ZIL
that would contain a log/journal of what should have been written to
the disk and in what order. If you lose this, your file system remains
consistent, but some writes may have made it out to the disk before
others.


> My use is for a home
> server -- I would like higher NFS write performance, but not by making it
> more likely I have corrupted or majorly lost data, but for my use, if I
> only lost the last few seconds or writes and things were in a consistent
> state, it would be of little consequence.

You need to first find out if your writes are synchronous or not,
otherwise you are wasting your time (and money) getting a separate log
device. It's mostly databases that require that file operations happen
in a specific order - for a home file server, you might not see any
benefit to a separate log device. Next, make sure you get an SSD with
fast sequential writes - many SSDs focus on random read speed (that's
what a desktop user wants to see).


Jan


From richard.elling at richardelling.com  Mon Jun  4 15:56:55 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Mon, 4 Jun 2012 08:56:55 -0700
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
Message-ID: <0DA8D232-9383-4E53-93F0-A50A42DD9B49@RichardElling.com>

On Jun 4, 2012, at 8:24 AM, Nick Hall wrote:

> I'm considering buying a separate SSD drive for my ZIL as I do quite a bit
> over NFS and would like the latency to improve. But first I'm trying to
> understand exactly how the ZIL works and what happens in case of a problem.
> I'll list my understanding here, and I'm hoping someone can correct me if
> I'm understanding this incorrectly:
> 
> - In normal operation, the ZIL drive would just be written to but never
> read from.
> 
> - In the case of a power failure, the ZIL will probably contain 5-10
> seconds (maybe up to 30 seconds) worth of writes that didn't make it onto
> the main hard drives. The next time the system boots, ZFS will use what's
> in the ZIL to bring the main hard drives up to date.
> 
> - I'm running ZFS version 28 -- in this version, if the ZIL drive were to
> die while the system were running, the system would switch back to using
> the main pool hard drives to store the ZIL, just as it currently does since
> I have no separate ZIL drive right now.

The above is conceptually correct. For the systems running zpool version 28, it
is also likely the default txg commit interval is 5 seconds.

> So, now I have a couple of questions:
> 
> - If the ZIL drive were to die while the system were running, I'm assuming
> no data would be lost? In order for this to work, the system would need to
> cache everything in the ZIL in RAM, so if the ZIL were to die, it would
> write the transactions that were on the ZIL from RAM to the main pool
> drives. Applications would not notice anything from their perspective. Is
> this what happens?

For data, there is nothing in the ZIL that is not also in the ARC.

> - So far, assuming I'm understanding this correctly, none of the above
> scenarios involve any data loss. The scenario I can think of that would
> involve data loss is if there's a power failure and the ZIL drive at the
> same time. It seems likely that this scenario would be caused by
> a catastrophic hardware failure, and the main system drives would also die,
> but let's pretend that only the ZIL drive is affected. So any transactions
> stored in the ZIL are lost. I'm thinking that the system would boot up,
> note that the ZIL drive is dead and switch the ZIL back to the main pool
> drives, and the last 5-30 seconds or writes would be lost forever. But
> would the system be in a consistent state, that is, things would be the
> same as if you went back in time 30 seconds before the system died and just
> pulled the plug? So there's no corruption, just the loss of those seconds
> of data?

In general, it takes a double failure: the slog device and something else.

> - Are there any other scenarios I'm not thinking, specifically any other
> scenarios that would cause corruption or loss of data? My use is for a home
> server -- I would like higher NFS write performance, but not by making it
> more likely I have corrupted or majorly lost data, but for my use, if I
> only lost the last few seconds or writes and things were in a consistent
> state, it would be of little consequence. I understand that for a
> commercial server that would be huge issue, though, as banking transactions
> lost or something would be a major problem. Thanks.

For NFS workloads, the ZIL implements the synchronous semantics between
the NFS server and client. The best way to get better performance is to have the
client run in async mode when possible (Solaris clients do this automatically, and 
have for a very long time, Linux... not so much).

The risk is that the server unexpectedly reboots and the synchronous writes from
the client are lost. In that case, the client thinks data is written, but it is not. The 
server is happy either way... it is the client that is sad.

There are some failure modes that can impact these systems that might not be
expected. For example, if the slog device responds very slowly to the write, then
the ripple effect impacts the performance as perceived by the client. For consumer-
grade flash SSDs, this can occur more often than for enterprise-grade flash SSDs.
 -- richard

--
ZFS Performance and Training
Richard.Elling at RichardElling.com
+1-760-896-4422




From whitetr6 at gmail.com  Mon Jun  4 15:57:12 2012
From: whitetr6 at gmail.com (Mark Creamer)
Date: Mon, 4 Jun 2012 11:57:12 -0400
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
Message-ID: <CA+EEQsqoN7KhzdM9pRo-p1TgrTbEmNvw6QKe5bk3CHEw=Lc69w@mail.gmail.com>

You might supplement the advice you get here with this post from
Constantin Gonzales on his blog. I found it very helpful when I was
setting up my Solaris storage server.
http://constantin.glez.de/blog/2010/07/solaris-zfs-synchronous-writes-and-zil-explained

-Mark

On Mon, Jun 4, 2012 at 11:24 AM, Nick Hall <darknovanick at gmail.com> wrote:
> I'm considering buying a separate SSD drive for my ZIL as I do quite a bit
> over NFS and would like the latency to improve. But first I'm trying to
> understand exactly how the ZIL works and what happens in case of a problem.
> I'll list my understanding here, and I'm hoping someone can correct me if
> I'm understanding this incorrectly:
>
> - In normal operation, the ZIL drive would just be written to but never
> read from.
>
> - In the case of a power failure, the ZIL will probably contain 5-10
> seconds (maybe up to 30 seconds) worth of writes that didn't make it onto
> the main hard drives. The next time the system boots, ZFS will use what's
> in the ZIL to bring the main hard drives up to date.
>
> - I'm running ZFS version 28 -- in this version, if the ZIL drive were to
> die while the system were running, the system would switch back to using
> the main pool hard drives to store the ZIL, just as it currently does since
> I have no separate ZIL drive right now.
>
>
> So, now I have a couple of questions:
>
> - If the ZIL drive were to die while the system were running, I'm assuming
> no data would be lost? In order for this to work, the system would need to
> cache everything in the ZIL in RAM, so if the ZIL were to die, it would
> write the transactions that were on the ZIL from RAM to the main pool
> drives. Applications would not notice anything from their perspective. Is
> this what happens?
>
> - So far, assuming I'm understanding this correctly, none of the above
> scenarios involve any data loss. The scenario I can think of that would
> involve data loss is if there's a power failure and the ZIL drive at the
> same time. It seems likely that this scenario would be caused by
> a catastrophic hardware failure, and the main system drives would also die,
> but let's pretend that only the ZIL drive is affected. So any transactions
> stored in the ZIL are lost. I'm thinking that the system would boot up,
> note that the ZIL drive is dead and switch the ZIL back to the main pool
> drives, and the last 5-30 seconds or writes would be lost forever. But
> would the system be in a consistent state, that is, things would be the
> same as if you went back in time 30 seconds before the system died and just
> pulled the plug? So there's no corruption, just the loss of those seconds
> of data?
>
> - Are there any other scenarios I'm not thinking, specifically any other
> scenarios that would cause corruption or loss of data? My use is for a home
> server -- I would like higher NFS write performance, but not by making it
> more likely I have corrupted or majorly lost data, but for my use, if I
> only lost the last few seconds or writes and things were in a consistent
> state, it would be of little consequence. I understand that for a
> commercial server that would be huge issue, though, as banking transactions
> lost or something would be a major problem. Thanks.
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



-- 
Mark


From richard.elling at richardelling.com  Mon Jun  4 16:03:46 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Mon, 4 Jun 2012 09:03:46 -0700
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
Message-ID: <FF7FD9C2-0164-47C7-A875-B53C8390D3BF@RichardElling.com>

On Jun 4, 2012, at 8:48 AM, Jan Owoc wrote:
> On Mon, Jun 4, 2012 at 9:24 AM, Nick Hall <darknovanick at gmail.com> wrote:
>> I'm considering buying a separate SSD drive for my ZIL as I do quite a bit
>> over NFS and would like the latency to improve. But first I'm trying to
>> understand exactly how the ZIL works and what happens in case of a problem.
>> I'll list my understanding here, and I'm hoping someone can correct me if
>> I'm understanding this incorrectly:
> 
> The ZIL fixes latency with synchronous writes.

I believe you mean, "the slog can improve latency for synchronous writes."

> Do you have a workload
> that you can benchmark with the ZIL disabled to determine if it's
> indeed the ZIL that's slowing you down?
> http://www.solarisinternals.com/wiki/index.php/ZFS_Evil_Tuning_Guide#Disabling_the_ZIL_.28Don.27t.29
> 
> (just remember to re-enable the ZIL after you are done benchmarking,
> if you care about data integrity)
> 
> 
>> - If the ZIL drive were to die while the system were running, I'm assuming
>> no data would be lost? In order for this to work, the system would need to
>> cache everything in the ZIL in RAM, so if the ZIL were to die, it would
>> write the transactions that were on the ZIL from RAM to the main pool
>> drives. Applications would not notice anything from their perspective. Is
>> this what happens?
> 
> The ZIL is sort of like a journal. Your application issues a "sync"
> and ZFS isn't supposed to return from the sync until the data actually
> makes it onto disk. With platters rotating etc., this can take tens of
> miliseconds. A ZIL on NVRAM (or an SSD) would allow this sync'ed data
> to hit the fast-write device, and the system call to return
> immediately. The data will also, as you'd read, make it to the disk in
> 5-30 seconds. Yes, a copy stays in the RAM, and it's this copy that is
> normally written (and not a copy re-read from the ZIL).

It is more appropriate to say the ZIL is like a database redo log. The term
"journal" is overloaded wrt file systems and can be confusing. Since the
core of ZFS is a transactional object store, the redo log notion fits better.

>> - So far, assuming I'm understanding this correctly, none of the above
>> scenarios involve any data loss. The scenario I can think of that would
>> involve data loss is if there's a power failure and the ZIL drive at the
>> same time. It seems likely that this scenario would be caused by
>> a catastrophic hardware failure, and the main system drives would also die,
>> but let's pretend that only the ZIL drive is affected. So any transactions
>> stored in the ZIL are lost. I'm thinking that the system would boot up,
>> note that the ZIL drive is dead and switch the ZIL back to the main pool
>> drives, and the last 5-30 seconds or writes would be lost forever. But
>> would the system be in a consistent state, that is, things would be the
>> same as if you went back in time 30 seconds before the system died and just
>> pulled the plug? So there's no corruption, just the loss of those seconds
>> of data?
> 
> I don't have first-hand experience with this case, so maybe someone
> can correct me if I'm wrong.
> 
> The data on the main pool is always consistent in that a certain
> operation either made it to the disk or it didn't. However, if your
> application depends on the fact that writes make it out to disk in a
> specific order (that's why it's sync'ing, right?), then it's the ZIL
> that would contain a log/journal of what should have been written to
> the disk and in what order. If you lose this, your file system remains
> consistent, but some writes may have made it out to the disk before
> others.

Correct.

>> My use is for a home
>> server -- I would like higher NFS write performance, but not by making it
>> more likely I have corrupted or majorly lost data, but for my use, if I
>> only lost the last few seconds or writes and things were in a consistent
>> state, it would be of little consequence.
> 
> You need to first find out if your writes are synchronous or not,
> otherwise you are wasting your time (and money) getting a separate log
> device. It's mostly databases that require that file operations happen
> in a specific order - for a home file server, you might not see any
> benefit to a separate log device. Next, make sure you get an SSD with
> fast sequential writes - many SSDs focus on random read speed (that's
> what a desktop user wants to see).

Two tools to help with understanding your client's workload: nfssvrtop and zilstat.
nfssvrtop is probably the first to use in this case. Both are now on my github repo :-)
	https://github.com/richardelling/tools

NB, ZIL is always present, a separate log device (slog) is often inappropriately
called a ZIL.

 -- richard

--
ZFS Performance and Training
Richard.Elling at RichardElling.com
+1-760-896-4422




From realrichardsharpe at gmail.com  Mon Jun  4 16:03:56 2012
From: realrichardsharpe at gmail.com (Richard Sharpe)
Date: Mon, 4 Jun 2012 09:03:56 -0700
Subject: [OpenIndiana-discuss] How do I get OpenIndana's make (not
 gmake) to accept the following
In-Reply-To: <CACyXjPwDhRDwBzh363A5nQhgt6dfgCncAFPVW2va5rX6P1MNvQ@mail.gmail.com>
References: <CACyXjPwEBPaCYFq6R714ye=J40gDOA020JBy-q=ehkPq2M2zYQ@mail.gmail.com>
	<1338750192.1300.7.camel@xylabone>
	<CACyXjPwDhRDwBzh363A5nQhgt6dfgCncAFPVW2va5rX6P1MNvQ@mail.gmail.com>
Message-ID: <CACyXjPzXA9sh9vRBaKxJQKitjsREDdypfuVedR+nV3jKsPfX_A@mail.gmail.com>

On Sun, Jun 3, 2012 at 12:08 PM, Richard Sharpe
<realrichardsharpe at gmail.com> wrote:
> On Sun, Jun 3, 2012 at 12:03 PM, Milan Jurik <milan.jurik at xylab.cz> wrote:
>> Hi Richard,
>>
>> Richard Sharpe p??e v ne 03. 06. 2012 v 06:55 -0700:
>>> Hi folks,
>>>
>>> I have figured out part of my problem with the OpenIndiana machine on
>>> the Samba build farm.
>>>
>>> It seems that the system goes not have GNU make installed or the
>>> OpenIndiana version of make is first on the path.
>>>
>>
>> is gmake not installed? GNU make package with gmake 3.81 is
>> developer/build/gnu-make
>
> I don't know at this stage. I have to wait for the owner of the system
> to respond to me.
>
> However, I would like to find a solution that produces few surprises
> for people :-)
>
> So, if they do not have GNU make installed it should still work. I do,
> however, need to improve the comments in the existing Makefile.in so
> that people have an idea of what to do when things do not work ...

After talking to Gordon Ross about it, it seems that the Solaris make
command does not do transitive evaluation of pattern rules.

The solution is to move to a single .c.so pattern rule rather than
splitting it into two.

Also, more comments in the Makefile will help people who run into
problems building a Samba VFS module for their special case.

-- 
Regards,
Richard Sharpe
(??????????--??)


From dswartz at druber.com  Mon Jun  4 17:06:28 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 04 Jun 2012 13:06:28 -0400
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <0DA8D232-9383-4E53-93F0-A50A42DD9B49@RichardElling.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<0DA8D232-9383-4E53-93F0-A50A42DD9B49@RichardElling.com>
Message-ID: <4FCCEB14.6040208@druber.com>

On 6/4/2012 11:56 AM, Richard Elling wrote:
> On Jun 4, 2012, at 8:24 AM, Nick Hall wrote:
> For NFS workloads, the ZIL implements the synchronous semantics between
> the NFS server and client. The best way to get better performance is to have the
> client run in async mode when possible (Solaris clients do this automatically, and
> have for a very long time, Linux... not so much).
>
> The risk is that the server unexpectedly reboots and the synchronous writes from
> the client are lost. In that case, the client thinks data is written, but it is not. The
> server is happy either way... it is the client that is sad.
>    
The most annoying client in this respect is ESXi, which insists on doing 
sync operations.  I understand the logic there - unlike, say, an 
application which can decide to do async operations, ESXi is using NFS 
as the backing store for virtual disks, so when a client (windows, 
linux, whatever) does disk writes to virtualized SCSI controller (frex), 
the guest may be doing writes on behalf of a journalized filesystem 
which is doing writes in a specific order, possibly even with write 
barriers.  In that case, cheating and forcing the writes to be 
asynchronous (say by 'sync=disabled') can in fact cause guest filesystem 
corruption.  I can't afford a high quality SSD to reduce latency, so I 
made an informed decision to disable sync mode.  The mitigation for me 
is that I do zfs snapshots every night of the ESXi datastore,  so the 
worst case is losing a day's work.  Given this is for a home/soho setup, 
and given that the openindiana SAN is on a hefty UPS, I'm willing to 
take the chance.


From richard.elling at richardelling.com  Mon Jun  4 17:15:27 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Mon, 4 Jun 2012 10:15:27 -0700
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <4FCCEB14.6040208@druber.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<0DA8D232-9383-4E53-93F0-A50A42DD9B49@RichardElling.com>
	<4FCCEB14.6040208@druber.com>
Message-ID: <6C215CED-D547-48B9-8949-8C23DB85E496@richardelling.com>

On Jun 4, 2012, at 10:06 AM, Dan Swartzendruber wrote:

> On 6/4/2012 11:56 AM, Richard Elling wrote:
>> On Jun 4, 2012, at 8:24 AM, Nick Hall wrote:
>> For NFS workloads, the ZIL implements the synchronous semantics between
>> the NFS server and client. The best way to get better performance is to have the
>> client run in async mode when possible (Solaris clients do this automatically, and
>> have for a very long time, Linux... not so much).
>> 
>> The risk is that the server unexpectedly reboots and the synchronous writes from
>> the client are lost. In that case, the client thinks data is written, but it is not. The
>> server is happy either way... it is the client that is sad.
>>   
> The most annoying client in this respect is ESXi, which insists on doing sync operations.  I understand the logic there - unlike, say, an application which can decide to do async operations, ESXi is using NFS as the backing store for virtual disks, so when a client (windows, linux, whatever) does disk writes to virtualized SCSI controller (frex), the guest may be doing writes on behalf of a journalized filesystem which is doing writes in a specific order, possibly even with write barriers.  In that case, cheating and forcing the writes to be asynchronous (say by 'sync=disabled') can in fact cause guest filesystem corruption.

AIUI, ESXi has its own, native NFS implementation and I've never seen it do async writes.
XenServer can do async writes, but it is not likely to be seen with OOB Solaris distros (!)
 -- richard

>  I can't afford a high quality SSD to reduce latency, so I made an informed decision to disable sync mode.  The mitigation for me is that I do zfs snapshots every night of the ESXi datastore,  so the worst case is losing a day's work.  Given this is for a home/soho setup, and given that the openindiana SAN is on a hefty UPS, I'm willing to take the chance.


--
ZFS Performance and Training
Richard.Elling at RichardElling.com
+1-760-896-4422




From dswartz at druber.com  Mon Jun  4 17:47:17 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 04 Jun 2012 13:47:17 -0400
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <6C215CED-D547-48B9-8949-8C23DB85E496@richardelling.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<0DA8D232-9383-4E53-93F0-A50A42DD9B49@RichardElling.com>
	<4FCCEB14.6040208@druber.com>
	<6C215CED-D547-48B9-8949-8C23DB85E496@richardelling.com>
Message-ID: <4FCCF4A5.7070801@druber.com>

On 6/4/2012 1:15 PM, Richard Elling wrote:
> On Jun 4, 2012, at 10:06 AM, Dan Swartzendruber wrote:
>
>> On 6/4/2012 11:56 AM, Richard Elling wrote:
>>> On Jun 4, 2012, at 8:24 AM, Nick Hall wrote:
>>> For NFS workloads, the ZIL implements the synchronous semantics between
>>> the NFS server and client. The best way to get better performance is 
>>> to have the
>>> client run in async mode when possible (Solaris clients do this 
>>> automatically, and
>>> have for a very long time, Linux... not so much).
>>>
>>> The risk is that the server unexpectedly reboots and the synchronous 
>>> writes from
>>> the client are lost. In that case, the client thinks data is 
>>> written, but it is not. The
>>> server is happy either way... it is the client that is sad.
>>>
>> The most annoying client in this respect is ESXi, which insists on 
>> doing sync operations.  I understand the logic there - unlike, say, 
>> an application which can decide to do async operations, ESXi is using 
>> NFS as the backing store for virtual disks, so when a client 
>> (windows, linux, whatever) does disk writes to virtualized SCSI 
>> controller (frex), the guest may be doing writes on behalf of a 
>> journalized filesystem which is doing writes in a specific order, 
>> possibly even with write barriers.  In that case, cheating and 
>> forcing the writes to be asynchronous (say by 'sync=disabled') can in 
>> fact cause guest filesystem corruption.
>
> AIUI, ESXi has its own, native NFS implementation and I've never seen 
> it do async writes.
>  -- richard

Right, for the reasons just explained.




From superscapesysman at hotmail.com  Mon Jun  4 17:57:21 2012
From: superscapesysman at hotmail.com (Dave Monk)
Date: Mon, 4 Jun 2012 17:57:21 +0000
Subject: [OpenIndiana-discuss] Best place for support on initial install of
	OI?
Message-ID: <DUB106-W2373CA02210CD59296EB23D10F0@phx.gbl>


I"m looking for some basic support on the initial install of OI and wondered if someone could point me to the best place?  Wasn't sure if this was, or perhaps the IRC channel #openindiana but I'd like to ask a simple question regarding the initial install (have tried both DVD and USB install and the install appears to run, then just halts asking for a username for system maintenance)... 		 	   		  

From mike.laspina at laspina.ca  Mon Jun  4 18:23:11 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Mon, 4 Jun 2012 13:23:11 -0500
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>

Everything you asked seems to be fully covered by our community.

Just wanted to add the following;

Not all SSDs are made for slog usage. Be aware that low end (and even
some high endones) SSDs may not successfully commit a write operation to
the flash write cell address boundary due to a power loss event. At a
minimum the use of a UPS is advisable or SSDs that guaranty complete
write operations in the event of a power loss.  

-----Original Message-----
From: Nick Hall [mailto:darknovanick at gmail.com] 
Sent: Monday, June 04, 2012 10:25 AM
To: OpenIndiana-discuss at openindiana.org
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?

I'm considering buying a separate SSD drive for my ZIL as I do quite a
bit over NFS and would like the latency to improve. But first I'm trying
to understand exactly how the ZIL works and what happens in case of a
problem.
I'll list my understanding here, and I'm hoping someone can correct me
if I'm understanding this incorrectly:

- In normal operation, the ZIL drive would just be written to but never
read from.

- In the case of a power failure, the ZIL will probably contain 5-10
seconds (maybe up to 30 seconds) worth of writes that didn't make it
onto the main hard drives. The next time the system boots, ZFS will use
what's in the ZIL to bring the main hard drives up to date.

- I'm running ZFS version 28 -- in this version, if the ZIL drive were
to die while the system were running, the system would switch back to
using the main pool hard drives to store the ZIL, just as it currently
does since I have no separate ZIL drive right now.


So, now I have a couple of questions:

- If the ZIL drive were to die while the system were running, I'm
assuming no data would be lost? In order for this to work, the system
would need to cache everything in the ZIL in RAM, so if the ZIL were to
die, it would write the transactions that were on the ZIL from RAM to
the main pool drives. Applications would not notice anything from their
perspective. Is this what happens?

- So far, assuming I'm understanding this correctly, none of the above
scenarios involve any data loss. The scenario I can think of that would
involve data loss is if there's a power failure and the ZIL drive at the
same time. It seems likely that this scenario would be caused by a
catastrophic hardware failure, and the main system drives would also
die, but let's pretend that only the ZIL drive is affected. So any
transactions stored in the ZIL are lost. I'm thinking that the system
would boot up, note that the ZIL drive is dead and switch the ZIL back
to the main pool drives, and the last 5-30 seconds or writes would be
lost forever. But would the system be in a consistent state, that is,
things would be the same as if you went back in time 30 seconds before
the system died and just pulled the plug? So there's no corruption, just
the loss of those seconds of data?

- Are there any other scenarios I'm not thinking, specifically any other
scenarios that would cause corruption or loss of data? My use is for a
home server -- I would like higher NFS write performance, but not by
making it more likely I have corrupted or majorly lost data, but for my
use, if I only lost the last few seconds or writes and things were in a
consistent state, it would be of little consequence. I understand that
for a commercial server that would be huge issue, though, as banking
transactions lost or something would be a major problem. Thanks.
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From sardonic.smiles at gmail.com  Mon Jun  4 18:42:02 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Mon, 4 Jun 2012 14:42:02 -0400
Subject: [OpenIndiana-discuss] Best place for support on initial install
 of OI?
In-Reply-To: <DUB106-W2373CA02210CD59296EB23D10F0@phx.gbl>
References: <DUB106-W2373CA02210CD59296EB23D10F0@phx.gbl>
Message-ID: <CAPVmm=ZHxac6WTFJ8pVURm73225Yjy_NVNpP77P6icJiDELwMw@mail.gmail.com>

As a general rule, it seems like this is the place for long-term questions
that need to be worked out, and the IRC channel on Freenode is where people
go to ask questions with immediate need.

As for your problem, I don't know enough to help out. I'd venture into IRC
for that.

On Mon, Jun 4, 2012 at 1:57 PM, Dave Monk <superscapesysman at hotmail.com>wrote:

>
> I"m looking for some basic support on the initial install of OI and
> wondered if someone could point me to the best place?  Wasn't sure if this
> was, or perhaps the IRC channel #openindiana but I'd like to ask a simple
> question regarding the initial install (have tried both DVD and USB install
> and the install appears to run, then just halts asking for a username for
> system maintenance)...
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
Seconds to the drop, but it seems like hours.

http://www.eff.org/
<http://www.eff.org/>http://creativecommons.org/

From ko at research.att.com  Mon Jun  4 19:10:04 2012
From: ko at research.att.com (Kostas Oikonomou)
Date: Mon, 04 Jun 2012 15:10:04 -0400
Subject: [OpenIndiana-discuss] libmtsk.so and Solaris Studio 12.3 with
	libsunperf
Message-ID: <4FCD080C.2060809@research.att.com>

Hi Milan,

That doesn't sound good.  However, I found that Oracle 
bundles an up-to-date libmtsk.so with the Studio 
distribution for Linux:

/opt/oracle/solarisstudio12.3/prod/lib/compilers/rtlibs/usr/lib/libmtsk.so.1

If they do that, cant' we get this for OI also?

			Kostas

> Hi,
>
> no. It looks like Oracle moved libmtsk to system/library/openmp package
> with something called openmp.license. From the license only one header
> file is under BSD like license, the rest is owned by Oracle and not
> redistributable. So there is no legal way to publish newer libmtsk in
> OpenIndiana, only if somebody reimplements libmtsk :-(
>
> Best regards,
>
> Milan



Kostas Oikonomou p??e v p? 01. 06. 2012 v 11:12 -0400:
> Is there any chance of updating the /lib/libmtsk.so.1 and
> /lib/amd64/libmtsko.so.1 that come with OI 151a3 to
> version SUNWprivate_1.5?
>
> This version is required by Solaris (Oracle) Studio 12.3's
> libsunperf.  Without this update, libsunperf is apparently
> not usable.
> You cannot get programs to compile because of
>
> Undefined            first referenced
>   symbol                  in file
> __mt_static_for_loop
> /opt/solstudio/lib/amd64/libsunperf.so
>
>
>                  Kostas
>





From milan.jurik at xylab.cz  Mon Jun  4 19:26:40 2012
From: milan.jurik at xylab.cz (Milan Jurik)
Date: Mon, 04 Jun 2012 21:26:40 +0200
Subject: [OpenIndiana-discuss] libmtsk.so and Solaris Studio 12.3 with
 libsunperf
In-Reply-To: <4FCD080C.2060809@research.att.com>
References: <4FCD080C.2060809@research.att.com>
Message-ID: <1338838000.1300.15.camel@xylabone>

Hi Kostas,

Kostas Oikonomou p??e v po 04. 06. 2012 v 15:10 -0400:
> Hi Milan,
> 
> That doesn't sound good.  However, I found that Oracle 
> bundles an up-to-date libmtsk.so with the Studio 
> distribution for Linux:
> 
> /opt/oracle/solarisstudio12.3/prod/lib/compilers/rtlibs/usr/lib/libmtsk.so.1
> 
> If they do that, cant' we get this for OI also?
> 

yes, they bundle it with Linux distro because they have no other
options. But in case of Solaris they distribute libs directly with
Solaris on the install media of Solaris 11 and these are not
redistributable.

Best regards,

Milan

> 			Kostas
> 
> > Hi,
> >
> > no. It looks like Oracle moved libmtsk to system/library/openmp package
> > with something called openmp.license. From the license only one header
> > file is under BSD like license, the rest is owned by Oracle and not
> > redistributable. So there is no legal way to publish newer libmtsk in
> > OpenIndiana, only if somebody reimplements libmtsk :-(
> >
> > Best regards,
> >
> > Milan
> 
> 
> 
> Kostas Oikonomou p??e v p? 01. 06. 2012 v 11:12 -0400:
> > Is there any chance of updating the /lib/libmtsk.so.1 and
> > /lib/amd64/libmtsko.so.1 that come with OI 151a3 to
> > version SUNWprivate_1.5?
> >
> > This version is required by Solaris (Oracle) Studio 12.3's
> > libsunperf.  Without this update, libsunperf is apparently
> > not usable.
> > You cannot get programs to compile because of
> >
> > Undefined            first referenced
> >   symbol                  in file
> > __mt_static_for_loop
> > /opt/solstudio/lib/amd64/libsunperf.so
> >
> >
> >                  Kostas
> >
> 
> 
> 
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss




From betchoubetchou at gmail.com  Mon Jun  4 20:22:23 2012
From: betchoubetchou at gmail.com (betchou betchou)
Date: Mon, 4 Jun 2012 22:22:23 +0200
Subject: [OpenIndiana-discuss] Driver rum0 SOooooo SLOW
Message-ID: <CACMHwCNPnyM+W_E9EZu7XBQKiuVY1qhB3zTnnNKGU7hF=b=oBw@mail.gmail.com>

Hy all,

I would like to know If someone has a "normal" connection with the driver
rum0. I have a Dual Boot computer, so I can test that the connection is
supposed to be good.
I can barely do everything. I can ping other computers in the network,
beeing ping by my hostname,... I think I can do everything but SOOOOOOOOOO
slowly.
I installed wireshark to check the network and the first thing I have seen
(don't know If that's normal) is that I'm not answering to ARP broadcast.
It seems I have a lot of trames going in timeout too.

If you have any idea to who I should ask questions... I would be glad to
ear it.

Thanks a lot,
Julien

From dave-oi at pooserville.com  Mon Jun  4 21:27:10 2012
From: dave-oi at pooserville.com (Dave Pooser)
Date: Mon, 04 Jun 2012 16:27:10 -0500
Subject: [OpenIndiana-discuss] Any OI experiences with SuperMicro X9DR7-LN4F?
Message-ID: <CBF2916F.3C0A4%dave-oi@pooserville.com>

The two concerns I have are the LSI SAS controller (LSI 2308) and the
Intel i350 4-port GigE network (which doesn't appear to have drivers under
OI151a but does under Solaris 11). I'm looking for a motherboard that
works well with the onboard SAS because I'm trying to fit it in 1U and
still have room for a fibre channel card. I know I can fall back to a
Socket 1366 motherboard if necessary but I hate to buy an older CPU now
that the E5 Xeons are out....
-- 
Dave Pooser
Cat-Herder-in-Chief, Pooserville.com
"...Life is not a journey to the grave with the intention of arriving
safely in one pretty and well-preserved piece, but to slide across the
finish line broadside, thoroughly used up, worn out, leaking oil, and
shouting GERONIMO!!!" -- Bill McKenna






From bfriesen at simple.dallas.tx.us  Mon Jun  4 23:11:40 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Mon, 4 Jun 2012 18:11:40 -0500 (CDT)
Subject: [OpenIndiana-discuss] Any OI experiences with SuperMicro
 X9DR7-LN4F?
In-Reply-To: <CBF2916F.3C0A4%dave-oi@pooserville.com>
References: <CBF2916F.3C0A4%dave-oi@pooserville.com>
Message-ID: <alpine.GSO.2.01.1206041807580.7383@freddy.simplesystems.org>

On Mon, 4 Jun 2012, Dave Pooser wrote:

> The two concerns I have are the LSI SAS controller (LSI 2308) and the
> Intel i350 4-port GigE network (which doesn't appear to have drivers under
> OI151a but does under Solaris 11). I'm looking for a motherboard that
> works well with the onboard SAS because I'm trying to fit it in 1U and
> still have room for a fibre channel card. I know I can fall back to a
> Socket 1366 motherboard if necessary but I hate to buy an older CPU now
> that the E5 Xeons are out....

I found a posting that says support for Intel i350 was pushed into 
Illumos some three or four months ago.  The work was done by Nextenta.

I hope it is working since a system I have on order uses the Intel 
i350.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From bfriesen at simple.dallas.tx.us  Mon Jun  4 23:15:16 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Mon, 4 Jun 2012 18:15:16 -0500 (CDT)
Subject: [OpenIndiana-discuss] Any OI experiences with SuperMicro
 X9DR7-LN4F?
In-Reply-To: <alpine.GSO.2.01.1206041807580.7383@freddy.simplesystems.org>
References: <CBF2916F.3C0A4%dave-oi@pooserville.com>
	<alpine.GSO.2.01.1206041807580.7383@freddy.simplesystems.org>
Message-ID: <alpine.GSO.2.01.1206041813450.7383@freddy.simplesystems.org>

On Mon, 4 Jun 2012, Bob Friesenhahn wrote:
>
> I found a posting that says support for Intel i350 was pushed into Illumos 
> some three or four months ago.  The work was done by Nextenta.

Here is the Illumos bug entry (2038):

   https://www.illumos.org/issues/2038

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From gbulfon at sonicle.com  Tue Jun  5 06:57:21 2012
From: gbulfon at sonicle.com (Gabriele Bulfon)
Date: Tue, 5 Jun 2012 08:57:21 +0200
Subject: [OpenIndiana-discuss] NFS hidden files
Message-ID: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>

Hi,

On NFS mounted file systems I often happen to find daemons of the client complaining about the hidden .nfsxxx files appearing and disappearing.
These are often annoying.

Is there any way to let the server completely hide these files to the client, and just keep them on the server file system for his own duties?

Thanx for any help
Gabriele.

Inviato da iPad

From gbulfon at sonicle.com  Tue Jun  5 09:36:56 2012
From: gbulfon at sonicle.com (Gabriele Bulfon)
Date: Tue, 5 Jun 2012 11:36:56 +0200
Subject: [OpenIndiana-discuss] Sun Restaurant.....
Message-ID: <F9FF8FF2-F9BB-4584-8588-690062588CED@sonicle.com>

....thought many of you will smile at this discovery....this is a restaurant in Italy, near Milan.
Look at the logo...... :)))) I think I'll have a dinner there sooner or later!

http://www.ristorantesun.it/

Gabriele

From carlsonj at workingcode.com  Tue Jun  5 11:15:25 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Tue, 05 Jun 2012 07:15:25 -0400
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>
Message-ID: <4FCDEA4D.5010708@workingcode.com>

Gabriele Bulfon wrote:
> Hi,
> 
> On NFS mounted file systems I often happen to find daemons of the client complaining about the hidden .nfsxxx files appearing and disappearing.
> These are often annoying.
> 
> Is there any way to let the server completely hide these files to the client, and just keep them on the server file system for his own duties?

No.  They represent files that have been removed and are being held open
on the client.  They're a required part of NFS to provide UNIX file
semantics, and the whole point of them is that they're *NOT* hidden from
the client.  They wouldn't work at all if they were hidden.

Close the file, and the problem should go away, as the server will then
remove the .nfs file.

It's possible that if the system crashes, the files could be abandoned.
 I suspect that's rarely the case.  But you could use a cron job to find
them if you were concerned about it.

Have you tried a google search on ".nfs files"?

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From jose.marcio.mc at gmail.com  Tue Jun  5 11:22:42 2012
From: jose.marcio.mc at gmail.com (Jose-Marcio Martins da Cruz)
Date: Tue, 05 Jun 2012 13:22:42 +0200
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <4FCDEA4D.5010708@workingcode.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>
	<4FCDEA4D.5010708@workingcode.com>
Message-ID: <4FCDEC02.5080605@gmail.com>


Sorry for the top post...

These files shouldn't be accessed by daemons other than those daemons in the NFS system. If other 
daemons are doing so, they're not respecting the NFS rules of the game.

The only thing to do with these files is to remove them after after a system crash or similar event.

James Carlson wrote:
> Gabriele Bulfon wrote:
>> Hi,
>>
>> On NFS mounted file systems I often happen to find daemons of the client complaining about the hidden .nfsxxx files appearing and disappearing.
>> These are often annoying.
>>
>> Is there any way to let the server completely hide these files to the client, and just keep them on the server file system for his own duties?
>
> No.  They represent files that have been removed and are being held open
> on the client.  They're a required part of NFS to provide UNIX file
> semantics, and the whole point of them is that they're *NOT* hidden from
> the client.  They wouldn't work at all if they were hidden.
>
> Close the file, and the problem should go away, as the server will then
> remove the .nfs file.
>
> It's possible that if the system crashes, the files could be abandoned.
>   I suspect that's rarely the case.  But you could use a cron job to find
> them if you were concerned about it.
>
> Have you tried a google search on ".nfs files"?
>



From carlsonj at workingcode.com  Tue Jun  5 11:43:21 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Tue, 05 Jun 2012 07:43:21 -0400
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <4FCDEC02.5080605@gmail.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>	<4FCDEA4D.5010708@workingcode.com>
	<4FCDEC02.5080605@gmail.com>
Message-ID: <4FCDF0D9.1050404@workingcode.com>

Jose-Marcio Martins da Cruz wrote:
> 
> Sorry for the top post...
> 
> These files shouldn't be accessed by daemons other than those daemons in
> the NFS system. If other daemons are doing so, they're not respecting
> the NFS rules of the game.

Well ... sort of.  What do you say when "rm -rf somedir" fails because
some of the files within "somedir," although owned by the invoker,
cannot be removed?  Or when the GUI "Trash" icon stays messy after
emptying because there are files that won't go away?

I certainly respect the original poster's opinion that these files get
in the way and that they're annoying.  They're nasty, but they're part
of the game.  Stick with local file systems if you really can't stand
them.  :-/

> The only thing to do with these files is to remove them after after a
> system crash or similar event.

+1

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From jose.marcio.mc at gmail.com  Tue Jun  5 12:31:43 2012
From: jose.marcio.mc at gmail.com (Jose-Marcio Martins da Cruz)
Date: Tue, 05 Jun 2012 14:31:43 +0200
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <4FCDF0D9.1050404@workingcode.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>	<4FCDEA4D.5010708@workingcode.com>
	<4FCDEC02.5080605@gmail.com> <4FCDF0D9.1050404@workingcode.com>
Message-ID: <4FCDFC2F.2090004@gmail.com>

James Carlson wrote:
> Jose-Marcio Martins da Cruz wrote:

...

> Well ... sort of.  What do you say when "rm -rf somedir" fails because
> some of the files within "somedir," although owned by the invoker,
> cannot be removed?  Or when the GUI "Trash" icon stays messy after
> emptying because there are files that won't go away?

That means that these files are still open and in use by some program, or some active process has 
its pwd inside "somedir", or some process ended without cleanly close its open files. Am I wrong ?

Either way, IMHO, it's usually not the fault of NFS system.




From jimklimov at cos.ru  Tue Jun  5 13:12:52 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 05 Jun 2012 17:12:52 +0400
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <4FCDFC2F.2090004@gmail.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>
	<4FCDEA4D.5010708@workingcode.com> <4FCDEC02.5080605@gmail.com>
	<4FCDF0D9.1050404@workingcode.com> <4FCDFC2F.2090004@gmail.com>
Message-ID: <4FCE05D4.7070100@cos.ru>

2012-06-05 16:31, Jose-Marcio Martins da Cruz wrote:
>>Well ... sort of.  What do you say when "rm -rf somedir" fails because
>> some of the files within "somedir," although owned by the invoker,
>> cannot be removed?
> That means that these files are still open and in use by some program,
> or some active process has its pwd inside "somedir", or some process
> ended without cleanly close its open files. Am I wrong ?
>
> Either way, IMHO, it's usually not the fault of NFS system.

I believe, there is also a scenario where a program opens a file,
deletes (unlinks) it from the filesystem, and uses the file handle.
Beside being a byproduct of a user deleting files still opened by
some program, this is often used for secure temporary files which
no-one can now break into - because there is no reference to the
file from any directory (but the FS inode exists until the file
handle is closed by the original program).

I wonder if in such cases the NFS server should hide the inode
(i.e. in case of ZFS - use some special directory under .zfs in
the dataset which contains the removed file) in order to allow
removal of directories as you outlined above.

QUESTION: I also wonder if there is an NFS-protocol action for
a server to send a "hint" to the NFS client, for example, if
the storage server is going to gracefully disable itself upon
poweroff, etc. Namely, compliant clients would flush their data
to disk and stop their server processes or failover to another
replica of the storage server, if available. This would allow
proper shutdowns of VMs with NFS-based disk images, databases
over iSCSI, etc. when the server goes down. Is that possible
or implementable as an RFE?

One scenario I do think of in particular is gracefully shutting
down a farm of servers upon an UPS on-battery event, where the
storage servers and the compute servers might rely on different
power sources, and the storage one happens to go down first
(before the VM hosts begin to shut down).

Thanks,
//Jim


From paolo.marcheschi at ftgm.it  Tue Jun  5 13:20:53 2012
From: paolo.marcheschi at ftgm.it (Paolo Marcheschi)
Date: Tue, 05 Jun 2012 15:20:53 +0200
Subject: [OpenIndiana-discuss] Sun Restaurant.....
In-Reply-To: <F9FF8FF2-F9BB-4584-8588-690062588CED@sonicle.com>
References: <F9FF8FF2-F9BB-4584-8588-690062588CED@sonicle.com>
Message-ID: <4FCE07B5.6010402@ftgm.it>

Very funny indeed,
a good place to make an openindiana summer dinner  ;-0

Paolo

On June  5, 2012 11:36:56 AM CEST, Gabriele Bulfon wrote:
> ....thought many of you will smile at this discovery....this is a restaurant in Italy, near Milan.
> Look at the logo...... :)))) I think I'll have a dinner there sooner or later!
>
> http://www.ristorantesun.it/
>
> Gabriele
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
>


From sardonic.smiles at gmail.com  Tue Jun  5 14:06:03 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Tue, 5 Jun 2012 10:06:03 -0400
Subject: [OpenIndiana-discuss] Sun Restaurant.....
In-Reply-To: <4FCE07B5.6010402@ftgm.it>
References: <F9FF8FF2-F9BB-4584-8588-690062588CED@sonicle.com>
	<4FCE07B5.6010402@ftgm.it>
Message-ID: <CAPVmm=b0jrPYRbbaCW9bGuQwZ7QE=9Fyx1s8rV8tWHe+uCY00w@mail.gmail.com>

There used to be a tanning salon like that in Winnipeg Canada in the
80s/90s. Before I knew who sun was I thought the logo was super awesome.

Sended from my Android.
On Jun 5, 2012 9:22 AM, "Paolo Marcheschi" <paolo.marcheschi at ftgm.it> wrote:

> Very funny indeed,
> a good place to make an openindiana summer dinner  ;-0
>
> Paolo
>
> On June  5, 2012 11:36:56 AM CEST, Gabriele Bulfon wrote:
>
>> ....thought many of you will smile at this discovery....this is a
>> restaurant in Italy, near Milan.
>> Look at the logo...... :)))) I think I'll have a dinner there sooner or
>> later!
>>
>> http://www.ristorantesun.it/
>>
>> Gabriele
>> ______________________________**_________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss at openindiana.org>
>> http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
>>
>>
>>
> ______________________________**_________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss at openindiana.org>
> http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
>

From gbulfon at sonicle.com  Tue Jun  5 14:29:46 2012
From: gbulfon at sonicle.com (Gabriele Bulfon)
Date: Tue, 5 Jun 2012 16:29:46 +0200 (CEST)
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <4FCDEA4D.5010708@workingcode.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>
	<4FCDEA4D.5010708@workingcode.com>
Message-ID: <13426003.78.1338906586177.JavaMail.sonicle@xstream>

I understand your point.
But, my question is...shouldn't a network filesystem try to completely emulate a local file system,
trying to hide as much as possible the fact of being a network share?
In this case, how does a local filesystem like ZFS or UFS manage these situations?
Local file systems do not create .xxx files, and they never show up even in the situations you describe.
So, why NFS should be different? I believe that the NFS server may hold this files for himself and
the processes that already have opened sessions on them, not showing them in folder listings
(as zfs can do with its .zfs folder).
Also, is it correct by the file system to allow deletion of a file opened by someone else?
For example, an "rm -r folder" will fail in case I have a bash inside it's tree.
I believe an option to hide them would do no harm.
Thx anyway
Gabriele.
----------------------------------------------------------------------------------
Da: James Carlson
A: Discussion list for OpenIndiana
Data: 5 giugno 2012 13.15.25 CEST
Oggetto: Re: [OpenIndiana-discuss] NFS hidden files
Gabriele Bulfon wrote:
Hi,
On NFS mounted file systems I often happen to find daemons of the client complaining about the hidden .nfsxxx files appearing and disappearing.
These are often annoying.
Is there any way to let the server completely hide these files to the client, and just keep them on the server file system for his own duties?
No.  They represent files that have been removed and are being held open
on the client.  They're a required part of NFS to provide UNIX file
semantics, and the whole point of them is that they're *NOT* hidden from
the client.  They wouldn't work at all if they were hidden.
Close the file, and the problem should go away, as the server will then
remove the .nfs file.
It's possible that if the system crashes, the files could be abandoned.
I suspect that's rarely the case.  But you could use a cron job to find
them if you were concerned about it.
Have you tried a google search on ".nfs files"?
--
James Carlson         42.703N 71.076W
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

From sardonic.smiles at gmail.com  Tue Jun  5 16:20:08 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Tue, 5 Jun 2012 12:20:08 -0400
Subject: [OpenIndiana-discuss] Mounting %userprofile% from Windows on OI?
Message-ID: <CAPVmm=b=-SBJhs53ktEcBxYd9vW8Gk1REr+BLWk1TNJFbeEEBw@mail.gmail.com>

I'm trying to use OI as the backend for my Windows desktops. One of the
things I have is a userprofile directory. Rather than manually link each
user's profile, I did what is normally done and have a login policy set to
map the user directory to a drive on Windows via something akin to:
net use U: \\server\%username%

However, that produces:
*Jun  5 11:42:16 thoth smbsrv: [ID 138215 kern.notice] NOTICE:
smbd[DOMAIN\robbie]: netlogs share not found*

I'm assuming this is because the username is passed to OI with the domain
for AD based authentication. This works great for everything else, and AD
users have no other issues getting things working, but I cannot figure out
how to get it to work.

I've tried setting:

zfs set sharesmb=DOMAIN\\robbie tank\Home\robbie, but that doesn't change
anything. I'd like to solve this server-side, but if I need to figure out
how to redo this on the Windows side, that's fine.

-- 
Seconds to the drop, but it seems like hours.

http://www.eff.org/
<http://www.eff.org/>http://creativecommons.org/

From darknovanick at gmail.com  Tue Jun  5 17:32:20 2012
From: darknovanick at gmail.com (Nick Hall)
Date: Tue, 5 Jun 2012 12:32:20 -0500
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
Message-ID: <CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>

On Mon, Jun 4, 2012 at 10:48 AM, Jan Owoc <jsowoc at gmail.com> wrote:

>
> The data on the main pool is always consistent in that a certain
> operation either made it to the disk or it didn't. However, if your
> application depends on the fact that writes make it out to disk in a
> specific order (that's why it's sync'ing, right?), then it's the ZIL
> that would contain a log/journal of what should have been written to
> the disk and in what order. If you lose this, your file system remains
> consistent, but some writes may have made it out to the disk before
> others.
>
>
>
Thanks everyone for all the responses. They were very helpful. My main
application cases are ESXi, which as stated below does a lot of syncs, and
MySQL. I had previously used the zilstat tool, but this is the first time
I've heard of nfssrvtop, and I really appreciate that, as it works really
well for analyzing these usage patterns. After doing more analysis, it
seems as though most of my writes are actually async, so it probably
wouldn't speed things up too dramatically to add an SLOG, so for now I'm
going to stick with what I have, so thank you for that advice.

I'm just wondering, for my own personal knowledge and for anyone else who
finds this thread later, for some clarification on the above quote. So, if
I'm understanding this correctly, are you saying that, say I have an
application and it writes to file A, then it writes to file B, then it
writes to file C, then finally calls fsync, that there could be a case
where if the computer crashed and at the same time the SLOG got fried
(after files A B and C were written to, but before the sync was finished),
then upon restart, the write to file B may have taken affect on the pool
but the write to file A wouldn't be on there? Or am I misunderstanding?
Usually when I think of journals I would think it would roll back the
change to file B because it doesn't have a record in the journal to
indicate that the sync was successful. I understand the possibility of
loosing the last few seconds of writes in this scenario -- I'm just trying
to wrap my head around the possibility of losing *part* of the last few
seconds of data, and the much worse implications this has. Thanks,

Nick

From bfriesen at simple.dallas.tx.us  Tue Jun  5 17:41:24 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Tue, 5 Jun 2012 12:41:24 -0500 (CDT)
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
	<CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1206051235040.8584@freddy.simplesystems.org>

On Tue, 5 Jun 2012, Nick Hall wrote:
>
> I'm just wondering, for my own personal knowledge and for anyone else who
> finds this thread later, for some clarification on the above quote. So, if
> I'm understanding this correctly, are you saying that, say I have an
> application and it writes to file A, then it writes to file B, then it
> writes to file C, then finally calls fsync, that there could be a case
> where if the computer crashed and at the same time the SLOG got fried
> (after files A B and C were written to, but before the sync was finished),
> then upon restart, the write to file B may have taken affect on the pool
> but the write to file A wouldn't be on there? Or am I misunderstanding?

While this is the case with most popular filesystems, I don't think 
that it is the case for zfs if the zil went missing at power-up.  ZFS 
always uses ordered writes with transaction groups and each 
transaction group represents a loss point/barrier.  If the system had 
a working zil and the system lost power, then the sync writes in the 
zil would be used to update the filesystem so that async data since 
the last TXG would be missing while the sync data is now there.  Due 
to this, it is wise to be consistent about how related data is 
written.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From richard.elling at richardelling.com  Tue Jun  5 17:53:53 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Tue, 5 Jun 2012 10:53:53 -0700
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
	<CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
Message-ID: <98FFD292-E548-4CB5-A912-D3218D171DB2@RichardElling.com>

On Jun 5, 2012, at 10:32 AM, Nick Hall wrote:
> On Mon, Jun 4, 2012 at 10:48 AM, Jan Owoc <jsowoc at gmail.com> wrote:
> 
>> 
>> The data on the main pool is always consistent in that a certain
>> operation either made it to the disk or it didn't. However, if your
>> application depends on the fact that writes make it out to disk in a
>> specific order (that's why it's sync'ing, right?), then it's the ZIL
>> that would contain a log/journal of what should have been written to
>> the disk and in what order. If you lose this, your file system remains
>> consistent, but some writes may have made it out to the disk before
>> others.
>> 
>> 
>> 
> Thanks everyone for all the responses. They were very helpful. My main
> application cases are ESXi, which as stated below does a lot of syncs, and
> MySQL. I had previously used the zilstat tool, but this is the first time
> I've heard of nfssrvtop, and I really appreciate that, as it works really
> well for analyzing these usage patterns. After doing more analysis, it
> seems as though most of my writes are actually async, so it probably
> wouldn't speed things up too dramatically to add an SLOG, so for now I'm
> going to stick with what I have, so thank you for that advice.
> 
> I'm just wondering, for my own personal knowledge and for anyone else who
> finds this thread later, for some clarification on the above quote. So, if
> I'm understanding this correctly, are you saying that, say I have an
> application and it writes to file A, then it writes to file B, then it
> writes to file C, then finally calls fsync, that there could be a case
> where if the computer crashed and at the same time the SLOG got fried
> (after files A B and C were written to, but before the sync was finished),
> then upon restart, the write to file B may have taken affect on the pool
> but the write to file A wouldn't be on there? Or am I misunderstanding?

This is no different than any other file system.

To clarify the events here:
	+ if the slog fails to write, then it will be marked offline and no longer used
	+ if the slog fails to read the data, then it might not be detected until the next
	   import
	+ if the slog is healthy when the system crashes, then it is expected to be 
	   healthy when the pool is imported, if not, then the import will fail
		+ depending on the OS release, you might be able to manually
		   import the pool by ignoring the slog and accepting the risk of data 
		   loss -- see the zpool import -m option
	+ if your application is sensitive to consistency, then it needs to manage
	    it own consistency (many do, many do not)
	+ not buffering disk I/O sux
	+ disks that do not honor the SYNCHRONIZE_CACHE command suck

> Usually when I think of journals I would think it would roll back the
> change to file B because it doesn't have a record in the journal to
> indicate that the sync was successful. I understand the possibility of
> loosing the last few seconds of writes in this scenario -- I'm just trying
> to wrap my head around the possibility of losing *part* of the last few
> seconds of data, and the much worse implications this has. Thanks,

Some journaling file systems only log metadata changes, so they can
avoid the pain of fsck. This is not the same as the ZIL.
 -- richard

--
ZFS Performance and Training
Richard.Elling at RichardElling.com
+1-760-896-4422




From bfriesen at simple.dallas.tx.us  Tue Jun  5 17:57:55 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Tue, 5 Jun 2012 12:57:55 -0500 (CDT)
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <98FFD292-E548-4CB5-A912-D3218D171DB2@RichardElling.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
	<CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
	<98FFD292-E548-4CB5-A912-D3218D171DB2@RichardElling.com>
Message-ID: <alpine.GSO.2.01.1206051256000.8584@freddy.simplesystems.org>

On Tue, 5 Jun 2012, Richard Elling wrote:
>
> This is no different than any other file system.

It is not different than EXT4?

While the promise should always be the same, what actually happens 
seems to be very file system dependent.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From jsowoc at gmail.com  Tue Jun  5 18:08:15 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Tue, 5 Jun 2012 12:08:15 -0600
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
	<CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
Message-ID: <CADCwuEaML5kZjicaLFj2xscMHm5SLdMEzandd3D5NEneCxFUgA@mail.gmail.com>

On Tue, Jun 5, 2012 at 11:32 AM, Nick Hall <darknovanick at gmail.com> wrote:
> On Mon, Jun 4, 2012 at 10:48 AM, Jan Owoc <jsowoc at gmail.com> wrote:
>>
>> The data on the main pool is always consistent in that a certain
>> operation either made it to the disk or it didn't. However, if your
>> application depends on the fact that writes make it out to disk in a
>> specific order (that's why it's sync'ing, right?), then it's the ZIL
>> that would contain a log/journal of what should have been written to
>> the disk and in what order. If you lose this, your file system remains
>> consistent, but some writes may have made it out to the disk before
>> others.
>
> I'm just wondering, for my own personal knowledge and for anyone else who
> finds this thread later, for some clarification on the above quote. So, if
> I'm understanding this correctly, are you saying that, say I have an
> application and it writes to file A, then it writes to file B, then it
> writes to file C, then finally calls fsync, that there could be a case
> where if the computer crashed and at the same time the SLOG got fried
> (after files A B and C were written to, but before the sync was finished),
> then upon restart, the write to file B may have taken affect on the pool
> but the write to file A wouldn't be on there? Or am I misunderstanding?
> Usually when I think of journals I would think it would roll back the
> change to file B because it doesn't have a record in the journal to
> indicate that the sync was successful. I understand the possibility of
> loosing the last few seconds of writes in this scenario -- I'm just trying
> to wrap my head around the possibility of losing *part* of the last few
> seconds of data, and the much worse implications this has. Thanks,

Maybe I can clarify my own quote :-).

Many filesystems attempt to maintain internal consistency. Either a
file is there, or it isn't. The filesize needs to match what is
actually on disk. The free space needs to match what isn't actually
used etc. Regardless of whether or not you have ZIL enabled, and
whether you have a SLOG or not, the filesystem will remain internally
consistent.

Some applications may depend on the files (or portions thereof) making
it out to disk in a specific order. The example you gave is perfect.
Let's say file "A" needs to exist before a change in file "B" happens.
A properly written program would write out file "A", fsync, wait for
fsync to complete, then change file "B". A properly written filesystem
will wait for the data from "A" to hit physical, permanent, storage
before allowing the change to "B". This can be slow on mechanical
storage, so you put the ZIL on a separate SLOG.

The SLOG will contain information like "hey, this file 'A' needs to
make it out to sector 135425, then this file 'B' needs to be updated".
The disks themselves will be written out when and how convenient, but
if a crash were to occur, the ZIL will be replayed (either from the
SLOG or from the disk) and file 'A' *will* make it out to disk if file
'B' does. A damaged SLOG could mean that file 'B' was changed on disk,
but file 'A' never made it out.

Something else to keep in mind with NFS is that you could have the
remote system crashing and rebooting without your local system
knowing. Applications have files open on the remote system and assume
the remote file system to be in a certain state... and it isn't if the
SLOG fails. Some people recommend mirroring SLOGs.

Jan


From bfriesen at simple.dallas.tx.us  Tue Jun  5 18:39:21 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Tue, 5 Jun 2012 13:39:21 -0500 (CDT)
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <CADCwuEaML5kZjicaLFj2xscMHm5SLdMEzandd3D5NEneCxFUgA@mail.gmail.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<CADCwuEawKveWvB+rduhbR4nvDALQHa+iM+PFXD4UvxS0QO1RpQ@mail.gmail.com>
	<CACORSuZywnne6TR=GFmrpXA+gGmBGcSC=h6odRFNMJswL6XSwA@mail.gmail.com>
	<CADCwuEaML5kZjicaLFj2xscMHm5SLdMEzandd3D5NEneCxFUgA@mail.gmail.com>
Message-ID: <alpine.GSO.2.01.1206051330001.8584@freddy.simplesystems.org>

On Tue, 5 Jun 2012, Jan Owoc wrote:
> Some applications may depend on the files (or portions thereof) making
> it out to disk in a specific order. The example you gave is perfect.
> Let's say file "A" needs to exist before a change in file "B" happens.
> A properly written program would write out file "A", fsync, wait for
> fsync to complete, then change file "B". A properly written filesystem
> will wait for the data from "A" to hit physical, permanent, storage
> before allowing the change to "B". This can be slow on mechanical
> storage, so you put the ZIL on a separate SLOG.

Both ZFS normal writes and zil-based recovery are ordered.  I don't 
see how you could have "B" updated but "A" not updated.  As far as ZFS 
is concerned, the ZIL is persistent storage and no less reliable than 
other storage units in the pool.

This is radically different from a filesystem like EXT4 where some 
sorts of updates (e.g. create/delete file or directory) take priority 
over others.  Ad hoc approaches are often used to improve the 
appearance of performance, or because the filesystem "knows" that one 
sort of metadata or data is more important than another.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From carlsonj at workingcode.com  Tue Jun  5 20:06:38 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Tue, 05 Jun 2012 16:06:38 -0400
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <13426003.78.1338906586177.JavaMail.sonicle@xstream>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>	<4FCDEA4D.5010708@workingcode.com>
	<13426003.78.1338906586177.JavaMail.sonicle@xstream>
Message-ID: <4FCE66CE.9010900@workingcode.com>

Gabriele Bulfon wrote:
> I understand your point.
> But, my question is...shouldn't a network filesystem try to completely emulate a local file system,
> trying to hide as much as possible the fact of being a network share?

Sure, although "try" is certainly the operative word here.

> In this case, how does a local filesystem like ZFS or UFS manage these situations?

A local file system doesn't have this problem, because the directory
entry is distinct from the "handle" that the program has on an open
file.  An open local file essentially references the inode for that
file.  If the directory entry (which points to the inode) is removed,
the program can keep on using the now-nameless inode without trouble.
When all references to the inode are dropped, the space is returned to
the free pool.

(Depending on the OS, you may even be able to use link(2) to reattach an
unlinked but still open file by using the procfs nodes.)

With NFS, the server doesn't know whether files are open or closed.  If
the client actually removed the file, that would immediately invalidate
any other client handles, and break the applications still using the
now-unreferenced file.

In short, this is just how NFS works.

> Local file systems do not create .xxx files, and they never show up even in the situations you describe.

True.  Local file systems aren't remote.  :-/

> So, why NFS should be different? I believe that the NFS server may hold this files for himself and
> the processes that already have opened sessions on them, not showing them in folder listings
> (as zfs can do with its .zfs folder).

I suppose that NFS clients could be designed to hide these files from
the user optionally.  It may well make some operations a little (or
perhaps a lot) strange, but I think it could be made to work.  It's just
not how it's done today.

> Also, is it correct by the file system to allow deletion of a file opened by someone else?

Sure; standard UNIX/POSIX semantics apply.

> For example, an "rm -r folder" will fail in case I have a bash inside it's tree.

That's not true.  In one window:

% bash
carlsonj at carlson:/build/carlsonj$ mkdir foo
carlsonj at carlson:/build/carlsonj$ cd foo
carlsonj at carlson:/build/carlsonj/foo$

Now, in another window:

carlsonj at carlson:/build/carlsonj$ rm -r foo
carlsonj at carlson:/build/carlsonj$

Now back in the first window:

carlsonj at carlson:/build/carlsonj/foo$ /bin/pwd
pwd: cannot determine current directory!
carlsonj at carlson:/build/carlsonj/foo$

You can always remove anything you want to remove, assuming you have the
right permissions.  Directory entries are just that -- directory
entries.  They have the name of the object and a pointer to where the
object resides.  They're not the object itself.

> I believe an option to hide them would do no harm.

Fortunately, it's an open process.  Read RFCs 1813 and 3010 to start,
and propose your own design.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From chris at westnet.com  Tue Jun  5 22:08:39 2012
From: chris at westnet.com (Christopher X. Candreva)
Date: Tue, 5 Jun 2012 18:08:39 -0400 (EDT)
Subject: [OpenIndiana-discuss] Help installing OI 151a on IBM x366.
Message-ID: <alpine.GSO.2.01.1206051804160.2381@westnet.com>


I am trying to install OI 151a on an IBM x366. This machine has the 
Serveraid 8i SAS backplane, with a legacy IDE DVD rom drive.

The machine will boot the DVD, but then gives a stream of errors on
pci at 0,0/pci-ide at f/edi at 0 time reset bus

I've read about problems with IDE, that offered adding options to the 
command line that boots the kernel:
-B atapi-cd-dma-enabled=0,atapi-other-dma-enabled=0

That didn't work. I also saw something about disabling multiprocessing with  
the -kd option, then entering "use_mp/W 0 :c" . That didn't work either.

I tried booting from a USB dvd drive. Again, that boots, but after it loads 
the kernel from the DVD, I get an error that the drive disappeared.

I tried making a bootable USB stick, but the x366 won't both from the USB 
for some reason.

Are there any other suggestions I can try ?

-Chris


==========================================================
Chris Candreva  -- chris at westnet.com -- (914) 948-3162
WestNet Internet Services of Westchester
http://www.westnet.com/


From jimklimov at cos.ru  Tue Jun  5 22:27:26 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 06 Jun 2012 02:27:26 +0400
Subject: [OpenIndiana-discuss] Help installing OI 151a on IBM x366.
In-Reply-To: <alpine.GSO.2.01.1206051804160.2381@westnet.com>
References: <alpine.GSO.2.01.1206051804160.2381@westnet.com>
Message-ID: <4FCE87CE.10608@cos.ru>

2012-06-06 2:08, Christopher X. Candreva ???????:
>
> I am trying to install OI 151a on an IBM x366. This machine has the
> Serveraid 8i SAS backplane, with a legacy IDE DVD rom drive.
>
> The machine will boot the DVD, but then gives a stream of errors ...

You can also try the remote management - if there is a way to
pass it an ISO image from your mgmt workstation (at least some
servers do have "Virtual DVD-ROM" via IPMI).

Alternatively, you can try networked boot (PXE) and an AI image
(auto-install) of OpenIndiana, but you'd have to read up on
installing the installation server, serving AI images and all
that. I did not do AI installs, so can't help directly ;(

If you do manage that, and if you find the Wiki instructions
lacking, please consider updating them so the next people know
what to do :)

I know of these pages:
* 
http://wiki.openindiana.org/display/oi/Automated+Installer+and+Networked+Installation


HTH,
//Jim Klimov


From rlhamil at smart.net  Tue Jun  5 23:52:06 2012
From: rlhamil at smart.net (Richard L. Hamilton)
Date: Tue, 5 Jun 2012 19:52:06 -0400
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <4FCE66CE.9010900@workingcode.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>	<4FCDEA4D.5010708@workingcode.com>
	<13426003.78.1338906586177.JavaMail.sonicle@xstream>
	<4FCE66CE.9010900@workingcode.com>
Message-ID: <EBFD124F-C27B-4835-95D9-E13C5D1B26AB@smart.net>


On Jun 5, 2012, at 4:06 PM, James Carlson wrote:

> Gabriele Bulfon wrote:
>> I understand your point.
>> But, my question is...shouldn't a network filesystem try to completely emulate a local file system,
>> trying to hide as much as possible the fact of being a network share?
> 
> Sure, although "try" is certainly the operative word here.
> 
>> In this case, how does a local filesystem like ZFS or UFS manage these situations?
> 
> A local file system doesn't have this problem, because the directory
> entry is distinct from the "handle" that the program has on an open
> file.  An open local file essentially references the inode for that
> file.  If the directory entry (which points to the inode) is removed,
> the program can keep on using the now-nameless inode without trouble.
> When all references to the inode are dropped, the space is returned to
> the free pool.
> 
> (Depending on the OS, you may even be able to use link(2) to reattach an
> unlinked but still open file by using the procfs nodes.)
> 
> With NFS, the server doesn't know whether files are open or closed.  If
> the client actually removed the file, that would immediately invalidate
> any other client handles, and break the applications still using the
> now-unreferenced file.
> 
> In short, this is just how NFS works.
> 
>> Local file systems do not create .xxx files, and they never show up even in the situations you describe.
> 
> True.  Local file systems aren't remote.  :-/
> 
>> So, why NFS should be different? I believe that the NFS server may hold this files for himself and
>> the processes that already have opened sessions on them, not showing them in folder listings
>> (as zfs can do with its .zfs folder).
> 
> I suppose that NFS clients could be designed to hide these files from
> the user optionally.  It may well make some operations a little (or
> perhaps a lot) strange, but I think it could be made to work.  It's just
> not how it's done today.
> 
>> Also, is it correct by the file system to allow deletion of a file opened by someone else?
> 
> Sure; standard UNIX/POSIX semantics apply.
> 
>> For example, an "rm -r folder" will fail in case I have a bash inside it's tree.
> 
> That's not true.  In one window:
> 
> % bash
> carlsonj at carlson:/build/carlsonj$ mkdir foo
> carlsonj at carlson:/build/carlsonj$ cd foo
> carlsonj at carlson:/build/carlsonj/foo$
> 
> Now, in another window:
> 
> carlsonj at carlson:/build/carlsonj$ rm -r foo
> carlsonj at carlson:/build/carlsonj$
> 
> Now back in the first window:
> 
> carlsonj at carlson:/build/carlsonj/foo$ /bin/pwd
> pwd: cannot determine current directory!
> carlsonj at carlson:/build/carlsonj/foo$
> 
> You can always remove anything you want to remove, assuming you have the
> right permissions.  Directory entries are just that -- directory
> entries.  They have the name of the object and a pointer to where the
> object resides.  They're not the object itself.
> 
>> I believe an option to hide them would do no harm.
> 
> Fortunately, it's an open process.  Read RFCs 1813 and 3010 to start,
> and propose your own design.

A remote filesystem protocol by AT&T (and present only in very early Solaris, as I recall), called RFS, went to great lengths to provide all the usual semantics.  You could even access remote device files (although presumably both client and server had to support the same byte order, word size, alignment, etc, AND ioctls, for ioctls to be packaged up properly to work with remote devices - not sure how that worked!).  In fact, processes on the client and server could communicate with each other through a FIFO on the shared filesystem!

The flip side was that unlike NFS, if the server crashed, the client didn't just wait for the server to come back up, it got an error, not unlike you would if someone unplugged a local disk.  That is, the server was NOT stateless, but had state that was lost in a crash, which left returning an error to the client as the only option.

Compatible, reliable, high-performance: pick two.  (like a number of other "pick two" cases)




From gbulfon at sonicle.com  Wed Jun  6 00:42:42 2012
From: gbulfon at sonicle.com (Gabriele Bulfon)
Date: Wed, 6 Jun 2012 02:42:42 +0200
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <4FCE66CE.9010900@workingcode.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>
	<4FCDEA4D.5010708@workingcode.com>
	<13426003.78.1338906586177.JavaMail.sonicle@xstream>
	<4FCE66CE.9010900@workingcode.com>
Message-ID: <6027D81B-E553-4C22-9996-DEFA94318875@sonicle.com>

Nice discussion.
Even though I remember not being able to remove because of a bash waiting there,
but probably was a zfs destroy.......and IMHO this is a more logic approach

I'll read the RFCs :) Thanx!

Inviato da iPad

Il giorno 05/giu/2012, alle ore 22:06, James Carlson <carlsonj at workingcode.com> ha scritto:

> Gabriele Bulfon wrote:
>> I understand your point.
>> But, my question is...shouldn't a network filesystem try to completely emulate a local file system,
>> trying to hide as much as possible the fact of being a network share?
> 
> Sure, although "try" is certainly the operative word here.
> 
>> In this case, how does a local filesystem like ZFS or UFS manage these situations?
> 
> A local file system doesn't have this problem, because the directory
> entry is distinct from the "handle" that the program has on an open
> file.  An open local file essentially references the inode for that
> file.  If the directory entry (which points to the inode) is removed,
> the program can keep on using the now-nameless inode without trouble.
> When all references to the inode are dropped, the space is returned to
> the free pool.
> 
> (Depending on the OS, you may even be able to use link(2) to reattach an
> unlinked but still open file by using the procfs nodes.)
> 
> With NFS, the server doesn't know whether files are open or closed.  If
> the client actually removed the file, that would immediately invalidate
> any other client handles, and break the applications still using the
> now-unreferenced file.
> 
> In short, this is just how NFS works.
> 
>> Local file systems do not create .xxx files, and they never show up even in the situations you describe.
> 
> True.  Local file systems aren't remote.  :-/
> 
>> So, why NFS should be different? I believe that the NFS server may hold this files for himself and
>> the processes that already have opened sessions on them, not showing them in folder listings
>> (as zfs can do with its .zfs folder).
> 
> I suppose that NFS clients could be designed to hide these files from
> the user optionally.  It may well make some operations a little (or
> perhaps a lot) strange, but I think it could be made to work.  It's just
> not how it's done today.
> 
>> Also, is it correct by the file system to allow deletion of a file opened by someone else?
> 
> Sure; standard UNIX/POSIX semantics apply.
> 
>> For example, an "rm -r folder" will fail in case I have a bash inside it's tree.
> 
> That's not true.  In one window:
> 
> % bash
> carlsonj at carlson:/build/carlsonj$ mkdir foo
> carlsonj at carlson:/build/carlsonj$ cd foo
> carlsonj at carlson:/build/carlsonj/foo$
> 
> Now, in another window:
> 
> carlsonj at carlson:/build/carlsonj$ rm -r foo
> carlsonj at carlson:/build/carlsonj$
> 
> Now back in the first window:
> 
> carlsonj at carlson:/build/carlsonj/foo$ /bin/pwd
> pwd: cannot determine current directory!
> carlsonj at carlson:/build/carlsonj/foo$
> 
> You can always remove anything you want to remove, assuming you have the
> right permissions.  Directory entries are just that -- directory
> entries.  They have the name of the object and a pointer to where the
> object resides.  They're not the object itself.
> 
>> I believe an option to hide them would do no harm.
> 
> Fortunately, it's an open process.  Read RFCs 1813 and 3010 to start,
> and propose your own design.
> 
> -- 
> James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From vab at bb-c.de  Wed Jun  6 06:12:57 2012
From: vab at bb-c.de (Volker A. Brandt)
Date: Wed, 6 Jun 2012 08:12:57 +0200
Subject: [OpenIndiana-discuss] Help installing OI 151a on IBM x366.
In-Reply-To: <alpine.GSO.2.01.1206051804160.2381@westnet.com>
References: <alpine.GSO.2.01.1206051804160.2381@westnet.com>
Message-ID: <20430.62697.144503.35316@gargle.gargle.HOWL>

> I am trying to install OI 151a on an IBM x366. This machine has the
> Serveraid 8i SAS backplane, with a legacy IDE DVD rom drive.
> 
> The machine will boot the DVD, but then gives a stream of errors on
> pci at 0,0/pci-ide at f/edi at 0 time reset bus

Yes, I have seen the same errors on an x3655 with Solaris 10.  It is
a known problem, IBM documents it somewhere.  It went away in some
Solaris 10 Update.  Solaris 11 Express also does not have that problem.
 
> I've read about problems with IDE, that offered adding options to
> the command line that boots the kernel: -B
> atapi-cd-dma-enabled=0,atapi-other-dma-enabled=0

No, that does not help.  These settings are the default anyway.
 
> That didn't work. I also saw something about disabling
> multiprocessing with the -kd option, then entering "use_mp/W 0 :c"
> . That didn't work either.

No, nothing to do with it.
 
> I tried booting from a USB dvd drive. Again, that boots, but after
> it loads the kernel from the DVD, I get an error that the drive
> disappeared.
>
> I tried making a bootable USB stick, but the x366 won't both from
> the USB for some reason.

I have also not been able to boot the x3655 off a USB stick.

> Are there any other suggestions I can try ?

Use AI.  Or install to another disk on another server, then boot off
a recent-enough live CD, and build the boot disk manually, using
snapshots from the other server.


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"


From matt at mattclark.net  Wed Jun  6 11:22:28 2012
From: matt at mattclark.net (Matt Clark)
Date: Wed, 6 Jun 2012 12:22:28 +0100
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
Message-ID: <F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>

It's true you need a decent SSD, but they don't have to be expensive.  The Intel 320 series has power loss protection and good performance.  The 80GB (10,000 write IOPS,  10TB endurance) model is available for ?100 un the UK.  Every ZFS server should have one!

http://www.intel.com/content/www/us/en/solid-state-drives/ssd-320-enterprise-server-storage-application-specification-addendum.html



On 4 Jun 2012, at 19:23, Mike La Spina wrote:

> Everything you asked seems to be fully covered by our community.
> 
> Just wanted to add the following;
> 
> Not all SSDs are made for slog usage. Be aware that low end (and even
> some high endones) SSDs may not successfully commit a write operation to
> the flash write cell address boundary due to a power loss event. At a
> minimum the use of a UPS is advisable or SSDs that guaranty complete
> write operations in the event of a power loss.  




From carlsonj at workingcode.com  Wed Jun  6 11:25:36 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Wed, 06 Jun 2012 07:25:36 -0400
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <6027D81B-E553-4C22-9996-DEFA94318875@sonicle.com>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>	<4FCDEA4D.5010708@workingcode.com>	<13426003.78.1338906586177.JavaMail.sonicle@xstream>	<4FCE66CE.9010900@workingcode.com>
	<6027D81B-E553-4C22-9996-DEFA94318875@sonicle.com>
Message-ID: <4FCF3E30.6020200@workingcode.com>

Gabriele Bulfon wrote:
> Nice discussion.
> Even though I remember not being able to remove because of a bash waiting there,
> but probably was a zfs destroy.......and IMHO this is a more logic approach

Even there, you can still do it if you want.  The issue isn't the "zfs
destroy" operation itself, but rather the normal semantics of the
umount(2) system call -- it returns an error if the file system is still
busy.

You can forcibly unmount the file system, even if it's busy, and then go
ahead and destroy the zfs file system from underneath bash.  The next
time bash attempts to access the current directory, it'll get an error.

The two operations, though, are fundamentally different.  In the case of
removing a file or a whole directory, you're just removing the directory
entries representing those objects.  The directory entries themselves
are never "in use" in any meaningful way when a file is open.  In the
case of unmounting a file system, though, you're revoking access to a
set of structures that are actively in use, and that requires a choice;
either the one removing loses (EBUSY) or the one using loses (ENOENT or
similar).

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From carlsonj at workingcode.com  Wed Jun  6 11:48:18 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Wed, 06 Jun 2012 07:48:18 -0400
Subject: [OpenIndiana-discuss] NFS hidden files
In-Reply-To: <EBFD124F-C27B-4835-95D9-E13C5D1B26AB@smart.net>
References: <18FE9A40-F1F5-42F6-B0E4-7FFD75885FE9@sonicle.com>	<4FCDEA4D.5010708@workingcode.com>	<13426003.78.1338906586177.JavaMail.sonicle@xstream>	<4FCE66CE.9010900@workingcode.com>
	<EBFD124F-C27B-4835-95D9-E13C5D1B26AB@smart.net>
Message-ID: <4FCF4382.8080604@workingcode.com>

Richard L. Hamilton wrote:
> A remote filesystem protocol by AT&T (and present only in very early Solaris, as I recall), called RFS, went to great lengths to provide all the usual semantics.  You could even access remote device files (although presumably both client and server had to support the same byte order, word size, alignment, etc, AND ioctls, for ioctls to be packaged up properly to work with remote devices - not sure how that worked!).  In fact, processes on the client and server could communicate with each other through a FIFO on the shared filesystem!

Yes, I remember RFS.  Besides using it myself, I worked on a related
protocol in the Annex terminal server called "TSTTY" that implemented
remote serial ports.

Basically, yes, the ioctls and (perhaps more critically) all of the data
structures passed along with the ioctls had to line up between the two
systems, or it wouldn't work.  But, then, all Real Machines are
big-endian, right?  ;-}

> The flip side was that unlike NFS, if the server crashed, the client didn't just wait for the server to come back up, it got an error, not unlike you would if someone unplugged a local disk.  That is, the server was NOT stateless, but had state that was lost in a crash, which left returning an error to the client as the only option.
> 
> Compatible, reliable, high-performance: pick two.  (like a number of other "pick two" cases)

There've been a number of other works in this area.  AFS is interesting
because you can still access your locally-cached files for a while after
the Vice server goes down.  It'll still grind to a halt like NFS when
something bad happens, it just tends to take longer.

In any event, remote file systems are different.  Sometimes subtly, and
sometimes brutally.  (File locking, not the silly ".nfs" files, is where
NFS users tend to get really tripped up.  NFS has advisory but not
mandatory locks, and crash recovery can be weird.)

For what it's worth, local file systems are sometimes different as well.
 UFS and ZFS aren't precisely the same -- check out the reported sizes
of your directories with "ls."   Nor is UFS at all like PCFS (DOS) or
like HSFS (CD/DVD).

I think the ".nfs" thing is a bit of a molehill.  Working on multiple
platforms, you'll see things that are far more jarring than that.  For
example, on HP/UX, memory-mapped files (e.g., shared libraries) are
locked good and hard.  You can't write to them.  You can't remove them.
 You can't even rename them.  They end up with a big yellow "police line
- do not cross" ribbon around them, which sometimes makes software
upgrade "interesting."

It's a weird world out there.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From iszczesniak at gmail.com  Wed Jun  6 11:58:15 2012
From: iszczesniak at gmail.com (Irek Szczesniak)
Date: Wed, 6 Jun 2012 13:58:15 +0200
Subject: [OpenIndiana-discuss]  NFS hidden files
Message-ID: <CALnxO55YTtW313T+1H0B9rFLZE_N6sU3YV93mNgRjSSkm2KAYw@mail.gmail.com>

On Tue, Jun 5, 2012 at 8:57 AM, Gabriele Bulfon <gbulfon at sonicle.com> wrote:
> Hi,
>
> On NFS mounted file systems I often happen to find daemons of the client complaining about the hidden .nfsxxx files appearing and disappearing.
> These are often annoying.
>
> Is there any way to let the server completely hide these files to the client, and just keep them on the server file system for his own duties?
>
> Thanx for any help
> Gabriele.

Which NFS version do you use? I might be wrong but AFAIK NFSv4 dropped
the dreaded .nfs* files.

Irek


From maybird1776 at yahoo.com  Wed Jun  6 13:42:00 2012
From: maybird1776 at yahoo.com (ken mays)
Date: Wed, 6 Jun 2012 06:42:00 -0700 (PDT)
Subject: [OpenIndiana-discuss] Linux Format: Issue 158 - OI vs. other
	alternative distros
In-Reply-To: <CALnxO55YTtW313T+1H0B9rFLZE_N6sU3YV93mNgRjSSkm2KAYw@mail.gmail.com>
References: <CALnxO55YTtW313T+1H0B9rFLZE_N6sU3YV93mNgRjSSkm2KAYw@mail.gmail.com>
Message-ID: <1338990120.12165.YahooMailNeo@web111302.mail.gq1.yahoo.com>

Linux Format did a recent article on OpenIndiana oi_151a in various categories on how it compares to other alternative distros (i.e. non-Linux). They gave an average of 3-4/5 stars in all categories, which was pretty good overall.

Linux Format: Issue 158 (June 2012)
Alternative operating systems
We take a look at PC-BSD, GhostBSD, OpenIndiana, Haiku and Icaros (Mayank Sharma)
Ref: http://www.linuxformat.com/archives?issue=158

~ Ken Mays

From richard.elling at richardelling.com  Wed Jun  6 15:14:49 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Wed, 6 Jun 2012 08:14:49 -0700
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
Message-ID: <BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>

On Jun 6, 2012, at 4:22 AM, Matt Clark wrote:

> It's true you need a decent SSD, but they don't have to be expensive.  The Intel 320 series has power loss protection and good performance.  The 80GB (10,000 write IOPS,  10TB endurance) model is available for ?100 un the UK.  Every ZFS server should have one!
> 
> http://www.intel.com/content/www/us/en/solid-state-drives/ssd-320-enterprise-server-storage-application-specification-addendum.html

NB, the 10k IOPS is for a write span limited to 8GB. For full-size random writes, the
IOPS dives to an astonishing 300. Still 2x a HDD, but only 2x a HDD. For slog use,
consider a partition size 8GB or less.
 -- richard

--
ZFS Performance and Training
Richard.Elling at RichardElling.com
+1-760-896-4422




From matt at mattclark.net  Wed Jun  6 19:23:09 2012
From: matt at mattclark.net (Matt Clark)
Date: Wed, 6 Jun 2012 20:23:09 +0100
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
Message-ID: <49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>

Yes, it's interesting to consider the possible real world performance.  ZIL writes, even by DDRDrive's stats, are very closely clustered around the tail of the ZIL, with most seeks being to near locations - it's certainly not going to seek more than 8 gig away.  So probably just leaving it at one big partition would be fine too.  In my home (i.e. toy) implementation the SLOG is just a partition on an 80GB drive shared with the root pool and L2ARC, and frankly the gigabit network runs out of puff long before I can tax the server IO with sync writes.  If anyone has one doing more than toy stuff it would be good to hear.

On 6 Jun 2012, at 16:14, Richard Elling wrote:

> NB, the 10k IOPS is for a write span limited to 8GB. For full-size random writes, the
> IOPS dives to an astonishing 300. Still 2x a HDD, but only 2x a HDD. For slog use,
> consider a partition size 8GB or less.
> -- richard



From gary at genashor.com  Wed Jun  6 19:29:51 2012
From: gary at genashor.com (Gary Gendel)
Date: Wed, 06 Jun 2012 15:29:51 -0400
Subject: [OpenIndiana-discuss] How to deal with IPV4/6 as a router
Message-ID: <4FCFAFAF.50801@genashor.com>

My Home OI box currently serves as my router/gateway to my ISP.

Under IPV4 I have

Cable Modem <-> bge0 <-> ipfilter/nat <-> bge1 <-> network.

My ISP has turned on IPV6 and I can get as many addresses as I want.  
However, some of my devices aren't ipv6 capable so I have to deal with a 
mix of ipv4 and ipv6 addresses until these are retired.

I turned on ipv6 on bge0 and have both an ipv4 and ipv6 address.  I also 
can run the ipv6 test (test-ipv6.com) perfectly.

The question is: How do I set up things so it works with my internal 
devices?  It seems that All I want to do is to leave the ipv4 setup as I 
have it now and pass all ipv6 packets (discovery, etc.) from bge0 to 
bge1 (and visa versa).  This way my ISP will provide ipv6 addresses to 
those devices that ask for one.

Or should I provide a "private" ipv6 address space for my LAN?  This 
doesn't seem to be in the spirit of ipv6, but it will provide me more 
firewall control of traffic in and out of the network and provide 
"static" addresses to my hosts.

Gary



From carlsonj at workingcode.com  Wed Jun  6 19:56:30 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Wed, 06 Jun 2012 15:56:30 -0400
Subject: [OpenIndiana-discuss] How to deal with IPV4/6 as a router
In-Reply-To: <4FCFAFAF.50801@genashor.com>
References: <4FCFAFAF.50801@genashor.com>
Message-ID: <4FCFB5EE.2030903@workingcode.com>

Gary Gendel wrote:
> The question is: How do I set up things so it works with my internal
> devices?  It seems that All I want to do is to leave the ipv4 setup as I
> have it now and pass all ipv6 packets (discovery, etc.) from bge0 to
> bge1 (and visa versa).  This way my ISP will provide ipv6 addresses to
> those devices that ask for one.
> 
> Or should I provide a "private" ipv6 address space for my LAN?  This
> doesn't seem to be in the spirit of ipv6, but it will provide me more
> firewall control of traffic in and out of the network and provide
> "static" addresses to my hosts.

What, precisely, did your ISP give you?  What do you see in the
configuration?

If they've given you just a single /64 on a broadcast-type interface
(e.g. Ethernet), then you're right that this is going to be a little
tough because you need either a bridge to get the unadulterated traffic
onto the internal network (including the RAs from their routers) or you
need the moral equivalent of "proxy ARP" for v6, which doesn't really
exist.  The best answer there might just be to put all of the v6
machines you have out on the switch connected to their router and be
done with it.

If they've given you a collection of two or more /64s so that you can
route, then you should be able to set the "ROUTER" flag on the
interfaces, set up some prefix advertising for the other prefixes, and
do it the "right way."  (Shame to burn a global /64 on a simple link to
the ISP, but, well, I don't see a better way with broadcast-type
interfaces.)

If they've given you a single /64 on a non-broadcast type interface
(such as a point-to-point tunnel), then please specify.  That'd be a
simple thing to handle.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From kristoff at skypro.be  Wed Jun  6 23:02:53 2012
From: kristoff at skypro.be (Kristoff Bonne)
Date: Thu, 07 Jun 2012 01:02:53 +0200
Subject: [OpenIndiana-discuss] How to deal with IPV4/6 as a router
In-Reply-To: <4FCFAFAF.50801@genashor.com>
References: <4FCFAFAF.50801@genashor.com>
Message-ID: <4FCFE19D.3000505@skypro.be>

Hi Gary,



On 06-06-12 21:29, Gary Gendel wrote:
> My Home OI box currently serves as my router/gateway to my ISP.
>
> Under IPV4 I have
>
> Cable Modem <-> bge0 <-> ipfilter/nat <-> bge1 <-> network.
>
> My ISP has turned on IPV6 and I can get as many addresses as I want.  
> However, some of my devices aren't ipv6 capable so I have to deal with 
> a mix of ipv4 and ipv6 addresses until these are retired.
> I turned on ipv6 on bge0 and have both an ipv4 and ipv6 address.  I 
> also can run the ipv6 test (test-ipv6.com) perfectly.
>
> The question is: How do I set up things so it works with my internal 
> devices?  It seems that All I want to do is to leave the ipv4 setup as 
> I have it now and pass all ipv6 packets (discovery, etc.) from bge0 to 
> bge1 (and visa versa).  This way my ISP will provide ipv6 addresses to 
> those devices that ask for one.
Normal "procedure" for IPv6 (at least as proposed by the RIPE for its 
region) is to provide a /64 for the link between the ISP and the CPE 
(customer router) and a /56 or a /48 to the customer for her own network.

If you have a DSL connection, the information of your network is 
provided over PPPoE, but I don't know how it is done over an ethernet 
modem. Ask your ISP what is your private LAN.


I would not advice simply bridging all traffic between the two networks 
as -unless you have a firewall that can inspect bridged ipv6 traffic- 
you place all your ipv6 enabled devices unprotected on the internet.

In the logic of ipv6 (actually, the logic of the internet before it got 
"corrupted" by NAT :-) ), all hosts have a globally unique IP-address 
(so are "addressable") but that does not mean they should be "accessable".
Either you must then install a firewall on your router, or you must rely 
on the security in the device.

As for a lot of devices you have no idea of the software or 
network-firmware is to be trusted, it is adviced to use a firewall on 
the edge of your network that -by default- blocks all incoming traffic, 
except for return traffic of an outgoing stream or towards anything you 
explicitely accept.




> Or should I provide a "private" ipv6 address space for my LAN? This 
> doesn't seem to be in the spirit of ipv6, but it will provide me more 
> firewall control of traffic in and out of the network and provide 
> "static" addresses to my hosts.
You can, but then you would need to do ipv6 NAT on your router for them 
to access the network.


However, what you can do (and what I also do) it to provide both global 
ip-addresses and "Unique Local" (ipv6 speak for "private" addresses, 
e.g. fc00::/64) to your devices. That way, your devices then have both a 
kinds of address.
You can then set up firewall rules in your devices that you provide 
access to certain services only from fc00::// addresses, but not from an 
IP-address that comes from outside your own network.


Anycase, another reason to set up a RADVD server to hand out 
Unique-local addresses is to have an idea exactly what devices on your 
network actually are ipv6 enabled and which are not. Sniff your network 
from your router-box and look what devices do respond to the router 
advertisement messages! (normally, they should do duplicate address 
queries for their address to make sure nobody else if already using that 
address).


> Gary
Cheerio! Kr. Bonne.


From bfriesen at simple.dallas.tx.us  Wed Jun  6 23:10:06 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Wed, 6 Jun 2012 18:10:06 -0500 (CDT)
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
	<49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
Message-ID: <alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>

On Wed, 6 Jun 2012, Matt Clark wrote:

> Yes, it's interesting to consider the possible real world 
> performance.  ZIL writes, even by DDRDrive's stats, are very closely 
> clustered around the tail of the ZIL, with most seeks being to near 
> locations - it's certainly not going to seek more than 8 gig away. 
> So probably just leaving it at one big partition would be fine too.

The ZIL is not used for anything but to replay pending synchronous 
writes if the system unexpectedly reboots.  It is not used as a source 
of data while the system is running.  It is normally a write-only 
device.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From t12nslookup at gmail.com  Thu Jun  7 08:28:07 2012
From: t12nslookup at gmail.com (Jonathan Adams)
Date: Thu, 7 Jun 2012 09:28:07 +0100
Subject: [OpenIndiana-discuss] How to deal with IPV4/6 as a router
In-Reply-To: <4FCFE19D.3000505@skypro.be>
References: <4FCFAFAF.50801@genashor.com>
	<4FCFE19D.3000505@skypro.be>
Message-ID: <CAKr4wiQ6k=khXJsx+Pvfqq=Z4BpE8HrCdBmZrvK274+WiSmTaw@mail.gmail.com>

> On 06-06-12 21:29, Gary Gendel wrote:
>>
>> My ISP has turned on IPV6 and I can get as many addresses as I want.
>> ?However, some of my devices aren't ipv6 capable so I have to deal with a
>> mix of ipv4 and ipv6 addresses until these are retired.
>> I turned on ipv6 on bge0 and have both an ipv4 and ipv6 address. ?I also
>> can run the ipv6 test (test-ipv6.com) perfectly.
>>
>> The question is: How do I set up things so it works with my internal
>> devices? ?It seems that All I want to do is to leave the ipv4 setup as I
>> have it now and pass all ipv6 packets (discovery, etc.) from bge0 to bge1
>> (and visa versa). ?This way my ISP will provide ipv6 addresses to those
>> devices that ask for one.
>

We cheated ... we installed Proxies (delegate and squid) ... IPv6 on
the external IPv4 on the internal, everything else is "firewalled"
(because IPv4 cannot use IPv6 DNS) ...

Jon


From matt at mattclark.net  Thu Jun  7 13:17:07 2012
From: matt at mattclark.net (Matt Clark)
Date: Thu, 7 Jun 2012 14:17:07 +0100
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
	<49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
	<alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>
Message-ID: <F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>

That's true, but if you look at slides 24 & 25 of http://www.ddrdrive.com/zil_accelerator.pdf you'll see seek distributions for a SLOG device with the ZILs for five filesystems - although each ZIL is broadly append only (slides 21 and 22), there is still a lot of seeking going on.  Of course if you only had one active FS on a pool, the activity would be almost pure append, so sequential write performance would be the most important factor.  

On 7 Jun 2012, at 00:10, Bob Friesenhahn wrote:

> On Wed, 6 Jun 2012, Matt Clark wrote:
> 
>> Yes, it's interesting to consider the possible real world performance.  ZIL writes, even by DDRDrive's stats, are very closely clustered around the tail of the ZIL, with most seeks being to near locations - it's certainly not going to seek more than 8 gig away. So probably just leaving it at one big partition would be fine too.
> 
> The ZIL is not used for anything but to replay pending synchronous writes if the system unexpectedly reboots.  It is not used as a source of data while the system is running.  It is normally a write-only device.
> 




From bfriesen at simple.dallas.tx.us  Thu Jun  7 14:01:12 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Thu, 7 Jun 2012 09:01:12 -0500 (CDT)
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
	<49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
	<alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>
	<F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>
Message-ID: <alpine.GSO.2.01.1206070859200.21691@freddy.simplesystems.org>

On Thu, 7 Jun 2012, Matt Clark wrote:

> That's true, but if you look at slides 24 & 25 of 
> http://www.ddrdrive.com/zil_accelerator.pdf you'll see seek 
> distributions for a SLOG device with the ZILs for five filesystems - 
> although each ZIL is broadly append only (slides 21 and 22), there 
> is still a lot of seeking going on.  Of course if you only had one 
> active FS on a pool, the activity would be almost pure append, so 
> sequential write performance would be the most important factor.

Agreed.  I posted my response out of fear that someone might construe 
your statement as meaning that the ZIL is also used to satisfy reads.

Bob

>
> On 7 Jun 2012, at 00:10, Bob Friesenhahn wrote:
>
>> On Wed, 6 Jun 2012, Matt Clark wrote:
>>
>>> Yes, it's interesting to consider the possible real world performance.  ZIL writes, even by DDRDrive's stats, are very closely clustered around the tail of the ZIL, with most seeks being to near locations - it's certainly not going to seek more than 8 gig away. So probably just leaving it at one big partition would be fine too.
>>
>> The ZIL is not used for anything but to replay pending synchronous writes if the system unexpectedly reboots.  It is not used as a source of data while the system is running.  It is normally a write-only device.
>>
>
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>

-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From gary at genashor.com  Thu Jun  7 14:08:01 2012
From: gary at genashor.com (Gary Gendel)
Date: Thu, 07 Jun 2012 10:08:01 -0400
Subject: [OpenIndiana-discuss] DHCP server for IPV6
Message-ID: <4FD0B5C1.4050003@genashor.com>

Moving from IPV4 to IPV4/IPV6 on my home network is like peeling an 
onion, so I'm taking it one step at a time. :(

Currently I only see the old Solaris dhcp server for OI.  Can this 
handle ipv6? I couldn't find any examples but ipv6 support was 
superficially mentioned in some documents I came across.  Is there a 
howto document available?  If not, do we have a supported install 
package for ISC DHCP now that it's gone from SFE?

Regards,
Gary



From jcea at jcea.es  Thu Jun  7 14:12:09 2012
From: jcea at jcea.es (Jesus Cea)
Date: Thu, 07 Jun 2012 16:12:09 +0200
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
	<49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
	<alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>
	<F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>
Message-ID: <4FD0B6B9.5060209@jcea.es>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/12 15:17, Matt Clark wrote:
> That's true, but if you look at slides 24 & 25 of 
> http://www.ddrdrive.com/zil_accelerator.pdf you'll see seek 
> distributions for a SLOG device with the ZILs for five filesystems
> - although each ZIL is broadly append only (slides 21 and 22),
> there is still a lot of seeking going on.  Of course if you only
> had one active FS on a pool, the activity would be almost pure
> append, so sequential write performance would be the most important
> factor.

I always wondered WHY. What is the point of keeping separate ZILs (one
per dataset) when having a discrete LOG device.

Any idea?.

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBT9C2uJlgi5GaxT1NAQIljAP/clw3QgYXen+eiIttr0O4tpQRHopILGit
MdGo6oo9alwNwNBoXSNPNrEp7gMCtekilDG5xVZXg8Pmm09d/QLZMLqYjYippY+W
kqiE6qy5RllgLCgyry80tu772+eY96c3Sb5j8cm5sYIqc73or5LojvqC2gyYf4Z3
06Zfj+QBRqE=
=EuFo
-----END PGP SIGNATURE-----


From bfriesen at simple.dallas.tx.us  Thu Jun  7 15:06:51 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Thu, 7 Jun 2012 10:06:51 -0500 (CDT)
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <4FD0B6B9.5060209@jcea.es>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
	<49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
	<alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>
	<F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>
	<4FD0B6B9.5060209@jcea.es>
Message-ID: <alpine.GSO.2.01.1206071003430.13841@freddy.simplesystems.org>

On Thu, 7 Jun 2012, Jesus Cea wrote:
>
> I always wondered WHY. What is the point of keeping separate ZILs (one
> per dataset) when having a discrete LOG device.
>
> Any idea?.

The implementation is obviously very much simplified by using discrete 
contiguous ZILs.  Otherwise there is a lot more complexity and 
activity to track which I/Os have completed.  With the current 
approach, only one write is necessary to record that a batch of writes 
have been committed to the pool.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From jcea at jcea.es  Thu Jun  7 15:15:17 2012
From: jcea at jcea.es (Jesus Cea)
Date: Thu, 07 Jun 2012 17:15:17 +0200
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <alpine.GSO.2.01.1206071003430.13841@freddy.simplesystems.org>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
	<49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
	<alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>
	<F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>
	<4FD0B6B9.5060209@jcea.es>
	<alpine.GSO.2.01.1206071003430.13841@freddy.simplesystems.org>
Message-ID: <4FD0C585.6010702@jcea.es>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/12 17:06, Bob Friesenhahn wrote:
> On Thu, 7 Jun 2012, Jesus Cea wrote:
>> 
>> I always wondered WHY. What is the point of keeping separate ZILs
>> (one per dataset) when having a discrete LOG device.
>> 
>> Any idea?.
> 
> The implementation is obviously very much simplified by using
> discrete contiguous ZILs.  Otherwise there is a lot more complexity
> and activity to track which I/Os have completed.  With the current
> approach, only one write is necessary to record that a batch of
> writes have been committed to the pool.

Uhm.... and how is it done when you don't have a LOG device?. That is,
when the ZILs are in the harddisk?. There moving the disk arm should
be something to avoid/reduce.

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBT9DFhZlgi5GaxT1NAQJMlgP/ackJX71mAhehXut2SngyQMjyxVDXddde
e3R3RM9uk3dIPxmJi13OiNobleBbwcT90VTqeKaXUfOohGqwn9oxx+Ofnie1VMXw
bz6ecmXrXdKXxufu9MLKIBS9gAxhTjEaxYplTPWcn6FMdO/3aNvT1k2pRU4XhL+Q
5b3bld5v5wU=
=hPoh
-----END PGP SIGNATURE-----


From tac12 at wbic.cam.ac.uk  Thu Jun  7 15:17:04 2012
From: tac12 at wbic.cam.ac.uk (Adrian Carpenter)
Date: Thu, 7 Jun 2012 16:17:04 +0100
Subject: [OpenIndiana-discuss] COMSTAR qlt dropping link and 	resetting
In-Reply-To: <65AAF874-7BDD-4ABA-9D48-B7DD24BD60F6@wbic.cam.ac.uk>
References: <AB7A02BC-343D-498C-AB8E-53F27A98F1C9@wbic.cam.ac.uk>
	<8F607366E3C0F9499212649291E0BD64047977@MS1.laspina.ca>
	<65AAF874-7BDD-4ABA-9D48-B7DD24BD60F6@wbic.cam.ac.uk>
Message-ID: <7762C8F2-A136-4CCA-8AC0-42318C81754D@wbic.cam.ac.uk>

Well,   this has happened again,  exactly a week later,  same time too?.

So the SSD ZILS didnt do the trick.


I think I am going to turn off the ZFS auto snapshot service ?.

Jun  7 15:50:22 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt1,0 LINK UP, portid 20300, topology Fabric Pt-to-Pt,speed 8G
Jun  7 15:50:23 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt0,0 LINK UP, portid 10400, topology Fabric Pt-to-Pt,speed 8G


On 31 May 2012, at 17:37, Adrian Carpenter wrote:

> A quick update for those who might be following  this thread, I started to collect zilstats,  and what I have found is that about once every four days a transaction takes over half an hour:
> 
> TIME                        txg    N-Bytes  N-Bytes/s N-Max-Rate    B-Bytes  B-Bytes/s B-Max-Rate    ops  <=4kB 4-32kB >=32kB
> ..
> ..
> 2012 May 31 15:21:36     475232    2044232      60124     390888   16531456     486219    2985984    175      0      0    175
> 2012 May 31 15:22:39     475233    2762416      43847     293064   19734528     313246    2244608    266      0     10    256
> 2012 May 31 16:00:06     475234   29059896      12927    3198840  148652032      66126   12713984   1825      0    181   1644
> 2012 May 31 16:08:05     475235    2544016       5311     657384   13819904      28851    3575808    182      0      2    180
> 
> at 15:32  xen pool master  tried reseting the fibre channel HBAs,  however since the volume was still blocked I presume,  the pool master became very unhappy??
> 
> I then see the following in dmesg:
> 
> May 31 16:00:08 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt1,0 LINK UP, portid 20300, topology Fabric Pt-to-Pt,speed 8G
> May 31 16:00:09 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt0,0 LINK UP, portid 10400, topology Fabric Pt-to-Pt,speed 8G
> 
> I've just taken delivery of some SSDs and will add them as mirrored ZILlog devices,  hopefully this will help.
> 
> 
> 
> 
> 
> 
> On 21 May 2012, at 16:47, Mike La Spina wrote:
> 
>> Hi Adrian,
>> 
>> The SanBoxes?   -   Nexsan nothing in their logs
>> OK
>> 
>> Dmesg? :  
>>> May 17 17:33:47 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt1,0 
>>> LINK UP, portid 20300, topology Fabric Pt-to-Pt,speed 8G May 17 
>>> 17:33:48 hagrid fct: [ID 132490 kern.notice] NOTICE: qlt0,0 LINK UP, 
>>> portid 10400, topology Fabric Pt-to-Pt,speed 8G
>> 
>> Seeing a single LINKUP notice would normally only occur on init. I would
>> say it's just that, otherwise you would have a LINKDOWN before the
>> LINKUP, meaning an event on the fabric is your root issue.
>> 
>> Stmf service?  Nothing at all in the logs
>> OK
>> 
>> Are you running snapshots?    yes am running auto snapshot service,  in
>> addition I'm running a script (hourly) that snapshots the volume and
>> send it over ssh to another machine.
>> 
>> I suspect an issue here. The snapshot service runs on fixed time
>> intervals e.g. 15Min 1Hour 24Hhour 1Month if your also adding a snapshot
>> that runs hourly to do a ZFS send/rec they will overlap. The overlap may
>> cause an excessive blocking to stmf sbd access and result in a timeout
>> for the XEN host initiators. I suggest you use the auto based existing
>> hourly snaps and simply send them over to the remote host or file system
>> using a script @ 15 minutes after the hour.
>> 
>> Dedup?   
>> 
>> Off - OK
>> 
>> Compression?
>> 
>> Lzjb - OK
>> 
>> 
>> IRQ sharing?
>> echo ::interrupts | mdb -k
>> 
>> IRQ  Vect IPL Bus    Trg Type   CPU Share APIC/INT# ISR(s) 
>> 1    0x41 5   ISA    Edg Fixed  3   1     0x0/0x1   i8042_intr
>> 3    0xb1 12  ISA    Edg Fixed  39  1     0x0/0x3   asyintr
>> 4    0xb0 12  ISA    Edg Fixed  38  1     0x0/0x4   asyintr
>> 5    0xb2 12  ISA    Edg Fixed  40  1     0x0/0x5   asyintr
>> 9    0x80 9   PCI    Lvl Fixed  1   1     0x0/0x9   acpi_wrapper_isr
>> 12   0x42 5   ISA    Edg Fixed  4   1     0x0/0xc   i8042_intr
>> 16   0x83 9   PCI    Lvl Fixed  7   2     0x0/0x10  ohci_intr, ohci_intr
>> 17   0x81 9   PCI    Lvl Fixed  5   1     0x0/0x11  ehci_intr
>> 18   0x84 9   PCI    Lvl Fixed  8   3     0x0/0x12  ohci_intr,
>> ohci_intr, 
>> ohci_intr
>> 19   0x82 9   PCI    Lvl Fixed  6   1     0x0/0x13  ehci_intr
>> 22   0x40 5   PCI    Lvl Fixed  2   2     0x0/0x16  ata_intr, ata_intr
>> 88   0x43 5   PCI    Edg MSI-X  9   1     -         ql_isr_aif
>> 89   0x44 5   PCI    Edg MSI-X  10  1     -         ql_isr_aif
>> 90   0x45 5   PCI    Edg MSI-X  11  1     -         ql_isr_aif
>> 91   0x46 5   PCI    Edg MSI-X  12  1     -         ql_isr_aif
>> 92   0x60 6   PCI    Edg MSI-X  13  1     -         igb_intr_tx_other
>> 93   0x61 6   PCI    Edg MSI-X  14  1     -         igb_intr_rx
>> 94   0x62 6   PCI    Edg MSI-X  15  1     -         igb_intr_tx_other
>> 95   0x63 6   PCI    Edg MSI-X  16  1     -         igb_intr_rx
>> 96   0x64 6   PCI    Edg MSI-X  36  1     -         igb_intr_tx_other
>> 97   0x65 6   PCI    Edg MSI-X  37  1     -         igb_intr_rx
>> 98   0x66 6   PCI    Edg MSI-X  41  1     -         igb_intr_tx_other
>> 99   0x67 6   PCI    Edg MSI-X  42  1     -         igb_intr_rx
>> 100  0x68 6   PCI    Edg MSI-X  43  1     -         igb_intr_tx_other
>> 101  0x69 6   PCI    Edg MSI-X  44  1     -         igb_intr_rx
>> 102  0x6a 6   PCI    Edg MSI-X  45  1     -         igb_intr_tx_other
>> 103  0x6b 6   PCI    Edg MSI-X  46  1     -         igb_intr_rx
>> 104  0x47 5   PCI    Edg MSI    30  1     -         qlt_isr
>> 105  0x48 5   PCI    Edg MSI    31  1     -         qlt_isr
>> 160  0xa0 0          Edg IPI    all 0     -         poke_cpu
>> 208  0xd0 14         Edg IPI    all 1     -
>> kcpc_hw_overflow_intr
>> 209  0xd1 14         Edg IPI    all 1     -         cbe_fire
>> 210  0xd3 14         Edg IPI    all 1     -         cbe_fire
>> 240  0xe0 15         Edg IPI    all 1     -         xc_serv
>> 241  0xe1 15         Edg IPI    all 1     -         apic_error_intr
>> 
>> OK
>> 
>> 
>> Dr T Adrian Carpenter
>> Reader in Imaging Sciences
>> Wolfson Brain Imaging Centre
>> 
>> 
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>> 
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



From bfriesen at simple.dallas.tx.us  Thu Jun  7 15:32:19 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Thu, 7 Jun 2012 10:32:19 -0500 (CDT)
Subject: [OpenIndiana-discuss] What happens when a ZIL drive dies?
In-Reply-To: <4FD0C585.6010702@jcea.es>
References: <CACORSuZ6yFkCWKb2XOS33cc0hNxS+vFUdLRfwQdnBh1kYYwRow@mail.gmail.com>
	<8F607366E3C0F9499212649291E0BD640D46D8@MS1.laspina.ca>
	<F3D567BC-AD6A-4CD1-BB5F-3E4D72003978@mattclark.net>
	<BBA2FD0D-655C-4BC9-8EFF-1D04C88D7089@RichardElling.com>
	<49EF3C2F-41E8-4B6E-A2B8-C20E1E16BFD3@mattclark.net>
	<alpine.GSO.2.01.1206061808260.9843@freddy.simplesystems.org>
	<F797AB07-BF33-4142-BF03-E76C84F9C668@mattclark.net>
	<4FD0B6B9.5060209@jcea.es>
	<alpine.GSO.2.01.1206071003430.13841@freddy.simplesystems.org>
	<4FD0C585.6010702@jcea.es>
Message-ID: <alpine.GSO.2.01.1206071027410.13841@freddy.simplesystems.org>

On Thu, 7 Jun 2012, Jesus Cea wrote:
>>
>> The implementation is obviously very much simplified by using
>> discrete contiguous ZILs.  Otherwise there is a lot more complexity
>> and activity to track which I/Os have completed.  With the current
>> approach, only one write is necessary to record that a batch of
>> writes have been committed to the pool.
>
> Uhm.... and how is it done when you don't have a LOG device?. That is,
> when the ZILs are in the harddisk?. There moving the disk arm should
> be something to avoid/reduce.

As discussed at length previously on the zfs-discuss list, rotational 
latency is the real performance killer with ZIL on a hard disk. Even 
if the head does not move at all, it is necessary to wait for the hard 
disk to spin back around before the next write can be committed.

This list is really not the best place for zfs discussions.  There are 
already two existing lists for such discussions.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From dminer at opensolaris.org  Thu Jun  7 16:14:30 2012
From: dminer at opensolaris.org (Dave Miner)
Date: Thu, 07 Jun 2012 12:14:30 -0400
Subject: [OpenIndiana-discuss] DHCP server for IPV6
In-Reply-To: <4FD0B5C1.4050003@genashor.com>
References: <4FD0B5C1.4050003@genashor.com>
Message-ID: <4FD0D366.70003@opensolaris.org>

On 06/07/12 10:08, Gary Gendel wrote:
> Moving from IPV4 to IPV4/IPV6 on my home network is like peeling an
> onion, so I'm taking it one step at a time. :(
>
> Currently I only see the old Solaris dhcp server for OI.  Can this
> handle ipv6? I couldn't find any examples but ipv6 support was
> superficially mentioned in some documents I came across.  Is there a
> howto document available?  If not, do we have a supported install
> package for ISC DHCP now that it's gone from SFE?
>

No, the Solaris server does not support IPv6.  ISC is your best bet.

Dave


From carlsonj at workingcode.com  Thu Jun  7 16:17:00 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Thu, 07 Jun 2012 12:17:00 -0400
Subject: [OpenIndiana-discuss] DHCP server for IPV6
In-Reply-To: <4FD0B5C1.4050003@genashor.com>
References: <4FD0B5C1.4050003@genashor.com>
Message-ID: <4FD0D3FC.9090700@workingcode.com>

Gary Gendel wrote:
> Moving from IPV4 to IPV4/IPV6 on my home network is like peeling an
> onion, so I'm taking it one step at a time. :(
> 
> Currently I only see the old Solaris dhcp server for OI.  Can this
> handle ipv6?

No.  DHCPv6 is really a very different protocol from IPv4 DHCP.

(Are you really sure you need DHCPv6 ... ?)

> I couldn't find any examples but ipv6 support was
> superficially mentioned in some documents I came across.  Is there a
> howto document available?  If not, do we have a supported install
> package for ISC DHCP now that it's gone from SFE?

When I was designing and testing the DHCPv6 client in OpenSolaris, I
used the WIDE-DHCPv6 server for much of the ad-hoc testing.  The patches
I needed to make it work on OpenSolaris are still available:

http://www.workingcode.com/dhcpv6/wide-dhcpv6-20061016.small.gdiff

I haven't really kept up with it since 2006, so things may well have
changed.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From gary at genashor.com  Thu Jun  7 16:25:01 2012
From: gary at genashor.com (Gary Gendel)
Date: Thu, 07 Jun 2012 12:25:01 -0400
Subject: [OpenIndiana-discuss] DHCP server for IPV6
In-Reply-To: <4FD0D3FC.9090700@workingcode.com>
References: <4FD0B5C1.4050003@genashor.com> <4FD0D3FC.9090700@workingcode.com>
Message-ID: <4FD0D5DD.3090906@genashor.com>

On 6/7/12 12:17 PM, James Carlson wrote:
> Gary Gendel wrote:
>> Moving from IPV4 to IPV4/IPV6 on my home network is like peeling an
>> onion, so I'm taking it one step at a time. :(
>>
>> Currently I only see the old Solaris dhcp server for OI.  Can this
>> handle ipv6?
> No.  DHCPv6 is really a very different protocol from IPv4 DHCP.
>
> (Are you really sure you need DHCPv6 ... ?)
My ISP provides me with both an IPV4 and an IPV6 address. My OI box 
currently does IPV4 firewall/routing/NAT and provides DHCP service for 
my internal network.  I'm trying to replicate this in IPV6 in parallel 
with IPV4.
>
>> I couldn't find any examples but ipv6 support was
>> superficially mentioned in some documents I came across.  Is there a
>> howto document available?  If not, do we have a supported install
>> package for ISC DHCP now that it's gone from SFE?
> When I was designing and testing the DHCPv6 client in OpenSolaris, I
> used the WIDE-DHCPv6 server for much of the ad-hoc testing.  The patches
> I needed to make it work on OpenSolaris are still available:
>
> http://www.workingcode.com/dhcpv6/wide-dhcpv6-20061016.small.gdiff
>
> I haven't really kept up with it since 2006, so things may well have
> changed.
>
Thanks.  I probably should move to ISC DHCP since that's where Oracle is 
headed as well.  Should I get the sources and build from there or will 
it be available as a package in the near future?

Gary



From carlsonj at workingcode.com  Thu Jun  7 16:51:54 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Thu, 07 Jun 2012 12:51:54 -0400
Subject: [OpenIndiana-discuss] DHCP server for IPV6
In-Reply-To: <4FD0D5DD.3090906@genashor.com>
References: <4FD0B5C1.4050003@genashor.com> <4FD0D3FC.9090700@workingcode.com>
	<4FD0D5DD.3090906@genashor.com>
Message-ID: <4FD0DC2A.1040702@workingcode.com>

Gary Gendel wrote:
> On 6/7/12 12:17 PM, James Carlson wrote:
>> Gary Gendel wrote:
>>> Moving from IPV4 to IPV4/IPV6 on my home network is like peeling an
>>> onion, so I'm taking it one step at a time. :(
>>>
>>> Currently I only see the old Solaris dhcp server for OI.  Can this
>>> handle ipv6?
>> No.  DHCPv6 is really a very different protocol from IPv4 DHCP.
>>
>> (Are you really sure you need DHCPv6 ... ?)
> My ISP provides me with both an IPV4 and an IPV6 address. My OI box
> currently does IPV4 firewall/routing/NAT and provides DHCP service for
> my internal network.  I'm trying to replicate this in IPV6 in parallel
> with IPV4.

As I said, things are different with DHCPv6.

In particular, although you *can* distribute global addresses with
DHCPv6, I wouldn't necessarily recommend that you do so.  It's a little
annoying to administer, and doesn't really add a whole lot of value over
the standard choices of stateless autoconf (for most clients) or static
(for most servers).

Notably, prefixes (aka "netmasks") are not provided by DHCPv6, but
instead by RAs.  If a DHCPv6 server gives out an address, it's just a
bare address with no prefix length.  That makes it quite a bit different
from IPv4 DHCP, because it means that you have to make sure that the
advertised prefixes (in "the" router's RAs) always line up with the
address pools on the DHCPv6 server.  And there's really no mechanism to
do this other than the administrator's fingers and short-term memory.  ;-}

In a well-managed and large network, I can certainly see a good bit of
value in a DHCPv6 server to make sure that everyone has the right name
server addresses and such, and to centralize the management of "static"
IP addresses.  It's harder to explain why you'd need it on a home
network ...

>> http://www.workingcode.com/dhcpv6/wide-dhcpv6-20061016.small.gdiff
>>
>> I haven't really kept up with it since 2006, so things may well have
>> changed.
>>
> Thanks.  I probably should move to ISC DHCP since that's where Oracle is
> headed as well.  Should I get the sources and build from there or will
> it be available as a package in the near future?

As I said, I haven't kept up.  I've been using IPv6 on my home network
for many years (with a tunnel to Hurricane Electric), and haven't really
had a need yet to set up a DHCP server, so it's not a question I've
tried to answer.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From gary_mills at fastmail.fm  Thu Jun  7 17:43:11 2012
From: gary_mills at fastmail.fm (Gary Mills)
Date: Thu, 7 Jun 2012 12:43:11 -0500
Subject: [OpenIndiana-discuss] DHCP server for IPV6
In-Reply-To: <4FD0D5DD.3090906@genashor.com>
References: <4FD0B5C1.4050003@genashor.com> <4FD0D3FC.9090700@workingcode.com>
	<4FD0D5DD.3090906@genashor.com>
Message-ID: <20120607174311.GA13720@mail.messagingengine.com>

On Thu, Jun 07, 2012 at 12:25:01PM -0400, Gary Gendel wrote:
> 
> Thanks.  I probably should move to ISC DHCP since that's where
> Oracle is headed as well.  Should I get the sources and build from
> there or will it be available as a package in the near future?

Yes, both the Sun and ISC DHCP servers are included with Oracle
Solaris 11.  You have to choose one.  OI has something in the works
for the ISC DHCP server.  It's visible at:

    https://hg.openindiana.org/upstream/oracle/userland-gate/file/tip/components

I don't know if it's been made into a package for OI yet.

-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-


From jimklimov at cos.ru  Thu Jun  7 18:32:02 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Thu, 07 Jun 2012 22:32:02 +0400
Subject: [OpenIndiana-discuss] DHCP auto-configuration for local zones and
	sysidcfg
Message-ID: <4FD0F3A2.8060907@cos.ru>

Hello all,

   I am trying to get automatic networking provisioning for local
zones working, ultimately in order to simplify rapid deployments
of testbeds and per-bug build environments.

   In the process I found a few nits, and wondered if I am doing
something wrong or things are according to current design and
that can be revised, perhaps? So, here goes:

1) In the SMF framework, local zones can not use netstrategy=dhcp
    by the definition in /lib/svc/share/smf_include.sh:
---
#   The network boot strategy for a zone is always "none".
#
smf_netstrategy () {
         if smf_is_nonglobalzone; then
                 _INIT_NET_STRATEGY="none" export _INIT_NET_STRATEGY
                 return 0
         fi
...
---

    This does make sense for shared-IP zones, but for exclusive-IP
    ones which can be DHCP clients indeed, this seems wrong (and
    further on forbids configuration of DNS resolver (resolv.conf,
    nsswitch.conf) from DHCP data via svc:/network/service:default
    method script /lib/svc/method/net-svc.

    Also, I did some limited testing:
    * on SXCE the "/sbin/netstrategy" returns "zfs none none"
      for both shared and exclusive-IP zones (all with static
      IP configuration),
    * on OI (oi_151a3) the exclusive-IP zone which is a DHCP
      client does return "zfs vnic127101 dhcp" properly,
    * while OI local zones with static IP config also return
      "zfs none none".

    Is there any known rationale for the snippet above from
    smf_netstrategy() - or can it be just removed? What are
    the possible negative consequences if this check is dropped?
    Is there a simple reliable way to check the zone's ip-type,
    or why don't we trust /sbin/netstrategy output?


2) In /etc/sysidcfg templates we can set name_service to be
    DNS, LDAP, NIS or NONE. Would it be inappropriate to define
    a new type and set it to "DHCP" (and then fetch name-service
    info from DHCP)?


3) Some networking clients might want the changes to their
    DNS/nsswitch config files from a dynamic wizard, others
    might not. The policy might even differ per-local zone.
    For example, there is "fear" of scripts which might
    corrupt manually crafted settings for files+dns+ldap
    host lookups, etc.

    So far I have not seen any configurable switch that would
    *request* or *forbid* changes to the /etc/resolv.conf and
    /etc/nsswitch.conf files using data from DHCP.
    Does such a switch exist?
    Is it reasonable to add one (if not)?

    As an option, might it make sense to integrate this solution
    (an SMF service to combine user-preferred and DHCP-dynamic
    resolver options, which can then be enabled or disabled on
    a particular zone)?

 
http://thestaticvoid.com/post/2011/01/11/persistent-search-domains-with-nwam-and-dhcp/


Thanks,
//Jim Klimov

PS: A draft Wiki page is cooking here so far:
http://wiki.illumos.org/display/~jimklimov/Using+host-only+networking+to+get+from+build+zones+and+test+VMs+to+the+Internet




From rich at redstar-assoc.com  Thu Jun  7 18:38:03 2012
From: rich at redstar-assoc.com (Rich Reynolds)
Date: Thu, 07 Jun 2012 12:38:03 -0600
Subject: [OpenIndiana-discuss] Fwd: Re: Unofficial Solaris 11/x86 3.4 build
Message-ID: <4FD0F50B.3010106@redstar-assoc.com>

FYI ...

rich

-------- Original Message --------
Subject: Re: Unofficial Solaris 11/x86 3.4 build
Date: Tue, 05 Jun 2012 00:15:46 +0200
From: Raphael Bircher <rbircher at apache.org>
Reply-To: ooo-dev at incubator.apache.org
To: ooo-dev at incubator.apache.org

Am 04.06.12 23:55, schrieb Nicolas Christener:
> Hi all :)
>
> After getting the OpenSolaris/SPARC build done, we could finally take a
> look at some of the Solaris11/x86 build-issues.
>
> We managed to produce a working build without any bad hacks and made
> this package (it also has mozilla/nss support):
> http://adfinis-sygroup.ch/aoo-solaris-x86
>
> This is an unofficial build we provide "as is" and without any warranty
> (you should not use this for production environments and for testing
> purpose only).
>
> This build is "smoke tested" and should work in general.
>
> We had to make some minor changes in our build script, but in general we
> used the same settings (--disable-systray and --with-system-libxml are
> the only real differences) as for the OpenSolaris/SPARC builds.
>
> Besides those minor changes we built this version using a Solaris 11 vm.
> We're not sure yet whether this build will also run on an OpenSolaris
> machine. We're going to try this as soon as possible.
Just tested on OpenIndiana and posted a nice Screenshot on Facebook

http://www.facebook.com/photo.php?fbid=379323098793240&set=a.379322975459919.85131.185963401462545&type=1&theater

Greetings Raphael



From jimklimov at cos.ru  Thu Jun  7 18:58:35 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Thu, 07 Jun 2012 22:58:35 +0400
Subject: [OpenIndiana-discuss] DHCP auto-configuration for local zones
 and sysidcfg
In-Reply-To: <4FD0F3A2.8060907@cos.ru>
References: <4FD0F3A2.8060907@cos.ru>
Message-ID: <4FD0F9DB.60409@cos.ru>

2012-06-07 22:32, Jim Klimov ???????:
> Hello all,
>
> I am trying to get automatic networking provisioning for local
> zones working, ultimately in order to simplify rapid deployments
> of testbeds and per-bug build environments.
>
> In the process I found a few nits, and wondered if I am doing
> something wrong or things are according to current design and
> that can be revised, perhaps? So, here goes:

A few more:

4) If I pre-configure the local zone with /etc/sysidcfg
    (created between installation and first boot), and use
      network_interface=PRIMARY {dhcp protocol_ipv6=no}
    then the interface is first attempting "auto-revarp"
    configuration and sends out RARP packets (not served
    by Sun DHCP) and then sends out DHCPREQUESTs as asked.

    If I don't provide the /etc/sysidcfg file, RARP is
    still attempted, times out and "in.rdisc" failure is
    logged, then the wizard asks for static IP settings.

    I wonder if it is possible to either tie in the RARP
    replies to Sun DHCP server, or to have the new client
    attempt DHCP by default - since it does use RARP?..
    (perhaps with a smaller timeout than 300sec waiting
    with explicitly requested DHCP setup).

5) Is it possible to make a hands-free installation
    (without supplying a /etc/sysidcfg manually) perhaps
    distributing all these settings via DHCP (in private
    options and/or as an URL to fetch the file via HTTP
    or TFTP) - *if* DHCP and/or the DNS resolution setup
    would now be also requested by default? ;)
    I am thinking towards Sun Ray DTU auto-configuration
    with a mix of DHCP and DNS settings for predefined
    names (i.e. sunray-server-config.yourdomain.com).

//Jim Klimov


From jimklimov at cos.ru  Fri Jun  8 00:11:40 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Fri, 08 Jun 2012 04:11:40 +0400
Subject: [OpenIndiana-discuss] [developer] review 2837 - remove
 print/lp* from gate and use CUPS from userland
In-Reply-To: <5B1B2AA8-6744-41FC-984B-B204D91C3165@damore.org>
References: <073a3fe5a1080de6259cda3fa2d9d87d@xylab.cz>
	<CBF55763.1A600%ikozhukhov@gmail.com>
	<CALnxO57_ouP3BVm_CUA_bF0FgH4Xbknefjyiz8iXZuYaxudXMQ@mail.gmail.com>
	<1339014475.1260.8.camel@xylabone>
	<D00F407F-3E90-4865-ACC5-EF17F67B86F5@damore.org>
	<4be2af7568fe50d388a53356aae1f4d1@xylab.cz>
	<5B1B2AA8-6744-41FC-984B-B204D91C3165@damore.org>
Message-ID: <4FD1433C.8090709@cos.ru>

A couple of observations follow...

2012-06-07 11:42, Garrett D'Amore wrote:
> I don't care either way about the "bullet point value" of those items
> unless someone else cares enough to contribute actual resources to the
> project. As far as I know, there is no commercial interest in either of
> these (sort of like SPARC, actually), except that some commercial
> companies want to be able to use illumos as a free alternative to other
> expensive commercial offerings. In theory having such consumers may
> bring mindshare and intangible value, but if it takes a lot of extra
> work on our part, then I want more than just intangibles. A bullet point
> on a power point slide that has nothing to do with actual purchasing
> decisions is totally and utterly meaningless to me.

I know that some time has passed and we all know more than we did
before (i.e. about the need for commercial interest to do some
harder tasks, such as, perhaps, is the SPARC support, and setting
realistic reachable priorities); still, it is interesting how the
points of view evolve :)

----

http://blog.davekoelmeyer.co.nz/2011/06/17/illumos-panel-discussion-some-highlights/

?Solaris 11 is mutating into what some people would call the bootloader 
for the Oracle database. Oracle?s priorities are clearly way different 
from what Sun?s were?I would not be entirely unsurprised if it turns 
that out you can?t actually license Solaris 11 separately?I would be 
actually very surprised if there?s ever a Solaris 12.? ? Garrett D?Amore


?There?s a huge installed base of Sun hardware out there in datacenters 
around the world, billions of dollars worth of equipment, and Oracle has 
basically given it the finger.? ? Garrett D?Amore

?Oracle has removed sun4u from Solaris 11. So there is no sun4u support 
in Solaris 11, which means that there is this huge amount of hardware, 
this installed base (anything earlier than a year or two ago) that can?t 
run, will not run Solaris 11 at all. And that?s a huge Illumos 
opportunity.? ? Bryan Cantrill and Adam Leventhal

---

2012-05-27 4:15, Alasdair Lumsden wrote:
 > I'm sorry to have to tell you this, but SVR4 and SPARC are both dead.
It's as simple as that. Get over it and stop bothering the rest of us.
 > The only SPARC boxes you can buy on eBay are relics, and I'd wager
my Samsung Galaxy S2 phone with it's dual core 1GHz ARM chip can 
outperform all of them.

Does the tab have LOM or RSC installed? ;)

 > Power is now incredibly expensive, and the economics of running old 
equipment make no sense what so ever. If you buy an old SPARC box on 
ebay for $500, it's going to cost you more than that per year to run it.
 > So at this point, as far as I'm concerned the people who want SPARC 
are hobbyists interested in running old equipment, much like how I like 
to get out my Commodore 64 and BBC Micro, or they're lunatics with no 
grip on reality.

Some countries generate the power, and it costs less there.
So, at least, keeping the existing old boxes running for years
may be not a big problem, especially in the non-commercial sector
which gets such things for granted (edu, gov). Some boxes are
pushed off the first-class countries or corporations into
third-class ones for free (as economical help and to sign off
some taxes). Our uni got a Sun E10K that way recently, and they
still think what to do with 108(? IIRC) 300MHz CPUs in a box -
perhaps they'll make a clustering/HPC lab for students...

And, as other experts presented above, around the globe there
are many already-deployed such boxes, which are engineered
well and might run like forever ;)

But, true, the lack of enthusiasm and help (and money) from
these boxes owners may be a showstopper, indeed.

//Jim


From jimklimov at cos.ru  Fri Jun  8 01:39:06 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Fri, 08 Jun 2012 05:39:06 +0400
Subject: [OpenIndiana-discuss] DHCP auto-configuration for local zones
 and sysidcfg
In-Reply-To: <4FD0F9DB.60409@cos.ru>
References: <4FD0F3A2.8060907@cos.ru> <4FD0F9DB.60409@cos.ru>
Message-ID: <4FD157BA.7020908@cos.ru>

It is nice talking to oneself, we make a smart and interesting
couple ;) (I do hope some experts would add to this thread)

Apparently, the "quick fix" in smf_netstrategy which just fully
removes the special handling for local zones is a flawed approach.
There are other scripts which seemingly expect local zones to have
$_INIT_NET_STRATEGY==none so this is a case for more careful
revision.

In particular, with the workaround in place, it seems that the
`zonename` or `uname -n` are no longer consulted to construct
the /etc/nodename file (or provide the value on the fly if the
file is absent/empty) to ultimately set the hostname, so the
zone came up as "unknown" on at least one test... For details
see /lib/svc/method/identity-node :)

Adding some code to the "dhcp" case seems to help (only the
first line was originally present):
---
# For non-global zones, fall back to the `uname -n` value provided by the
# kernel if /etc/nodename does not exist, as is expected on an initial boot.
#

smf_netstrategy

case "$_INIT_NET_STRATEGY" in
         "dhcp") hostname=`/sbin/dhcpinfo Hostname`
                 if [ -z "$hostname" ]; then
                         if smf_is_globalzone; then
                                 hostname=`/sbin/hostconfig -h -p 
bootparams`
                         else
                                 hostname=`/sbin/zonename`
                         fi
                 fi ;;
---

Use of "uname -n" as proposed by the script's comments seems
pointless, but maybe that's because I'm testing after the name
"unknown" has got assigned during zone startup:

root at unknown:~# hostname
unknown
root at unknown:~# zonename
build-ss12sun
root at unknown:~# uname -n
unknown

An arguable bonus is to add these lines someplace there:
                 [ ! -z "$hostname" -a ! -s /etc/nodename ] && \
                         echo "$hostname" > /etc/nodename &&
                         /usr/bin/chmod 644 /etc/nodename
If we discovered a "$hostname" and the "/etc/nodename" was
empty or nonexistent, seed that file with the name we found.
Q: Should this be done at all, and in the identity-node SMF
method script in particular?

On a side note, I found that `zonename -t` should return the
ip-type (shared or exclusive) which can help me make a more
"educated guess" crafting the workaround...

Good night,
//Jim Klimov


From paolo.marcheschi at ftgm.it  Fri Jun  8 16:46:50 2012
From: paolo.marcheschi at ftgm.it (Paolo Marcheschi)
Date: Fri, 08 Jun 2012 18:46:50 +0200
Subject: [OpenIndiana-discuss] Firefox and thunderbird 13 for openindiana
Message-ID: <4FD22C7A.6040705@ftgm.it>

Hi
here they are :

http://releases.mozilla.org/pub/mozilla.org/firefox/releases/13.0/contrib/solaris_pkgadd/
http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/13.0/contrib/solaris_pkgadd/

get the opensolaris pkgadd one and  bunzip2 it.
after as superuser :

pkgrm SFWfirefox

pkgadd -d ./firefox-13.0.en-US.opensolaris-i386-pkg

the same for thunderbird:

pkgrm SFWthunderbird

pkgadd -d ./thunderbird-13.0.en-US.opensolaris-i386-pkg

I hope this helps someone.


Ciao

Paolo



From tokaji.attila at gmx.com  Fri Jun  8 22:27:51 2012
From: tokaji.attila at gmx.com (Attila Tokaji)
Date: Sat, 09 Jun 2012 00:27:51 +0200
Subject: [OpenIndiana-discuss] Source of Oracle Solaris 11 11/11
Message-ID: <20120608222751.270970@gmx.com>

Hi All,

 Did you know that the Oracle distributed the source of the Solaris 11? You can find it :

http://www.oracle.com/technetwork/opensource/systems-solaris-1562786.html 

 Best regards,

 Attila

From vab at bb-c.de  Fri Jun  8 22:40:38 2012
From: vab at bb-c.de (Volker A. Brandt)
Date: Sat, 9 Jun 2012 00:40:38 +0200
Subject: [OpenIndiana-discuss] Source of Oracle Solaris 11 11/11
In-Reply-To: <20120608222751.270970@gmx.com>
References: <20120608222751.270970@gmx.com>
Message-ID: <20434.32614.547883.387045@gargle.gargle.HOWL>

Dear Attila:


>  Did you know that the Oracle distributed the source of the Solaris
> 11? You can find it :
>
> http://www.oracle.com/technetwork/opensource/systems-solaris-1562786.html

This is a very common misunderstanding.  This is not the source
of Solaris 11, but of the "Open Source Software Components" contained
in Oracle Solaris.  So it is only a very small part of the sources.

All the rest of the Solaris 11 source is not available in the current
version.


Regards -- Volker
-- 
------------------------------------------------------------------------
Volker A. Brandt               Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH                   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANY            Email: vab at bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513              Schuhgr??e: 46
Gesch?ftsf?hrer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"


From james.c.mcpherson at gmail.com  Fri Jun  8 22:41:28 2012
From: james.c.mcpherson at gmail.com (James C. McPherson)
Date: Sat, 09 Jun 2012 08:41:28 +1000
Subject: [OpenIndiana-discuss] Source of Oracle Solaris 11 11/11
In-Reply-To: <20120608222751.270970@gmx.com>
References: <20120608222751.270970@gmx.com>
Message-ID: <4FD27F98.7070802@gmail.com>

On  9/06/12 08:27 AM, Attila Tokaji wrote:
> Hi All,
>
>   Did you know that the Oracle distributed the source of the Solaris 11? You can find it :
>
> http://www.oracle.com/technetwork/opensource/systems-solaris-1562786.html

That's the source for the Open components which went into
Oracle Solaris 11 11/11. It is _not_ the same as "the whole
source" for Solaris, which you can ascertain by reading the
comment above the links on that page:

=====
The source code for open source software and firmware components, as
licensed under the applicable open source licenses, may be found by
following the links below.
=====

  
James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
               http://www.jmcp.homeunix.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson



From tokaji.attila at gmx.com  Sat Jun  9 05:02:05 2012
From: tokaji.attila at gmx.com (Attila Tokaji)
Date: Sat, 09 Jun 2012 07:02:05 +0200
Subject: [OpenIndiana-discuss] Source of Oracle Solaris 11 11/11
Message-ID: <20120609050206.270980@gmx.com>

Ok, I see. Sorry, I was inattentive. ;-)
 I was glad when I read the words "open source solaris 11" in one sentence.
----- Original Message -----
From: James C. McPherson
Sent: 06/09/12 12:41 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Source of Oracle Solaris 11 11/11

 On 9/06/12 08:27 AM, Attila Tokaji wrote: > Hi All, > > Did you know that the Oracle distributed the source of the Solaris 11? You can find it : > > http://www.oracle.com/technetwork/opensource/systems-solaris-1562786.html That's the source for the Open components which went into Oracle Solaris 11 11/11. It is _not_ the same as "the whole source" for Solaris, which you can ascertain by reading the comment above the links on that page: ===== The source code for open source software and firmware components, as licensed under the applicable open source licenses, may be found by following the links below. ===== James C. McPherson -- Solaris kernel software engineer, system admin and troubleshooter http://www.jmcp.homeunix.com/blog Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson

From jay at frelled.us  Sat Jun  9 20:41:58 2012
From: jay at frelled.us (Jay Heyl)
Date: Sat, 9 Jun 2012 13:41:58 -0700
Subject: [OpenIndiana-discuss] Drive compatibility
Message-ID: <CAACKFo=1Qa2b2UR7A3cOeGXq7xvQTwZCk-17CjdVCkrscEw4pA@mail.gmail.com>

I had a bit of a hiccup last week with my zfs pool. It's a ten-drive raidz2
vdev. All the drives are Samsung F4s, though of two slightly different
models. Two of the drives showed up one morning as "degraded". In somewhat
of a panic I rushed out and bought a couple Seagate drives as replacements.
When I tried to do the actual replace operation zfs told me the new drive
was not compatible with the existing drive array. I don't recall the
wording of the error message.

I have since learned what I thought was complete disaster was zfs being
extremely cautious. I ended up clearing the errors and two subsequent
scrubs have turned up no errors.

Just in case, I bought some more Samsung F4 drives. Last night I installed
one of them as a spare drive. No problem. Then, since it was still mounted,
I designated the Seagate drive as a spare. Again, no problem. Since I know
it doesn't like the Seagate drive for use with this array, this tells me
mounting a drive as a spare doesn't check to see if the drive will really
work as a spare.

Is there any way short of actually doing a zpool replace to determine if a
drive will be truly compatible with an existing vdev?

From ppkomatsu at gmail.com  Sun Jun 10 03:46:50 2012
From: ppkomatsu at gmail.com (Pepe Komatsu)
Date: Sat, 9 Jun 2012 22:46:50 -0500
Subject: [OpenIndiana-discuss] Firefox and thunderbird 13 for openindiana
In-Reply-To: <4FD22C7A.6040705@ftgm.it>
References: <4FD22C7A.6040705@ftgm.it>
Message-ID: <CAK8SrzoMmB2wgsXRK2JKzjaWNMow7d16o_OiMdncijnzv9OcoQ@mail.gmail.com>

This is a very big news, finally OI is ready for my desktop...

Firefox 13 + OO 3.4 + Blender + Gimp

I'm a lucky man.... :-)

2012/6/8 Paolo Marcheschi <paolo.marcheschi at ftgm.it>

> Hi
> here they are :
>
> http://releases.mozilla.org/**pub/mozilla.org/firefox/**
> releases/13.0/contrib/solaris_**pkgadd/<http://releases.mozilla.org/pub/mozilla.org/firefox/releases/13.0/contrib/solaris_pkgadd/>
> http://releases.mozilla.org/**pub/mozilla.org/thunderbird/**
> releases/13.0/contrib/solaris_**pkgadd/<http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/13.0/contrib/solaris_pkgadd/>
>
> get the opensolaris pkgadd one and  bunzip2 it.
> after as superuser :
>
> pkgrm SFWfirefox
>
> pkgadd -d ./firefox-13.0.en-US.**opensolaris-i386-pkg
>
> the same for thunderbird:
>
> pkgrm SFWthunderbird
>
> pkgadd -d ./thunderbird-13.0.en-US.**opensolaris-i386-pkg
>
> I hope this helps someone.
>
>
> Ciao
>
> Paolo
>
>
> ______________________________**_________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss at openindiana.org>
> http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
>



-- 
Ricardo Komatsu
IT Consultant

From michelle at msknight.com  Sun Jun 10 09:35:21 2012
From: michelle at msknight.com (michelle)
Date: Sun, 10 Jun 2012 10:35:21 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
Message-ID: <4FD46A59.5030106@msknight.com>

Hi Folks,

I'm not having much luck and if someone can help with solid suggestions 
before I start poking around, it could save me stuffing up the machine.

Firstly, I think that the graphics is having a problem with my TV, so if 
someone can tell me how to stop the system from wanting to boot in to 
the GUI, that would be a real help.

Second, I'm replacing 2tb drives with 3tb drives.
I'm runnning...

                       OpenIndiana Development oi_151a X86
         Copyright 2010 Oracle and/or its affiliates. All rights reserved.
                         Use is subject to license terms.
                            Assembled 01 September 2011

I'm reluctant to upgrade because the system doesn't seem to be listening 
to USB keyboards on the selection screen.

On attaching the 3tb I get...

Jun 10 10:08:07 jaguar genunix: [ID 936769 kern.info] devinfo0 is 
/pseudo/devinfo at 0
Jun 10 10:08:07 jaguar sata: [ID 801593 kern.warning] WARNING: 
/pci at 0,0/pci1458,b005 at 1f,2:
Jun 10 10:08:07 jaguar  SATA device detected at port 2
Jun 10 10:08:07 jaguar sata: [ID 663010 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2 :
Jun 10 10:08:07 jaguar sata: [ID 761595 kern.info]      SATA disk device 
at port 2
Jun 10 10:08:07 jaguar sata: [ID 846691 kern.info]      model WDC 
WD30EZRX-00MMMB0
Jun 10 10:08:07 jaguar sata: [ID 693010 kern.info]      firmware 80.00A80
Jun 10 10:08:07 jaguar sata: [ID 163988 kern.info]      serial 
number      WD-WMAWZ0278326
Jun 10 10:08:07 jaguar sata: [ID 594940 kern.info]      supported features:
Jun 10 10:08:07 jaguar sata: [ID 981177 kern.info]       48-bit LBA, 
DMA, Native Command Queueing, SMART, SMART self-test
Jun 10 10:08:07 jaguar sata: [ID 643337 kern.info]      SATA Gen2 
signaling speed (3.0Gbps)
Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      Supported queue 
depth 32
Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      capacity = 
5860533168 sectors
Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:35 jaguar  timeout: abort request, target=0 lun=0
Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:35 jaguar  timeout: abort device, target=0 lun=0
Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:35 jaguar  timeout: reset target, target=0 lun=0
Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:35 jaguar  timeout: reset bus, target=0 lun=0
Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:58 jaguar  timeout: abort request, target=0 lun=0
Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:58 jaguar  timeout: abort device, target=0 lun=0
Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:58 jaguar  timeout: reset target, target=0 lun=0
Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:08:58 jaguar  timeout: reset bus, target=0 lun=0
Jun 10 10:09:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:09:58 jaguar  timeout: early timeout, target=0 lun=0
Jun 10 10:09:58 jaguar genunix: [ID 859416 kern.info] 
ghd_timer_newstate: HBA reset failed hba 0xffffff01ce0f3900 gcmdp 0x0 
gtgtp 0xffffff01d0598100
Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:10:58 jaguar  timeout: abort request, target=0 lun=0
Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:10:58 jaguar  timeout: abort device, target=0 lun=0
Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:10:58 jaguar  timeout: reset target, target=0 lun=0
Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING: 
/pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
Jun 10 10:10:58 jaguar  timeout: reset bus, target=0 lun=0

I know the drive works as I've been testing it in another machine, but 
the moment I plug it in, the system has problems.

Any ideas please?

Michelle.


From michelle at msknight.com  Sun Jun 10 10:07:23 2012
From: michelle at msknight.com (michelle)
Date: Sun, 10 Jun 2012 11:07:23 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD46A59.5030106@msknight.com>
References: <4FD46A59.5030106@msknight.com>
Message-ID: <4FD471DB.3040704@msknight.com>

I've bitten the bullet and have started an upgrade process.

The troubled graphics card has been removed and I'm currently using the 
on-board graphics which, as OI starts, is fine up until launching GNOME 
and then no display, but I can ssh in to the box.

My efforts on Google are so far coming to nothing.

When I've sorted the graphic/boot stability out, I've still got the hard 
drive issue to resolve.



From michelle at msknight.com  Sun Jun 10 10:31:05 2012
From: michelle at msknight.com (michelle)
Date: Sun, 10 Jun 2012 11:31:05 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD471DB.3040704@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
Message-ID: <4FD47769.1050703@msknight.com>

I'm getting somewhere, but I might have a RAM corruption issue.

In the mean time, trying to replace a 2tb drive with a 3tb drive in a 
three drive RaidZ, gives ...

cannot replace c2t5d0 with c2t2d0: devices have different sector alignment


How do I get around this please? I want to remain with three drives in 
the set.

Should I remove c2t5d0 and then add c2t2d0?

Any help gratefully appreciated because I don't think I can sort this 
one out.


From michelle at msknight.com  Sun Jun 10 11:37:16 2012
From: michelle at msknight.com (michelle)
Date: Sun, 10 Jun 2012 12:37:16 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD47769.1050703@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com>
Message-ID: <4FD486EC.4000405@msknight.com>

OK - so far...

System RAM passes Memtest86 v4.20

That leaves me with two problems...

1) Disable Gnome from starting, or remove it completely.

2) How to get around the sector alignment problem.

I have a very ugly feeling that the only way is going to be to destroy 
the set and start again, as everything I've tried so far hasn't worked.

Any help on these two would be gratefully appreciated.

Michelle.


From james.c.mcpherson at gmail.com  Sun Jun 10 11:48:48 2012
From: james.c.mcpherson at gmail.com (James C. McPherson)
Date: Sun, 10 Jun 2012 21:48:48 +1000
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD486EC.4000405@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
Message-ID: <4FD489A0.8060200@gmail.com>

On 10/06/12 09:37 PM, michelle wrote:
> OK - so far...
>
> System RAM passes Memtest86 v4.20
>
> That leaves me with two problems...
>
> 1) Disable Gnome from starting, or remove it completely.

svcadm disable gnome
is a good place to start.



> 2) How to get around the sector alignment problem.

I can't help with this one, sorry.




James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
               http://www.jmcp.homeunix.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson



From jimklimov at cos.ru  Sun Jun 10 11:53:24 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sun, 10 Jun 2012 15:53:24 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD47769.1050703@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com>
Message-ID: <4FD48AB4.2080606@cos.ru>

2012-06-10 14:31, michelle wrote:
 > That leaves me with two problems...
 >
 > 1) Disable Gnome from starting, or remove it completely.

As for GNOME, try "svcadm disable gdm". I'd think there may  be some
video driver problems, but just about any card should work as a VESA
or SVGA driver. Still, I also only use remote SSH so can't help much ;)

> In the mean time, trying to replace a 2tb drive with a 3tb drive in a
> three drive RaidZ, gives ...
>
> cannot replace c2t5d0 with c2t2d0: devices have different sector alignment
>
>
> How do I get around this please? I want to remain with three drives in
> the set.

I have not encountered this error directly, but it would seem that
your older drives may have had native 512 byte sectors, and new ones
use 4KB sectors. At least, this is highly likely.

For the sake of data integrity, there is nothing you can safely do
to replace such older drives with such newer ones, and would be
better off creating the new raidz set of new drives from scartch,
and zfs send|zfs recv your data into it.

Also it is possible that your partitions on a 4KB-sectored drive
are not aligned at multiples of 8 512-byte blocks (ex-sectors).
I.e. for older releases a 34-sector offset was typical for the
first partition, while newer releases use 256*512b offsets.
MAYBE the system complains about that; use parted to check your
offsets, i.e.:

# parted /dev/rdsk/c4t1d0p0 uni s pri
Model: Generic Ide (ide)
Disk /dev/rdsk/c4t1d0p0: 156301488s
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start       End         Size       Type      File system  Flags
  1      16065s      75487103s   75471039s  primary   solaris      boot
  3      75487104s   108517247s  33030144s  primary
  4      108517248s  156301487s  47784240s  extended               lba
  5      108519264s  112648031s  4128768s   logical
  6      112664160s  116792927s  4128768s   logical
  7      116809056s  156301487s  39492432s  logical

# parted /dev/rdsk/c7t1d0p0 uni s pri
Model: Generic Ide (ide)
Disk /dev/rdsk/c7t1d0p0: 3907029168s
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start        End          Size         File system  Name  Flags
  1      256s         3907012750s  3907012495s               zfs
  9      3907012751s  3907029134s  16384s

The second disk lies, it is 4KB native ;)



>
> Should I remove c2t5d0 and then add c2t2d0?

ZFS would likely not let you programmatically reduce the raidz
set to an unprotected one, but you could yank the drive physically.

Still, this is not what you'd likely want to do.


HTH,
//Jim


From michelle at msknight.com  Sun Jun 10 12:30:20 2012
From: michelle at msknight.com (michelle)
Date: Sun, 10 Jun 2012 13:30:20 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD486EC.4000405@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
Message-ID: <4FD4935C.7020502@msknight.com>

Hi Jim,

Thanks for the gdm, I just couldn't work out what the service name was. 
I've disabled that.

I did try yanking the drive, with kindness, of course, but still got the 
same error message; zfs is obviously smarter than me

At the moment, I'm backing up the drives so I had to revert the set to 
the way it was, but one of the original drives reports...

mich at jaguar:~# parted /dev/rdsk/c2t3d0p0 uni s pri
Model: Generic Ide (ide)
Disk /dev/rdsk/c2t3d0p0: 3907029168s
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start        End          Size         File system  Name  Flags
  1      256s         3907012750s  3907012495s               zfs
  9      3907012751s  3907029134s  16384s

To test the 3tb drive in a Linux system, before I trusted it to the 
server, I did create a partition on it; however my understanding is that 
when I give a zfs command at device level ... zpool replace data c2t3d0 
c2t5d0 ... it shouldn't matter what partitions are on the device.

...

... and now I appear to have problems. The screen on the server has 
gone, "corrupt" (it was blank before, but now it has all sorts of white 
noise on the top third) and the backup process has halted.

Any attempt to query the drives, freezes the console session that 
requested it.

...and now the system is refusing to start new sessions.

Hmmm....

That was odd.

For the record, I'm now running ...
              OpenIndiana Development oi_151.1.4 X86 (powered by illumos)
         Copyright 2011 Oracle and/or its affiliates. All rights reserved.
                         Use is subject to license terms.
                            Assembled 22 April 2012


Messages at the time of crash were..

Jun 10 13:10:14 jaguar ntpd[1469]: [ID 702911 daemon.notice] ntpd 
4.2.5p200 at 1.1948-o Wed May  2 18:21:11 BST 2012 (1)
Jun 10 13:10:15 jaguar ntpd[1471]: [ID 702911 daemon.notice] proto: 
precision = 0.288 usec
Jun 10 13:10:21 jaguar ntpd[1471]: [ID 702911 daemon.notice] ntpd 
exiting on signal 15
Jun 10 13:10:21 jaguar ntpd[1490]: [ID 702911 daemon.notice] ntpd 
4.2.5p200 at 1.1948-o Wed May  2 18:21:11 BST 2012 (1)
Jun 10 13:10:21 jaguar ntpd[1492]: [ID 702911 daemon.notice] proto: 
precision = 0.285 usec
Jun 10 13:11:17 jaguar syslog[1252]: [ID 702911 daemon.warning] WARNING: 
Failed to send buffer
Jun 10 13:21:47 jaguar genunix: [ID 108120 kern.notice] ^MOpenIndiana 
Build oi_151a4 64-bit (illumos 13676:98ca40df9171)



From jimklimov at cos.ru  Sun Jun 10 13:13:59 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sun, 10 Jun 2012 17:13:59 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD4935C.7020502@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4935C.7020502@msknight.com>
Message-ID: <4FD49D97.1090107@cos.ru>

2012-06-10 16:30, michelle wrote:
> To test the 3tb drive in a Linux system, before I trusted it to the
> server, I did create a partition on it; however my understanding is that
> when I give a zfs command at device level ... zpool replace data c2t3d0
> c2t5d0 ... it shouldn't matter what partitions are on the device.

I did not try to give ZFS disks with random pre-existing partition
tables - I either had cleared them or pre-created to my liking.
I am not sure that ZFS would quietly recreate a table if one exists,
and/or that it would change MSDOS/MBR tables to EFI/GPT (there was
discussion of that on the dev list recently), as well as I am not
certain it won't ;)

So, when you get the 3Tb disk into the system, you might want to
revise its partitioning (now, likely, after ZFS tried to do someting
to it). If ZFS failed to change the partitioning stuff safely -
maybe that was what it complained about?..

HTH,
//Jim


From jimklimov at cos.ru  Sun Jun 10 13:21:08 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sun, 10 Jun 2012 17:21:08 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD46A59.5030106@msknight.com>
References: <4FD46A59.5030106@msknight.com>
Message-ID: <4FD49F44.7070704@cos.ru>

BTW, can you give some more detail on the machine and its HDD
controllers? There were recently discussions on zfs-discuss
list about Dell-branded HBAs with Dell firmware bent on power
saving, which sent the WD disks in particular to slep mode
right away instead of having them work. There were published
workarounds with Solaris driver configuration, so if the
description roughly mathches - you can try and see that
list's recent archives.

2012-06-10 13:35, michelle wrote:
> Hi Folks,
>
> I'm not having much luck and if someone can help with solid suggestions
> before I start poking around, it could save me stuffing up the machine.
>
> Firstly, I think that the graphics is having a problem with my TV, so if
> someone can tell me how to stop the system from wanting to boot in to
> the GUI, that would be a real help.
>
> Second, I'm replacing 2tb drives with 3tb drives.
> I'm runnning...
>
>                        OpenIndiana Development oi_151a X86
>          Copyright 2010 Oracle and/or its affiliates. All rights reserved.
>                          Use is subject to license terms.
>                             Assembled 01 September 2011
>
> I'm reluctant to upgrade because the system doesn't seem to be listening
> to USB keyboards on the selection screen.
>
> On attaching the 3tb I get...
>
> Jun 10 10:08:07 jaguar genunix: [ID 936769 kern.info] devinfo0 is
> /pseudo/devinfo at 0
> Jun 10 10:08:07 jaguar sata: [ID 801593 kern.warning] WARNING:
> /pci at 0,0/pci1458,b005 at 1f,2:
> Jun 10 10:08:07 jaguar  SATA device detected at port 2
> Jun 10 10:08:07 jaguar sata: [ID 663010 kern.info]
> /pci at 0,0/pci1458,b005 at 1f,2 :
> Jun 10 10:08:07 jaguar sata: [ID 761595 kern.info]      SATA disk device
> at port 2
> Jun 10 10:08:07 jaguar sata: [ID 846691 kern.info]      model WDC
> WD30EZRX-00MMMB0
> Jun 10 10:08:07 jaguar sata: [ID 693010 kern.info]      firmware 80.00A80
> Jun 10 10:08:07 jaguar sata: [ID 163988 kern.info]      serial
> number      WD-WMAWZ0278326
> Jun 10 10:08:07 jaguar sata: [ID 594940 kern.info]      supported features:
> Jun 10 10:08:07 jaguar sata: [ID 981177 kern.info]       48-bit LBA,
> DMA, Native Command Queueing, SMART, SMART self-test
> Jun 10 10:08:07 jaguar sata: [ID 643337 kern.info]      SATA Gen2
> signaling speed (3.0Gbps)
> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      Supported queue
> depth 32
> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      capacity =
> 5860533168 sectors
> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:35 jaguar  timeout: abort request, target=0 lun=0
> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:35 jaguar  timeout: abort device, target=0 lun=0
> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:35 jaguar  timeout: reset target, target=0 lun=0
> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:35 jaguar  timeout: reset bus, target=0 lun=0
> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:58 jaguar  timeout: abort request, target=0 lun=0
> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:58 jaguar  timeout: abort device, target=0 lun=0
> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:58 jaguar  timeout: reset target, target=0 lun=0
> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:08:58 jaguar  timeout: reset bus, target=0 lun=0
> Jun 10 10:09:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:09:58 jaguar  timeout: early timeout, target=0 lun=0
> Jun 10 10:09:58 jaguar genunix: [ID 859416 kern.info]
> ghd_timer_newstate: HBA reset failed hba 0xffffff01ce0f3900 gcmdp 0x0
> gtgtp 0xffffff01d0598100
> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:10:58 jaguar  timeout: abort request, target=0 lun=0
> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:10:58 jaguar  timeout: abort device, target=0 lun=0
> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:10:58 jaguar  timeout: reset target, target=0 lun=0
> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
> Jun 10 10:10:58 jaguar  timeout: reset bus, target=0 lun=0
>
> I know the drive works as I've been testing it in another machine, but
> the moment I plug it in, the system has problems.


From michelle at msknight.com  Sun Jun 10 13:53:41 2012
From: michelle at msknight.com (michelle)
Date: Sun, 10 Jun 2012 14:53:41 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD49F44.7070704@cos.ru>
References: <4FD46A59.5030106@msknight.com> <4FD49F44.7070704@cos.ru>
Message-ID: <4FD4A6E5.5010307@msknight.com>

Thanks for the info Jim,

The motherboard is a Gigabyte GA-H55M-UD2H and has five SATA sockets, 
two IDE and one E-sata.

The SATA are, I believe, Intel.

I think I've got an i5 in it, with 4gig of RAM. I don't use compression 
or encryption.

There are two Intel SSDs in a ZFS mirror and I copied across the boot 
sector so in failure, the other will boot successfully.

The three others are used for the internal drives on a ZFS raid; a 
balance between number of drives in a redundancy/heat/power consumption 
sort of ratio. The drives are WD Green units which are reasonably power 
saving, but they do the control themselves as I didn't want to risk 
driver issues. They have turned out to be reasonable for the money (the 
existing 2tb's are WD Green and have served about 18 months with no 
issues) but with the price hikes it will be another two months before I 
am able to replace the whole set.

I have an external, "toaster" for two hard drives, so I wanted to get a 
second e-sata in there, so I bought a Rocket 62X RocketRAID 62X/62XM 
using the Marvel chipset, but unfortunately this turned out to be one 
that wasn't supported. So one external drive is on the Esata and the 
other is on the USB channel, but still working as a mirrored ZFS set for 
backup purposes. It's a shame as the USB link is doubling the backup time.

When the backup is finished tomorrow, I'll wipe the 3tb and see if it 
will take it again.


On 10/06/12 14:21, Jim Klimov wrote:
> BTW, can you give some more detail on the machine and its HDD
> controllers? There were recently discussions on zfs-discuss
> list about Dell-branded HBAs with Dell firmware bent on power
> saving, which sent the WD disks in particular to slep mode
> right away instead of having them work. There were published
> workarounds with Solaris driver configuration, so if the
> description roughly mathches - you can try and see that
> list's recent archives.
>
> 2012-06-10 13:35, michelle wrote:
>> Hi Folks,
>>
>> I'm not having much luck and if someone can help with solid suggestions
>> before I start poking around, it could save me stuffing up the machine.
>>
>> Firstly, I think that the graphics is having a problem with my TV, so if
>> someone can tell me how to stop the system from wanting to boot in to
>> the GUI, that would be a real help.
>>
>> Second, I'm replacing 2tb drives with 3tb drives.
>> I'm runnning...
>>
>>                        OpenIndiana Development oi_151a X86
>>          Copyright 2010 Oracle and/or its affiliates. All rights 
>> reserved.
>>                          Use is subject to license terms.
>>                             Assembled 01 September 2011
>>
>> I'm reluctant to upgrade because the system doesn't seem to be listening
>> to USB keyboards on the selection screen.
>>
>> On attaching the 3tb I get...
>>
>> Jun 10 10:08:07 jaguar genunix: [ID 936769 kern.info] devinfo0 is
>> /pseudo/devinfo at 0
>> Jun 10 10:08:07 jaguar sata: [ID 801593 kern.warning] WARNING:
>> /pci at 0,0/pci1458,b005 at 1f,2:
>> Jun 10 10:08:07 jaguar  SATA device detected at port 2
>> Jun 10 10:08:07 jaguar sata: [ID 663010 kern.info]
>> /pci at 0,0/pci1458,b005 at 1f,2 :
>> Jun 10 10:08:07 jaguar sata: [ID 761595 kern.info]      SATA disk device
>> at port 2
>> Jun 10 10:08:07 jaguar sata: [ID 846691 kern.info]      model WDC
>> WD30EZRX-00MMMB0
>> Jun 10 10:08:07 jaguar sata: [ID 693010 kern.info]      firmware 
>> 80.00A80
>> Jun 10 10:08:07 jaguar sata: [ID 163988 kern.info]      serial
>> number      WD-WMAWZ0278326
>> Jun 10 10:08:07 jaguar sata: [ID 594940 kern.info]      supported 
>> features:
>> Jun 10 10:08:07 jaguar sata: [ID 981177 kern.info]       48-bit LBA,
>> DMA, Native Command Queueing, SMART, SMART self-test
>> Jun 10 10:08:07 jaguar sata: [ID 643337 kern.info]      SATA Gen2
>> signaling speed (3.0Gbps)
>> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      Supported queue
>> depth 32
>> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      capacity =
>> 5860533168 sectors
>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:35 jaguar  timeout: abort request, target=0 lun=0
>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:35 jaguar  timeout: abort device, target=0 lun=0
>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:35 jaguar  timeout: reset target, target=0 lun=0
>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:35 jaguar  timeout: reset bus, target=0 lun=0
>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:58 jaguar  timeout: abort request, target=0 lun=0
>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:58 jaguar  timeout: abort device, target=0 lun=0
>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:58 jaguar  timeout: reset target, target=0 lun=0
>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:08:58 jaguar  timeout: reset bus, target=0 lun=0
>> Jun 10 10:09:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:09:58 jaguar  timeout: early timeout, target=0 lun=0
>> Jun 10 10:09:58 jaguar genunix: [ID 859416 kern.info]
>> ghd_timer_newstate: HBA reset failed hba 0xffffff01ce0f3900 gcmdp 0x0
>> gtgtp 0xffffff01d0598100
>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:10:58 jaguar  timeout: abort request, target=0 lun=0
>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:10:58 jaguar  timeout: abort device, target=0 lun=0
>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:10:58 jaguar  timeout: reset target, target=0 lun=0
>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>> Jun 10 10:10:58 jaguar  timeout: reset bus, target=0 lun=0
>>
>> I know the drive works as I've been testing it in another machine, but
>> the moment I plug it in, the system has problems.
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>


From michelle at msknight.com  Sun Jun 10 14:45:49 2012
From: michelle at msknight.com (michelle)
Date: Sun, 10 Jun 2012 15:45:49 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD4A6E5.5010307@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD49F44.7070704@cos.ru>
	<4FD4A6E5.5010307@msknight.com>
Message-ID: <4FD4B31D.1010801@msknight.com>

The system seems to have hung again, any query to the ZFS system hangs 
the session.

Nothing in /var/adm/messages.

I'm wondering whether the combination of having a mirrored zfs set with 
one drive on e-sata and one drive on USB could be upsetting it.


On 10/06/12 14:53, michelle wrote:
> Thanks for the info Jim,
>
> The motherboard is a Gigabyte GA-H55M-UD2H and has five SATA sockets, 
> two IDE and one E-sata.
>
> The SATA are, I believe, Intel.
>
> I think I've got an i5 in it, with 4gig of RAM. I don't use 
> compression or encryption.
>
> There are two Intel SSDs in a ZFS mirror and I copied across the boot 
> sector so in failure, the other will boot successfully.
>
> The three others are used for the internal drives on a ZFS raid; a 
> balance between number of drives in a redundancy/heat/power 
> consumption sort of ratio. The drives are WD Green units which are 
> reasonably power saving, but they do the control themselves as I 
> didn't want to risk driver issues. They have turned out to be 
> reasonable for the money (the existing 2tb's are WD Green and have 
> served about 18 months with no issues) but with the price hikes it 
> will be another two months before I am able to replace the whole set.
>
> I have an external, "toaster" for two hard drives, so I wanted to get 
> a second e-sata in there, so I bought a Rocket 62X RocketRAID 62X/62XM 
> using the Marvel chipset, but unfortunately this turned out to be one 
> that wasn't supported. So one external drive is on the Esata and the 
> other is on the USB channel, but still working as a mirrored ZFS set 
> for backup purposes. It's a shame as the USB link is doubling the 
> backup time.
>
> When the backup is finished tomorrow, I'll wipe the 3tb and see if it 
> will take it again.
>
>
> On 10/06/12 14:21, Jim Klimov wrote:
>> BTW, can you give some more detail on the machine and its HDD
>> controllers? There were recently discussions on zfs-discuss
>> list about Dell-branded HBAs with Dell firmware bent on power
>> saving, which sent the WD disks in particular to slep mode
>> right away instead of having them work. There were published
>> workarounds with Solaris driver configuration, so if the
>> description roughly mathches - you can try and see that
>> list's recent archives.
>>
>> 2012-06-10 13:35, michelle wrote:
>>> Hi Folks,
>>>
>>> I'm not having much luck and if someone can help with solid suggestions
>>> before I start poking around, it could save me stuffing up the machine.
>>>
>>> Firstly, I think that the graphics is having a problem with my TV, 
>>> so if
>>> someone can tell me how to stop the system from wanting to boot in to
>>> the GUI, that would be a real help.
>>>
>>> Second, I'm replacing 2tb drives with 3tb drives.
>>> I'm runnning...
>>>
>>>                        OpenIndiana Development oi_151a X86
>>>          Copyright 2010 Oracle and/or its affiliates. All rights 
>>> reserved.
>>>                          Use is subject to license terms.
>>>                             Assembled 01 September 2011
>>>
>>> I'm reluctant to upgrade because the system doesn't seem to be 
>>> listening
>>> to USB keyboards on the selection screen.
>>>
>>> On attaching the 3tb I get...
>>>
>>> Jun 10 10:08:07 jaguar genunix: [ID 936769 kern.info] devinfo0 is
>>> /pseudo/devinfo at 0
>>> Jun 10 10:08:07 jaguar sata: [ID 801593 kern.warning] WARNING:
>>> /pci at 0,0/pci1458,b005 at 1f,2:
>>> Jun 10 10:08:07 jaguar  SATA device detected at port 2
>>> Jun 10 10:08:07 jaguar sata: [ID 663010 kern.info]
>>> /pci at 0,0/pci1458,b005 at 1f,2 :
>>> Jun 10 10:08:07 jaguar sata: [ID 761595 kern.info]      SATA disk 
>>> device
>>> at port 2
>>> Jun 10 10:08:07 jaguar sata: [ID 846691 kern.info]      model WDC
>>> WD30EZRX-00MMMB0
>>> Jun 10 10:08:07 jaguar sata: [ID 693010 kern.info]      firmware 
>>> 80.00A80
>>> Jun 10 10:08:07 jaguar sata: [ID 163988 kern.info]      serial
>>> number      WD-WMAWZ0278326
>>> Jun 10 10:08:07 jaguar sata: [ID 594940 kern.info]      supported 
>>> features:
>>> Jun 10 10:08:07 jaguar sata: [ID 981177 kern.info]       48-bit LBA,
>>> DMA, Native Command Queueing, SMART, SMART self-test
>>> Jun 10 10:08:07 jaguar sata: [ID 643337 kern.info]      SATA Gen2
>>> signaling speed (3.0Gbps)
>>> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      Supported queue
>>> depth 32
>>> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      capacity =
>>> 5860533168 sectors
>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:35 jaguar  timeout: abort request, target=0 lun=0
>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:35 jaguar  timeout: abort device, target=0 lun=0
>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:35 jaguar  timeout: reset target, target=0 lun=0
>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:35 jaguar  timeout: reset bus, target=0 lun=0
>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:58 jaguar  timeout: abort request, target=0 lun=0
>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:58 jaguar  timeout: abort device, target=0 lun=0
>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:58 jaguar  timeout: reset target, target=0 lun=0
>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:08:58 jaguar  timeout: reset bus, target=0 lun=0
>>> Jun 10 10:09:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:09:58 jaguar  timeout: early timeout, target=0 lun=0
>>> Jun 10 10:09:58 jaguar genunix: [ID 859416 kern.info]
>>> ghd_timer_newstate: HBA reset failed hba 0xffffff01ce0f3900 gcmdp 0x0
>>> gtgtp 0xffffff01d0598100
>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:10:58 jaguar  timeout: abort request, target=0 lun=0
>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:10:58 jaguar  timeout: abort device, target=0 lun=0
>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:10:58 jaguar  timeout: reset target, target=0 lun=0
>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>> Jun 10 10:10:58 jaguar  timeout: reset bus, target=0 lun=0
>>>
>>> I know the drive works as I've been testing it in another machine, but
>>> the moment I plug it in, the system has problems.
>>
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>


From jimklimov at cos.ru  Sun Jun 10 15:02:22 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sun, 10 Jun 2012 19:02:22 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD4B31D.1010801@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD49F44.7070704@cos.ru>
	<4FD4A6E5.5010307@msknight.com> <4FD4B31D.1010801@msknight.com>
Message-ID: <4FD4B6FE.4060308@cos.ru>

2012-06-10 18:45, michelle wrote:
> The system seems to have hung again, any query to the ZFS system hangs
> the session.

There is also a dev-discussion going on about zfs commands hanging
on some long tasks, as it is a problem which annoys (to say the least)
or has annoyed several people including myself, so I'll make a copy
to that list too. "+1" on "this bug bites us" part.

> Nothing in /var/adm/messages.
>
> I'm wondering whether the combination of having a mirrored zfs set with
> one drive on e-sata and one drive on USB could be upsetting it.

Maybe, at least, it is technically possible for a USB driver to hang -
I've seen that a lot with Solaris 8/9 on some older projects of mine.

I think some people on the zfs-discuss list might help if you give
some more detail (a concise summary of this thread in one post) on
what is going on with the system - what it is, what you did with the
drives, what is the pool busy with until it hangs...

//Jim


From jimklimov at cos.ru  Sun Jun 10 15:08:52 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sun, 10 Jun 2012 19:08:52 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD4B31D.1010801@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD49F44.7070704@cos.ru>
	<4FD4A6E5.5010307@msknight.com> <4FD4B31D.1010801@msknight.com>
Message-ID: <4FD4B884.3040807@cos.ru>

2012-06-10 18:45, michelle wrote:
> The system seems to have hung again, any query to the ZFS system hangs
> the session.
>
> Nothing in /var/adm/messages.
>
> I'm wondering whether the combination of having a mirrored zfs set with
> one drive on e-sata and one drive on USB could be upsetting it.



The situation sounds reminiscent of my large data deletions on a
deduped pool, when the system was running out of kernel memory and
collapsed into a "scanrate-hell" while processing deferred-frees
of zfs blocks. You can monitor this with "vmstat 1" in an SSH
terminal, if this condition is the case, the "free" memory will
go under 32Mb (or 128Mb in some cases), and the "sr" column may
reach millions. I am not sure if there's much one can DO about
this, except reset the box and wait - my deferred-frees cleared
up after a couple of weeks...

I've made a "freeram-watchdog" program which tries to catch the
condition and reset the system before it is too late, but it
often misses the moment (kstat checks can't be more frequent
than 1 second, and this is sometimes enough to bring the box down).
I later learned of the "deadman timer" but haven't got to test
if it applies in this case. See here:

http://wiki.illumos.org/pages/viewpage.action?pageId=1146983
http://81.5.113.5/~jim/freeram-watchdog-20110531-smf.tgz

HTH,
//Jim Klimov


From richard.elling at richardelling.com  Sun Jun 10 17:21:25 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Sun, 10 Jun 2012 10:21:25 -0700
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD4B31D.1010801@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD49F44.7070704@cos.ru>
	<4FD4A6E5.5010307@msknight.com> <4FD4B31D.1010801@msknight.com>
Message-ID: <5FC51390-8B7B-4A2C-A1C2-1CDE69305CBB@RichardElling.com>


On Jun 10, 2012, at 7:45 AM, michelle wrote:

> The system seems to have hung again, any query to the ZFS system hangs the session.
> 
> Nothing in /var/adm/messages.

Try fmdump -eV
 -- richard

> 
> I'm wondering whether the combination of having a mirrored zfs set with one drive on e-sata and one drive on USB could be upsetting it.
> 
> 
> On 10/06/12 14:53, michelle wrote:
>> Thanks for the info Jim,
>> 
>> The motherboard is a Gigabyte GA-H55M-UD2H and has five SATA sockets, two IDE and one E-sata.
>> 
>> The SATA are, I believe, Intel.
>> 
>> I think I've got an i5 in it, with 4gig of RAM. I don't use compression or encryption.
>> 
>> There are two Intel SSDs in a ZFS mirror and I copied across the boot sector so in failure, the other will boot successfully.
>> 
>> The three others are used for the internal drives on a ZFS raid; a balance between number of drives in a redundancy/heat/power consumption sort of ratio. The drives are WD Green units which are reasonably power saving, but they do the control themselves as I didn't want to risk driver issues. They have turned out to be reasonable for the money (the existing 2tb's are WD Green and have served about 18 months with no issues) but with the price hikes it will be another two months before I am able to replace the whole set.
>> 
>> I have an external, "toaster" for two hard drives, so I wanted to get a second e-sata in there, so I bought a Rocket 62X RocketRAID 62X/62XM using the Marvel chipset, but unfortunately this turned out to be one that wasn't supported. So one external drive is on the Esata and the other is on the USB channel, but still working as a mirrored ZFS set for backup purposes. It's a shame as the USB link is doubling the backup time.
>> 
>> When the backup is finished tomorrow, I'll wipe the 3tb and see if it will take it again.
>> 
>> 
>> On 10/06/12 14:21, Jim Klimov wrote:
>>> BTW, can you give some more detail on the machine and its HDD
>>> controllers? There were recently discussions on zfs-discuss
>>> list about Dell-branded HBAs with Dell firmware bent on power
>>> saving, which sent the WD disks in particular to slep mode
>>> right away instead of having them work. There were published
>>> workarounds with Solaris driver configuration, so if the
>>> description roughly mathches - you can try and see that
>>> list's recent archives.
>>> 
>>> 2012-06-10 13:35, michelle wrote:
>>>> Hi Folks,
>>>> 
>>>> I'm not having much luck and if someone can help with solid suggestions
>>>> before I start poking around, it could save me stuffing up the machine.
>>>> 
>>>> Firstly, I think that the graphics is having a problem with my TV, so if
>>>> someone can tell me how to stop the system from wanting to boot in to
>>>> the GUI, that would be a real help.
>>>> 
>>>> Second, I'm replacing 2tb drives with 3tb drives.
>>>> I'm runnning...
>>>> 
>>>>                       OpenIndiana Development oi_151a X86
>>>>         Copyright 2010 Oracle and/or its affiliates. All rights reserved.
>>>>                         Use is subject to license terms.
>>>>                            Assembled 01 September 2011
>>>> 
>>>> I'm reluctant to upgrade because the system doesn't seem to be listening
>>>> to USB keyboards on the selection screen.
>>>> 
>>>> On attaching the 3tb I get...
>>>> 
>>>> Jun 10 10:08:07 jaguar genunix: [ID 936769 kern.info] devinfo0 is
>>>> /pseudo/devinfo at 0
>>>> Jun 10 10:08:07 jaguar sata: [ID 801593 kern.warning] WARNING:
>>>> /pci at 0,0/pci1458,b005 at 1f,2:
>>>> Jun 10 10:08:07 jaguar  SATA device detected at port 2
>>>> Jun 10 10:08:07 jaguar sata: [ID 663010 kern.info]
>>>> /pci at 0,0/pci1458,b005 at 1f,2 :
>>>> Jun 10 10:08:07 jaguar sata: [ID 761595 kern.info]      SATA disk device
>>>> at port 2
>>>> Jun 10 10:08:07 jaguar sata: [ID 846691 kern.info]      model WDC
>>>> WD30EZRX-00MMMB0
>>>> Jun 10 10:08:07 jaguar sata: [ID 693010 kern.info]      firmware 80.00A80
>>>> Jun 10 10:08:07 jaguar sata: [ID 163988 kern.info]      serial
>>>> number      WD-WMAWZ0278326
>>>> Jun 10 10:08:07 jaguar sata: [ID 594940 kern.info]      supported features:
>>>> Jun 10 10:08:07 jaguar sata: [ID 981177 kern.info]       48-bit LBA,
>>>> DMA, Native Command Queueing, SMART, SMART self-test
>>>> Jun 10 10:08:07 jaguar sata: [ID 643337 kern.info]      SATA Gen2
>>>> signaling speed (3.0Gbps)
>>>> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      Supported queue
>>>> depth 32
>>>> Jun 10 10:08:07 jaguar sata: [ID 349649 kern.info]      capacity =
>>>> 5860533168 sectors
>>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:35 jaguar  timeout: abort request, target=0 lun=0
>>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:35 jaguar  timeout: abort device, target=0 lun=0
>>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:35 jaguar  timeout: reset target, target=0 lun=0
>>>> Jun 10 10:08:35 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:35 jaguar  timeout: reset bus, target=0 lun=0
>>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:58 jaguar  timeout: abort request, target=0 lun=0
>>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:58 jaguar  timeout: abort device, target=0 lun=0
>>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:58 jaguar  timeout: reset target, target=0 lun=0
>>>> Jun 10 10:08:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:08:58 jaguar  timeout: reset bus, target=0 lun=0
>>>> Jun 10 10:09:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:09:58 jaguar  timeout: early timeout, target=0 lun=0
>>>> Jun 10 10:09:58 jaguar genunix: [ID 859416 kern.info]
>>>> ghd_timer_newstate: HBA reset failed hba 0xffffff01ce0f3900 gcmdp 0x0
>>>> gtgtp 0xffffff01d0598100
>>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:10:58 jaguar  timeout: abort request, target=0 lun=0
>>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:10:58 jaguar  timeout: abort device, target=0 lun=0
>>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:10:58 jaguar  timeout: reset target, target=0 lun=0
>>>> Jun 10 10:10:58 jaguar scsi: [ID 107833 kern.warning] WARNING:
>>>> /pci at 0,0/pci8086,3b4a at 1c,4/pci-ide at 0/ide at 0 (ata0):
>>>> Jun 10 10:10:58 jaguar  timeout: reset bus, target=0 lun=0
>>>> 
>>>> I know the drive works as I've been testing it in another machine, but
>>>> the moment I plug it in, the system has problems.
>>> 
>>> _______________________________________________
>>> OpenIndiana-discuss mailing list
>>> OpenIndiana-discuss at openindiana.org
>>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>>> 
>> 
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>> 
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

--
ZFS Performance and Training
Richard.Elling at RichardElling.com
+1-760-896-4422




From sommerfeld at alum.mit.edu  Sun Jun 10 17:29:55 2012
From: sommerfeld at alum.mit.edu (Bill Sommerfeld)
Date: Sun, 10 Jun 2012 10:29:55 -0700
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD486EC.4000405@msknight.com>
References: <4FD46A59.5030106@msknight.com>
	<4FD471DB.3040704@msknight.com>	<4FD47769.1050703@msknight.com>
	<4FD486EC.4000405@msknight.com>
Message-ID: <4FD4D993.3080901@alum.mit.edu>

On 06/10/12 04:37, michelle wrote:
> 2) How to get around the sector alignment problem.
>
> I have a very ugly feeling that the only way is going to be to destroy
> the set and start again, as everything I've tried so far hasn't worked.

That was my conclusion as well - I wound up using zfs send | zfs receive 
to migrate data across the 512-byte to 4K gulf.





From udo.grabowski at kit.edu  Sun Jun 10 21:49:44 2012
From: udo.grabowski at kit.edu (Udo Grabowski (IMK))
Date: Sun, 10 Jun 2012 23:49:44 +0200
Subject: [OpenIndiana-discuss] Mouse lost by power management
Message-ID: <4FD51678.9050708@kit.edu>

Hello,

oi-151a4 (=prestable3, and probably a3 also) disconnect the USB /
mouse when power management is on (and screensaver goes to standby
or suspend). This shouldn't happen, as the mouse can only be
reactivated by replugging (and only if the hotplug daemon runs).

I can circumvent this problem by declaring a always-on in
/etc/power.conf, but this should be the default for a USB mouse
(and keyboard) devices:

device-thresholds /pci at 0,0/pci1043,82d4 at 1d/mouse at 1 always-on
device-dependency-property removable-media /dev/fb
autopm                  enable
autoS3                  default
cpu-threshold           1s
S3-support              default
# Auto-Shutdown         Idle(min)       Start/Finish(hh:mm)     Behavior
autoshutdown            30              9:00 9:00               noshutdown
cpupm  enable event-mode
cpu_deep_idle enable

The only message I see in /var/adm/messages and /var/log/Xorg.0.log:

Jun 10 12:57:58 opensolaris genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1043,82d4 at 1d/mouse at 1 (hid0) removed

mouse: Device no longer present - removing.
(WW) mouse: cannot pop module 'usbms' off mouse device: No such device
(WW) mouse: cannot pop module 'usbms' off mouse device: No such device
(II) UnloadModule: "mouse"


This quirk is not present on a2 and Osol 2009 134b.


From ryan.cunningham.xyzzy at gmail.com  Mon Jun 11 04:22:42 2012
From: ryan.cunningham.xyzzy at gmail.com (Ryan Cunningham)
Date: Mon, 11 Jun 2012 00:22:42 -0400
Subject: [OpenIndiana-discuss] zone install hangs/never completes
Message-ID: <CAEunHtVPF7gFKXitR-rcgdvE2LbYurnFRzza5Y_+MYnRXZR8+w@mail.gmail.com>

Hello,

I've tried Googling but haven't had any luck thus far--I'm attempting
to install a zone on my oi_151-a4 system but it looks to be hanging
for some reason. fwiw the system was initially installed using oi_147
media, upgraded to oi_148 and then recently upgraded to oi_151-a4.

The output to my terminal isn't especially informative:

# zoneadm -z azone install
   Publisher: Using openindiana.org (http://pkg.openindiana.org/dev/ ).
       Image: Preparing at /zone/azone/root.

ptree shows:

1469  screen
  1470  /bin/bash
    1474  sudo su -
      1475  -bash
        1493  zoneadm -z azone install
          1494  /bin/ksh -p /usr/lib/brand/ipkg/pkgcreatezone -z azone
-R /zone/azone
            1652  /usr/bin/python2.6 /usr/bin/pkg image-create -f
--no-refresh --zone --full -p o

pfiles doesn't reveal anything I find to be particularly illuminating:

# pfiles 1652
1652:   /usr/bin/python2.6 /usr/bin/pkg image-create -f --no-refresh --zone --
  Current rlimit: 65536 file descriptors
   0: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7 rdev:27,4
      O_RDWR
      /dev/pts/4
      offset:14832
   1: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7 rdev:27,4
      O_RDWR
      /dev/pts/4
      offset:14832
   2: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7 rdev:27,4
      O_RDWR
      /dev/pts/4
      offset:14832
   3: S_IFDOOR mode:0444 dev:560,0 ino:49 uid:0 gid:0 size:0
      O_RDONLY|O_LARGEFILE FD_CLOEXEC  door to nscd[616]
      /var/run/name_service_door
   4: S_IFCHR mode:0666 dev:550,0 ino:19398660 uid:0 gid:3 rdev:37,0
      O_RDWR
      /devices/pseudo/zfs at 0:zfs
      offset:0
   5: S_IFREG mode:0444 dev:555,1 ino:2 uid:0 gid:0 size:3520
      O_RDONLY
      /etc/mnttab
      offset:0
   6: S_IFREG mode:0444 dev:558,1 ino:128 uid:0 gid:0 size:233
      O_RDONLY
      /etc/dfs/sharetab
      offset:0
   7: S_IFREG mode:0600 dev:556,3 ino:1000972048 uid:0 gid:0 size:0
      O_RDWR|O_CREAT
      advisory write lock set by process 1493
      /var/run/zones/azone.zoneadm.lock
      offset:0

truss shows that the Python process isn't actually doing much of anything:

# truss -p 1652
lwp_mutex_timedlock(0xFCF10000, 0x00000000, 0xFEE22A40) (sleeping...)

Is there something really obvious I'm missing with this?

Thanks in advance for any insights,
Ryan


From milan.jurik at xylab.cz  Mon Jun 11 06:32:53 2012
From: milan.jurik at xylab.cz (Milan Jurik)
Date: Mon, 11 Jun 2012 08:32:53 +0200
Subject: [OpenIndiana-discuss] zone install hangs/never completes
In-Reply-To: <CAEunHtVPF7gFKXitR-rcgdvE2LbYurnFRzza5Y_+MYnRXZR8+w@mail.gmail.com>
References: <CAEunHtVPF7gFKXitR-rcgdvE2LbYurnFRzza5Y_+MYnRXZR8+w@mail.gmail.com>
Message-ID: <a254244aaca4d452694f468b34a55990@xylab.cz>

Hi Ryan,

On 11.06.2012 06:22, Ryan Cunningham wrote:
> Hello,
>
> I've tried Googling but haven't had any luck thus far--I'm attempting
> to install a zone on my oi_151-a4 system but it looks to be hanging
> for some reason. fwiw the system was initially installed using oi_147
> media, upgraded to oi_148 and then recently upgraded to oi_151-a4.
>
> The output to my terminal isn't especially informative:
>
> # zoneadm -z azone install
>    Publisher: Using openindiana.org (http://pkg.openindiana.org/dev/ 
> ).
>        Image: Preparing at /zone/azone/root.
>
> ptree shows:
>
> 1469  screen
>   1470  /bin/bash
>     1474  sudo su -
>       1475  -bash
>         1493  zoneadm -z azone install
>           1494  /bin/ksh -p /usr/lib/brand/ipkg/pkgcreatezone -z 
> azone
> -R /zone/azone
>             1652  /usr/bin/python2.6 /usr/bin/pkg image-create -f
> --no-refresh --zone --full -p o
>
> pfiles doesn't reveal anything I find to be particularly 
> illuminating:
>
> # pfiles 1652
> 1652:   /usr/bin/python2.6 /usr/bin/pkg image-create -f --no-refresh
> --zone --
>   Current rlimit: 65536 file descriptors
>    0: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7 
> rdev:27,4
>       O_RDWR
>       /dev/pts/4
>       offset:14832
>    1: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7 
> rdev:27,4
>       O_RDWR
>       /dev/pts/4
>       offset:14832
>    2: S_IFCHR mode:0620 dev:551,0 ino:1001224776 uid:1000 gid:7 
> rdev:27,4
>       O_RDWR
>       /dev/pts/4
>       offset:14832
>    3: S_IFDOOR mode:0444 dev:560,0 ino:49 uid:0 gid:0 size:0
>       O_RDONLY|O_LARGEFILE FD_CLOEXEC  door to nscd[616]
>       /var/run/name_service_door
>    4: S_IFCHR mode:0666 dev:550,0 ino:19398660 uid:0 gid:3 rdev:37,0
>       O_RDWR
>       /devices/pseudo/zfs at 0:zfs
>       offset:0
>    5: S_IFREG mode:0444 dev:555,1 ino:2 uid:0 gid:0 size:3520
>       O_RDONLY
>       /etc/mnttab
>       offset:0
>    6: S_IFREG mode:0444 dev:558,1 ino:128 uid:0 gid:0 size:233
>       O_RDONLY
>       /etc/dfs/sharetab
>       offset:0
>    7: S_IFREG mode:0600 dev:556,3 ino:1000972048 uid:0 gid:0 size:0
>       O_RDWR|O_CREAT
>       advisory write lock set by process 1493
>       /var/run/zones/azone.zoneadm.lock
>       offset:0
>
> truss shows that the Python process isn't actually doing much of 
> anything:
>
> # truss -p 1652
> lwp_mutex_timedlock(0xFCF10000, 0x00000000, 0xFEE22A40) (sleeping...)
>

truss shows only the current call in the active thread. Try pstack to 
see what it is doing.

Best regards,

Milan

> Is there something really obvious I'm missing with this?
>
> Thanks in advance for any insights,
> Ryan
>



From michelle at msknight.com  Mon Jun 11 06:53:56 2012
From: michelle at msknight.com (michelle)
Date: Mon, 11 Jun 2012 07:53:56 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD4D993.3080901@alum.mit.edu>
References: <4FD46A59.5030106@msknight.com>
	<4FD471DB.3040704@msknight.com>	<4FD47769.1050703@msknight.com>
	<4FD486EC.4000405@msknight.com> <4FD4D993.3080901@alum.mit.edu>
Message-ID: <4FD59604.9040003@msknight.com>

Broke the mirror and tried to a single drive and the backup worked; the 
combination of USB and e-sata was obviously upsetting it.

If only this Marvel chipset was supported then I could get the second 
e-sata channel working. Ah well.

After the backup was complete I have tried reconnecting and reformatting 
the 3tb drive but still the same error. I don't really want to 
retard/downgrade the 3tb drive's abilities.

It will be another two months before I have enough replacement 3tb 
drives; and where I'd copy the main chunk of data off to when I have 
them, I'm not sure as my plan was to use the 2tb drives as a backup.

With these extra problems/restrictions that are appearing when using the 
ZFS raidz, the lack of flexibility is starting to hurt. There was 
another restriction as well, I think it was something like not being 
able to dynamically add more drives to the set. But it was the promise 
of flexibility which is why I went for ZFS in the first place.

If anyone has any insight in to an alternative strategy than raidz that 
would keep the heat generation down but still give tolerance and ability 
to change hard drives without destroying the set, I'd be grateful to 
hear it. My current target is 6tb of data storage and I'm not confident 
enough with my low grade consumer items for a single mirror.

Thanks in advance for any advice.


From dswartz at druber.com  Mon Jun 11 13:10:02 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 11 Jun 2012 09:10:02 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
Message-ID: <58350FC0BE1940039994847849EB1933@manticore>

I've been seeing a ton of messages like:

 

Jun 11 08:59:08 nas     Log info 0x31120303 received for target 9.

Jun 11 08:59:08 nas     scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc

Jun 11 08:59:08 nas scsi: [ID 365881 kern.info]
/pci at 0,0/pci8086,27d0 at 1c/pci1000,3040 at 0 (mpt_sas10):

 

root pool is a single sata drive:

 

        NAME                        STATE     READ WRITE CKSUM

        rpool                       ONLINE       0     0     0

          c10t5000C5000D3C80FDd0s0  ONLINE       0     0     0

 

tank pool is 6 sata drives with a sas and ssd as cache:

 

        NAME                        STATE     READ WRITE CKSUM

        tank                        ONLINE       0     0     0

          mirror-0                  ONLINE       0     0     0

            c9t50014EE2AF872299d0   ONLINE       0     0     0

            c1t50014EE2AEDF73CEd0   ONLINE       0     0     0

          mirror-1                  ONLINE       0     0     0

            c3t50014EE206CED4ECd0   ONLINE       0     0     0

            c2t50014EE25C240034d0   ONLINE       0     0     0

          mirror-2                  ONLINE       0     0     0

            c13t50014EE204411A53d0  ONLINE       0     0     0

            c6t50014EE0ABCEE0A9d0   ONLINE       0     0     0

        cache

          c5t500A07510324D633d0     ONLINE       0     0     0

          c8t5000CCA00B078F2Dd0     ONLINE       0     0     0

 

How do I map 'target 9' to a drive?  Google was not remotely helpful - the
only thread I found recommended downloading lsiutil (which I can't find
anywhere).  I installed sasinfo, which prints a lot of info, but nothing
obviously useful to me.  Any help appreciated...


From jimklimov at cos.ru  Mon Jun 11 13:20:04 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 11 Jun 2012 17:20:04 +0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <58350FC0BE1940039994847849EB1933@manticore>
References: <58350FC0BE1940039994847849EB1933@manticore>
Message-ID: <4FD5F084.5070001@cos.ru>

2012-06-11 17:10, Dan Swartzendruber ?????:
>
> How do I map 'target 9' to a drive?  Google was not remotely helpful - the
> only thread I found recommended downloading lsiutil (which I can't find
> anywhere).  I installed sasinfo, which prints a lot of info, but nothing
> obviously useful to me.  Any help appreciated...

There were some references in zfs-discuss list last month,
I think the URL should be like this (I did not check myself):

=====
http://www.lsi.com/channel/products/storagecomponents/Pages/LSISAS9211-8i.aspx

select * SUPPORT & DOWNLOADS
download  SAS2IRCU_P13
=====

HTH,
//Jim Klimov


From jimklimov at cos.ru  Mon Jun 11 13:59:54 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 11 Jun 2012 17:59:54 +0400
Subject: [OpenIndiana-discuss] Is it possible to do shared networking for LZ
 different from IP stack in GZ?
Message-ID: <4FD5F9DA.60509@cos.ru>

Hello all,

   In OpenSolaris and its descendants it is possible to create
local zones (LZ) which share an IP stack with the global zone
(GZ) or have an exclusive IP stack. While exclusive stacks
have better separation between zones, the shared stacks may
yield higher performance comparable to loopback links.

   I wondered if it is possible (now, or technically feasible
through an RFE) to go a step beyond, and either:
1) Have a number of LZs with a shared IP stack, while the GZ
    uses an exclusive IP stack, or
2) Define a number of IP stacks and bind certain zones to one
    or another stack (and perhaps allow creation of routing
    zones which can route/firewall between the two, although
    several zones connected by an etherstub could do that).
    Separate stacks shared by several zones might combine the
    best of two worlds - groups of related zones would have
    faster and more intimate interlinks, while unrelated zones
    (and groups thereof) would be well isolated.
(actually, option 1 is a subset of option 2's capabilities)

   For example, now I was documenting how to pass several LZs
with a host-only networked connection (exclusive stacks on
an etherstub) to Internet through NAT on their GZ. This is,
apparently, not a way to go for zones with a shared stack -
because the GZ's stack would have a hard time defining itself
as the default route for those local zones (if the GZ is used
as a router and not some routing LZ with an exclusive stack).

   This is not an RFE per se, but rather food for thought and
discussion - did anyone ponder about this? Are there reasons
not to do it?

Thanks,
//Jim Klimov



From dswartz at druber.com  Mon Jun 11 14:06:59 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 11 Jun 2012 10:06:59 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <4FD5F084.5070001@cos.ru>
References: <58350FC0BE1940039994847849EB1933@manticore>
	<4FD5F084.5070001@cos.ru>
Message-ID: <3FBC71B0A9B849DB975D19DB25BFE257@manticore>

thanks, i got it.  unfortunately, the solaris x86 executable doesn't seem to
run under openindiana.  Here is the result:

root at nas:/tank/windows/dswartz# file sas2ircu
sas2ircu:       ELF 32-bit LSB executable 80386 Version 1, dynamically
linked, stripped
root at nas:/tank/windows/dswartz# ./sas2ircu
Killed

Maybe I am dense, but I am not sure I see the point of having kernel
messages identifying a specific HW item that is impossible (or at the very
least extremely difficult and/or non-intuitive) to chase back to the
specific device that is having issues.  Ugh, not how I wanted to start
Monday :(

-----Original Message-----
From: Jim Klimov [mailto:jimklimov at cos.ru] 
Sent: Monday, June 11, 2012 9:20 AM
To: Discussion list for OpenIndiana
Cc: Dan Swartzendruber
Subject: Re: [OpenIndiana-discuss] mapping target number to disk?

2012-06-11 17:10, Dan Swartzendruber ?????:
>
> How do I map 'target 9' to a drive?  Google was not remotely helpful - the
> only thread I found recommended downloading lsiutil (which I can't find
> anywhere).  I installed sasinfo, which prints a lot of info, but nothing
> obviously useful to me.  Any help appreciated...

There were some references in zfs-discuss list last month,
I think the URL should be like this (I did not check myself):

=====
http://www.lsi.com/channel/products/storagecomponents/Pages/LSISAS9211-8i.as
px

select * SUPPORT & DOWNLOADS
download  SAS2IRCU_P13
=====

HTH,
//Jim Klimov



From rercola at acm.jhu.edu  Mon Jun 11 14:33:32 2012
From: rercola at acm.jhu.edu (Rich)
Date: Mon, 11 Jun 2012 10:33:32 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <3FBC71B0A9B849DB975D19DB25BFE257@manticore>
References: <58350FC0BE1940039994847849EB1933@manticore>
	<4FD5F084.5070001@cos.ru>
	<3FBC71B0A9B849DB975D19DB25BFE257@manticore>
Message-ID: <CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com>

That's news to me. Are you sure you're running the correct executable?

# ./sas2ircu.SunOS
LSI Corporation SAS2 IR Configuration Utility.
Version 13.00.00.00 (2012.02.17)
Copyright (c) 2009-2012 LSI Corporation. All rights reserved.

SAS2IRCU: No command specified.
  sas2ircu <controller #> <command> <parameters> ...
    where <controller #> is:
      Number between 0 and 255
    where <command> is:
      DISPLAY    - display controller, volume and physical device info
      LIST       - Lists all available LSI adapters (does not need ctlr #>
      CREATE     - create an IR volume
      DELETE     - Delete entire RAID configuration on the selected controller
      DELETEVOLUME  - Delete a specific RAID Volume on the selected controller
      HOTSPARE   - make drive a hot spare
      STATUS     - display current volume status info
      CONSTCHK   - Start Consistency Check operation on the specified IR Volume
      ACTIVATE   - Activate an Inactive IR volume
      LOCATE     - Locate a disk drive on an enclosure
      LOGIR      - Upload or Clear IR Log data
      BOOTIR     - Select an IR Boot Volume as primary boot device
      BOOTENCL   - Select an Enclosure/Bay as primary boot device
      HELP       - Display help information
    where <parameters> are:
      Command specific values; enter "sas2ircu <controller #> <command>"
      to get command specific help
# file ./sas2ircu.SunOS
./sas2ircu.SunOS:       ELF 32-bit LSB executable 80386 Version 1,
dynamically linked, stripped
# uname -a
SunOS [hostname] 5.11 oi_151a4 i86pc i386 i86pc Solaris

- Rich

On Mon, Jun 11, 2012 at 10:06 AM, Dan Swartzendruber <dswartz at druber.com> wrote:
> thanks, i got it. ?unfortunately, the solaris x86 executable doesn't seem to
> run under openindiana. ?Here is the result:
>
> root at nas:/tank/windows/dswartz# file sas2ircu
> sas2ircu: ? ? ? ELF 32-bit LSB executable 80386 Version 1, dynamically
> linked, stripped
> root at nas:/tank/windows/dswartz# ./sas2ircu
> Killed
>
> Maybe I am dense, but I am not sure I see the point of having kernel
> messages identifying a specific HW item that is impossible (or at the very
> least extremely difficult and/or non-intuitive) to chase back to the
> specific device that is having issues. ?Ugh, not how I wanted to start
> Monday :(
>
> -----Original Message-----
> From: Jim Klimov [mailto:jimklimov at cos.ru]
> Sent: Monday, June 11, 2012 9:20 AM
> To: Discussion list for OpenIndiana
> Cc: Dan Swartzendruber
> Subject: Re: [OpenIndiana-discuss] mapping target number to disk?
>
> 2012-06-11 17:10, Dan Swartzendruber ?????:
>>
>> How do I map 'target 9' to a drive? ?Google was not remotely helpful - the
>> only thread I found recommended downloading lsiutil (which I can't find
>> anywhere). ?I installed sasinfo, which prints a lot of info, but nothing
>> obviously useful to me. ?Any help appreciated...
>
> There were some references in zfs-discuss list last month,
> I think the URL should be like this (I did not check myself):
>
> =====
> http://www.lsi.com/channel/products/storagecomponents/Pages/LSISAS9211-8i.as
> px
>
> select * SUPPORT & DOWNLOADS
> download ?SAS2IRCU_P13
> =====
>
> HTH,
> //Jim Klimov
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From dswartz at druber.com  Mon Jun 11 14:40:14 2012
From: dswartz at druber.com (dswartz at druber.com)
Date: Mon, 11 Jun 2012 10:40:14 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com>
References: <58350FC0BE1940039994847849EB1933@manticore>
	<4FD5F084.5070001@cos.ru> <3FBC71B0A9B849DB975D19DB25BFE257@manticore>
	<CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com>
Message-ID: <3c7b3533f8889472e899ec752e67dac3.squirrel@webmail.druber.com>


The program I was trying to run didn't have the SUNOS on the end. 
Unfortunately, my VPN to home seems to be down, so I cannot check now.



From rercola at acm.jhu.edu  Mon Jun 11 14:41:49 2012
From: rercola at acm.jhu.edu (Rich)
Date: Mon, 11 Jun 2012 10:41:49 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <3c7b3533f8889472e899ec752e67dac3.squirrel@webmail.druber.com>
References: <58350FC0BE1940039994847849EB1933@manticore>
	<4FD5F084.5070001@cos.ru>
	<3FBC71B0A9B849DB975D19DB25BFE257@manticore>
	<CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com>
	<3c7b3533f8889472e899ec752e67dac3.squirrel@webmail.druber.com>
Message-ID: <CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>

I added that because I have a folder with the Win32/Linux x86/Solaris
x86 binaries all in it; it should be the same file you have.

I'm wondering if there's any problems with executing binaries from the
FS or user you were?

- Rich

On Mon, Jun 11, 2012 at 10:40 AM,  <dswartz at druber.com> wrote:
>
> The program I was trying to run didn't have the SUNOS on the end.
> Unfortunately, my VPN to home seems to be down, so I cannot check now.
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From rercola at acm.jhu.edu  Mon Jun 11 14:50:00 2012
From: rercola at acm.jhu.edu (Rich)
Date: Mon, 11 Jun 2012 10:50:00 -0400
Subject: [OpenIndiana-discuss] Drive compatibility
In-Reply-To: <CAACKFo=1Qa2b2UR7A3cOeGXq7xvQTwZCk-17CjdVCkrscEw4pA@mail.gmail.com>
References: <CAACKFo=1Qa2b2UR7A3cOeGXq7xvQTwZCk-17CjdVCkrscEw4pA@mail.gmail.com>
Message-ID: <CAOeNLuo9juVF_CZAMHgwd9+hDqEsjx+S3_vgnejvixkjcLZJyQ@mail.gmail.com>

I would guess the error you're having involves the devices having
different block sizes.

# ./smartctl -d sat -i /dev/rdsk/c7t5000C5003886DDA4d0s0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda Green (Adv. Format)
Device Model:     ST2000DL003-9VT166
[snip]
Sector Size:      512 bytes logical/physical
# ./smartctl -d sat -i /dev/rdsk/c7t5000C500459476F2d0s0
smartctl 5.42 2011-10-20 r3458 [i386-pc-solaris2.11] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda Green (Adv. Format)
Device Model:     ST2000DL003-9VT166
[snip]
Sector Sizes:     512 bytes logical, 4096 bytes physical


You can also look at zdb's output and see what the ashift value of the
disks in the pool is (it's a 2 << [ashift], so ashift=9 is 512b, =12
is 4096b,etc)

- Rich

On Sat, Jun 9, 2012 at 4:41 PM, Jay Heyl <jay at frelled.us> wrote:
> I had a bit of a hiccup last week with my zfs pool. It's a ten-drive raidz2
> vdev. All the drives are Samsung F4s, though of two slightly different
> models. Two of the drives showed up one morning as "degraded". In somewhat
> of a panic I rushed out and bought a couple Seagate drives as replacements.
> When I tried to do the actual replace operation zfs told me the new drive
> was not compatible with the existing drive array. I don't recall the
> wording of the error message.
>
> I have since learned what I thought was complete disaster was zfs being
> extremely cautious. I ended up clearing the errors and two subsequent
> scrubs have turned up no errors.
>
> Just in case, I bought some more Samsung F4 drives. Last night I installed
> one of them as a spare drive. No problem. Then, since it was still mounted,
> I designated the Seagate drive as a spare. Again, no problem. Since I know
> it doesn't like the Seagate drive for use with this array, this tells me
> mounting a drive as a spare doesn't check to see if the drive will really
> work as a spare.
>
> Is there any way short of actually doing a zpool replace to determine if a
> drive will be truly compatible with an existing vdev?
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From dswartz at druber.com  Mon Jun 11 14:53:59 2012
From: dswartz at druber.com (dswartz at druber.com)
Date: Mon, 11 Jun 2012 10:53:59 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
References: <58350FC0BE1940039994847849EB1933@manticore>
	<4FD5F084.5070001@cos.ru> <3FBC71B0A9B849DB975D19DB25BFE257@manticore>
	<CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com>
	<3c7b3533f8889472e899ec752e67dac3.squirrel@webmail.druber.com>
	<CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
Message-ID: <35441bd39eef12abb63892e248162b00.squirrel@webmail.druber.com>

> I added that because I have a folder with the Win32/Linux x86/Solaris
> x86 binaries all in it; it should be the same file you have.
>
> I'm wondering if there's any problems with executing binaries from the
> FS or user you were?

I was running as root.  I ssh'ed to the OI box, ran 'sudo -i' and went to
the share I had unzipped things into.  Hmmmm...



From dswartz at druber.com  Mon Jun 11 15:12:19 2012
From: dswartz at druber.com (dswartz at druber.com)
Date: Mon, 11 Jun 2012 11:12:19 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
References: <58350FC0BE1940039994847849EB1933@manticore>
	<4FD5F084.5070001@cos.ru> <3FBC71B0A9B849DB975D19DB25BFE257@manticore>
	<CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com>
	<3c7b3533f8889472e899ec752e67dac3.squirrel@webmail.druber.com>
	<CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
Message-ID: <037815cea7c3c15d3f471d63288ea4f9.squirrel@webmail.druber.com>

> I added that because I have a folder with the Win32/Linux x86/Solaris
> x86 binaries all in it; it should be the same file you have.
>
> I'm wondering if there's any problems with executing binaries from the
> FS or user you were?

I seem to recall you see that "Killed" behavior when there is something
the dynamic linker is unhappy about.  I will check whenI get home...



From dswartz at druber.com  Mon Jun 11 16:31:22 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 11 Jun 2012 12:31:22 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
References: <58350FC0BE1940039994847849EB1933@manticore><4FD5F084.5070001@cos.ru><3FBC71B0A9B849DB975D19DB25BFE257@manticore><CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com><3c7b3533f8889472e899ec752e67dac3.squirrel@webmail.druber.com>
	<CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
Message-ID: <F832EAC5BBD3456184EC368F64BC271C@manticore>

Ah, I think I know what happened.  It didn't seem to want me to execute it
while it was on that cifs shared dataset.  No idea why.  I copied it to a
system directory and it runs fine now.  Go figure.  Now I need to figure out
how to use it to figure out what "Target 9" is...

-----Original Message-----
From: Rich [mailto:rercola at acm.jhu.edu] 
Sent: Monday, June 11, 2012 10:42 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] mapping target number to disk?

I added that because I have a folder with the Win32/Linux x86/Solaris
x86 binaries all in it; it should be the same file you have.

I'm wondering if there's any problems with executing binaries from the
FS or user you were?

- Rich

On Mon, Jun 11, 2012 at 10:40 AM,  <dswartz at druber.com> wrote:
>
> The program I was trying to run didn't have the SUNOS on the end.
> Unfortunately, my VPN to home seems to be down, so I cannot check now.
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss



From dswartz at druber.com  Mon Jun 11 16:48:55 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 11 Jun 2012 12:48:55 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
References: <58350FC0BE1940039994847849EB1933@manticore><4FD5F084.5070001@cos.ru><3FBC71B0A9B849DB975D19DB25BFE257@manticore><CAOeNLurHceY0R_Q6vRG27Mi5_kckBY6zMhc-hv9O8qYpG8dYgw@mail.gmail.com><3c7b3533f8889472e899ec752e67dac3.squirrel@webmail.druber.com>
	<CAOeNLuqMsmfjfAZN+d6UPPR-4-9AFiMWGzaQuzB7nSgU5ByPmw@mail.gmail.com>
Message-ID: <938B980BF57B4932BD566B8F05FBAF91@manticore>


Hmmm, nothing obvious leaps out.  Looking at output from sasinfo command:

sasinfo target-port -v

Target Port SAS Address: 50014ee204411a53
    Type: SATA Device
    HBA Port Name: /dev/cfg/c13
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 50014ee0abcee0a9
    Type: SATA Device
    HBA Port Name: /dev/cfg/c6
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 50014ee206ced4ec
    Type: SATA Device
    HBA Port Name: /dev/cfg/c3
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 5000c5000d3c80fd
    Type: SAS Device
    HBA Port Name: /dev/cfg/c10
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 50014ee2af872299
    Type: SATA Device
    HBA Port Name: /dev/cfg/c9
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 5000cca00b078f2d
    Type: SAS Device
    HBA Port Name: /dev/cfg/c8
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 500a07510324d633
    Type: SATA Device
    HBA Port Name: /dev/cfg/c5
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 50014ee25c240034
    Type: SATA Device
    HBA Port Name: /dev/cfg/c2
        Expander Device SAS Address: None (Failed to Get Attached Port)
Target Port SAS Address: 50014ee2aedf73ce
    Type: SATA Device
    HBA Port Name: /dev/cfg/c1
        Expander Device SAS Address: None (Failed to Get Attached Port)

is the integer after /dev/cfg/c in these strings the target number?  If not,
how do I figure this out?



From michelle at msknight.com  Mon Jun 11 17:16:12 2012
From: michelle at msknight.com (michelle)
Date: Mon, 11 Jun 2012 18:16:12 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD59604.9040003@msknight.com>
References: <4FD46A59.5030106@msknight.com>
	<4FD471DB.3040704@msknight.com>	<4FD47769.1050703@msknight.com>
	<4FD486EC.4000405@msknight.com> <4FD4D993.3080901@alum.mit.edu>
	<4FD59604.9040003@msknight.com>
Message-ID: <4FD627DC.9050400@msknight.com>

Someone posted this comment about my description of the problem on YouTube.

Anyone care to comment please?

nope I don't think it does, I think you experiencing 4K and "Advance 
Format" compatibility issues. The solution is a patched version of 
zpool. I am not so sure that OpenIndiana has been updated to included it.


From rennieallen at gmail.com  Mon Jun 11 17:36:38 2012
From: rennieallen at gmail.com (Rennie Allen)
Date: Mon, 11 Jun 2012 10:36:38 -0700
Subject: [OpenIndiana-discuss] Firefox and thunderbird 13 for openindiana
In-Reply-To: <CBF77C61.25574%paolo.marcheschi@ftgm.it>
References: <CBF77C61.25574%paolo.marcheschi@ftgm.it>
Message-ID: <CANrkj=7mRGQus_-OTbZqgCKMafiftqV_fFhZ8-+F30dJGyi-Ag@mail.gmail.com>

Fantastic job!

Thanks!

On Fri, Jun 8, 2012 at 9:46 AM, Paolo Marcheschi
<paolo.marcheschi at ftgm.it>wrote:

> Hi
> here they are :
>
>
> http://releases.mozilla.org/pub/mozilla.org/firefox/releases/13.0/contrib/so
> laris_pkgadd/
>
> http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/13.0/contri
> b/solaris_pkgadd/
>
> get the opensolaris pkgadd one and  bunzip2 it.
> after as superuser :
>
> pkgrm SFWfirefox
>
> pkgadd -d ./firefox-13.0.en-US.opensolaris-i386-pkg
>
> the same for thunderbird:
>
> pkgrm SFWthunderbird
>
> pkgadd -d ./thunderbird-13.0.en-US.opensolaris-i386-pkg
>
> I hope this helps someone.
>
>
> Ciao
>
> Paolo
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>
>
>


-- 
"I hope some animal never bores a hole in my head and lays its eggs in my
brain, because later you might think you're having a good idea but it's
just eggs hatching" - Jack Handy

From jimklimov at cos.ru  Mon Jun 11 18:15:00 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 11 Jun 2012 22:15:00 +0400
Subject: [OpenIndiana-discuss] [discuss] Is it possible to do shared
 networking for LZ different from IP stack in GZ?
In-Reply-To: <DB7C315A-31B3-43C3-A44E-37A369F59D75@nexenta.com>
References: <4FD5F9DA.60509@cos.ru>
	<DB7C315A-31B3-43C3-A44E-37A369F59D75@nexenta.com>
Message-ID: <4FD635A4.20901@cos.ru>

2012-06-11 18:19, Dan McDonald wrote:
2012-06-11 18:47, Sebastien Roy wrote:

DAN> The fundamental question is always:  What problem are you really 
trying to solve?

And as always (or often), it is a valid question.
Technically, there is no immediate problem that I'd solve only
this way, or, likely, that can't be solved by etherstubs and
exclusive VNICs. While writing the Wikidoc I seemingly found a
blind spot not catered for, and wanted to confirm the finding :)

Nevertheless, if someone were to take upon this task, benefits
could be found (I'm not pushing anyone to do it - I don't really
have a usecase so far)...

DAN> Are you trying to increase performance of inter-zone, but 
intra-machine, communication?

Yes, this might be a worthy goal.

SEB> shared-IP zones do indeed have better inter-zone networking
 > performance  (due to IP loopback and tcp-fusion).
 > Exclusive-IP inter-zone performance could be improved, though,
 > if it were made to take advantage of similar fast-paths.

Are you sure? I think its relative slowness was due to isolation
and, for example, different firewalling and requirement of an
external router (including a routing local zone) to connect two
IP subnets - in shared stack two zones from different subnets
can still communicate through the kernel (within the IP stack).

I don't think there is much fast-pathing to shave off, while
still keeping reached the goals of isolation. But the devs
would know better ;)

DAN> Again... what problem are you really trying to solve?
 >  Your theoretical construct of breaking stack instances apart
 >  from zones (or allowing multiple zones on a given stack instance)
>  is interesting theoretically, but I'm not grasping what problem
 >  you're trying to solve.

When you get a hammer, everything would look like a nail ;)

I can try to invent some usecases or "customer stories", but
I have little doubt that if this feature gets imlemented,
people will find problems which are otherwise difficult
or clumsy or under-performant to solve with current methods.

Also, if this is a success, it may be a differentiator from
Oracle Solaris ;)

>>   This is not an RFE per se, but rather food for thought and
>> discussion - did anyone ponder about this? Are there reasons
>> not to do it?
>
DAN> The sheer complexity of implementing, and worse, testing, such
 > a generalization makes it difficult to recommend attempting it, IMHO.

Why? After they made CrossBow and zones and stuff, and actually
made the concept of several IP stacks? Letting several zones
use one common stack now would be, I think, a nearly bite-size
problem in comparison to what has already been achieved.
To me (though a non-developer), it seems like most of the
building blocks are already there.

Basically, if this feature is completed, then the difference
between shared and exclusive stacks would become ephemeral -
with one or more zones using a certain IP stack, and either
dedicated (V)NICs with configs provisioned by the zone, or
aliases of one or more (V)NIC provisioned by zoneadm/zonecfg.
While the GZ would still have the authority to configure the
networking configs of such shared stacks, it would not
necessarily use (be attached to and routed by) one of them
itself.

SEB> It's not possible today, as there is quite a bit of code
 > in the kernel that assumes and enforces the assumptions that
 > the global zone stack is the stack that is shared by shared-IP
 > zones, and that only global zone processes have the ability to
 > manipulate configuration for that stack.

Is it very difficult to find to rewrite that code to use and
reference the ip_stack[0] instead? ;)

But, anyway, thanks to both of you for the discussion.
Everyone is still welcome to chime in ;)
//Jim Klimov


From jimklimov at cos.ru  Mon Jun 11 18:31:25 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 11 Jun 2012 22:31:25 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD627DC.9050400@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com>
Message-ID: <4FD6397D.7080507@cos.ru>

2012-06-11 21:16, michelle wrote:
> Someone posted this comment about my description of the problem on YouTube.
>
> Anyone care to comment please?
>
> nope I don't think it does, I think you experiencing 4K and "Advance
> Format" compatibility issues. The solution is a patched version of
> zpool. I am not so sure that OpenIndiana has been updated to included it.

Well, this is another wording for what I suggested about
older 512 byte-per-sector disks and newer 4KB-per-sector
ones which often emulate and announce 512 bytes-per-sector.
Replacing such older disks with such newer disks is not
a good idea, and while it may be possible, it can lead
to worse performance and heavier corruptions (writing
into a 512B sector requires the disk to read and rewrite
whole 4KB, while breakage of one 4KB native sector breaks
8 emulates 512B sectors).

As for the patched zpool, there are blogs which describe
the issue and publish the updated code and binary. Indeed,
for a number of reasons the fix did not make it into OI
distro, AFAIK. Basically, this part of the issue is that
ZFS trusts what the disk says is its native sector size.
If the disk emulates 512BpS and misleadingly announces
that as the native sector size (which many cheaper drives
apparently do), then ZFS creates pool with an ashift=9
parameter (2^9 = 512), while it should really have used
ashift=12 (2^12 = 4096). For disks which do not lie, it
works properly out of the box. The patched zpool binary
forced ashift=12 at the user's discretion.

HTH,
//Jim Klimov



From jimklimov at cos.ru  Mon Jun 11 18:50:40 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 11 Jun 2012 22:50:40 +0400
Subject: [OpenIndiana-discuss] [discuss] Is it possible to do shared
 networking for LZ different from IP stack in GZ?
In-Reply-To: <DB7C315A-31B3-43C3-A44E-37A369F59D75@nexenta.com>
References: <4FD5F9DA.60509@cos.ru>
	<DB7C315A-31B3-43C3-A44E-37A369F59D75@nexenta.com>
Message-ID: <4FD63E00.7040505@cos.ru>

2012-06-11 18:19, Dan McDonald wrote:
> The fundamental question is always:  What problem are you really trying to solve?

Okay, I found another rationale beside performance and simplified
intra-zone routing (though not as apparent as exclusive routing).
It seems that the shared IP stack offer better protection against
sniffing on colocated environments (i.e. zone-based hosting): it
is not allowed to use promiscuous mode on NIC aliases used in the
shared stack, while sniffing does work on exclusive VNICs.

That might be a serious difference in some cases...

HTH,
//Jim Klimov


From dswartz at druber.com  Mon Jun 11 19:15:22 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 11 Jun 2012 15:15:22 -0400
Subject: [OpenIndiana-discuss] mapping target number to disk?
In-Reply-To: <4FD64204.4080802@cos.ru>
References: <58350FC0BE1940039994847849EB1933@manticore>
	<4FD64204.4080802@cos.ru>
Message-ID: <896883FC0DEC45E58D8E5FDDF09ED322@manticore>

Thanks, Jim!  The WWN would be good enough, since all my drives (in the data
pool anyway) have the WWN printed on the top :)

-----Original Message-----
From: Jim Klimov [mailto:jim at cos.ru] 
Sent: Monday, June 11, 2012 3:08 PM
To: Discussion list for OpenIndiana
Cc: Dan Swartzendruber
Subject: Re: [OpenIndiana-discuss] mapping target number to disk?

2012-06-11 17:10, Dan Swartzendruber wrote:
> I've been seeing a ton of messages like:
>
>
>
> Jun 11 08:59:08 nas     Log info 0x31120303 received for target 9.
>
> Jun 11 08:59:08 nas     scsi_status=0x0, ioc_status=0x804b, scsi_state=0xc
>
> Jun 11 08:59:08 nas scsi: [ID 365881 kern.info]
> /pci at 0,0/pci8086,27d0 at 1c/pci1000,3040 at 0 (mpt_sas10):
>

Actually, re-reading that original post, I have some more ideas :)
Methods 1 and 2 can help you find the OS device name that it is
complaining about. Method 3 can help find the serial number of
the disk, which should help to physically locate it.

1) Run the "format" command to list the drives. You might see
    the /pci... device string there, i.e.:
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
        0. c0t0d0 <ATA-SEAGATE ST32500N-3AZQ-232.88GB>
           /pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 0,0
        1. c0t1d0 <ATA-SEAGATE ST32500N-3AZQ-232.88GB>
           /pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
     ....

2) Run a listing of /dev/dsk and grep for the device path, i.e.:
    # ls -la /dev/dsk | grep pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
lrwxrwxrwx   1 root     root          63 Jul 14  2009 c0t1d0 -> 
../../devices/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0:wd
lrwxrwxrwx   1 root     root          62 Jul 14  2009 c0t1d0p0 -> 
../../devices/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0:q
...
lrwxrwxrwx   1 root     root          62 Jul 14  2009 c0t1d0s9 -> 
../../devices/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0:j



3) Search the /var/adm/messages* logs for the device path,
    this may yield the hardware details (like smartctl might).
    If your log rotation works, this may need to be done soon
    after boot, or after a pool import. Example:

# cat /var/adm/messages* | ggrep -A12 -B1 
pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
May 16 03:11:48 thumper scsi: [ID 583861 kern.info] sd10 at 
marvell88sx0: target 1 lun 0
May 16 03:11:48 thumper genunix: [ID 936769 kern.info] sd10 is 
/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0
May 16 03:11:48 thumper genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1/disk at 1,0 (sd10) online
May 16 03:11:48 thumper sata: [ID 663010 kern.info] 
/pci at 0,0/pci1022,7458 at 1/pci11ab,11ab at 1 :
May 16 03:11:48 thumper sata: [ID 761595 kern.info]     SATA disk device 
at port 2
May 16 03:11:48 thumper sata: [ID 846691 kern.info]     model SEAGATE 
ST32500NSSUN250G 0743B590GG
May 16 03:11:48 thumper sata: [ID 693010 kern.info]     firmware     3AZQ
May 16 03:11:48 thumper sata: [ID 163988 kern.info]     serial number 
5QE590GG
May 16 03:11:48 thumper sata: [ID 594940 kern.info]     supported features:
May 16 03:11:48 thumper sata: [ID 981177 kern.info]      48-bit LBA, 
DMA, Native Command Queueing, SMART, SMART self-test
May 16 03:11:48 thumper sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
May 16 03:11:48 thumper sata: [ID 349649 kern.info]     Supported queue 
depth 32
May 16 03:11:48 thumper sata: [ID 349649 kern.info]     capacity = 
488390625 sectors
...

HTH,
//Jim Klimov



From jimklimov at cos.ru  Mon Jun 11 19:37:58 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 11 Jun 2012 23:37:58 +0400
Subject: [OpenIndiana-discuss] [discuss] Is it possible to do shared
 networking for LZ different from IP stack in GZ?
In-Reply-To: <4FD63FB6.4020409@joyent.com>
References: <4FD5F9DA.60509@cos.ru>
	<DB7C315A-31B3-43C3-A44E-37A369F59D75@nexenta.com>
	<4FD63E00.7040505@cos.ru> <4FD63FB6.4020409@joyent.com>
Message-ID: <4FD64916.9090208@cos.ru>

2012-06-11 22:57, Robert Mustacchi wrote:
> This isn't a problem. When you promiscuously sniff traffic on a VNIC
> regardless of zone, you only get the following:
>
> * unicast traffic with your zones MAC address
Okay, one problem less, maybe

> * Broadcast and multicast traffic
This might expose some knowledge about the network, i.e.
CIFS host and domain names, which may be undesirable as
a minor aid to a hacker researching the network.

Also, since an exclusive-IP zone can set any IP addresses,
it is free to disrupt your LAN or hijack some services by
trying to capture used addresses. On a shared stack the
addressing and routing is enforced from outside the zone
by the GZ admins.

Can that count in favor of enhancing the shared stack
usability when I don't want the hypervisor (GZ) on the
same net as the end-users' restricted local zones? ;)

Now, we're getting closer to what Dan wanted - a user story :)

>
> Specifically if you create a vnic over an underlying physical NIC you do
> not see all the traffic of the underlying device. See
> http://src.illumos.org/source/xref/illumos-gate/usr/src/uts/common/io/mac/mac_client.c#3134.
> VNICs are always of type MAC_CLIENT_PROMISC_FILTERED.

Thanks,
//Jim Klimov



From carlsonj at workingcode.com  Mon Jun 11 20:32:22 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Mon, 11 Jun 2012 16:32:22 -0400
Subject: [OpenIndiana-discuss] [discuss] Is it possible to do shared
 networking for LZ different from IP stack in GZ?
In-Reply-To: <4FD63E00.7040505@cos.ru>
References: <4FD5F9DA.60509@cos.ru>	<DB7C315A-31B3-43C3-A44E-37A369F59D75@nexenta.com>
	<4FD63E00.7040505@cos.ru>
Message-ID: <4FD655D6.3090400@workingcode.com>

Jim Klimov wrote:
> 2012-06-11 18:19, Dan McDonald wrote:
>> The fundamental question is always:  What problem are you really
>> trying to solve?
> 
> Okay, I found another rationale beside performance and simplified
> intra-zone routing (though not as apparent as exclusive routing).
> It seems that the shared IP stack offer better protection against
> sniffing on colocated environments (i.e. zone-based hosting): it
> is not allowed to use promiscuous mode on NIC aliases used in the
> shared stack, while sniffing does work on exclusive VNICs.
> 
> That might be a serious difference in some cases...

Yanking away PRIV_NET_RAWACCESS and PRIV_NET_OBSERVABILITY ought to
prevent sniffing.  (I haven't tested, though, to see what else breaks,
as that seems to be a cruel thing to do to zone administrators.)

For what it's worth (and having worked on the code in the now-distant
past), I certainly agree with you at a high level.  What you're
describing is an "obvious" generalization of the exclusive stack
concept.  It was "obvious" enough that we actually discussed it
internally when the feature was being added.  Testing complexity and
lack of a clear use-case were the main factors in deciding not to
generalize.

A related factor was feedback from the field.  The addition of exclusive
stacks was done because customers told Sun that they did not or could
not use shared stacks at all, and they adamantly didn't want to share.
Well, with no desire to share, that makes the implementation simpler; it
becomes just an on/off flag rather than a multi-valued and
reference-counted beast.

Depending on what you're trying to accomplish, there may be other ways
to go about providing higher-performance data paths between zones.  One
is by communicating between zones via shared (loopback-mounted) file
systems.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From carlsonj at workingcode.com  Mon Jun 11 20:46:04 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Mon, 11 Jun 2012 16:46:04 -0400
Subject: [OpenIndiana-discuss] [discuss] Is it possible to do shared
 networking for LZ different from IP stack in GZ?
In-Reply-To: <4FD655D6.3090400@workingcode.com>
References: <4FD5F9DA.60509@cos.ru>	<DB7C315A-31B3-43C3-A44E-37A369F59D75@nexenta.com>	<4FD63E00.7040505@cos.ru>
	<4FD655D6.3090400@workingcode.com>
Message-ID: <4FD6590C.6050103@workingcode.com>

James Carlson wrote:
> For what it's worth (and having worked on the code in the now-distant
> past), I certainly agree with you at a high level.  What you're
> describing is an "obvious" generalization of the exclusive stack
> concept.  It was "obvious" enough that we actually discussed it
> internally when the feature was being added.  Testing complexity and
> lack of a clear use-case were the main factors in deciding not to
> generalize.

A good amount of the architectural discussion is still available on-line:

http://arc.opensolaris.org/caselog/PSARC/2006/366/

(At least, I guess, until someone notices ...)

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From hans.j.albertsson at branneriet.se  Mon Jun 11 22:39:32 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Tue, 12 Jun 2012 00:39:32 +0200
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to new
	one. only one system available
In-Reply-To: <mailman.7717.1339447568.9998.openindiana-discuss@openindiana.org>
References: <mailman.7717.1339447568.9998.openindiana-discuss@openindiana.org>
Message-ID: <4FD673A4.5030604@branneriet.se>

Suppose:

I have a system with but two disks. They're fairly small: 300GB, and use 
512B sectors.

These two disks are a mirror zpool, creqated from the entire disks.

There are about 20 or so filesystems in there.

The system has room for only two disks.

I'd like to replace these two small disks with two 2TB disks using 4kB 
blocks.

So:

Is there a writeup on how to connect one of these new disks to the 
existing machine, using an external esata cabinet.
set up a new zpool on this new disk, and transfer all the root pool data 
to the new single disk zpool.
then set up the new zpool to be bootable.
And last: taking the old disks out of the machine, place the new single 
disk, and another, empty, similar 2TB disk in the machine, and boot from 
the single new one as the new root zpool. And then add the second new 
disk as a mirror.. effectively running the old system exactly as it was 
w/o reinstalling anything significant, but with much roomier disks.

Note: in this case there is no way to get another system to do it on. 
And a third disk can only be connected using an external cabinet and 
Esata or USB.





From james.c.mcpherson at gmail.com  Mon Jun 11 23:12:32 2012
From: james.c.mcpherson at gmail.com (James C. McPherson)
Date: Tue, 12 Jun 2012 09:12:32 +1000
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD673A4.5030604@branneriet.se>
References: <mailman.7717.1339447568.9998.openindiana-discuss@openindiana.org>
	<4FD673A4.5030604@branneriet.se>
Message-ID: <4FD67B60.70909@gmail.com>

On 12/06/12 08:39 AM, Hans J. Albertsson wrote:
> Suppose:
>
> I have a system with but two disks. They're fairly small: 300GB, and use 512B sectors.
>
> These two disks are a mirror zpool, creqated from the entire disks.
>
> There are about 20 or so filesystems in there.
>
> The system has room for only two disks.
>
> I'd like to replace these two small disks with two 2TB disks using 4kB blocks.
>
> So:
>
> Is there a writeup on how to connect one of these new disks to the existing machine, using an external esata cabinet.
> set up a new zpool on this new disk, and transfer all the root pool data to the new single disk zpool.
> then set up the new zpool to be bootable.
> And last: taking the old disks out of the machine, place the new single disk, and another, empty, similar 2TB disk in the machine, and boot from the single new one as the new root zpool. And then add the second new disk as a mirror.. effectively running the old system exactly as it was w/o reinstalling anything significant, but with much roomier disks.
>
> Note: in this case there is no way to get another system to do it on. And a third disk can only be connected using an external cabinet and Esata or USB.

Hi Hans,
I suggest this:

#1 set autoexpand=on for rpool
#2 connect your esata enclosure
#3 once you've got them sliced up as desired (I suggest slice 0 should cover all
    except cylinders 0 and 1), run installgrub on both new disks, to the mbr
#4 zpool replace one of your rpool disks
#5 zpool replace the other rpool disk
#6 poweroff
#7 do the physical replacement
#8 poweron



James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
               http://www.jmcp.homeunix.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson



From rercola at acm.jhu.edu  Mon Jun 11 23:16:55 2012
From: rercola at acm.jhu.edu (Rich)
Date: Mon, 11 Jun 2012 19:16:55 -0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD67B60.70909@gmail.com>
References: <mailman.7717.1339447568.9998.openindiana-discuss@openindiana.org>
	<4FD673A4.5030604@branneriet.se> <4FD67B60.70909@gmail.com>
Message-ID: <CAOeNLurttyXPbctAw-_0oAy62tTaE_AXqSwJsRDJfgThQ9xvoA@mail.gmail.com>

Won't zpool replace fail b/c the new disks require ashift=12 and his
existing pool devices have ashift=9?

- Rich

On Mon, Jun 11, 2012 at 7:12 PM, James C. McPherson
<james.c.mcpherson at gmail.com> wrote:
> On 12/06/12 08:39 AM, Hans J. Albertsson wrote:
>>
>> Suppose:
>>
>> I have a system with but two disks. They're fairly small: 300GB, and use
>> 512B sectors.
>>
>> These two disks are a mirror zpool, creqated from the entire disks.
>>
>> There are about 20 or so filesystems in there.
>>
>> The system has room for only two disks.
>>
>> I'd like to replace these two small disks with two 2TB disks using 4kB
>> blocks.
>>
>> So:
>>
>> Is there a writeup on how to connect one of these new disks to the
>> existing machine, using an external esata cabinet.
>> set up a new zpool on this new disk, and transfer all the root pool data
>> to the new single disk zpool.
>> then set up the new zpool to be bootable.
>> And last: taking the old disks out of the machine, place the new single
>> disk, and another, empty, similar 2TB disk in the machine, and boot from the
>> single new one as the new root zpool. And then add the second new disk as a
>> mirror.. effectively running the old system exactly as it was w/o
>> reinstalling anything significant, but with much roomier disks.
>>
>> Note: in this case there is no way to get another system to do it on. And
>> a third disk can only be connected using an external cabinet and Esata or
>> USB.
>
>
> Hi Hans,
> I suggest this:
>
> #1 set autoexpand=on for rpool
> #2 connect your esata enclosure
> #3 once you've got them sliced up as desired (I suggest slice 0 should cover
> all
> ? except cylinders 0 and 1), run installgrub on both new disks, to the mbr
> #4 zpool replace one of your rpool disks
> #5 zpool replace the other rpool disk
> #6 poweroff
> #7 do the physical replacement
> #8 poweron
>
>
>
> James C. McPherson
> --
> Solaris kernel software engineer, system admin and troubleshooter
> ? ? ? ? ? ? ?http://www.jmcp.homeunix.com/blog
> Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
>
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From james.c.mcpherson at gmail.com  Mon Jun 11 23:55:29 2012
From: james.c.mcpherson at gmail.com (James C. McPherson)
Date: Tue, 12 Jun 2012 09:55:29 +1000
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <CAOeNLurttyXPbctAw-_0oAy62tTaE_AXqSwJsRDJfgThQ9xvoA@mail.gmail.com>
References: <mailman.7717.1339447568.9998.openindiana-discuss@openindiana.org>
	<4FD673A4.5030604@branneriet.se> <4FD67B60.70909@gmail.com>
	<CAOeNLurttyXPbctAw-_0oAy62tTaE_AXqSwJsRDJfgThQ9xvoA@mail.gmail.com>
Message-ID: <4FD68571.4090209@gmail.com>

On 12/06/12 09:16 AM, Rich wrote:
> Won't zpool replace fail b/c the new disks require ashift=12 and his
> existing pool devices have ashift=9?

I have no idea. I don't think it's too much of a stretch to
assume that an error provided during zpool replace would result
in a quick response to the list saying "that didn't work, now what?"
or something similar.


James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
               http://www.jmcp.homeunix.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson



From bfriesen at simple.dallas.tx.us  Tue Jun 12 01:08:12 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Mon, 11 Jun 2012 20:08:12 -0500 (CDT)
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD6397D.7080507@cos.ru>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
Message-ID: <alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>

On Mon, 11 Jun 2012, Jim Klimov wrote:
> ashift=12 (2^12 = 4096). For disks which do not lie, it
> works properly out of the box. The patched zpool binary
> forced ashift=12 at the user's discretion.

It seems like new pools should provide the option to be created with 
ashift=12 even if none of the original disks need it.  The reason is 
to allow adding 4K sector disks later.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From richard.elling at richardelling.com  Tue Jun 12 04:50:14 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Mon, 11 Jun 2012 21:50:14 -0700
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
Message-ID: <BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>

On Jun 11, 2012, at 6:08 PM, Bob Friesenhahn wrote:

> On Mon, 11 Jun 2012, Jim Klimov wrote:
>> ashift=12 (2^12 = 4096). For disks which do not lie, it
>> works properly out of the box. The patched zpool binary
>> forced ashift=12 at the user's discretion.
> 
> It seems like new pools should provide the option to be created with ashift=12 even if none of the original disks need it.  The reason is to allow adding 4K sector disks later.

I don't disagree, in principle. However, history has shown that people don't plan very well
(eg, reason #1 dedup exists). Is there some other way to be more clever?
 -- richard

-- 

ZFS storage and performance consulting at http://www.RichardElling.com








From rercola at acm.jhu.edu  Tue Jun 12 04:58:03 2012
From: rercola at acm.jhu.edu (Rich)
Date: Tue, 12 Jun 2012 00:58:03 -0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
Message-ID: <CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>

On Tue, Jun 12, 2012 at 12:50 AM, Richard Elling
<richard.elling at richardelling.com> wrote:
> On Jun 11, 2012, at 6:08 PM, Bob Friesenhahn wrote:
>
>> On Mon, 11 Jun 2012, Jim Klimov wrote:
>>> ashift=12 (2^12 = 4096). For disks which do not lie, it
>>> works properly out of the box. The patched zpool binary
>>> forced ashift=12 at the user's discretion.
>>
>> It seems like new pools should provide the option to be created with ashift=12 even if none of the original disks need it. ?The reason is to allow adding 4K sector disks later.
>
> I don't disagree, in principle. However, history has shown that people don't plan very well
> (eg, reason #1 dedup exists). Is there some other way to be more clever?
> ?-- richard

I believe that the consensus the last time this came up was agreement
on that point, but contention over how the semantics of specifying it
should work?


From hans.j.albertsson at branneriet.se  Tue Jun 12 07:00:20 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Tue, 12 Jun 2012 09:00:20 +0200
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD68571.4090209@gmail.com>
References: <mailman.7717.1339447568.9998.openindiana-discuss@openindiana.org>
	<4FD673A4.5030604@branneriet.se> <4FD67B60.70909@gmail.com>
	<CAOeNLurttyXPbctAw-_0oAy62tTaE_AXqSwJsRDJfgThQ9xvoA@mail.gmail.com>
	<4FD68571.4090209@gmail.com>
Message-ID: <4FD6E904.4050903@branneriet.se>

We know, from people like Michelle on HDD problems, recently, that just 
adding an ashift=12 disk to a pool with ashift=9 won't work.



On 2012-06-12 01:55, James C. McPherson wrote:
> On 12/06/12 09:16 AM, Rich wrote:
>> Won't zpool replace fail b/c the new disks require ashift=12 and his
>> existing pool devices have ashift=9?
>
> I have no idea. I don't think it's too much of a stretch to
> assume that an error provided during zpool replace would result
> in a quick response to the list saying "that didn't work, now what?"
> or something similar.
>
>
> James C. McPherson
> --
> Solaris kernel software engineer, system admin and troubleshooter
>               http://www.jmcp.homeunix.com/blog
> Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson


From michelle at msknight.com  Tue Jun 12 07:24:09 2012
From: michelle at msknight.com (michelle)
Date: Tue, 12 Jun 2012 08:24:09 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
Message-ID: <4FD6EE99.2010705@msknight.com>

Is there a way for the system to me a bit more clever; we have 4k 
sectors now but how long before that is upped again; maybe another decade?

After all, if it is a redundant set, what is the reason why it can't 
just dump the disk to be replaced and rebuild on the new drive?

I know I'm being a noob here as I don't have the in depth knowledge of 
many people on this list ... but from my "user" perspective, it strikes 
me that this is the more obvious question.


From pepeshopping at gmail.com  Tue Jun 12 11:40:20 2012
From: pepeshopping at gmail.com (J. V.)
Date: Tue, 12 Jun 2012 07:40:20 -0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
Message-ID: <CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>

On 12/06/12 09:16 AM, Rich wrote:
> Won't zpool replace fail b/c the new disks require ashift=12 and his
> existing pool devices have ashift=9?

This should work fine:

HP Microserver, upgrading a mirrored pool from 2TB HDs to 3TB HDs. At one
point, the pool had one 2TB HD with 512 sectors and the other with 4k
sectors (both in a mirror). Seems there was a bit of a performance hit, but
everything worked fine.

When I upgraded from 2TB to 3TB, the 3TB HDs were both 4k sectors:

- poweroff
- Exchange ONE 2TB HD for a 3TB.
- Power on. Wait for resilver.
- poweroff
- Exchange the other 2TB with 3TB.
- Power on. Wait for resilver.

(My pool had autoexpand = off. I am using napp-it so I simply went into the
Web interface and changed it to ON).
3TB, 4k sec mirror ready.

Cheers.

Jose V.

From jimklimov at cos.ru  Tue Jun 12 12:00:33 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 12 Jun 2012 16:00:33 +0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
	<CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>
Message-ID: <4FD72F61.9010004@cos.ru>

2012-06-12 15:40, J. V. ?????:
> On 12/06/12 09:16 AM, Rich wrote:
>> Won't zpool replace fail b/c the new disks require ashift=12 and his
>> existing pool devices have ashift=9?
>
> This should work fine:
>
> HP Microserver, upgrading a mirrored pool from 2TB HDs to 3TB HDs. At one
> point, the pool had one 2TB HD with 512 sectors and the other with 4k
> sectors (both in a mirror). Seems there was a bit of a performance hit, but
> everything worked fine.
>
> When I upgraded from 2TB to 3TB, the 3TB HDs were both 4k sectors:

Did the 3TB disk also report to the OS that it uses 4k sectors?
What ashift value is used by the pool, ultimately? Example:
# zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
         ashift: 9
         ashift: 9
         ashift: 9
         ashift: 9

If your 4KB disks use ashift=9 it is possible to get problems
worse than decreased performance ;)

Note that the ashift is set on a top-level vdev (the second-tier
component of a pool) and the value is saved into/read from its
vdevs (edge-tier components), and a pool can mix top-level vdevs
with different ashifts, i.e. if it is a raid10 type of setup.

PS: Do you use an HP N40L? Did you test if more than 8Gb RAM
can fit into it (using DDR3 ECC sticks larger than 4Gb), or
does the server's BIOS forbid that?

HTH,
//Jim Klimov


From jimklimov at cos.ru  Tue Jun 12 12:12:37 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 12 Jun 2012 16:12:37 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD6EE99.2010705@msknight.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
	<4FD6EE99.2010705@msknight.com>
Message-ID: <4FD73235.2010409@cos.ru>

2012-06-12 11:24, michelle wrote:
> Is there a way for the system to me a bit more clever; we have 4k
> sectors now but how long before that is upped again; maybe another decade?
>
> After all, if it is a redundant set, what is the reason why it can't
> just dump the disk to be replaced and rebuild on the new drive?
>
> I know I'm being a noob here as I don't have the in depth knowledge of
> many people on this list ... but from my "user" perspective, it strikes
> me that this is the more obvious question.

You can look in the zfs-discuss list archives of the past month,
I asked about how scrubbing and resilvers work, dumping my
understanding onto the list and asking for corrections :)

Basically, a redundant/striped ZFS data block is striped over
several sectors of hard disks, with chunk sizes based on the
ashift value. Rebuilding the same pool onto a new disk requires
that these chunks have the same size - even if they no longer
match (are smaller than) native sector size, leading to various
possible problems regarding performance and reliability.

On the other hand, chunks larger than the typical metadata
block size (of which there are plenty in ZFS), even these 4KB
minimal writes, bump the pool's storage overheads considerably.
Many people have noticed the inflation of consumed disk space
when migrating their data from an old pool onto a new one.
But this is unnoticeable on Windows and other dominant OSes
which use 4KB cluster/block sizes by default for many years
now, and HW RAID controllers often use yet larger "chunks"
ranging 16-64KB to lay out userdata onto RAIDed disks.

That's the short story :)
//Jim Klimov


From gary at genashor.com  Tue Jun 12 12:45:06 2012
From: gary at genashor.com (Gary Gendel)
Date: Tue, 12 Jun 2012 08:45:06 -0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD72F61.9010004@cos.ru>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
	<CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>
	<4FD72F61.9010004@cos.ru>
Message-ID: <4FD739D2.9060900@genashor.com>

On 6/12/12 8:00 AM, Jim Klimov wrote:
>
> Did the 3TB disk also report to the OS that it uses 4k sectors?
> What ashift value is used by the pool, ultimately? Example:
> # zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
>         ashift: 9
>         ashift: 9
>         ashift: 9
>         ashift: 9
>
> If your 4KB disks use ashift=9 it is possible to get problems
> worse than decreased performance ;)

I'm a bit confused.  I checked my mirrored Seagate ST33000651AS 3TB 
drives using this method and I see "ashift: 9".  I'm sure that the 
Seagates told them it had 512 sectors, but I thought that you couldn't 
see the whole 3TBs with 512 sectors.  I have these striped with a 1TB 
mirrored drive in the pool and zpool list shows 3.62T which seems about 
right.  Is my understanding flawed?

Gary



From richard.elling at richardelling.com  Tue Jun 12 12:55:54 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Tue, 12 Jun 2012 05:55:54 -0700
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
Message-ID: <57FA5437-B050-490A-B4F9-F886AD83CE3D@RichardElling.com>

On Jun 11, 2012, at 9:58 PM, Rich wrote:

> On Tue, Jun 12, 2012 at 12:50 AM, Richard Elling
> <richard.elling at richardelling.com> wrote:
>> On Jun 11, 2012, at 6:08 PM, Bob Friesenhahn wrote:
>> 
>>> On Mon, 11 Jun 2012, Jim Klimov wrote:
>>>> ashift=12 (2^12 = 4096). For disks which do not lie, it
>>>> works properly out of the box. The patched zpool binary
>>>> forced ashift=12 at the user's discretion.
>>> 
>>> It seems like new pools should provide the option to be created with ashift=12 even if none of the original disks need it.  The reason is to allow adding 4K sector disks later.
>> 
>> I don't disagree, in principle. However, history has shown that people don't plan very well
>> (eg, reason #1 dedup exists). Is there some other way to be more clever?
>>  -- richard
> 
> I believe that the consensus the last time this came up was agreement
> on that point, but contention over how the semantics of specifying it
> should work?

For illumos, this is solved by overriding the physical block size parameter
in the sd.conf file.

The answer to "will it work" depends on the logical block size reported by the drive.

The answer to "will it work with best efficiency" depends on the physical block
size reported by the drive. No surprises here.
 -- richard

-- 

ZFS storage and performance consulting at http://www.RichardElling.com








From pepeshopping at gmail.com  Tue Jun 12 13:02:31 2012
From: pepeshopping at gmail.com (J. V.)
Date: Tue, 12 Jun 2012 09:02:31 -0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD72F61.9010004@cos.ru>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
	<CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>
	<4FD72F61.9010004@cos.ru>
Message-ID: <CACxtc7x2g8Fu9LsniD9bf7GhAZbBG6VMJaP3mE--g4FXKmjCbg@mail.gmail.com>

I did check the ashift after the upgrade and both 3TB HDs report ashift=12.

I am actually using an HP N35L (1.3 Ghz vs. 1.5 GHz in the N40L) and I have
8 GB of non-ECC DDR3 so I could not answer the memory question.

These little machines are really great (If they came with SATA 3, they
would be the ultimate small server):
I do have an N40L with ESXi 5 running my firewall/router (Untangle 9.2) and
Windows Home Server 2011 (For the Media Server, Backup and WSUS services)..

The OpenIndiana server has 6 HDs (loaded modified BIOS so the extra
internal and external SATA ports run at full speeds):
4 x 3TB Seagate ST3000DM001 (Newer Seagates: Fastest 7200 rpm HD right now
... ~140 MB on SATA 2, ~160 on SATA 3).
2 x OCZ 60 GB SSD (Agility 3). Mounted where the CD-ROM would go with a Vantec
5 1/4, 2 x 2.5 in. (Used an eSATA to SATA cable for one of the SSDs).

Config:
Partitioned the SSDs in 3 slices:
rpool (16GB), zil1 (4GB), arc1 (~40GB)
rpool (16GB), zil2 (4GB), arc2 (~40GB)

rpool = 2 x 16GB mirrored
Storage pool 1 = 2 x 3TB mirrored + zil1 + arc1
Storage pool 2 = 2 x 3TB mirrored + zil2 + arc2

The mirrored rpool saved my butt last month when I was playing around and
over-wrote the boot rpool (gets confusing between slices and partitions
with my SSD config). Took me whole 20 min. to fix it:
Exchange SSD places, boot from good rpool, wait 5 min. for resilver,
re-install grub in damaged rpool, poweroff, exchange SSDs again).

No other dual cpu machine that I have uses less power:
The whole server only uses 23, 24 Watts when idle (2 SSDs active, 4 HDs
powered-down).
35 W with 1 pool active (2 SSDs, 2 HDs active)
~50 W with all HDs active and getting hammered.

Once I added zil + arc to the pools, the little thing runs at wire speeds:
Could not get any better!

It took me months to start gathering the hardware and fully learn ZFS,
but I am really glad to be back running a Solaris derivative: I started in
college administering Ultrix, Sun-OS, AIX, NeXTStep and others. Then later
I went to the dark side to learn all about MS, and finally feel back at
home with OpenIndiana!

Thanks to the IllumOS people and contributors here and everywhere else!

(Sorry for the long post. Hope my full config can help/inspire others).

Jose V.

On Tue, Jun 12, 2012 at 8:00 AM, Jim Klimov <jimklimov at cos.ru> wrote:

> 2012-06-12 15:40, J. V. ?????:
>
>  On 12/06/12 09:16 AM, Rich wrote:
>>
>>> Won't zpool replace fail b/c the new disks require ashift=12 and his
>>> existing pool devices have ashift=9?
>>>
>>
>> This should work fine:
>>
>> HP Microserver, upgrading a mirrored pool from 2TB HDs to 3TB HDs. At one
>> point, the pool had one 2TB HD with 512 sectors and the other with 4k
>> sectors (both in a mirror). Seems there was a bit of a performance hit,
>> but
>> everything worked fine.
>>
>> When I upgraded from 2TB to 3TB, the 3TB HDs were both 4k sectors:
>>
>
> Did the 3TB disk also report to the OS that it uses 4k sectors?
> What ashift value is used by the pool, ultimately? Example:
> # zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
>        ashift: 9
>        ashift: 9
>        ashift: 9
>        ashift: 9
>
> If your 4KB disks use ashift=9 it is possible to get problems
> worse than decreased performance ;)
>
> Note that the ashift is set on a top-level vdev (the second-tier
> component of a pool) and the value is saved into/read from its
> vdevs (edge-tier components), and a pool can mix top-level vdevs
> with different ashifts, i.e. if it is a raid10 type of setup.
>
> PS: Do you use an HP N40L? Did you test if more than 8Gb RAM
> can fit into it (using DDR3 ECC sticks larger than 4Gb), or
> does the server's BIOS forbid that?
>
> HTH,
> //Jim Klimov
>

From jimklimov at cos.ru  Tue Jun 12 13:32:01 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 12 Jun 2012 17:32:01 +0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD739D2.9060900@genashor.com>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
	<CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>
	<4FD72F61.9010004@cos.ru> <4FD739D2.9060900@genashor.com>
Message-ID: <4FD744D1.1020807@cos.ru>

2012-06-12 16:45, Gary Gendel wrote:
> On 6/12/12 8:00 AM, Jim Klimov wrote:
>>
>> Did the 3TB disk also report to the OS that it uses 4k sectors?
>> What ashift value is used by the pool, ultimately? Example:
>> # zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
>>         ashift: 9
>>         ashift: 9
>>         ashift: 9
>>         ashift: 9
>>
>> If your 4KB disks use ashift=9 it is possible to get problems
>> worse than decreased performance ;)
>
> I'm a bit confused.  I checked my mirrored Seagate ST33000651AS 3TB
> drives using this method and I see "ashift: 9".  I'm sure that the
> Seagates told them it had 512 sectors, but I thought that you couldn't
> see the whole 3TBs with 512 sectors.  I have these striped with a 1TB
> mirrored drive in the pool and zpool list shows 3.62T which seems about
> right.  Is my understanding flawed?

I failed to find the specs on the Seagate site which would state
that this model uses 512B or 4KB sectors, or the Advanced Format.
I thought that only Hitachi Desk/Ultra-Stars had 3TB disks with
512B native sectors (and 4TB models are Advanced-Formatted too),
but that is not definitive. Maybe Seagate did that, maybe not.

As for "ability to see", that's related to the disk size and
the partitioning table used (GPT vs. older MBR, which can only
address 2TB max), and not to the native sector size.

As for the striped pool size - it seems about right.
My 3TB disk is 2.72T, so a 4TB set being 3.6T seems okay.
The raid10 mix also can have mixed ashifts, i.e. using ashift=12
for the 3TB disks and ashift=9 for 1TB disks, if that's configured.

Is your 1TB disk mirrored? Otherwise its single failure can bring
the whole pool down.

HTH,
//Jim


From jimklimov at cos.ru  Tue Jun 12 13:39:13 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 12 Jun 2012 17:39:13 +0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD744D1.1020807@cos.ru>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
	<CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>
	<4FD72F61.9010004@cos.ru> <4FD739D2.9060900@genashor.com>
	<4FD744D1.1020807@cos.ru>
Message-ID: <4FD74681.6040501@cos.ru>

2012-06-12 17:32, Jim Klimov wrote:
>> I have these striped with a 1TB mirrored drive
> Is your 1TB disk mirrored? Otherwise its single failure can bring
> the whole pool down.

Scratch that question, my bad ;)

//Jim


From carlsonj at workingcode.com  Tue Jun 12 13:40:43 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Tue, 12 Jun 2012 09:40:43 -0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD744D1.1020807@cos.ru>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>	<CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>	<4FD72F61.9010004@cos.ru>
	<4FD739D2.9060900@genashor.com> <4FD744D1.1020807@cos.ru>
Message-ID: <4FD746DB.7070108@workingcode.com>

Jim Klimov wrote:
> As for the striped pool size - it seems about right.
> My 3TB disk is 2.72T, so a 4TB set being 3.6T seems okay.
> The raid10 mix also can have mixed ashifts, i.e. using ashift=12
> for the 3TB disks and ashift=9 for 1TB disks, if that's configured.

Don't forget that disk manufacturers (sadly) have only ten fingers and
toes, unlike the rest of us with either 16, 8, or 2.  ;-}

3,000,000,000,000 bytes is 2.72848TB and 4,000,000,000,000 bytes is
3.63798TB.

3000000000000/1024/1024/1024/1024
2.72848410531878471374
4000000000000/1024/1024/1024/1024
3.63797880709171295166

With the numbers you quote above, you're not actually missing any storage.

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From gary at genashor.com  Tue Jun 12 13:48:31 2012
From: gary at genashor.com (Gary Gendel)
Date: Tue, 12 Jun 2012 09:48:31 -0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
 new one. only one system available
In-Reply-To: <4FD744D1.1020807@cos.ru>
References: <CACxtc7x6PWuLLF-D9xvwbP70fxcJO+70_GGtN1Yni7u17aeMDw@mail.gmail.com>
	<CACxtc7yysrMMU3qtYvgf7aYWbqefJzrTpuF2vi6CQ1n2OcaL_Q@mail.gmail.com>
	<4FD72F61.9010004@cos.ru> <4FD739D2.9060900@genashor.com>
	<4FD744D1.1020807@cos.ru>
Message-ID: <4FD748AF.9070800@genashor.com>

On 6/12/12 9:32 AM, Jim Klimov wrote:
> 2012-06-12 16:45, Gary Gendel wrote:
>> On 6/12/12 8:00 AM, Jim Klimov wrote:
>>>
>>> Did the 3TB disk also report to the OS that it uses 4k sectors?
>>> What ashift value is used by the pool, ultimately? Example:
>>> # zdb -l /dev/rdsk/c2t0d0s0 | grep ashift
>>>         ashift: 9
>>>         ashift: 9
>>>         ashift: 9
>>>         ashift: 9
>>>
>>> If your 4KB disks use ashift=9 it is possible to get problems
>>> worse than decreased performance ;)
>>
>> I'm a bit confused.  I checked my mirrored Seagate ST33000651AS 3TB
>> drives using this method and I see "ashift: 9".  I'm sure that the
>> Seagates told them it had 512 sectors, but I thought that you couldn't
>> see the whole 3TBs with 512 sectors.  I have these striped with a 1TB
>> mirrored drive in the pool and zpool list shows 3.62T which seems about
>> right.  Is my understanding flawed?
>
> I failed to find the specs on the Seagate site which would state
> that this model uses 512B or 4KB sectors, or the Advanced Format.
> I thought that only Hitachi Desk/Ultra-Stars had 3TB disks with
> 512B native sectors (and 4TB models are Advanced-Formatted too),
> but that is not definitive. Maybe Seagate did that, maybe not.
>
> As for "ability to see", that's related to the disk size and
> the partitioning table used (GPT vs. older MBR, which can only
> address 2TB max), and not to the native sector size.
>
> As for the striped pool size - it seems about right.
> My 3TB disk is 2.72T, so a 4TB set being 3.6T seems okay.
> The raid10 mix also can have mixed ashifts, i.e. using ashift=12
> for the 3TB disks and ashift=9 for 1TB disks, if that's configured.
>
> Is your 1TB disk mirrored? Otherwise its single failure can bring
> the whole pool down.

I have a pair of 1TB mirrored drives striped with a pair of 3TB mirrored 
drives.  It looks like I have access to all the available storage.  I 
was just confused at why I was seeing all of the 3TB drives if I had 
ashift=9.  The specs for the drive on Seagate indicate that it has 512 
sectors, but it supports Advanced 4k sectors.  It's not clear if that 
means I will get better performance if I use ashift=12 or not.

At this time I'm just happy that it's working error free and I've got 
full access to the drives.  I was just surprised when I saw it didn't 
have ashift=12.

Gary




From jmcentee at stirling-dynamics.com  Tue Jun 12 13:52:23 2012
From: jmcentee at stirling-dynamics.com (John McEntee)
Date: Tue, 12 Jun 2012 14:52:23 +0100
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows regularly
	hangs.
Message-ID: <001501cd48a2$984e9100$c8ebb300$@com>

I am having problems with a openindiana storage server I have built am I am
trying to track down the cause to fix it. The current symptoms are seen from
all windows clients (both 7 and XP) that will report an error stating. 

 

Path File is not accessible. The specified network name is no longer
available. 

 

Another symptom  is windows explorer hangs and the user has to wait for it
to some back.

 

Just waiting a while ( a few minutes) and the box comes back.

 

I  currently think the root cause is in openindiana somewhere but am at a
bit of a loss. I have tried many things and have still not fixed it. I think
the box is lightly loaded for the hardware spec but kernel load increases to
40% when a zfssnap is taking place.

 

Hardware spec.

2 x Xeon E6520 cpus

48 GB RAM

Intel HC5520 motherboard

3 x LSI SAS 9211-8i  cards 

 

Currently on openindiana 148 

 

The box is joined to a windows 2003 domain.

 

Zpool tank is 3 way mirror of 7 x 3TB hitachi disk (using 21 disks in total,
zpool size of 19 TB, ) with 2 x SSD   8GB ZIL  on each and 140GB L2ARC on
each, default checksum, no dedup and no compression.

 

Server operates as a windows home directory for 58 users (some laptops users
so just a backup location), a main shared drive for the company of 120
users.

It is also a nfs server to a vmware vsphere 4 server hosting 10 virtual
machines.

 

There are only 8 active production file systems, and 12 backup file systems
from other hosts (done out of hours).

 

Zpool iostat peaks at about 35 MB for the pool mostly around the 0 to 7 MB
level.

 

Turning of time-sliderd does not stop the problem. (backups run out of
hours)

 

A  dtrace -n 'sched:::off-cpu { @[execname]=count()}'

Used to give a sched count in the 6 to 7 fiqures over 3 seconds, but  turing
apci off with

#eeprom acpi-user-options=0x8

Reduced this to 5 figures.

 

What can I do to identify the problem to be able to fix it?

 

Thanks

 

John

 

Other information:

 

dtrace -n 'sched:::off-cpu { @[execname]=count()}'

dtrace: description 'sched:::off-cpu ' matched 3 probes

^C

 

  gconfd-2                                                          2

  idmapd                                                            2

  inetd                                                             2

  nscd                                                              2

  sendmail                                                          2

  svc.startd                                                        2

  gnome-power-mana                                                  3

  fmd                                                               4

  sshd                                                              4

  devfsadm                                                          6

  fsflush                                                           7

  nfsmapid                                                          7

  ntpd                                                              7

  dtrace                                                           13

  Xorg                                                             17

  gdm-simple-greet                                                 17

  svc.configd                                                      71

  smbd                                                            113

  time-sliderd                                                    138

  zpool-rpool                                                     597

  nfsd                                                            918

  zpool-tank                                                     1968

  sched                                                         80542

 

# echo hz/D | sudo mdb -k

hz:

hz:             100

 

# echo apic_timer::print apic_timer_t | sudo mdb -k

{

    mode = 0

    apic_timer_enable_ops = oneshot_timer_enable

    apic_timer_disable_ops = oneshot_timer_disable

    apic_timer_reprogram_ops = oneshot_timer_reprogram

}



_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to admin at stirling-dynamics.com and delete this e-mail.  Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure.  Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. Registered In England No. 2092114 Registered Office: 26 Regent Street, Clifton, Bristol. BS8 4HG
VAT no. GB 464 6551 29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.

From george.wilson at delphix.com  Tue Jun 12 14:14:53 2012
From: george.wilson at delphix.com (George Wilson)
Date: Tue, 12 Jun 2012 10:14:53 -0400
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
	new one. only one system available
In-Reply-To: <CAOeNLurttyXPbctAw-_0oAy62tTaE_AXqSwJsRDJfgThQ9xvoA@mail.gmail.com>
References: <mailman.7717.1339447568.9998.openindiana-discuss@openindiana.org>
	<4FD673A4.5030604@branneriet.se> <4FD67B60.70909@gmail.com>
	<CAOeNLurttyXPbctAw-_0oAy62tTaE_AXqSwJsRDJfgThQ9xvoA@mail.gmail.com>
Message-ID: <84103339-29E1-4420-AC17-246CFBB8B551@delphix.com>

Yes it will. The only way to do this is to create a secondary pool and send/receive your root pool to the new pool.

- George

On Jun 11, 2012, at 7:16 PM, Rich wrote:

> Won't zpool replace fail b/c the new disks require ashift=12 and his
> existing pool devices have ashift=9?
> 
> - Rich
> 
> On Mon, Jun 11, 2012 at 7:12 PM, James C. McPherson
> <james.c.mcpherson at gmail.com> wrote:
>> On 12/06/12 08:39 AM, Hans J. Albertsson wrote:
>>> 
>>> Suppose:
>>> 
>>> I have a system with but two disks. They're fairly small: 300GB, and use
>>> 512B sectors.
>>> 
>>> These two disks are a mirror zpool, creqated from the entire disks.
>>> 
>>> There are about 20 or so filesystems in there.
>>> 
>>> The system has room for only two disks.
>>> 
>>> I'd like to replace these two small disks with two 2TB disks using 4kB
>>> blocks.
>>> 
>>> So:
>>> 
>>> Is there a writeup on how to connect one of these new disks to the
>>> existing machine, using an external esata cabinet.
>>> set up a new zpool on this new disk, and transfer all the root pool data
>>> to the new single disk zpool.
>>> then set up the new zpool to be bootable.
>>> And last: taking the old disks out of the machine, place the new single
>>> disk, and another, empty, similar 2TB disk in the machine, and boot from the
>>> single new one as the new root zpool. And then add the second new disk as a
>>> mirror.. effectively running the old system exactly as it was w/o
>>> reinstalling anything significant, but with much roomier disks.
>>> 
>>> Note: in this case there is no way to get another system to do it on. And
>>> a third disk can only be connected using an external cabinet and Esata or
>>> USB.
>> 
>> 
>> Hi Hans,
>> I suggest this:
>> 
>> #1 set autoexpand=on for rpool
>> #2 connect your esata enclosure
>> #3 once you've got them sliced up as desired (I suggest slice 0 should cover
>> all
>>   except cylinders 0 and 1), run installgrub on both new disks, to the mbr
>> #4 zpool replace one of your rpool disks
>> #5 zpool replace the other rpool disk
>> #6 poweroff
>> #7 do the physical replacement
>> #8 poweron
>> 
>> 
>> 
>> James C. McPherson
>> --
>> Solaris kernel software engineer, system admin and troubleshooter
>>              http://www.jmcp.homeunix.com/blog
>> Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
>> 
>> 
>> 
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



From george.wilson at delphix.com  Tue Jun 12 14:23:04 2012
From: george.wilson at delphix.com (George Wilson)
Date: Tue, 12 Jun 2012 10:23:04 -0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
Message-ID: <A3D3C4C4-418B-427B-BEB3-D1DE6C4C11D1@delphix.com>


On Jun 12, 2012, at 12:58 AM, Rich wrote:

> On Tue, Jun 12, 2012 at 12:50 AM, Richard Elling
> <richard.elling at richardelling.com> wrote:
>> On Jun 11, 2012, at 6:08 PM, Bob Friesenhahn wrote:
>> 
>>> On Mon, 11 Jun 2012, Jim Klimov wrote:
>>>> ashift=12 (2^12 = 4096). For disks which do not lie, it
>>>> works properly out of the box. The patched zpool binary
>>>> forced ashift=12 at the user's discretion.
>>> 
>>> It seems like new pools should provide the option to be created with ashift=12 even if none of the original disks need it.  The reason is to allow adding 4K sector disks later.
>> 
>> I don't disagree, in principle. However, history has shown that people don't plan very well
>> (eg, reason #1 dedup exists). Is there some other way to be more clever?
>>  -- richard
> 
> I believe that the consensus the last time this came up was agreement
> on that point, but contention over how the semantics of specifying it
> should work?
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

Illumos has a way to override the physical block size of a given disk by using the sd.conf file. Here's an example:

sd-config-list =
	"DGC     RAID", "physical-block-size:4096",
	"NETAPP  LUN", "physical-block-size:4096";


By adding the VID PID values into the sd-config-list along with the 'physical-block-size' parameter you can override the value that the disk will use for it's block size. ZFS will pick this up and use the correct ashift value.

- George

From bfriesen at simple.dallas.tx.us  Tue Jun 12 15:00:10 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Tue, 12 Jun 2012 10:00:10 -0500 (CDT)
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <A3D3C4C4-418B-427B-BEB3-D1DE6C4C11D1@delphix.com>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
	<A3D3C4C4-418B-427B-BEB3-D1DE6C4C11D1@delphix.com>
Message-ID: <alpine.GSO.2.01.1206120958380.21691@freddy.simplesystems.org>

On Tue, 12 Jun 2012, George Wilson wrote:
>
> Illumos has a way to override the physical block size of a given disk by using the sd.conf file. Here's an example:
>
> sd-config-list =
> 	"DGC     RAID", "physical-block-size:4096",
> 	"NETAPP  LUN", "physical-block-size:4096";
>
>
> By adding the VID PID values into the sd-config-list along with the 
> 'physical-block-size' parameter you can override the value that the 
> disk will use for it's block size. ZFS will pick this up and use the 
> correct ashift value.

This can obviously work once the OS is installed and it is possible to 
edit system files.  Is there a way to apply it to the root pool when 
the system is installed?

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From george.wilson at delphix.com  Tue Jun 12 15:17:07 2012
From: george.wilson at delphix.com (George Wilson)
Date: Tue, 12 Jun 2012 11:17:07 -0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <alpine.GSO.2.01.1206120958380.21691@freddy.simplesystems.org>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
	<A3D3C4C4-418B-427B-BEB3-D1DE6C4C11D1@delphix.com>
	<alpine.GSO.2.01.1206120958380.21691@freddy.simplesystems.org>
Message-ID: <04FD4C39-FBC7-4C3B-8583-FCEBEE00919F@delphix.com>


On Jun 12, 2012, at 11:00 AM, Bob Friesenhahn wrote:

> On Tue, 12 Jun 2012, George Wilson wrote:
>> 
>> Illumos has a way to override the physical block size of a given disk by using the sd.conf file. Here's an example:
>> 
>> sd-config-list =
>> 	"DGC     RAID", "physical-block-size:4096",
>> 	"NETAPP  LUN", "physical-block-size:4096";
>> 
>> 
>> By adding the VID PID values into the sd-config-list along with the 'physical-block-size' parameter you can override the value that the disk will use for it's block size. ZFS will pick this up and use the correct ashift value.
> 
> This can obviously work once the OS is installed and it is possible to edit system files.  Is there a way to apply it to the root pool when the system is installed?
> 
> Bob
> -- 
> Bob Friesenhahn
> bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

I have not tried this but you might be able to do change sd.conf and then run 'update_drv -f sd' prior to starting the installation.

- George



From hans.j.albertsson at branneriet.se  Tue Jun 12 15:18:21 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Tue, 12 Jun 2012 17:18:21 +0200
Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to,
 new	one. only one system available
In-Reply-To: <mailman.7761.1339484426.9998.openindiana-discuss@openindiana.org>
References: <mailman.7761.1339484426.9998.openindiana-discuss@openindiana.org>
Message-ID: <4FD75DBD.9040909@branneriet.se>

Actually I found the following blog quite illuminating.

http://www.big-bubbles.fluff.org/blogs/bubbles/blog/2012/02/04/placeholder-migrating-a-zfs-root-pool/


It would have to be worked thru for a number of specific cases. But it 
is basically sound.

A bird's eye view might be: format the new disk to have a partition s0 
starting from cyl 1 and a boot partition 8 on cyl 0
set up a zpool (using the hacked version with --blocksize if you'r not 
certain the disk reports a truthful 4k block size) on s0
create a new BE on that zpool as a clone of your current BE. Add swap 
and dump in the new zpool too
zfs send/recv using -R anything that wasn't brought over by the beadm 
cloning
installgrub -R the new device, and edit vfstab and do a dumpadm to point 
swap and dump as seen from the new environment to the new ones.

Name will be not rpool, and you can do another round as above if you care.

Read that blog while doing it: this bird's eye isn't anywhere near complete.




On 2012-06-12 09:00, openindiana-discuss-request at openindiana.org wrote:
> Message: 1
> Date: Tue, 12 Jun 2012 00:39:32 +0200
> From: "Hans J. Albertsson"<hans.j.albertsson at branneriet.se>
> To:openindiana-discuss at openindiana.org
> Subject: [OpenIndiana-discuss] Migrating root zpool from old disks to
> 	new	one. only one system available
> Message-ID:<4FD673A4.5030604 at branneriet.se>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Suppose:
>
> I have a system with but two disks. They're fairly small: 300GB, and use
> 512B sectors.
>
> These two disks are a mirror zpool, creqated from the entire disks.
>
> There are about 20 or so filesystems in there.
>
> The system has room for only two disks.
>
> I'd like to replace these two small disks with two 2TB disks using 4kB
> blocks.
>
> So:
>
> Is there a writeup on how to connect one of these new disks to the
> existing machine, using an external esata cabinet.
> set up a new zpool on this new disk, and transfer all the root pool data
> to the new single disk zpool.
> then set up the new zpool to be bootable.
> And last: taking the old disks out of the machine, place the new single
> disk, and another, empty, similar 2TB disk in the machine, and boot from
> the single new one as the new root zpool. And then add the second new
> disk as a mirror.. effectively running the old system exactly as it was
> w/o reinstalling anything significant, but with much roomier disks.
>
> Note: in this case there is no way to get another system to do it on.
> And a third disk can only be connected using an external cabinet and
> Esata or USB.


From jimklimov at cos.ru  Tue Jun 12 15:22:49 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 12 Jun 2012 19:22:49 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <alpine.GSO.2.01.1206120958380.21691@freddy.simplesystems.org>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
	<A3D3C4C4-418B-427B-BEB3-D1DE6C4C11D1@delphix.com>
	<alpine.GSO.2.01.1206120958380.21691@freddy.simplesystems.org>
Message-ID: <4FD75EC9.5050406@cos.ru>

2012-06-12 19:00, Bob Friesenhahn wrote:
> On Tue, 12 Jun 2012, George Wilson wrote:
>>
>> Illumos has a way to override the physical block size of a given disk
>> by using the sd.conf file. Here's an example:
>>
>> sd-config-list =
>>     "DGC     RAID", "physical-block-size:4096",
>>     "NETAPP  LUN", "physical-block-size:4096";
>>
>>
>> By adding the VID PID values into the sd-config-list along with the
>> 'physical-block-size' parameter you can override the value that the
>> disk will use for it's block size. ZFS will pick this up and use the
>> correct ashift value.
>
> This can obviously work once the OS is installed and it is possible to
> edit system files.  Is there a way to apply it to the root pool when the
> system is (being) installed?

First of all, I believe this snippet belongs on a Wiki page,
and I'll try to make one to sum up all knowledge and FUD we
have about The AShift Problem ;) At least, it would be easier
to point people to this page as a common answer ;)

Second, I believe the sd.conf fix won't apply to drives used
in IDE mode via BIOS, and users might have that (although it
is an item best fixed before installation).

Third, perhaps the sd.conf settings can be re-read by reloading
the module and/or using add_drv or something like that? From
a different thread (on disabling power-saving on Dell HBAs):
...enter into sd.conf and reload the driver via "update_drv -vf sd".

Also regarding the install-time setting - if the installation
is done using the wizard, then the zpool binary at the moment
of installation should use the ashift=12 you need, without
extra command-line parameters (as to not go hacking inside
the wizard). Earlier I did this by using a modified binary
from that blog entry instead of the system-provided one,
now I guess this can be done better with sd.conf :)

HTH,
//Jim Klimov


From jimklimov at cos.ru  Tue Jun 12 16:44:25 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 12 Jun 2012 20:44:25 +0400
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD75EC9.5050406@cos.ru>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
	<A3D3C4C4-418B-427B-BEB3-D1DE6C4C11D1@delphix.com>
	<alpine.GSO.2.01.1206120958380.21691@freddy.simplesystems.org>
	<4FD75EC9.5050406@cos.ru>
Message-ID: <4FD771E9.9040009@cos.ru>

2012-06-12 19:22, Jim Klimov wrote:
> First of all, I believe this snippet belongs on a Wiki page,
> and I'll try to make one to sum up all knowledge and FUD we
> have about The AShift Problem ;) At least, it would be easier
> to point people to this page as a common answer ;)

FWIW, here is the first draft:

http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS

Comments/additions welcome,
//Jim


From michelle at msknight.com  Tue Jun 12 18:37:45 2012
From: michelle at msknight.com (michelle)
Date: Tue, 12 Jun 2012 19:37:45 +0100
Subject: [OpenIndiana-discuss] HDD Upgrade problem
In-Reply-To: <4FD771E9.9040009@cos.ru>
References: <4FD46A59.5030106@msknight.com> <4FD471DB.3040704@msknight.com>
	<4FD47769.1050703@msknight.com> <4FD486EC.4000405@msknight.com>
	<4FD4D993.3080901@alum.mit.edu> <4FD59604.9040003@msknight.com>
	<4FD627DC.9050400@msknight.com> <4FD6397D.7080507@cos.ru>
	<alpine.GSO.2.01.1206112006270.21691@freddy.simplesystems.org>
	<BC8B8163-0A0E-4355-8924-950C8A89B89C@RichardElling.com>
	<CAOeNLuqD6v9YPKZBMCMSbSzKktfvuZEbEkA+K8SJ7gUFE=kX1Q@mail.gmail.com>
	<A3D3C4C4-418B-427B-BEB3-D1DE6C4C11D1@delphix.com>
	<alpine.GSO.2.01.1206120958380.21691@freddy.simplesystems.org>
	<4FD75EC9.5050406@cos.ru> <4FD771E9.9040009@cos.ru>
Message-ID: <4FD78C79.3070109@msknight.com>

That is absolutely stunning.

Many thanks for that. I guess I'm going to have to bite the bullet, wait 
until I've got another two 3tb drives and create a new pool.

Thanks to all for the feedback. Your patience with me is much appreciated.

On 12/06/12 17:44, Jim Klimov wrote:
> 2012-06-12 19:22, Jim Klimov wrote:
>> First of all, I believe this snippet belongs on a Wiki page,
>> and I'll try to make one to sum up all knowledge and FUD we
>> have about The AShift Problem ;) At least, it would be easier
>> to point people to this page as a common answer ;)
>
> FWIW, here is the first draft:
>
> http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS 
>
>
> Comments/additions welcome,
> //Jim
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>


From bfriesen at simple.dallas.tx.us  Wed Jun 13 01:55:14 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Tue, 12 Jun 2012 20:55:14 -0500 (CDT)
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
 regularly hangs.
In-Reply-To: <001501cd48a2$984e9100$c8ebb300$@com>
References: <001501cd48a2$984e9100$c8ebb300$@com>
Message-ID: <alpine.GSO.2.01.1206122051020.21691@freddy.simplesystems.org>

On Tue, 12 Jun 2012, John McEntee wrote:

> I am having problems with a openindiana storage server I have built am I am
> trying to track down the cause to fix it. The current symptoms are seen from
> all windows clients (both 7 and XP) that will report an error stating.
>
> Path File is not accessible. The specified network name is no longer
> available.

The first thing to verify is your network and network interface.  Run 
continuous traffic and see if there are any hickups.  You can use 
/usr/sbin/ping for testing with larger packets.

Also check the log files under /var/adm and /var/log.  Also check 
output of 'fmadm -ev' and 'fmadm faulty'.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From sardonic.smiles at gmail.com  Wed Jun 13 02:46:02 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Tue, 12 Jun 2012 22:46:02 -0400
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
 regularly hangs.
In-Reply-To: <alpine.GSO.2.01.1206122051020.21691@freddy.simplesystems.org>
References: <001501cd48a2$984e9100$c8ebb300$@com>
	<alpine.GSO.2.01.1206122051020.21691@freddy.simplesystems.org>
Message-ID: <CAPVmm=bfO9nRPn+K22LEuxcV_VDDY-M2Wbck+VcsiptPNapSYA@mail.gmail.com>

I had similar issues before I enabled TLER, and disabled the head parking
on my WD Green drives. A quick Google shows some evidence of similar
features on the 3TB Hitachis.

On Tue, Jun 12, 2012 at 9:55 PM, Bob Friesenhahn <
bfriesen at simple.dallas.tx.us> wrote:

> On Tue, 12 Jun 2012, John McEntee wrote:
>
>  I am having problems with a openindiana storage server I have built am I
>> am
>> trying to track down the cause to fix it. The current symptoms are seen
>> from
>> all windows clients (both 7 and XP) that will report an error stating.
>>
>> Path File is not accessible. The specified network name is no longer
>> available.
>>
>
> The first thing to verify is your network and network interface.  Run
> continuous traffic and see if there are any hickups.  You can use
> /usr/sbin/ping for testing with larger packets.
>
> Also check the log files under /var/adm and /var/log.  Also check output
> of 'fmadm -ev' and 'fmadm faulty'.
>
> Bob
> --
> Bob Friesenhahn
> bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/**
> users/bfriesen/ <http://www.simplesystems.org/users/bfriesen/>
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
>
>
> ______________________________**_________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss@**openindiana.org<OpenIndiana-discuss at openindiana.org>
> http://openindiana.org/**mailman/listinfo/openindiana-**discuss<http://openindiana.org/mailman/listinfo/openindiana-discuss>
>



-- 
Seconds to the drop, but it seems like hours.

http://www.eff.org/
<http://www.eff.org/>http://creativecommons.org/

From mike.laspina at laspina.ca  Wed Jun 13 03:50:24 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Tue, 12 Jun 2012 22:50:24 -0500
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
	regularlyhangs.
In-Reply-To: <001501cd48a2$984e9100$c8ebb300$@com>
References: <001501cd48a2$984e9100$c8ebb300$@com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>


Does the suspend event only occur on SMB clients or does it impact the
other storage clients when triggered by the Windows clients?
Any domain controller event errors?

dmsg output?
fmdump -eV output?
uname -a output?

Have you attempted a packet capture of the event?
snoop -o smb-client.cap <clientip> 

-----Original Message-----
From: John McEntee [mailto:jmcentee at stirling-dynamics.com] 
Sent: Tuesday, June 12, 2012 8:52 AM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
regularlyhangs.

I am having problems with a openindiana storage server I have built am I
am trying to track down the cause to fix it. The current symptoms are
seen from all windows clients (both 7 and XP) that will report an error
stating. 

 

Path File is not accessible. The specified network name is no longer
available. 

 

Another symptom  is windows explorer hangs and the user has to wait for
it to some back.

 

Just waiting a while ( a few minutes) and the box comes back.

 

I  currently think the root cause is in openindiana somewhere but am at
a bit of a loss. I have tried many things and have still not fixed it. I
think the box is lightly loaded for the hardware spec but kernel load
increases to 40% when a zfssnap is taking place.

 

Hardware spec.

2 x Xeon E6520 cpus

48 GB RAM

Intel HC5520 motherboard

3 x LSI SAS 9211-8i  cards 

 

Currently on openindiana 148 

 

The box is joined to a windows 2003 domain.

 

Zpool tank is 3 way mirror of 7 x 3TB hitachi disk (using 21 disks in
total,
zpool size of 19 TB, ) with 2 x SSD   8GB ZIL  on each and 140GB L2ARC
on
each, default checksum, no dedup and no compression.

 

Server operates as a windows home directory for 58 users (some laptops
users so just a backup location), a main shared drive for the company of
120 users.

It is also a nfs server to a vmware vsphere 4 server hosting 10 virtual
machines.

 

There are only 8 active production file systems, and 12 backup file
systems from other hosts (done out of hours).

 

Zpool iostat peaks at about 35 MB for the pool mostly around the 0 to 7
MB level.

 

Turning of time-sliderd does not stop the problem. (backups run out of
hours)

 

A  dtrace -n 'sched:::off-cpu { @[execname]=count()}'

Used to give a sched count in the 6 to 7 fiqures over 3 seconds, but
turing apci off with

#eeprom acpi-user-options=0x8

Reduced this to 5 figures.

 

What can I do to identify the problem to be able to fix it?

 

Thanks

 

John

 

Other information:

 

dtrace -n 'sched:::off-cpu { @[execname]=count()}'

dtrace: description 'sched:::off-cpu ' matched 3 probes

^C

 

  gconfd-2                                                          2

  idmapd                                                            2

  inetd                                                             2

  nscd                                                              2

  sendmail                                                          2

  svc.startd                                                        2

  gnome-power-mana                                                  3

  fmd                                                               4

  sshd                                                              4

  devfsadm                                                          6

  fsflush                                                           7

  nfsmapid                                                          7

  ntpd                                                              7

  dtrace                                                           13

  Xorg                                                             17

  gdm-simple-greet                                                 17

  svc.configd                                                      71

  smbd                                                            113

  time-sliderd                                                    138

  zpool-rpool                                                     597

  nfsd                                                            918

  zpool-tank                                                     1968

  sched                                                         80542

 

# echo hz/D | sudo mdb -k

hz:

hz:             100

 

# echo apic_timer::print apic_timer_t | sudo mdb -k

{

    mode = 0

    apic_timer_enable_ops = oneshot_timer_enable

    apic_timer_disable_ops = oneshot_timer_disable

    apic_timer_reprogram_ops = oneshot_timer_reprogram

}



_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly
confidential and are solely for the person(s) at the e-mail address(es)
above. If you are not an addressee, you may not disclose, distribute,
copy or use this e-mail, and we request that you send an e-mail to
admin at stirling-dynamics.com and delete this e-mail.  Stirling Dynamics
Ltd. accepts no legal liability for the contents of this e-mail
including any errors, interception or interference, as internet
communications are not secure.  Any views or opinions presented are
solely those of the author and do not necessarily represent those of
Stirling Dynamics Ltd. Registered In England No. 2092114 Registered
Office: 26 Regent Street, Clifton, Bristol. BS8 4HG VAT no. GB 464 6551
29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From jmcentee at stirling-dynamics.com  Wed Jun 13 08:39:00 2012
From: jmcentee at stirling-dynamics.com (John McEntee)
Date: Wed, 13 Jun 2012 09:39:00 +0100
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
	regularly hangs.
In-Reply-To: <alpine.GSO.2.01.1206122051020.21691@freddy.simplesystems.org>
References: <001501cd48a2$984e9100$c8ebb300$@com>
	<alpine.GSO.2.01.1206122051020.21691@freddy.simplesystems.org>
Message-ID: <006e01cd493f$fac675d0$f0536170$@com>

> The first thing to verify is your network and network interface.  Run
continuous traffic and see if there are any hickups.  
> You can use /usr/sbin/ping for testing with larger packets.
>
> Also check the log files under /var/adm and /var/log.  Also check output
of 'fmadm -ev' and 'fmadm faulty'.

Nothing shows in dmesg, or in the logs under /var/adm and /var/log  no
hardware errors are logged by zfs either. 

'fmadm -ev' errors on invalid options and 'fmadm faulty' is clear (nothing
to report).

The nfs share to the vmware server seems fine as well, but it may be more
accommodating of problems. Large file transfers initiated from a windows
desktop run at 40 to 50 MB/s (desktop probably the bottle neck).

Thanks

John


_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to admin at stirling-dynamics.com and delete this e-mail.  Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure.  Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. Registered In England No. 2092114 Registered Office: 26 Regent Street, Clifton, Bristol. BS8 4HG
VAT no. GB 464 6551 29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.


From jmcentee at stirling-dynamics.com  Wed Jun 13 08:41:20 2012
From: jmcentee at stirling-dynamics.com (John McEntee)
Date: Wed, 13 Jun 2012 09:41:20 +0100
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
	regularly hangs.
In-Reply-To: <CAPVmm=bfO9nRPn+K22LEuxcV_VDDY-M2Wbck+VcsiptPNapSYA@mail.gmail.com>
References: <001501cd48a2$984e9100$c8ebb300$@com>	<alpine.GSO.2.01.1206122051020.21691@freddy.simplesystems.org>
	<CAPVmm=bfO9nRPn+K22LEuxcV_VDDY-M2Wbck+VcsiptPNapSYA@mail.gmail.com>
Message-ID: <006f01cd4940$4e149a00$ea3dce00$@com>

> I had similar issues before I enabled TLER, and disabled the head parking
on my WD Green drives. A quick Google shows some evidence of similar
features on the 3TB Hitachis.

I chose Hitachi because I didn't think they had this "feature". I would have
thought ZFS would have reported errors and removed them from the array if it
was happening? I will go and search the internet.

John



_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to admin at stirling-dynamics.com and delete this e-mail.  Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure.  Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. Registered In England No. 2092114 Registered Office: 26 Regent Street, Clifton, Bristol. BS8 4HG
VAT no. GB 464 6551 29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.


From jmcentee at stirling-dynamics.com  Wed Jun 13 08:57:56 2012
From: jmcentee at stirling-dynamics.com (John McEntee)
Date: Wed, 13 Jun 2012 09:57:56 +0100
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from
	windows	regularlyhangs.
In-Reply-To: <8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>
References: <001501cd48a2$984e9100$c8ebb300$@com>
	<8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>
Message-ID: <007001cd4942$9ffb7b20$dff27160$@com>

> Does the suspend event only occur on SMB clients or does it impact the
other storage clients when triggered by the Windows clients?

It does not seem to effect the vmware hosted machines via nfs. Next time it
hangs I will try a nfs transfer to it.

> Any domain controller event errors?

Yes there are, I will go and resolve this first before I go any further.

> dmsg output?

Attached - is this the correct etiquette?

> fmdump -eV output?

Also attached.

> uname -a output?

SunOS ringwood 5.11 oi_148 i86pc i386 i86pc Solaris

> Have you attempted a packet capture of the event?
> snoop -o smb-client.cap <clientip> 

Not yet, It could be caputureing for 4 hours before it happens, I will
resolve the AD domain issue first.

John



_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to admin at stirling-dynamics.com and delete this e-mail.  Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure.  Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. Registered In England No. 2092114 Registered Office: 26 Regent Street, Clifton, Bristol. BS8 4HG
VAT no. GB 464 6551 29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg.txt
URL: <http://openindiana.org/pipermail/openindiana-discuss/attachments/20120613/c0876952/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: fmdump.txt
URL: <http://openindiana.org/pipermail/openindiana-discuss/attachments/20120613/c0876952/attachment-0003.txt>

From gordon.w.ross at gmail.com  Thu Jun 14 01:08:32 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Wed, 13 Jun 2012 21:08:32 -0400
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
 regularly hangs.
In-Reply-To: <001501cd48a2$984e9100$c8ebb300$@com>
References: <001501cd48a2$984e9100$c8ebb300$@com>
Message-ID: <CAD0Ztp3m_kmAg-73UTd3f844rzP2p-dPX3H_m1PV3PQoVDZcWA@mail.gmail.com>

Have you done a snoop (or wireshark) capture to see what the box is
doing during the pause?
It's possible that it's trying to talk to an AD server...

On Tue, Jun 12, 2012 at 9:52 AM, John McEntee
<jmcentee at stirling-dynamics.com> wrote:
> I am having problems with a openindiana storage server I have built am I am
> trying to track down the cause to fix it. The current symptoms are seen from
> all windows clients (both 7 and XP) that will report an error stating.
>
>
>
> Path File is not accessible. The specified network name is no longer
> available.
>
>
>
> Another symptom ?is windows explorer hangs and the user has to wait for it
> to some back.
>
>
>
> Just waiting a while ( a few minutes) and the box comes back.
>
>
>
> I ?currently think the root cause is in openindiana somewhere but am at a
> bit of a loss. I have tried many things and have still not fixed it. I think
> the box is lightly loaded for the hardware spec but kernel load increases to
> 40% when a zfssnap is taking place.
>
>
>
> Hardware spec.
>
> 2 x Xeon E6520 cpus
>
> 48 GB RAM
>
> Intel HC5520 motherboard
>
> 3 x LSI SAS 9211-8i ?cards
>
>
>
> Currently on openindiana 148
>
>
>
> The box is joined to a windows 2003 domain.
>
>
>
> Zpool tank is 3 way mirror of 7 x 3TB hitachi disk (using 21 disks in total,
> zpool size of 19 TB, ) with 2 x SSD ? 8GB ZIL ?on each and 140GB L2ARC on
> each, default checksum, no dedup and no compression.
>
>
>
> Server operates as a windows home directory for 58 users (some laptops users
> so just a backup location), a main shared drive for the company of 120
> users.
>
> It is also a nfs server to a vmware vsphere 4 server hosting 10 virtual
> machines.
>
>
>
> There are only 8 active production file systems, and 12 backup file systems
> from other hosts (done out of hours).
>
>
>
> Zpool iostat peaks at about 35 MB for the pool mostly around the 0 to 7 MB
> level.
>
>
>
> Turning of time-sliderd does not stop the problem. (backups run out of
> hours)
>
>
>
> A ?dtrace -n 'sched:::off-cpu { @[execname]=count()}'
>
> Used to give a sched count in the 6 to 7 fiqures over 3 seconds, but ?turing
> apci off with
>
> #eeprom acpi-user-options=0x8
>
> Reduced this to 5 figures.
>
>
>
> What can I do to identify the problem to be able to fix it?
>
>
>
> Thanks
>
>
>
> John
>
>
>
> Other information:
>
>
>
> dtrace -n 'sched:::off-cpu { @[execname]=count()}'
>
> dtrace: description 'sched:::off-cpu ' matched 3 probes
>
> ^C
>
>
>
> ?gconfd-2 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2
>
> ?idmapd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2
>
> ?inetd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 2
>
> ?nscd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2
>
> ?sendmail ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2
>
> ?svc.startd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?2
>
> ?gnome-power-mana ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?3
>
> ?fmd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 4
>
> ?sshd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?4
>
> ?devfsadm ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?6
>
> ?fsflush ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 7
>
> ?nfsmapid ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?7
>
> ?ntpd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?7
>
> ?dtrace ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 13
>
> ?Xorg ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 17
>
> ?gdm-simple-greet ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 17
>
> ?svc.configd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?71
>
> ?smbd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?113
>
> ?time-sliderd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?138
>
> ?zpool-rpool ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 597
>
> ?nfsd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?918
>
> ?zpool-tank ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 1968
>
> ?sched ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? 80542
>
>
>
> # echo hz/D | sudo mdb -k
>
> hz:
>
> hz: ? ? ? ? ? ? 100
>
>
>
> # echo apic_timer::print apic_timer_t | sudo mdb -k
>
> {
>
> ? ?mode = 0
>
> ? ?apic_timer_enable_ops = oneshot_timer_enable
>
> ? ?apic_timer_disable_ops = oneshot_timer_disable
>
> ? ?apic_timer_reprogram_ops = oneshot_timer_reprogram
>
> }
>
>
>
> _______________________________________________________________________
>
> The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to admin at stirling-dynamics.com and delete this e-mail. ?Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure. ?Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. Registered In England No. 2092114 Registered Office: 26 Regent Street, Clifton, Bristol. BS8 4HG
> VAT no. GB 464 6551 29
> _______________________________________________________________________
>
> This e-mail has been scanned for all viruses MessageLabs.
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From mike.laspina at laspina.ca  Thu Jun 14 03:42:59 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Wed, 13 Jun 2012 22:42:59 -0500
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS
	fromwindows	regularlyhangs.
In-Reply-To: <007001cd4942$9ffb7b20$dff27160$@com>
References: <001501cd48a2$984e9100$c8ebb300$@com><8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>
	<007001cd4942$9ffb7b20$dff27160$@com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D46E9@MS1.laspina.ca>


> Does the suspend event only occur on SMB clients or does it impact the
other storage clients when triggered by the Windows clients?

It does not seem to effect the vmware hosted machines via nfs. Next time
it hangs I will try a nfs transfer to it.
- If this is correct its a further indication of an AD/SMB issue, but
not verified at this point.

> Any domain controller event errors?

Yes there are, I will go and resolve this first before I go any further.

- Highly suspect this is where you need to focus.
- This error is suspicious and does look like a issue on the domain. 
- Jun 12 11:26:07 ringwood smbd[6032]: [ID 702911 daemon.notice]
smbd_dc_update: stirling-dynamics.com: located red
- Jun 12 11:34:17 ringwood smbd[6032]: [ID 702911 daemon.error]
smbrdr_exchange[4]: failed (INVALID_HANDLE)
- I would look further back in time and see if it correlates with the
suspended access event. That would define a clear resolution path.

> dmsg output?

Attached - is this the correct etiquette?

- Jun 11 21:38:18 ringwood fmd: [ID 377184 daemon.error] SUNW-MSG-ID:
SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
- Jun 11 21:38:18 ringwood EVENT-TIME: Mon Jun 11 21:38:18 BST 2012
- Jun 11 21:38:18 ringwood PLATFORM: S5520HC, CSN: ............,
HOSTNAME: ringwood
- Jun 11 21:38:18 ringwood SOURCE: software-diagnosis, REV: 0.1
- Jun 11 21:38:18 ringwood EVENT-ID:
cc9f2029-a779-cbd2-e425-8ffbaa19f639
- Jun 11 21:38:18 ringwood DESC: A service failed - a method is failing
in a retryable manner but too often.
- Jun 11 21:38:18 ringwood   Refer to http://sun.com/msg/SMF-8000-YX for
more information.
- Jun 11 21:38:18 ringwood AUTO-RESPONSE: The service has been placed
into the maintenance state.
- Jun 11 21:38:18 ringwood IMPACT: svc:/application/time-slider:default
is unavailable.

- The time slider snapshot service failed? Or was it stopped manually?

> fmdump -eV output?

Also attached.
- Nothing remarkable

> uname -a output?

SunOS ringwood 5.11 oi_148 i86pc i386 i86pc Solaris

> Have you attempted a packet capture of the event?
> snoop -o smb-client.cap <clientip>

Not yet, It could be caputureing for 4 hours before it happens, I will
resolve the AD domain issue first.
- Good approach. 4 hours of packet tracing is hard to digest! It would
certainly need to be truncated down to the trigger event. 

- Mike



_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly
confidential and are solely for the person(s) at the e-mail address(es)
above. If you are not an addressee, you may not disclose, distribute,
copy or use this e-mail, and we request that you send an e-mail to
admin at stirling-dynamics.com and delete this e-mail.  Stirling Dynamics
Ltd. accepts no legal liability for the contents of this e-mail
including any errors, interception or interference, as internet
communications are not secure.  Any views or opinions presented are
solely those of the author and do not necessarily represent those of
Stirling Dynamics Ltd. Registered In England No. 2092114 Registered
Office: 26 Regent Street, Clifton, Bristol. BS8 4HG VAT no. GB 464 6551
29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.


From ano at bestmx.ru  Thu Jun 14 13:14:13 2012
From: ano at bestmx.ru (Andrey N. Oktyabrski)
Date: Thu, 14 Jun 2012 17:14:13 +0400
Subject: [OpenIndiana-discuss] oi151a4 does not wake up
Message-ID: <4FD9E3A5.7030104@bestmx.ru>

Good day.

I have a ThinkPad T61 with oi151a installed from scratch. It does not 
enable screen on wake up. To be clear: I have set in the Gnome menu to 
suspend when laptop lid is closed. It does. When I open a lid and press 
power button, laptop wakes up, but screen does not. What settings I must 
change?


From michaelsprivate at gmail.com  Thu Jun 14 13:17:28 2012
From: michaelsprivate at gmail.com (Michael Schuster)
Date: Thu, 14 Jun 2012 15:17:28 +0200
Subject: [OpenIndiana-discuss] oi151a4 does not wake up
In-Reply-To: <4FD9E3A5.7030104@bestmx.ru>
References: <4FD9E3A5.7030104@bestmx.ru>
Message-ID: <CADqw_g+NSy1YVw-wYjHDKLG0pcGWiL=w20qHXZr_WaGh5gWB1w@mail.gmail.com>

which graphics adapter (ATI or Nvidia) is installed on this Thinkpad?

On Thu, Jun 14, 2012 at 3:14 PM, Andrey N. Oktyabrski <ano at bestmx.ru> wrote:
> Good day.
>
> I have a ThinkPad T61 with oi151a installed from scratch. It does not enable
> screen on wake up. To be clear: I have set in the Gnome menu to suspend when
> laptop lid is closed. It does. When I open a lid and press power button,
> laptop wakes up, but screen does not. What settings I must change?
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



-- 
Michael Schuster
http://recursiveramblings.wordpress.com/


From ano at bestmx.ru  Thu Jun 14 13:51:22 2012
From: ano at bestmx.ru (Andrey N. Oktyabrski)
Date: Thu, 14 Jun 2012 17:51:22 +0400
Subject: [OpenIndiana-discuss] oi151a4 does not wake up
In-Reply-To: <CADqw_g+NSy1YVw-wYjHDKLG0pcGWiL=w20qHXZr_WaGh5gWB1w@mail.gmail.com>
References: <4FD9E3A5.7030104@bestmx.ru>
	<CADqw_g+NSy1YVw-wYjHDKLG0pcGWiL=w20qHXZr_WaGh5gWB1w@mail.gmail.com>
Message-ID: <4FD9EC5A.9000008@bestmx.ru>

On 14.06.12 17:17, Michael Schuster wrote:
> which graphics adapter (ATI or Nvidia) is installed on this Thinkpad?
nvidia




From michaelsprivate at gmail.com  Thu Jun 14 14:17:00 2012
From: michaelsprivate at gmail.com (Michael Schuster)
Date: Thu, 14 Jun 2012 16:17:00 +0200
Subject: [OpenIndiana-discuss] oi151a4 does not wake up
In-Reply-To: <4FD9EC5A.9000008@bestmx.ru>
References: <4FD9E3A5.7030104@bestmx.ru>
	<CADqw_g+NSy1YVw-wYjHDKLG0pcGWiL=w20qHXZr_WaGh5gWB1w@mail.gmail.com>
	<4FD9EC5A.9000008@bestmx.ru>
Message-ID: <CADqw_gKjoTuS4jDAHYmQNNAfLsqok3DNgznLk2Azvq6ensgG=A@mail.gmail.com>

On Thu, Jun 14, 2012 at 3:51 PM, Andrey N. Oktyabrski <ano at bestmx.ru> wrote:
> On 14.06.12 17:17, Michael Schuster wrote:
>>
>> which graphics adapter (ATI or Nvidia) is installed on this Thinkpad?
>
> nvidia

hmm ... IIRC those were supported. I guess this may depend on which
specific chip, can't add anything myself though, I'm afraid. Perhaps
you can dig up the X log, in case someone asks for it :-)

good luck
Michael
-- 
Michael Schuster
http://recursiveramblings.wordpress.com/


From jimklimov at cos.ru  Thu Jun 14 14:53:23 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Thu, 14 Jun 2012 18:53:23 +0400
Subject: [OpenIndiana-discuss] Serial console for OI/Solaris on Intel MFSYS
	blades
Message-ID: <4FD9FAE3.30106@cos.ru>

Hello all,

   I have a peculiar problem: the Intel MFSYS blade servers, in short ;)

   They have a number of interesting features, due to which are deployed
at a number of our customers, but with somewhat under-cooked firmware
features wherever I've seen. The one bugging me this week is a Remote
Serial Console implementation.

   This blade chassis has up to 6 server blades, a management module,
1 or 2 storage controller modules driving the 14 disks (the SCMs do
the RAID and publish LUNs to server blades), and 1 or 2 networking
modules (GbE switches). Overall, quite a bit of redundancy would
make it a good box, if its code was all working properly ;)

   So, the management module takes the servers' redirected text console
IO and publishes that as a "SOLCLI" (Serial-Over-LAN CLI) session via
SSH on dedicated ports like 2201-2206 for the 6 blades. I found next
to zero specific info on the serial emulation, but it seems to be
either auto-bauding or (as the Linux blades successfully use it) a
"115200,8,n,1,-" link. I'd bet auto-bauding, because "9600,8,n,1,-"
also seems to work. Terminal emulation is unknown, but somewhat like
VT100 (however, GRUB menu fails to render properly, unless I specify
"--dumb" for a simplified rendering mode).

   The problem is, the redirected console gets lost after Solaris 10
or OI boots on the blade. It works somewhat for BIOS and GRUB (but
even there it sometimes loses connections or farts out invalid
characters), and if I boot with "-B console=ttya" - sercon usually
makes it through the OS build version banner and prints a character
or two of the OS initialization (console logs from SMF startups).

   Afterwards nothing comes in out of the ttya console: echos to it
hang (sometimes the first character is printed), cats from it hang
and in half a minute cause restart of the SSH session to the console.
The ttymon greeting never comes up, either.

   However, when the OS is rebooted, it does fully print the line
"rebooting..." on the sercon.

   I guess that some of the OS components working with the serial
port (ttymon, stty, pm, saf) might be setting "invalid" options
on the port which cause the Intel Remote Console fail into coma.
Likewise, when such component is unloaded and un-initialized
before reboot, console becomes responsive again.

   Does this ring a bell to someone? What can be (un-)set or at
least debugged in this case? I learned a lot of new stuff about
pmadm, sttyadm, ttymon, stty settings and console-login SMF
services, but this did not get me a working serial console
on this box. Same settings work for other IPMI-enabled boxes
(mostly various Sun Fire models; they don't have any other
Intel-branded servers, so I don't know if their other models
share such bugginess).


   Side note: Linux installations had few hiccups using serial
consoles on the same blades with just this line in /etc/inittab:
   co::respawn:/sbin/mgetty -s 115200 -r /dev/ttyS0
Using "difficult" terminal emulations or fast-scrolling outputs
can also cause the sercon collapse into a long coma to reboot,
or at least break the SSH session to it; simply running "vi"
was notorious for that effect.

Thanks in advance,
//Jim Klimov


From rdparker at gmail.com  Thu Jun 14 16:54:52 2012
From: rdparker at gmail.com (Ron Parker)
Date: Thu, 14 Jun 2012 11:54:52 -0500
Subject: [OpenIndiana-discuss] oi151a4 does not wake up
In-Reply-To: <CADqw_gKjoTuS4jDAHYmQNNAfLsqok3DNgznLk2Azvq6ensgG=A@mail.gmail.com>
References: <4FD9E3A5.7030104@bestmx.ru>
	<CADqw_g+NSy1YVw-wYjHDKLG0pcGWiL=w20qHXZr_WaGh5gWB1w@mail.gmail.com>
	<4FD9EC5A.9000008@bestmx.ru>
	<CADqw_gKjoTuS4jDAHYmQNNAfLsqok3DNgznLk2Azvq6ensgG=A@mail.gmail.com>
Message-ID: <CAMQ-0Rn5GKzgnidS1uSiNVE0zSoaaNs1yO371Zm-Tb6WnvPC5Q@mail.gmail.com>

On Thu, Jun 14, 2012 at 9:17 AM, Michael Schuster
<michaelsprivate at gmail.com> wrote:
> On Thu, Jun 14, 2012 at 3:51 PM, Andrey N. Oktyabrski <ano at bestmx.ru> wrote:
>> On 14.06.12 17:17, Michael Schuster wrote:
>>>
>>> which graphics adapter (ATI or Nvidia) is installed on this Thinkpad?
>>
>> nvidia
>
> hmm ... IIRC those were supported. I guess this may depend on which
> specific chip, can't add anything myself though, I'm afraid. Perhaps
> you can dig up the X log, in case someone asks for it :-)

Just to add a data point, this also happens on my Dell E6410 with the
NVIDIA NVS 3100M using the 302.07 beta driver.

--
Ron Parker
Don't type things you find on the Internet into your computer!
:(){ :|:&};:


From ewald.ertl at gmail.com  Thu Jun 14 17:08:21 2012
From: ewald.ertl at gmail.com (Ewald Ertl)
Date: Thu, 14 Jun 2012 19:08:21 +0200
Subject: [OpenIndiana-discuss] oi151a4 does not wake up
In-Reply-To: <CAMQ-0Rn5GKzgnidS1uSiNVE0zSoaaNs1yO371Zm-Tb6WnvPC5Q@mail.gmail.com>
References: <4FD9E3A5.7030104@bestmx.ru>
	<CADqw_g+NSy1YVw-wYjHDKLG0pcGWiL=w20qHXZr_WaGh5gWB1w@mail.gmail.com>
	<4FD9EC5A.9000008@bestmx.ru>
	<CADqw_gKjoTuS4jDAHYmQNNAfLsqok3DNgznLk2Azvq6ensgG=A@mail.gmail.com>
	<CAMQ-0Rn5GKzgnidS1uSiNVE0zSoaaNs1yO371Zm-Tb6WnvPC5Q@mail.gmail.com>
Message-ID: <CANzcY7d2RmJNGS4tbjm1O6OHXwKtvRHPMHrfy61r8so0w+dkLQ@mail.gmail.com>

Hi,

On Thu, Jun 14, 2012 at 6:54 PM, Ron Parker <rdparker at gmail.com> wrote:

> On Thu, Jun 14, 2012 at 9:17 AM, Michael Schuster
> <michaelsprivate at gmail.com> wrote:
> > On Thu, Jun 14, 2012 at 3:51 PM, Andrey N. Oktyabrski <ano at bestmx.ru>
> wrote:
> >> On 14.06.12 17:17, Michael Schuster wrote:
> >>>
> >>> which graphics adapter (ATI or Nvidia) is installed on this Thinkpad?
> >>
> >> nvidia
> >
> > hmm ... IIRC those were supported. I guess this may depend on which
> > specific chip, can't add anything myself though, I'm afraid. Perhaps
> > you can dig up the X log, in case someone asks for it :-)
>
> Just to add a data point, this also happens on my Dell E6410 with the
> NVIDIA NVS 3100M using the 302.07 beta driver.
>

AFAIK the NVidia driver in OI151* is directly from NVidia and does not
contain the code
for suspend/resume in Solaris and that's the reason.
The "original" driver in OpenSolaris contained that code part.

From gary_mills at fastmail.fm  Thu Jun 14 17:28:29 2012
From: gary_mills at fastmail.fm (Gary Mills)
Date: Thu, 14 Jun 2012 12:28:29 -0500
Subject: [OpenIndiana-discuss] Serial console for OI/Solaris on Intel
 MFSYS blades
In-Reply-To: <4FD9FAE3.30106@cos.ru>
References: <4FD9FAE3.30106@cos.ru>
Message-ID: <20120614172829.GA25217@mail.messagingengine.com>

On Thu, Jun 14, 2012 at 06:53:23PM +0400, Jim Klimov wrote:
> 
>   I have a peculiar problem: the Intel MFSYS blade servers, in short ;)
> 
>   The problem is, the redirected console gets lost after Solaris 10
> or OI boots on the blade. It works somewhat for BIOS and GRUB (but
> even there it sometimes loses connections or farts out invalid
> characters), and if I boot with "-B console=ttya" - sercon usually
> makes it through the OS build version banner and prints a character
> or two of the OS initialization (console logs from SMF startups).

You will always get output for BIOS and GRUB because these do their
I/O through the BIOS, using BIOS redirection.  Once Linux or Solaris
start, they do their own I/O directly to the serial port.

How many `asy' ports show up in `prtconf -v'?  It's usually COM3
(ttyc) that's used for serial-over-lan.  You'll likely need to use
`console=ttyc' in the GRUB menu.  Try also these settings in
/boot/solaris/bootenv.rc:

    setprop ttyc-rts-dtr-off false
    setprop ttyc-ignore-cd true
    setprop ttyc-mode 9600,8,n,1,-
    setprop console ttyc

You might also have to set the serial bit rate to match in the
firmware on the remote management card.  You can also change it in
OI to match the card's.

-- 
-Gary Mills-		-refurb-		-Winnipeg, Manitoba, Canada-


From ano at bestmx.ru  Thu Jun 14 17:51:12 2012
From: ano at bestmx.ru (Andrey N. Oktyabrski)
Date: Thu, 14 Jun 2012 21:51:12 +0400
Subject: [OpenIndiana-discuss] oi151a4 does not wake up
In-Reply-To: <CANzcY7d2RmJNGS4tbjm1O6OHXwKtvRHPMHrfy61r8so0w+dkLQ@mail.gmail.com>
References: <4FD9E3A5.7030104@bestmx.ru>
	<CADqw_g+NSy1YVw-wYjHDKLG0pcGWiL=w20qHXZr_WaGh5gWB1w@mail.gmail.com>
	<4FD9EC5A.9000008@bestmx.ru>
	<CADqw_gKjoTuS4jDAHYmQNNAfLsqok3DNgznLk2Azvq6ensgG=A@mail.gmail.com>
	<CAMQ-0Rn5GKzgnidS1uSiNVE0zSoaaNs1yO371Zm-Tb6WnvPC5Q@mail.gmail.com>
	<CANzcY7d2RmJNGS4tbjm1O6OHXwKtvRHPMHrfy61r8so0w+dkLQ@mail.gmail.com>
Message-ID: <4FDA2490.9000808@bestmx.ru>

On 14.06.12 21:08, Ewald Ertl wrote:
>>>>> which graphics adapter (ATI or Nvidia) is installed on this Thinkpad?
>>>>
>>>> nvidia
>>>
>>> hmm ... IIRC those were supported. I guess this may depend on which
>>> specific chip, can't add anything myself though, I'm afraid. Perhaps
>>> you can dig up the X log, in case someone asks for it :-)
>>
>> Just to add a data point, this also happens on my Dell E6410 with the
>> NVIDIA NVS 3100M using the 302.07 beta driver.
>
> AFAIK the NVidia driver in OI151* is directly from NVidia and does not
> contain the code
> for suspend/resume in Solaris and that's the reason.
> The "original" driver in OpenSolaris contained that code part.
Thank you, Michael, Ron, Ewald. What I have tried:
- nv driver
- nvidia 295.49
- nvidia 302.07 beta

All three doesn't wake up. I think, the problem is anywhere in other 
place, not in driver. On my old dead hdd I have had oi148 updated to 
oi151 and suspend/resume worked fine.



From jimklimov at cos.ru  Thu Jun 14 17:58:29 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Thu, 14 Jun 2012 21:58:29 +0400
Subject: [OpenIndiana-discuss] Serial console for OI/Solaris on Intel
 MFSYS blades
In-Reply-To: <20120614172829.GA25217@mail.messagingengine.com>
References: <4FD9FAE3.30106@cos.ru>
	<20120614172829.GA25217@mail.messagingengine.com>
Message-ID: <4FDA2645.9050505@cos.ru>

Thanks for the suggestions, but they did not help :(
Waiting for more ideas ;)

Details follow:

2012-06-14 21:28, Gary Mills wrote:
> On Thu, Jun 14, 2012 at 06:53:23PM +0400, Jim Klimov wrote:
>>
>>    I have a peculiar problem: the Intel MFSYS blade servers, in short ;)
>>
>>    The problem is, the redirected console gets lost after Solaris 10
>> or OI boots on the blade. It works somewhat for BIOS and GRUB (but
>> even there it sometimes loses connections or farts out invalid
>> characters), and if I boot with "-B console=ttya" - sercon usually
>> makes it through the OS build version banner and prints a character
>> or two of the OS initialization (console logs from SMF startups).
>
> You will always get output for BIOS and GRUB because these do their
> I/O through the BIOS, using BIOS redirection.  Once Linux or Solaris
> start, they do their own I/O directly to the serial port.

No, GRUB can also own its I/O to the serial port (also, in BIOS
the redirection-after-POST is disabled). GRUB's menu.lst defines:
   serial --unit=0 --speed=9600 ---word=8 --parity=no --stop=1
   terminal --dumb --timeout=10 console serial

So wherever a key is pressed during the first 10-second timeout,
the interactive menu would pop up, with its own timeout to boot.


 > You might also have to set the serial bit rate to match in the
 > firmware on the remote management card.  You can also change it in
 > OI to match the card's.

That one is a tricky part, as I wrote. I have tried a few
settings of baud-rate, DTR/DTS, flowctl, parity via eeprom
and /etc/ttydefs and /etc/saf/zsmon/_pmtab and such; that
had no noticeable influence over several non-fast reboots.
I also my did tests over all located serial port names
(below) like "/dev/(term/a|ttya|tty00|cua/a|cua0|ttyd0)".

Except that in some cases I got no output at all, or the
OS version output headers broke mid-string even before SMF
report messages, but it certainly was not an improvement,
but not a definitive change either...

Is eeprom (/boot/solaris/bootenv.rc) the only location which
influences the serial port settings during the OS uptime?

Is there a way to dynamically set and change the serial port
options (i.e. via some terminal emulator, etc.) and recover
the logical port/driver from a hung position without a reboot?
Is the serial driver (asy?) instrumented for debug or dtrace?

> How many `asy' ports show up in `prtconf -v'?  It's usually COM3
> (ttyc) that's used for serial-over-lan.

Actually, on Sun Fire servers those are usually ttya's as well.
On this box it certainly is, "unit=0" in GRUB, "ttyS0" in Linux
and "console=ttya" works for a short while in Solaris/OI.

Answering the direct question, there is only one "asy" unit
(thanks, I didn't think of asy, I only looked for uart, but
they lead to the same piece of hardware):

# prtconf -v | gegrep -B1 -A15 -i 'asy|uart'
             name='ddi-forceload' type=string items=7
                 value='misc/scsi_vhci/scsi_vhci_f_asym_sun' + 
'misc/scsi_vhci/scsi_vhci_f_asym_lsi' + 
'misc/scsi_vhci/scsi_vhci_f_asym_emc' + 
'misc/scsi_vhci/scsi_vhci_f_sym_emc' + 
'misc/scsi_vhci/scsi_vhci_f_sym_hds' + 'misc/scsi_vhci/scsi_vhci_f_sym' 
+ 'misc/scsi_vhci/scsi_vhci_f_tpgs'

...

             asy, instance #0
                 System software properties:
                     name='interrupt-priorities' type=int items=1
                         value=0000000c
                 Hardware properties:
                     name='interrupts' type=int items=1
                         value=00000004
                     name='reg' type=int items=3
                         value=00000001.000003f8.00000008
                     name='model' type=string items=1
                         value='Standard PC COM port'
                     name='compatible' type=string items=1
                         value='PNP0500'
                 Register Specifications:
                     Bus Type=0x1, Address=0x3f8, Size=0x8
                 Interrupt Specifications:
                     Interrupt Priority=0xc (ipl 12), vector=0x4 (4)
                 Device Minor Nodes:
                     dev=(106,0)
                         dev_path=/pci at 0,0/isa at 1f/asy at 1,3f8:a
                             spectype=chr type=minor
                             dev_link=/dev/ttya
                             dev_link=/dev/tty00
                             dev_link=/dev/term/a
                         Minor properties:
                             name='uart' type=string items=1 dev=(106,0)
                                 value='16550A'
                     dev=(106,131072)
                         dev_path=/pci at 0,0/isa at 1f/asy at 1,3f8:a,cu
                             spectype=chr type=minor
                             dev_link=/dev/ttyd0
                             dev_link=/dev/cua0
                             dev_link=/dev/cua/a

...

//Jim Klimov


From jimklimov at cos.ru  Thu Jun 14 20:27:28 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Fri, 15 Jun 2012 00:27:28 +0400
Subject: [OpenIndiana-discuss] Serial console for OI/Solaris on Intel
 MFSYS blades
In-Reply-To: <4FD9FAE3.30106@cos.ru>
References: <4FD9FAE3.30106@cos.ru>
Message-ID: <4FDA4930.60305@cos.ru>

2012-06-14 18:53, Jim Klimov ?????:
> Hello all,
>
>    I have a peculiar problem: the Intel MFSYS blade servers, in short ;)
>
>    They have a number of interesting features, due to which are deployed
> at a number of our customers, but with somewhat under-cooked firmware
> features wherever I've seen. The one bugging me this week is a Remote
> Serial Console implementation.
>
>    This blade chassis has up to 6 server blades, a management module,
> 1 or 2 storage controller modules driving the 14 disks (the SCMs do
> the RAID and publish LUNs to server blades), and 1 or 2 networking
> modules (GbE switches). Overall, quite a bit of redundancy would
> make it a good box, if its code was all working properly ;)
>
>    So, the management module takes the servers' redirected text console
> IO and publishes that as a "SOLCLI" (Serial-Over-LAN CLI) session via
> SSH on dedicated ports like 2201-2206 for the 6 blades. I found next
> to zero specific info on the serial emulation, but it seems to be
> either auto-bauding or (as the Linux blades successfully use it) a
> "115200,8,n,1,-" link. I'd bet auto-bauding, because "9600,8,n,1,-"
> also seems to work. Terminal emulation is unknown, but somewhat like
> VT100 (however, GRUB menu fails to render properly, unless I specify
> "--dumb" for a simplified rendering mode).
>
>    The problem is, the redirected console gets lost after Solaris 10
> or OI boots on the blade. It works somewhat for BIOS and GRUB (but
> even there it sometimes loses connections or farts out invalid
> characters), and if I boot with "-B console=ttya" - sercon usually
> makes it through the OS build version banner and prints a character
> or two of the OS initialization (console logs from SMF startups).

Just in case, here's all the text that makes it to the console:

========
OpenIndiana Build oi_151a4 64-bit (illumos 13676:98ca40df9171)
SunOS Release 5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
All rights reserved. Use is subject to license terms.
WARNING: No randomness provider enabled for /dev/random. Use 
cryptoadm(1M) to enable a provider.
Mo
========

("Mo" seems to be part of the messages reporting the mounting
of root dataset components, I added debugging to my SMF scripts
and that should not be so fatal).

Thanks to Gary's pointers, I looked at "asy" driver code and
found a few tunables (to disable or enforce some tests, and
to limit the FIFO size). I've set them into /etc/system, and
they do get applied upon boot, but they did not help too :(

*** 
http://src.illumos.org/source/xref/illumos-gate/usr/src/uts/common/io/asy.c
set asy:asy_max_tx_fifo=1
set asy:asy_fifo_test=0
set asy:asy_scr_test=0

However, while playing around when the system was booted with
the serial console as the system one, restarting the console
ttymon (svcadm restart console-login:default) has led to the
cached characters (of that SMF script debug output) being
output from the serial console, one character per ttymon stop,
unless I restart them too quickly. Now, that is kind of weird,
but it is something for us to follow on... (and for volunteers
to elaborate on) ;)

Thanks,
//Jim


From jimklimov at cos.ru  Thu Jun 14 21:06:57 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Fri, 15 Jun 2012 01:06:57 +0400
Subject: [OpenIndiana-discuss] Keyboard works sometimes but not always
Message-ID: <4FDA5271.3030804@cos.ru>

There was a comment thread on the Wiki, but the poster did not
manage to write to the mailing list (says he did, but I've not
seen any such posts).

http://wiki.openindiana.org/display/oi/2011.Q4+-+Foreverware?focusedCommentId=23855507#comment-23855507

In short, his latest issue was unstable workability of the
keyboard - sometimes it doesn't work after OI boot, while
it has no issues with older OpenSolaris, SCSE, and newer
OpenBSD and FreeBSD.

Any ideas?

Thanks,
//Jim


From hans.j.albertsson at branneriet.se  Sat Jun 16 15:41:46 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Sat, 16 Jun 2012 17:41:46 +0200
Subject: [OpenIndiana-discuss]
	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <mailman.7891.1339559427.9998.openindiana-discuss@openindiana.org>
References: <mailman.7891.1339559427.9998.openindiana-discuss@openindiana.org>
Message-ID: <4FDCA93A.8000206@branneriet.se>

are the overrides described in that wiki page available in OI151a4??

On 2012-06-13 05:50, openindiana-discuss-request at openindiana.org wrote:
> Message: 4
> Date: Tue, 12 Jun 2012 20:44:25 +0400
> From: Jim Klimov<jimklimov at cos.ru>
> To: Discussion list for OpenIndiana
> 	<openindiana-discuss at openindiana.org>
> Subject: Re: [OpenIndiana-discuss] HDD Upgrade problem
> Message-ID:<4FD771E9.9040009 at cos.ru>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> 2012-06-12 19:22, Jim Klimov wrote:
>> >  First of all, I believe this snippet belongs on a Wiki page,
>> >  and I'll try to make one to sum up all knowledge and FUD we
>> >  have about The AShift Problem;)  At least, it would be easier
>> >  to point people to this page as a common answer;)
> FWIW, here is the first draft:
>
> http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS
>
> Comments/additions welcome,
> //Jim
>


From jimklimov at cos.ru  Sat Jun 16 15:52:37 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sat, 16 Jun 2012 19:52:37 +0400
Subject: [OpenIndiana-discuss]
	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <4FDCA93A.8000206@branneriet.se>
References: <mailman.7891.1339559427.9998.openindiana-discuss@openindiana.org>
	<4FDCA93A.8000206@branneriet.se>
Message-ID: <4FDCABC5.7030307@cos.ru>

2012-06-16 19:41, Hans J. Albertsson wrote:
> are the overrides described in that wiki page available in OI151a4??

>> http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS

Renamed to:
  http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks

In the course of discussion, and by further updates from Richard Elling,
I was led to believe that the sd.conf overrides are part of the lowlevel
illumos-gate shared by several distros, including OI.

Having said that, I did not yet get to test this myself, so can't truly
vouch for accuracy - in this case I only copy-pasted the mail discussion
onto the Wiki. I don't know *when* these overrides got into the kernel,
and if other OpenSolaris derivates (like Solaris 11) have them too.

HTH,
//Jim Klimov


From richard.elling at richardelling.com  Sun Jun 17 15:51:33 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Sun, 17 Jun 2012 08:51:33 -0700
Subject: [OpenIndiana-discuss]
	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <4FDCABC5.7030307@cos.ru>
References: <mailman.7891.1339559427.9998.openindiana-discuss@openindiana.org>
	<4FDCA93A.8000206@branneriet.se> <4FDCABC5.7030307@cos.ru>
Message-ID: <321231C4-8D56-474D-8E78-4DF61997717C@RichardElling.com>

On Jun 16, 2012, at 8:52 AM, Jim Klimov wrote:

> 2012-06-16 19:41, Hans J. Albertsson wrote:
>> are the overrides described in that wiki page available in OI151a4??
> 
>>> http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS
> 
> Renamed to:
> http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks
> 
> In the course of discussion, and by further updates from Richard Elling,
> I was led to believe that the sd.conf overrides are part of the lowlevel
> illumos-gate shared by several distros, including OI.

There are two ways to set overrides:
1. compile them into the driver, which was common for Sun to do for Sun hardware
2. add them to the driver configuration files

IMHO, #2 is much easier than compiling them in, and can be done more easily by
distros. When I worked at Nexenta, I proposed fixes that did change the default
driver config files, but I do not follow Nexenta's current distributions to see if the 
fixes were integrated. In any case, your distribution might have applied changes there.
 -- richard

-- 

ZFS storage and performance consulting at http://www.RichardElling.com








From hans.j.albertsson at branneriet.se  Sun Jun 17 16:04:41 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Sun, 17 Jun 2012 18:04:41 +0200
Subject: [OpenIndiana-discuss]
	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <321231C4-8D56-474D-8E78-4DF61997717C@RichardElling.com>
References: <mailman.7891.1339559427.9998.openindiana-discuss@openindiana.org>
	<4FDCA93A.8000206@branneriet.se> <4FDCABC5.7030307@cos.ru>
	<321231C4-8D56-474D-8E78-4DF61997717C@RichardElling.com>
Message-ID: <4FDE0019.3040705@branneriet.se>

Are you saying that you have no idea at all if these facilities have 
been implemented anywhere??

Can anyone else say???

On 2012-06-17 17:51, Richard Elling wrote:
> On Jun 16, 2012, at 8:52 AM, Jim Klimov wrote:
>
>> 2012-06-16 19:41, Hans J. Albertsson wrote:
>>> are the overrides described in that wiki page available in OI151a4??
>>>> http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS
>> Renamed to:
>> http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks
>>
>> In the course of discussion, and by further updates from Richard Elling,
>> I was led to believe that the sd.conf overrides are part of the lowlevel
>> illumos-gate shared by several distros, including OI.
> There are two ways to set overrides:
> 1. compile them into the driver, which was common for Sun to do for Sun hardware
> 2. add them to the driver configuration files
>
> IMHO, #2 is much easier than compiling them in, and can be done more easily by
> distros. When I worked at Nexenta, I proposed fixes that did change the default
> driver config files, but I do not follow Nexenta's current distributions to see if the
> fixes were integrated. In any case, your distribution might have applied changes there.
>   -- richard
>


From rercola at acm.jhu.edu  Sun Jun 17 19:54:47 2012
From: rercola at acm.jhu.edu (Rich)
Date: Sun, 17 Jun 2012 15:54:47 -0400
Subject: [OpenIndiana-discuss]
	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <4FDE0019.3040705@branneriet.se>
References: <mailman.7891.1339559427.9998.openindiana-discuss@openindiana.org>
	<4FDCA93A.8000206@branneriet.se> <4FDCABC5.7030307@cos.ru>
	<321231C4-8D56-474D-8E78-4DF61997717C@RichardElling.com>
	<4FDE0019.3040705@branneriet.se>
Message-ID: <CAOeNLuqLfS577jx5_V8KrdFMVJcxxkcz8JbBtF1oA92zb+YNNQ@mail.gmail.com>

https://github.com/illumos/illumos-gate/commit/2384d9f8fcca0a7ef8b3ae674d94df82832c0fce
sure looks like it does this in Illumos, though I don't think the OI
kernel in 151a4 is that new [OI IllumOS kernel is dated April 2012,
that patch went into IllumOS early May].

- Rich

On Sun, Jun 17, 2012 at 12:04 PM, Hans J. Albertsson
<hans.j.albertsson at branneriet.se> wrote:
> Are you saying that you have no idea at all if these facilities have been
> implemented anywhere??
>
> Can anyone else say???
>
>
> On 2012-06-17 17:51, Richard Elling wrote:
>>
>> On Jun 16, 2012, at 8:52 AM, Jim Klimov wrote:
>>
>>> 2012-06-16 19:41, Hans J. Albertsson wrote:
>>>>
>>>> are the overrides described in that wiki page available in OI151a4??
>>>>>
>>>>>
>>>>> http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS
>>>
>>> Renamed to:
>>> http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks
>>>
>>> In the course of discussion, and by further updates from Richard Elling,
>>> I was led to believe that the sd.conf overrides are part of the lowlevel
>>> illumos-gate shared by several distros, including OI.
>>
>> There are two ways to set overrides:
>> 1. compile them into the driver, which was common for Sun to do for Sun
>> hardware
>> 2. add them to the driver configuration files
>>
>> IMHO, #2 is much easier than compiling them in, and can be done more
>> easily by
>> distros. When I worked at Nexenta, I proposed fixes that did change the
>> default
>> driver config files, but I do not follow Nexenta's current distributions
>> to see if the
>> fixes were integrated. In any case, your distribution might have applied
>> changes there.
>> ?-- richard
>>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From ramble1035 at dslextreme.com  Sun Jun 17 20:15:49 2012
From: ramble1035 at dslextreme.com (ramble1035 @dslextreme.com)
Date: Sun, 17 Jun 2012 13:15:49 -0700
Subject: [OpenIndiana-discuss] intermittent network? (rge device)
Message-ID: <CAFn3HkNEgh2Lw2qr8PS2ds=+aVthuCTiKZ7tXBijbV-zT0SMTg@mail.gmail.com>

I've got a small PC with two rge networking interfaces (one on the
motherboard, one on a separate pcie card).  I'm seeing some
intermittently flakey behavior, where the network just stops talking.
Looking at it seems to indicate things are alive and well, and my
internal LAN switch shows a hardware connection but no activity.

This last episode, I experienced:
a completely unresponsive local net connection on rge0
ifconfig showed correct values (possibly left over from when it *was* working)
ping out got nothing
ping in got request timeouts and no route to host errors
the other network interface worked fine
netstat -r  produced (eventually) a routing table with a correct
default route, but it took a while.

a reboot produced a "failure to plumb rge0" message on the console

a physical power cycle brought everything up just fine.  It's all
currently working as expected.

Has anyone experienced intermittent network outages?  Is it possible
there are some issues with the rge driver?  Are there any things I can
try to identify an error condition and/or reset the network by hand?

Thanks -

-- C


From hans.j.albertsson at branneriet.se  Mon Jun 18 10:44:22 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Mon, 18 Jun 2012 12:44:22 +0200
Subject: [OpenIndiana-discuss] Very simple network speed testing tools in
	OpenIndiana?
Message-ID: <4FDF0686.4080707@branneriet.se>

Are there any network testing tools that would be suitable to put in the 
hands of people with little or no real understanding of computers?

I'm hoping for some (Web??)server package with client tools for Windows, 
Linux and Mac, or for any web browser.
And I'm hoping for a single-click test to check for speed both ways, 
possibly response times, latency and variations in performance.

I don't want to visit all 1400 residents to test their network connections.


From mike.laspina at laspina.ca  Mon Jun 18 18:54:32 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Mon, 18 Jun 2012 13:54:32 -0500
Subject: [OpenIndiana-discuss] Very simple network speed testing tools
	inOpenIndiana?
In-Reply-To: <4FDF0686.4080707@branneriet.se>
References: <4FDF0686.4080707@branneriet.se>
Message-ID: <8F607366E3C0F9499212649291E0BD640D46F8@MS1.laspina.ca>

You may want to look at http://www.speedtest.net/mini.php

-----Original Message-----
From: Hans J. Albertsson [mailto:hans.j.albertsson at branneriet.se] 
Sent: Monday, June 18, 2012 5:44 AM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] Very simple network speed testing tools
inOpenIndiana?

Are there any network testing tools that would be suitable to put in the
hands of people with little or no real understanding of computers?

I'm hoping for some (Web??)server package with client tools for Windows,
Linux and Mac, or for any web browser.
And I'm hoping for a single-click test to check for speed both ways,
possibly response times, latency and variations in performance.

I don't want to visit all 1400 residents to test their network
connections.

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From chip at innovates.com  Tue Jun 19 19:04:34 2012
From: chip at innovates.com (Schweiss, Chip)
Date: Tue, 19 Jun 2012 14:04:34 -0500
Subject: [OpenIndiana-discuss] OpenIndiana on EC2
Message-ID: <CALeZrrQ8O83fAQCn-zBEJ26pEYrW2qe6+_uAq6HkxNZhC9vpVw@mail.gmail.com>

I've been working from the wiki page:
http://wiki.openindiana.org/oi/Creating+OpenIndiana+EC2+image

No problem getting OI running in Xen on Debian Squeeze w/ the pv-grub.gz
built with the supplied patches.   The problem comes in when launching on
EC2.  The kernel can never mount root.

I've moved my testing to my local Xen and get the same problem anytime the
device numbers are set to 2048 and 2064:

disk = [
'file:/etc/xen/vm/oi_boot.img,2048,w','file:/etc/xen/vm/images/oi_147.img,2064,w'
]

It doesn't seem to matter which build I'm using.   I've tried 147, 148,
151a and 151a3.   This leads me to believe I'm missing something.

If I set the device numbers to 0 and 1,  OI boots fine.

While it was running this way I created the links in /dev/dsk and /dev/rdsk
and changed the device numbers back to 2048 and 2064, but it still fails to
mount root:

Booting command-list

findroot (pool_rpool,0,a)

 Filesystem type is zfs, partition type 0xbf
bootfs rpool/ROOT/openindiana
kernel$ /platform/i86xpv/kernel/$ISADIR/unix -B $ZFS-BOOTFS
loading '/platform/i86xpv/kernel/$ISADIR/unix -B $ZFS-BOOTFS' ...

'/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/85,bootpath="/xpvd/xdf@
1:a"' is loaded
module$ /platform/i86pc/$ISADIR/boot_archive
loading '/platform/i86pc/$ISADIR/boot_archive' ...

'/platform/i86pc/amd64/boot_archive' is loaded

kexec(......,'/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=rpool/85,bootpat
h="/xpvd/xdf at 1:a"')
xc: error: panic: xc_dom_bzimageloader.c:556:
xc_dom_probe_bzimage_kernel: kernel is not a bzImage: Invalid kernel

close blk: backend=/local/domain/0/backend/vbd/68/2048 node=device/vbd/2048
close blk: backend=/local/domain/0/backend/vbd/68/2064 node=device/vbd/2064
v4.0.1 chgset 'unavailable'
OpenIndiana Build oi_147 64-bit

SunOS Release 5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
All rights reserved. Use is subject to license terms.
NOTICE: Can not read the pool label from '/xpvd/xdf at 1:a'
NOTICE: spa_import_rootpool: error 5

Cannot mount root on /xpvd/xdf at 1:a fstype zfs

panic[cpu0]/thread=fffffffffbc609e0: vfs_mountroot: cannot mount root

Warning - stack not written to the dump buffer
fffffffffbcb5080 genunix:vfs_mountroot+33e <http://genunixvfs_mountroot+33e> ()

fffffffffbcb50b0 genunix:main+136 <http://genunixmain+136> ()
fffffffffbcb50c0 unix:_locore_start+7e ()

skipping system dump - no dump device configured
rebooting...


I'm guessing the links were not loaded properly.  Any help would be greatly
appreciated.

From matt.connolly.au at gmail.com  Tue Jun 19 22:28:35 2012
From: matt.connolly.au at gmail.com (Matt Connolly)
Date: Wed, 20 Jun 2012 08:28:35 +1000
Subject: [OpenIndiana-discuss] intermittent network? (rge device)
In-Reply-To: <CAFn3HkNEgh2Lw2qr8PS2ds=+aVthuCTiKZ7tXBijbV-zT0SMTg@mail.gmail.com>
References: <CAFn3HkNEgh2Lw2qr8PS2ds=+aVthuCTiKZ7tXBijbV-zT0SMTg@mail.gmail.com>
Message-ID: <CAJ9ip5yJgUMNCtrvRbG=3GLMwE0Q3nHN0EaaC4fUoUo+dFonDQ@mail.gmail.com>

I have oi-151a4 running on an Intel D510 (atom) motherboard for a
storage server at home, and it has an rge interface. In the days of
OpenSolaris there were some problems with the driver which sound
similar to your description. I haven't seen those problems since it
was openSolaris-133 i think. Certainly not since OpenIndiana.

My driver shows up in `prtconf -v` as:

dev_path=/pci at 0,0/pci8086,27d0 at 1c/pci8086,d615 at 0:rge0

I take it the problem is with the motherboard interface (rge0)? Are
there any bios/firmware updates for your machine?

Best,
Matt

On 18 June 2012 06:15, ramble1035 @dslextreme.com
<ramble1035 at dslextreme.com> wrote:
> I've got a small PC with two rge networking interfaces (one on the
> motherboard, one on a separate pcie card). ?I'm seeing some
> intermittently flakey behavior, where the network just stops talking.
> Looking at it seems to indicate things are alive and well, and my
> internal LAN switch shows a hardware connection but no activity.
>
> This last episode, I experienced:
> a completely unresponsive local net connection on rge0
> ifconfig showed correct values (possibly left over from when it *was* working)
> ping out got nothing
> ping in got request timeouts and no route to host errors
> the other network interface worked fine
> netstat -r ?produced (eventually) a routing table with a correct
> default route, but it took a while.
>
> a reboot produced a "failure to plumb rge0" message on the console
>
> a physical power cycle brought everything up just fine. ?It's all
> currently working as expected.
>
> Has anyone experienced intermittent network outages? ?Is it possible
> there are some issues with the rge driver? ?Are there any things I can
> try to identify an error condition and/or reset the network by hand?
>
> Thanks -
>
> -- C
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From mike.laspina at laspina.ca  Wed Jun 20 02:19:54 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Tue, 19 Jun 2012 21:19:54 -0500
Subject: [OpenIndiana-discuss] intermittent network? (rge device)
In-Reply-To: <CAFn3HkNEgh2Lw2qr8PS2ds=+aVthuCTiKZ7tXBijbV-zT0SMTg@mail.gmail.com>
References: <CAFn3HkNEgh2Lw2qr8PS2ds=+aVthuCTiKZ7tXBijbV-zT0SMTg@mail.gmail.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D46FD@MS1.laspina.ca>

I have one system running an rge card. No issues at all, it's running 2
years now with 134 through 151a4. It a storage server and it's running
light to medium load. 

What else do you have configured? 
NWAM? 
Layer 2 dladm elements? 
dmesg output? 
Does snoop reveal anything when it goes unresponsive?
Shared irqs? echo ::interrupts | pfexec mdb -k
pfexec intrstat seem normal during the event?

-----Original Message-----
From: ramble1035 @dslextreme.com [mailto:ramble1035 at dslextreme.com] 
Sent: Sunday, June 17, 2012 3:16 PM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] intermittent network? (rge device)

I've got a small PC with two rge networking interfaces (one on the
motherboard, one on a separate pcie card).  I'm seeing some
intermittently flakey behavior, where the network just stops talking.
Looking at it seems to indicate things are alive and well, and my
internal LAN switch shows a hardware connection but no activity.

This last episode, I experienced:
a completely unresponsive local net connection on rge0 ifconfig showed
correct values (possibly left over from when it *was* working) ping out
got nothing ping in got request timeouts and no route to host errors the
other network interface worked fine netstat -r  produced (eventually) a
routing table with a correct default route, but it took a while.

a reboot produced a "failure to plumb rge0" message on the console

a physical power cycle brought everything up just fine.  It's all
currently working as expected.

Has anyone experienced intermittent network outages?  Is it possible
there are some issues with the rge driver?  Are there any things I can
try to identify an error condition and/or reset the network by hand?

Thanks -

-- C

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From hans.j.albertsson at branneriet.se  Wed Jun 20 08:42:38 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Wed, 20 Jun 2012 10:42:38 +0200
Subject: [OpenIndiana-discuss] ,
	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
References: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
Message-ID: <4FE18CFE.1020204@branneriet.se>

Is the OI151 kernel going to be updated anytime soon?

Alternatively, if I have an OI151a4 machine running well on a SuperMicro 
machine, is there another Illumos distro I could move to w/o too much pain?

On 2012-06-20 00:28, openindiana-discuss-request at openindiana.org wrote:
> Date: Sun, 17 Jun 2012 15:54:47 -0400
> From: Rich<rercola at acm.jhu.edu>
> To: Discussion list for OpenIndiana
> 	<openindiana-discuss at openindiana.org>
> Subject: Re: [OpenIndiana-discuss]
> 	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
> Message-ID:
> 	<CAOeNLuqLfS577jx5_V8KrdFMVJcxxkcz8JbBtF1oA92zb+YNNQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> https://github.com/illumos/illumos-gate/commit/2384d9f8fcca0a7ef8b3ae674d94df82832c0fce
> sure looks like it does this in Illumos, though I don't think the OI
> kernel in 151a4 is that new [OI IllumOS kernel is dated April 2012,
> that patch went into IllumOS early May].
>
> - Rich
>
> On Sun, Jun 17, 2012 at 12:04 PM, Hans J. Albertsson
> <hans.j.albertsson at branneriet.se>  wrote:
>> >  Are you saying that you have no idea at all if these facilities have been
>> >  implemented anywhere??
>> >
>> >  Can anyone else say???
>> >
>> >
>> >  On 2012-06-17 17:51, Richard Elling wrote:
>>> >>
>>> >>  On Jun 16, 2012, at 8:52 AM, Jim Klimov wrote:
>>> >>
>>>> >>>  2012-06-16 19:41, Hans J. Albertsson wrote:
>>>>> >>>>
>>>>> >>>>  are the overrides described in that wiki page available in OI151a4??
>>>>>> >>>>>
>>>>>> >>>>>
>>>>>> >>>>>  http://wiki.illumos.org/display/illumos/The+AShift+Value+and+Advanced+Format+disks+and+ZFS
>>>> >>>
>>>> >>>  Renamed to:
>>>> >>>  http://wiki.illumos.org/display/illumos/ZFS+and+Advanced+Format+disks
>>>> >>>
>>>> >>>  In the course of discussion, and by further updates from Richard Elling,
>>>> >>>  I was led to believe that the sd.conf overrides are part of the lowlevel
>>>> >>>  illumos-gate shared by several distros, including OI.
>>> >>
>>> >>  There are two ways to set overrides:
>>> >>  1. compile them into the driver, which was common for Sun to do for Sun
>>> >>  hardware
>>> >>  2. add them to the driver configuration files
>>> >>
>>> >>  IMHO, #2 is much easier than compiling them in, and can be done more
>>> >>  easily by
>>> >>  distros. When I worked at Nexenta, I proposed fixes that did change the
>>> >>  default
>>> >>  driver config files, but I do not follow Nexenta's current distributions
>>> >>  to see if the
>>> >>  fixes were integrated. In any case, your distribution might have applied
>>> >>  changes there.
>>> >>  ?-- richard
>>> >>
>> >
>> >  _______________________________________________
>> >  OpenIndiana-discuss mailing list
>> >  OpenIndiana-discuss at openindiana.org
>> >  http://openindiana.org/mailman/listinfo/openindiana-discuss


From jimklimov at cos.ru  Wed Jun 20 10:54:59 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 20 Jun 2012 14:54:59 +0400
Subject: [OpenIndiana-discuss] ,
	The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <4FE18CFE.1020204@branneriet.se>
References: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
	<4FE18CFE.1020204@branneriet.se>
Message-ID: <4FE1AC03.1090301@cos.ru>

2012-06-20 12:42, Hans J. Albertsson wrote:
> Is the OI151 kernel going to be updated anytime soon?

I don't know - I'm also on the outside of the project core.
I think the idea was to have roughly monthly (or quarterly?)
dev-releases, and some time has passed since early May ;)

> Alternatively, if I have an OI151a4 machine running well on a SuperMicro
> machine, is there another Illumos distro I could move to w/o too much pain?

Technically yes, you can follow the How To Build Illumos
wiki page and build your own kernel from up-to-date bits,
while the rest would remain the same OI at your discretion
(you can also rebuild that according to a different manual).
You'd need to ensure that your build's number is higher
than the installed packages (described in Wiki) and wait
a while for the compilation to complete. The process is
quite straightforward, I think - I spent some time earlier
revising this wiki page in places where there was something
to elaborate on in greater detail (now seen as child pages).

HTH,
//Jim Klimov


From rjp_sun at fubegra.net  Wed Jun 20 11:38:58 2012
From: rjp_sun at fubegra.net (Russ Price)
Date: Wed, 20 Jun 2012 06:38:58 -0500
Subject: [OpenIndiana-discuss] intermittent network? (rge device)
In-Reply-To: <CAFn3HkNEgh2Lw2qr8PS2ds=+aVthuCTiKZ7tXBijbV-zT0SMTg@mail.gmail.com>
References: <CAFn3HkNEgh2Lw2qr8PS2ds=+aVthuCTiKZ7tXBijbV-zT0SMTg@mail.gmail.com>
Message-ID: <4FE1B652.50605@fubegra.net>

On 06/17/2012 03:15 PM, ramble1035 @dslextreme.com wrote:
> I've got a small PC with two rge networking interfaces (one on the
> motherboard, one on a separate pcie card).  I'm seeing some
> intermittently flakey behavior, where the network just stops talking.
> Looking at it seems to indicate things are alive and well, and my
> internal LAN switch shows a hardware connection but no activity.
>
> This last episode, I experienced:
> a completely unresponsive local net connection on rge0
> ifconfig showed correct values (possibly left over from when it *was* working)
> ping out got nothing
> ping in got request timeouts and no route to host errors
> the other network interface worked fine
> netstat -r  produced (eventually) a routing table with a correct
> default route, but it took a while.
>

Until recently, my experience with rge was good - at least on
Asus M4A785-M and M5A97 motherboards, where they've never skipped a beat.
However, I ran into the exact same behavior you're seeing on an
M5A88-V EVO that I recently built up. My solution was to disable it
and use an Intel PCIe card.


From jimklimov at cos.ru  Wed Jun 20 11:40:40 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 20 Jun 2012 15:40:40 +0400
Subject: [OpenIndiana-discuss] Idea on mixing OI and SVR4 sparse zones
Message-ID: <4FE1B6B8.2050109@cos.ru>

Hello David et al,

I had a new idea for your project of using OI as a base for
the distro to sustain/update existing Solaris deployments.

In *our* systems management we have relatively little use
for sparse-root zones, but quite a bit more of full-root
ones, and to save on disk space (and minimize human error)
we pre-create a "golden dummy" zone which remains unused
per se, while its zfs clones are used to initialize the
application zones. I understand that other deployments
may have more use for sparse-root zones.

I believe that fundamental differences between zones of
different packaging would be in their branding and the
scripts which implement this zone-branding (i.e. actions
upon boot/attach/upgrade/etc.) - for example, an SVR4
"native" zone-attachment or even bootup might involve
detection of packages installed in the global zone
(or some other SVR4 template zone) and migration of zone
info into the local zone's /var/sadm/install/contents,
/var/sadm/pkg/* and similar databases.

I wonder: if we add support for SVR4 zones into OI, maybe
with an option to support sparse-root zones in some manner
like read-only lofi-mounts of *some* /usr /lib etc. images,
why not also support an svr4-golden zone type which would
be a golden-image zone for mounting into sparse zones (and
maybe for cloning into full-root zones - though any source
zone can be cloned). This way updates of an svr4-golden
zone would automatically propagate into svr4-sparse zones
which are based on this golden zone instance, just like
it used to take place for native SVR4 global zones.

The differences now would be:
1) Instead of one global zone, there can be several golden
    zones to template for different tasks; it would also be
    more simple to have a "full" installation with GUI in GZ
    and a "minimized" installation in its zones

2) The GZ can be of any type (like IPS or DEB), while SVR4
    packaging can be used to instantiate and bulk-upgrade
    sparse-root zones;

3) Possibly, it might make sense to change an LZ's assigned
    golden zone (where it mounts its binaries from) so as to
    change versions or whole software sets - perhaps this
    could aid in one-by-one migrations into newer software.
    Maybe, even, migrate an SVR4-based zone into an ipkg zone
    with an identical set of software in different packaging.

PS: I think some terminology should be made, because the
way I wrote it above, "GZ" stands for Global Zones as usual,
but could be mistaken for "golden zones". Maybe, define TZ
(template zones) or something like that? ;)

HTH,
//Jim Klimov



From hans.j.albertsson at branneriet.se  Wed Jun 20 12:31:57 2012
From: hans.j.albertsson at branneriet.se (Hans J. Albertsson)
Date: Wed, 20 Jun 2012 14:31:57 +0200
Subject: [OpenIndiana-discuss] OI151a4: ld.so.1: cadaver: fatal: relocation
 error: file /usr/lib/libreadline.so.5: symbol tgetent: referenced symbol
 not found
In-Reply-To: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
References: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
Message-ID: <4FE1C2BD.1030506@branneriet.se>

I installed the cadaver WebDav program from SFE, and when running it, I 
get the below error.


cadaver http://www.branneriet.se/
.....
Connection to `www.branneriet.se' closed.
ld.so.1: cadaver: fatal: relocation error: file 
/usr/lib/libreadline.so.5: symbol tgetent: referenced symbol not found
Killed


Before I spend a lot of effort finding a cure ( I suppose it's a problem 
in libreadline linking termcap) I thought to ask if there's a known easy 
fix.

An alternative would be to point me at some other way to run a webdav 
client on OI151a4


From udo.grabowski at kit.edu  Wed Jun 20 12:46:42 2012
From: udo.grabowski at kit.edu (Udo Grabowski (IMK))
Date: Wed, 20 Jun 2012 14:46:42 +0200
Subject: [OpenIndiana-discuss] OI151a4: ld.so.1: cadaver: fatal:
 relocation error: file /usr/lib/libreadline.so.5: symbol tgetent:
 referenced symbol not found
In-Reply-To: <4FE1C2BD.1030506@branneriet.se>
References: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
	<4FE1C2BD.1030506@branneriet.se>
Message-ID: <4FE1C632.5060808@kit.edu>

On 20/06/2012 14:31, Hans J. Albertsson wrote:
> I installed the cadaver WebDav program from SFE, and when running it, I get the
> below error.
>
>
> cadaver http://www.branneriet.se/
> .....
> Connection to `www.branneriet.se' closed.
> ld.so.1: cadaver: fatal: relocation error: file /usr/lib/libreadline.so.5:
> symbol tgetent: referenced symbol not found
> Killed
>
>
> Before I spend a lot of effort finding a cure ( I suppose it's a problem in
> libreadline linking termcap) I thought to ask if there's a known easy fix.
>
> An alternative
would be to point me at some other way to run a webdav client on
> OI151a4

This workaround helps (and reveals that the server is not WebDAV enabled....)
setenv LD_PRELOAD /usr/lib/libcurses.so (for csh/tcsh, or
export LD_PRELOAD=/usr/lib/libcurses.so for bash)
cadaver http://www.branneriet.se/ or https://www.branneriet.se/


-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026


From bfriesen at simple.dallas.tx.us  Wed Jun 20 13:48:45 2012
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Wed, 20 Jun 2012 08:48:45 -0500 (CDT)
Subject: [OpenIndiana-discuss] ,
 The+AShift+Value+and+Advanced+Format+disks+and+ZFS
In-Reply-To: <4FE18CFE.1020204@branneriet.se>
References: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
	<4FE18CFE.1020204@branneriet.se>
Message-ID: <alpine.GSO.2.01.1206200839360.10821@freddy.simplesystems.org>

On Wed, 20 Jun 2012, Hans J. Albertsson wrote:

> Is the OI151 kernel going to be updated anytime soon?
>
> Alternatively, if I have an OI151a4 machine running well on a SuperMicro 
> machine, is there another Illumos distro I could move to w/o too much pain?

OpenIndiana build 151a is indeed rather stale and not capable of 
installing on some recent hardware.  Illumos has progressed quite a 
lot since last September.  Illumos has recently made some significant 
leaps (e.g. GCC 4.4 compilation) and perhaps OpenIndiana wants to pick 
up these and make sure that it is all stable before making another 
formal release.

I hope to accept delivery of a SuperMicro machine this week which 
required 151a4 in order to use its network interfaces and support 
audio.

Bob
-- 
Bob Friesenhahn
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


From hans.j.albertsson at branneriet.se  Wed Jun 20 14:11:02 2012
From: hans.j.albertsson at branneriet.se (Hans J Albertsson)
Date: Wed, 20 Jun 2012 16:11:02 +0200
Subject: [OpenIndiana-discuss] OI151a4: ld.so.1: cadaver: fatal:
 relocation error: file /usr/lib/libreadline.so.5: symbol tgetent:
 referenced symbol not found
Message-ID: <4x6qghym0nd3kudjknmbg487.1340201451099@email.android.com>

Thanks. I know it isn't dav enabled.






Skickat fr?n min Android Mobil"Udo Grabowski (IMK)" <udo.grabowski at kit.edu> skrev:On 20/06/2012 14:31, Hans J. Albertsson wrote:
> I installed the cadaver WebDav program from SFE, and when running it, I get the
> below error.
>
>
> cadaver http://www.branneriet.se/
> .....
> Connection to `www.branneriet.se' closed.
> ld.so.1: cadaver: fatal: relocation error: file /usr/lib/libreadline.so.5:
> symbol tgetent: referenced symbol not found
> Killed
>
>
> Before I spend a lot of effort finding a cure ( I suppose it's a problem in
> libreadline linking termcap) I thought to ask if there's a known easy fix.
>
> An alternative
would be to point me at some other way to run a webdav client on
> OI151a4

This workaround helps (and reveals that the server is not WebDAV enabled....)
setenv LD_PRELOAD /usr/lib/libcurses.so (for csh/tcsh, or
export LD_PRELOAD=/usr/lib/libcurses.so for bash)
cadaver http://www.branneriet.se/ or https://www.branneriet.se/


-- 
Dr.Udo Grabowski??? Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology??????????? http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany? T:(+49)721 608-26026 F:-926026

From jimklimov at cos.ru  Wed Jun 20 15:22:17 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 20 Jun 2012 19:22:17 +0400
Subject: [OpenIndiana-discuss] VirtualBox in an IPS repo?
Message-ID: <4FE1EAA9.1010008@cos.ru>

Hello,

   I was asked why the OI repos don't provide VirtualBox?

   My first reply was that this may be because of PUEL license
limitations; however, since release of the 4.x branch, the
basic software and its source code are GPLv2, with only the
Extended Pack being PUEL.

   Hence the question: it there anything (but lack of time
and other resources) forbidding the IPS redistribution of
VirtualBox? Can the original Oracle SVR4 package be repacked
for IPS, or must that be a private rebuild? Finally, which
repo would that best fit into (illumos-userland, SFE, etc.)
if anyone were to do this quest?

Thanks for info,
//Jim Klimov


From gordon.w.ross at gmail.com  Wed Jun 20 16:51:04 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Wed, 20 Jun 2012 12:51:04 -0400
Subject: [OpenIndiana-discuss] OI151a4: ld.so.1: cadaver: fatal:
 relocation error: file /usr/lib/libreadline.so.5: symbol tgetent:
 referenced symbol not found
In-Reply-To: <4FE1C632.5060808@kit.edu>
References: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>
	<4FE1C2BD.1030506@branneriet.se> <4FE1C632.5060808@kit.edu>
Message-ID: <CAD0Ztp3o2ap4op_280EDbromsONLObnuyZMeiZLoGbtLuVG-mw@mail.gmail.com>

On Wed, Jun 20, 2012 at 8:46 AM, Udo Grabowski (IMK)
<udo.grabowski at kit.edu> wrote:
> On 20/06/2012 14:31, Hans J. Albertsson wrote:
>>
>> I installed the cadaver WebDav program from SFE, and when running it, I
>> get the
>> below error.
>>
>>
>> cadaver http://www.branneriet.se/
>> .....
>> Connection to `www.branneriet.se' closed.
>> ld.so.1: cadaver: fatal: relocation error: file /usr/lib/libreadline.so.5:
>> symbol tgetent: referenced symbol not found
>> Killed
>>
>>
>> Before I spend a lot of effort finding a cure ( I suppose it's a problem
>> in
>> libreadline linking termcap) I thought to ask if there's a known easy fix.
>>
>> An alternative

Huh.  After I implemented https://www.illumos.org/issues/1168
I thought libreadline got fixed so it would always find either the
tgetent from the calling program, or the one in libtermcap.
Right: here is the second issue, for readline:
https://www.illumos.org/issues/1206

Unfortunately it looks like this never got integrated.
What does this command show you:
  elfdump -d /usr/lib/libreadline.so.5

On my system, there's no NEEDED line for libcurses
(and I think I'm up to date).

So consider this a request to integrate 1206.

Thanks,

-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From udo.grabowski at kit.edu  Wed Jun 20 17:07:36 2012
From: udo.grabowski at kit.edu (Udo Grabowski (IMK))
Date: Wed, 20 Jun 2012 19:07:36 +0200
Subject: [OpenIndiana-discuss] OI151a4: ld.so.1: cadaver: fatal:
 relocation error: file /usr/lib/libreadline.so.5: symbol tgetent:
 referenced symbol not found
In-Reply-To: <CAD0Ztp3o2ap4op_280EDbromsONLObnuyZMeiZLoGbtLuVG-mw@mail.gmail.com>
References: <mailman.8574.1340144918.9998.openindiana-discuss@openindiana.org>	<4FE1C2BD.1030506@branneriet.se>
	<4FE1C632.5060808@kit.edu>
	<CAD0Ztp3o2ap4op_280EDbromsONLObnuyZMeiZLoGbtLuVG-mw@mail.gmail.com>
Message-ID: <4FE20358.7030601@kit.edu>

On 20/06/2012 18:51, Gordon Ross wrote:
> On Wed, Jun 20, 2012 at 8:46 AM, Udo Grabowski (IMK)
> <udo.grabowski at kit.edu>  wrote:
>> On 20/06/2012 14:31, Hans J. Albertsson wrote:
>>>
>>> I installed the cadaver WebDav program from SFE, and when running it, I
>>> get the
>>> below error.
>>>
>>>
>>> cadaver http://www.branneriet.se/
>>> .....
>>> Connection to `www.branneriet.se' closed.
>>> ld.so.1: cadaver: fatal: relocation error: file /usr/lib/libreadline.so.5:
>>> symbol tgetent: referenced symbol not found
>>> Killed
>>>
>>>
>>> Before I spend a lot of effort finding a cure ( I suppose it's a problem
>>> in
>>> libreadline linking termcap) I thought to ask if there's a known easy fix.
>>>
>>> An alternative
>
> Huh.  After I implemented https://www.illumos.org/issues/1168
> I thought libreadline got fixed so it would always find either the
> tgetent from the calling program, or the one in libtermcap.
> Right: here is the second issue, for readline:
> https://www.illumos.org/issues/1206
>
> Unfortunately it looks like this never got integrated.
> What does this command show you:
>    elfdump -d /usr/lib/libreadline.so.5
>

oi_151a4:

Dynamic Section:  .dynamic
      index  tag                value
        [0]  NEEDED            0x381b              libc.so.1
        [1]  SONAME            0x1                 libreadline.so.5
        [2]  HASH              0x1c4
        [3]  STRTAB            0x4c80
        [4]  STRSZ             0x3a57
        [5]  SYMTAB            0x2240
        [6]  SYMENT            0x10
        [7]  SUNW_SYMTAB       0x16f0
        [8]  SUNW_SYMSZ        0x3590
        [9]  SUNW_SORTENT      0x4
       [10]  SUNW_SYMSORT      0x8c80
       [11]  SUNW_SYMSORTSZ    0xb78
       [12]  CHECKSUM          0xc96b
       [13]  VERNEED           0x86d8
       [14]  VERNEEDNUM        0x1
       [15]  RELCOUNT          0xfc
       [16]  PLTRELSZ          0xaa0
       [17]  PLTREL            0x11
       [18]  JMPREL            0xc158
       [19]  REL               0x97f8
       [20]  RELSZ             0x3400
       [21]  RELENT            0x8
       [22]  FLAGS             0                   0
       [23]  FLAGS_1           0                   0
       [24]  SUNW_STRPAD       0x200
       [25]  SUNW_LDMACH       0x3e                EM_AMD64
       [26]  PLTGOT            0x3c094
    [27-37]  NULL              0


-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026


From milan.jurik at xylab.cz  Wed Jun 20 19:24:59 2012
From: milan.jurik at xylab.cz (Milan Jurik)
Date: Wed, 20 Jun 2012 21:24:59 +0200
Subject: [OpenIndiana-discuss] VirtualBox in an IPS repo?
In-Reply-To: <4FE1EAA9.1010008@cos.ru>
References: <4FE1EAA9.1010008@cos.ru>
Message-ID: <1340220299.1366.4.camel@xylabone>

Hi,

Jim Klimov p??e v st 20. 06. 2012 v 19:22 +0400:
> Hello,
> 
>    I was asked why the OI repos don't provide VirtualBox?
> 
>    My first reply was that this may be because of PUEL license
> limitations; however, since release of the 4.x branch, the
> basic software and its source code are GPLv2, with only the
> Extended Pack being PUEL.
> 
>    Hence the question: it there anything (but lack of time
> and other resources) forbidding the IPS redistribution of
> VirtualBox? Can the original Oracle SVR4 package be repacked
> for IPS, or must that be a private rebuild? Finally, which
> repo would that best fit into (illumos-userland, SFE, etc.)
> if anyone were to do this quest?
> 

VBox team was delivering IPS package for some time. But their
requirements for preinstall/postinstall were in collision with IPS team
view. It is hard to judge who was/is right but generally, what is wrong
with this SVR4 package (except "autoupdate" I would not recommend in
case of VBox anyway)?

As if the original SVR4 package can be repacked - you need to do more
than just publish it as IPS, you have to deal with all work needed
during install process. Also building VBox on Solaris was not simple
task, not sure if it improved.

> Thanks for info,
> //Jim Klimov
> 

Best regards,

Milan



From philippe at twixel.be  Thu Jun 21 07:01:46 2012
From: philippe at twixel.be (Philippe Huybrechts)
Date: Thu, 21 Jun 2012 07:01:46 +0000 (UTC)
Subject: [OpenIndiana-discuss] NFS Server permission problems
References: <4F7EC6B0.2080606@acw.at>
Message-ID: <loom.20120621T084015-759@post.gmane.org>

If you disable init logging , the file will not be created.

in /etc/vz/vz.conf:
INITLOG=no

The underlying issue is that the file is created from outside the container with
the synchronous attribute set. This gets interpreted by the Indiana NFS server
as "mandatory locking": as NFS3 has no locking, all access to the file will be
blocked via NFS, unless the execute bit is set.

So you can either disable init logging or fixup the permissions after creation
of the file (will survive a restart of the container)

It is also something to be aware of when moving vz/private areas from local
storage onto the NFS server, as any file with these bits set will become
inaccessible. Not that there are a lot, but for example Subversion repositories
use it.





From mklassen at imaging.robarts.ca  Thu Jun 21 17:56:42 2012
From: mklassen at imaging.robarts.ca (Martyn Klassen)
Date: Thu, 21 Jun 2012 13:56:42 -0400
Subject: [OpenIndiana-discuss] Time slider missing some snapshots and not
	deleting snapshots
Message-ID: <8FC7D58A-1AAF-4E88-B343-9B4335D623D9@imaging.robarts.ca>

Time slider is missing the creation of some and deletion of all snapshot of filesystems on my data pool. The snapshots are only create for the last filesystem in a tree, for example with pool data and filesystems

data/fsA
data/fsB/fs1
data/fsC
data/fsD/fs1
data/fsE

only data/fsB/fs1 and data/fsD/fs1 get a snapshot and the snapshots are not deleted properly, ie frequent snapshots just keep getting added beyond the 3 that are supposed to be kept. 

After playing with various setting, I found a solution that appears to be working for me. So far it is handling frequent snapshots correctly.

The short version:
Do not set com.sun:auto-snapshot properties on the pool, ie data, but on filesystems created on the pool, ie fsA - fsB.

The long version:
The issue seems to be related to inheriting com.sun:auto-snapshot and the recursion algorithms being used to make and destroy snapshots.

I found this old post http://mail.opensolaris.org/pipermail/indiana-discuss/2009-December/017161.html which made me investigate whether the issue is related to the snapshot properties being inherited directly from the pool and auto-snapshots recursion algorithm. The time slider code base has obvious changed since that post, but I decided to try the following anyway

zfs create data/nosnap
zfs set com.sun:auto-snapshot=false data/nosnap
zfs set com.sun:auto-snapshot:hourly=false data/nosnap
zfs set  com.sun:auto-snapshot:frequent=false  data/nosnap
zfs set  com.sun:auto-snapshot:daily=false data/nosnap
zfs set  com.sun:auto-snapshot:weekly=false  data/nosnap
zfs set  com.sun:auto-snapshot:monthly=false data/nosnap

Basically the idea is that the data/nosnap filesystem with all auto-snapshot properties set to false should force auto-snapshot to address each filesystem separately. and not act recursively on data. With this change time-slider starting making snapshots for data/fsD/fs1 and data/fsE get snapshots, but none of the rest, and none of the snapshots get deleted properly.

My next attempt was to clear all the com.sun:auto-snapshot properties from data and set them on the filesystems fsA, fsB, fsC, fsD, and fsE, and then all the snapshots were create and destroyed as expected.

zfs set com.sun:auto-snapshot=true data/fsA
zfs set com.sun:auto-snapshot=true data/fsB
zfs set com.sun:auto-snapshot=true data/fsC
zfs set com.sun:auto-snapshot=true data/fsD
zfs set com.sun:auto-snapshot=true data/fsE

Obviously this is more tedious that just setting the properties on data, but at least the snapshots seem to work for me now. Hopefully this is useful for anyone else running into this issue, and if someone can point me in the right direction to submit a bug report on this, maybe it can get fixed in a future release.

Just a bit more about my configuration for reference:

# uname
SunOS ****** 5.11 oi_151a4 i86pc i386 i86pc Solaris
# pkg info time-slider
          Name: desktop/time-slider
       Summary: Time Slider ZFS snapshot management for GNOME
   Description: Time Slider ZFS snapshot management for GNOME
      Category: Applications/Configuration and Preferences
         State: Installed
     Publisher: openindiana.org
       Version: 0.2.97
 Build Release: 5.11
        Branch: 0.151.1.4
Packaging Date: May  2, 2012 10:25:35 PM 
          Size: 715.80 kB
          FMRI: pkg://openindiana.org/desktop/time-slider at 0.2.97,5.11-0.151.1.4:20120502T222535Z



From mklassen at imaging.robarts.ca  Fri Jun 22 14:01:42 2012
From: mklassen at imaging.robarts.ca (Martyn Klassen)
Date: Fri, 22 Jun 2012 10:01:42 -0400
Subject: [OpenIndiana-discuss] Time slider missing some snapshots and
	not deleting snapshots
In-Reply-To: <8FC7D58A-1AAF-4E88-B343-9B4335D623D9@imaging.robarts.ca>
References: <8FC7D58A-1AAF-4E88-B343-9B4335D623D9@imaging.robarts.ca>
Message-ID: <4360A1C2-4358-46F9-BF83-AFF0B22F8F4F@imaging.robarts.ca>

I guess I spoke too soon. After letting time-slider run for the day, I ended up with way too many frequent snapshot and a bunch of missing snapshots, so something is more seriously wrong with the recursion algorithms being used by time-slider. I even ran another test - with 5 minute interval frequent snapshots - intentionally changing every filesystem so that no snapshot is ever zero sized and still some filesystems are not getting snapshots. Missing snapshots always occurs in filesystems preceding those with children, which seems to point to recursion issues. My guess is the deletion problems are related.

If anyone has any suggestions on how to debug these time-slider issues they would be appreciated. 

Martyn

On 2012-06-21, at 13:56 , Martyn Klassen wrote:

> Time slider is missing the creation of some and deletion of all snapshot of filesystems on my data pool. The snapshots are only create for the last filesystem in a tree, for example with pool data and filesystems
> 
> data/fsA
> data/fsB/fs1
> data/fsC
> data/fsD/fs1
> data/fsE
> 
> only data/fsB/fs1 and data/fsD/fs1 get a snapshot and the snapshots are not deleted properly, ie frequent snapshots just keep getting added beyond the 3 that are supposed to be kept. 
> 
> After playing with various setting, I found a solution that appears to be working for me. So far it is handling frequent snapshots correctly.
> 
> The short version:
> Do not set com.sun:auto-snapshot properties on the pool, ie data, but on filesystems created on the pool, ie fsA - fsB.
> 
> The long version:
> The issue seems to be related to inheriting com.sun:auto-snapshot and the recursion algorithms being used to make and destroy snapshots.
> 
> I found this old post http://mail.opensolaris.org/pipermail/indiana-discuss/2009-December/017161.html which made me investigate whether the issue is related to the snapshot properties being inherited directly from the pool and auto-snapshots recursion algorithm. The time slider code base has obvious changed since that post, but I decided to try the following anyway
> 
> zfs create data/nosnap
> zfs set com.sun:auto-snapshot=false data/nosnap
> zfs set com.sun:auto-snapshot:hourly=false data/nosnap
> zfs set  com.sun:auto-snapshot:frequent=false  data/nosnap
> zfs set  com.sun:auto-snapshot:daily=false data/nosnap
> zfs set  com.sun:auto-snapshot:weekly=false  data/nosnap
> zfs set  com.sun:auto-snapshot:monthly=false data/nosnap
> 
> Basically the idea is that the data/nosnap filesystem with all auto-snapshot properties set to false should force auto-snapshot to address each filesystem separately. and not act recursively on data. With this change time-slider starting making snapshots for data/fsD/fs1 and data/fsE get snapshots, but none of the rest, and none of the snapshots get deleted properly.
> 
> My next attempt was to clear all the com.sun:auto-snapshot properties from data and set them on the filesystems fsA, fsB, fsC, fsD, and fsE, and then all the snapshots were create and destroyed as expected.
> 
> zfs set com.sun:auto-snapshot=true data/fsA
> zfs set com.sun:auto-snapshot=true data/fsB
> zfs set com.sun:auto-snapshot=true data/fsC
> zfs set com.sun:auto-snapshot=true data/fsD
> zfs set com.sun:auto-snapshot=true data/fsE
> 
> Obviously this is more tedious that just setting the properties on data, but at least the snapshots seem to work for me now. Hopefully this is useful for anyone else running into this issue, and if someone can point me in the right direction to submit a bug report on this, maybe it can get fixed in a future release.
> 
> Just a bit more about my configuration for reference:
> 
> # uname
> SunOS ****** 5.11 oi_151a4 i86pc i386 i86pc Solaris
> # pkg info time-slider
>          Name: desktop/time-slider
>       Summary: Time Slider ZFS snapshot management for GNOME
>   Description: Time Slider ZFS snapshot management for GNOME
>      Category: Applications/Configuration and Preferences
>         State: Installed
>     Publisher: openindiana.org
>       Version: 0.2.97
> Build Release: 5.11
>        Branch: 0.151.1.4
> Packaging Date: May  2, 2012 10:25:35 PM 
>          Size: 715.80 kB
>          FMRI: pkg://openindiana.org/desktop/time-slider at 0.2.97,5.11-0.151.1.4:20120502T222535Z
> 
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



From o.h.weiergraeber at fz-juelich.de  Fri Jun 22 14:01:09 2012
From: o.h.weiergraeber at fz-juelich.de (=?iso-8859-1?Q?=22Weiergr=E4ber=2C_Oliver_H=2E=22?=)
Date: Fri, 22 Jun 2012 14:01:09 +0000
Subject: [OpenIndiana-discuss] ACPI errors
In-Reply-To: <FF7867E8B89EAE4891E7A47C724A50910657B0@MBX2010-K01.ad.fz-juelich.de>
References: <FF7867E8B89EAE4891E7A47C724A50910657B0@MBX2010-K01.ad.fz-juelich.de>
Message-ID: <FF7867E8B89EAE4891E7A47C724A5091067376@MBX2010-K01.ad.fz-juelich.de>

Hello,

while testing OpenIndiana (and Solaris 11) on an HP xw8600 workstation,
I noticed messages like this occurring regularly during bootup:

----------------------------------------------------------------------------------------------------------------------------
May 17 21:13:48 mymachine.mydomain acpica: [ID 879926 kern.notice] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20100915/dsfield-231)
May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
May 17 21:13:48 mymachine.mydomain acpica: [ID 804433 kern.notice] **** Exception AE_ALREADY_EXISTS during execution of method [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80)
May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
May 17 21:13:48 mymachine.mydomain acpica: [ID 652514 kern.notice] Method Execution Stack:
May 17 21:13:48 mymachine.mydomain acpica: [ID 489567 kern.notice] Method [_OSC] executing: CreateDWordField (CAPB, Local1, CAPD)
May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
May 17 21:13:48 mymachine.mydomain last message repeated 1 time
May 17 21:13:48 mymachine.mydomain acpica: [ID 405112 kern.notice] Local Variables for method [_OSC]:
May 17 21:13:48 mymachine.mydomain acpica: [ID 228379 kern.notice] Local0: ffffff02d59d2eb8 <Obj> Integer 0 1
May 17 21:13:48 mymachine.mydomain acpica: [ID 261160 kern.notice] Local1: ffffff02d59d27d8 <Obj> Integer 0 5
May 17 21:13:48 mymachine.mydomain acpica: [ID 172508 kern.notice] Local2: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 174556 kern.notice] Local3: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 176604 kern.notice] Local4: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 178652 kern.notice] Local5: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 180700 kern.notice] Local6: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 182748 kern.notice] Local7: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
May 17 21:13:48 mymachine.mydomain acpica: [ID 394624 kern.notice] Arguments for Method [_OSC]: (4 arguments defined, max concurrency = 0)
May 17 21:13:48 mymachine.mydomain acpica: [ID 376163 kern.notice] Arg0: ffffff02d59d2918 <Obj> Buffer(16) 5B 4D DB 33 F7 1F 1C 40
May 17 21:13:48 mymachine.mydomain acpica: [ID 153173 kern.notice] Arg1: ffffff02d59d29b8 <Obj> Integer 0 1
May 17 21:13:48 mymachine.mydomain acpica: [ID 152427 kern.notice] Arg2: ffffff02d59d2a08 <Obj> Integer 0 3
May 17 21:13:48 mymachine.mydomain acpica: [ID 407908 kern.notice] Arg3: ffffff02d59d2788 <Obj> Buffer(12) 0 0 0 0 1F 0 0 0
May 17 21:13:48 mymachine.mydomain acpica: [ID 975567 kern.notice] Arg4: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 975569 kern.notice] Arg5: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 975571 kern.notice] Arg6: 0 <Null Object>
May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
May 17 21:13:48 mymachine.mydomain acpica: [ID 342246 kern.notice] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80), AE_ALREADY_EXISTS (20100915/psparse-632)
May 17 21:13:48 mymachine.mydomain acpica: [ID 117524 kern.notice] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
----------------------------------------------------------------------------------------------------------------------------

What kind of ACPI problem is indicated here? Anything to worry about? I did notice stability issues on Solaris 11, but not on OpenIndiana, so I guess these are unrelated to the ACPI stuff.
The BIOS version is the latest available for this machine.

Thanks in advance
Oliver




------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Kennen Sie schon unseren neuen Film? http://www.fz-juelich.de/film
Kennen Sie schon unsere app? http://www.fz-juelich.de/app


From Eamon.Roque at lex-com.net  Fri Jun 22 15:06:37 2012
From: Eamon.Roque at lex-com.net (Eamon Roque)
Date: Fri, 22 Jun 2012 17:06:37 +0200
Subject: [OpenIndiana-discuss] =?iso-8859-1?q?AUTO=3A_Eamon_Roque_ist_au?=
 =?iso-8859-1?q?=DFer_Haus_=28R=FCckkehr_am_02=2E07=2E2012=29?=
Message-ID: <OFD3CC24DB.EA19F481-ONC1257A25.00530115-C1257A25.0053010D@lex-com.net>


Ich bin bis 02.07.2012 abwesend.

Ab dem 02.07.2012 werde ich wieder zur Verf?gung stehen.


Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht
"OpenIndiana-discuss Digest, Vol 23, Issue 27" gesendet am 20.06.2012
00:28:38.

Diese ist die einzige Benachrichtigung, die Sie empfangen werden, w?hrend
diese Person abwesend ist.



From dswartz at druber.com  Fri Jun 22 15:15:25 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Fri, 22 Jun 2012 11:15:25 -0400
Subject: [OpenIndiana-discuss]
 =?iso-8859-1?q?AUTO=3A_Eamon_Roque_ist_au?=
 =?iso-8859-1?q?=DFer_Haus_=28R=FCckkehr_am_02=2E07=2E2012=29?=
In-Reply-To: <OFD3CC24DB.EA19F481-ONC1257A25.00530115-C1257A25.0053010D@lex-com.net>
References: <OFD3CC24DB.EA19F481-ONC1257A25.00530115-C1257A25.0053010D@lex-com.net>
Message-ID: <4FE48C0D.9000803@druber.com>

On 6/22/2012 11:06 AM, Eamon Roque wrote:
> Ich bin bis 02.07.2012 abwesend.
>
> Ab dem 02.07.2012 werde ich wieder zur Verf?gung stehen.
>
>
> Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht
> "OpenIndiana-discuss Digest, Vol 23, Issue 27" gesendet am 20.06.2012
> 00:28:38.
>
> Diese ist die einzige Benachrichtigung, die Sie empfangen werden, w?hrend
> diese Person abwesend ist.
>    
Uh, okay, sure.




From karl.rossing at barobinson.ca  Fri Jun 22 20:54:02 2012
From: karl.rossing at barobinson.ca (Karl Rossing)
Date: Fri, 22 Jun 2012 15:54:02 -0500
Subject: [OpenIndiana-discuss] hplip libusb compile error
In-Reply-To: <fbbd826e16d98.4fe4db52@barobinson.ca>
References: <fbbd826e16d98.4fe4db52@barobinson.ca>
Message-ID: <fbaf9e1917871.4fe4951a@barobinson.ca>

Hi,

I'm trying to compile hplip 3.12.6 on oi_151a3. I'm getting the following error:

checking for cups/cups.h... yes
checking for libusb_init in -lusb-1.0... no
configure: error: cannot find libusb 1.0 support

How can I get around this?

Thanks
Karl



CONFIDENTIALITY NOTICE:  This communication (including all attachments) is
confidential and is intended for the use of the named addressee(s) only and
may contain information that is private, confidential, privileged, and
exempt from disclosure under law.  All rights to privilege are expressly
claimed and reserved and are not waived.  Any use, dissemination,
distribution, copying or disclosure of this message and any attachments, in
whole or in part, by anyone other than the intended recipient(s) is strictly
prohibited.  If you have received this communication in error, please notify
the sender immediately, delete this communication from all data storage
devices and destroy all hard copies.

From jimklimov at cos.ru  Fri Jun 22 22:52:05 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sat, 23 Jun 2012 02:52:05 +0400
Subject: [OpenIndiana-discuss] hplip libusb compile error
In-Reply-To: <fbaf9e1917871.4fe4951a@barobinson.ca>
References: <fbbd826e16d98.4fe4db52@barobinson.ca>
	<fbaf9e1917871.4fe4951a@barobinson.ca>
Message-ID: <4FE4F715.5030902@cos.ru>

2012-06-23 0:54, Karl Rossing ?????:
> Hi,
>
> I'm trying to compile hplip 3.12.6 on oi_151a3. I'm getting the following error:
>
> checking for cups/cups.h... yes
> checking for libusb_init in -lusb-1.0... no
> configure: error: cannot find libusb 1.0 support
>
> How can I get around this?

Speaking from general experience only - did you compile or install
the libusb? If you installed this as a package, is there a *-devel
one (with headers)? Check config.log and/or other logs for details
on the test and error (usually a missing header, although at times
simple compiler-execution problems are misdiagnosed).

Sorry, I did not touch CUPS nor libusb in particular, so can't help
more directly...

HTH,
//Jim


From jimklimov at cos.ru  Fri Jun 22 23:17:10 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Sat, 23 Jun 2012 03:17:10 +0400
Subject: [OpenIndiana-discuss] hplip libusb compile error
In-Reply-To: <fbaf9e1917871.4fe4951a@barobinson.ca>
References: <fbbd826e16d98.4fe4db52@barobinson.ca>
	<fbaf9e1917871.4fe4951a@barobinson.ca>
Message-ID: <4FE4FCF6.5060604@cos.ru>

2012-06-23 0:54, Karl Rossing wrote:
> Hi,
>
> I'm trying to compile hplip 3.12.6 on oi_151a3. I'm getting the following error:
>
> checking for cups/cups.h... yes
> checking for libusb_init in -lusb-1.0... no
> configure: error: cannot find libusb 1.0 support
>
> How can I get around this?

Speaking from general experience only - did you compile or install
the libusb? If you installed this as a package, is there a *-devel
one (with headers)? Check config.log and/or other logs for details
on the test and error (usually a missing header, although at times
simple compiler-execution problems are misdiagnosed).

Sorry, I did not touch CUPS nor libusb in particular, so can't help
more directly...

HTH,
//Jim


From gordon.w.ross at gmail.com  Sat Jun 23 15:39:00 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Sat, 23 Jun 2012 11:39:00 -0400
Subject: [OpenIndiana-discuss] ACPI errors
In-Reply-To: <FF7867E8B89EAE4891E7A47C724A5091067376@MBX2010-K01.ad.fz-juelich.de>
References: <FF7867E8B89EAE4891E7A47C724A50910657B0@MBX2010-K01.ad.fz-juelich.de>
	<FF7867E8B89EAE4891E7A47C724A5091067376@MBX2010-K01.ad.fz-juelich.de>
Message-ID: <CAD0Ztp1TPJMqXVw3s7v5x_3G4iNh4LB=oCjpgsE2SuiQk4DSLA@mail.gmail.com>

On Fri, Jun 22, 2012 at 10:01 AM, "Weiergr?ber, Oliver H."
<o.h.weiergraeber at fz-juelich.de> wrote:
> Hello,
>
> while testing OpenIndiana (and Solaris 11) on an HP xw8600 workstation,
> I noticed messages like this occurring regularly during bootup:
>
> ----------------------------------------------------------------------------------------------------------------------------
> May 17 21:13:48 mymachine.mydomain acpica: [ID 879926 kern.notice] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20100915/dsfield-231)
> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
> May 17 21:13:48 mymachine.mydomain acpica: [ID 804433 kern.notice] **** Exception AE_ALREADY_EXISTS during execution of method [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80)
> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
> May 17 21:13:48 mymachine.mydomain acpica: [ID 652514 kern.notice] Method Execution Stack:
> May 17 21:13:48 mymachine.mydomain acpica: [ID 489567 kern.notice] Method [_OSC] executing: CreateDWordField (CAPB, Local1, CAPD)
[...]
> May 17 21:13:48 mymachine.mydomain acpica: [ID 342246 kern.notice] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80), AE_ALREADY_EXISTS (20100915/psparse-632)
> May 17 21:13:48 mymachine.mydomain acpica: [ID 117524 kern.notice] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
> ----------------------------------------------------------------------------------------------------------------------------
>
> What kind of ACPI problem is indicated here? Anything to worry about? I did notice stability issues on Solaris 11, but not on OpenIndiana, so I guess these are unrelated to the ACPI stuff.
> The BIOS version is the latest available for this machine.
>
> Thanks in advance
> Oliver

When I was last working on an ACPI update (which I think is what's
currently in illumos and OI) Yuri Pankov was helping me test the code,
and observed a problem on his HP laptop that looked something like
this, if I recall correctly.  He did some further experimenting and
found that he could make his laptop boot without the ACPI errors by
attaching the "EC" device a bit later.

He showed me a possible fix, which I asked him to do some more work
on, but then he ran out of time or something.  Maybe you'd like to
pick up his changes and try them?

-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From pulaskite at yahoo.com  Sun Jun 24 01:04:06 2012
From: pulaskite at yahoo.com (Reginald Beardsley)
Date: Sat, 23 Jun 2012 18:04:06 -0700 (PDT)
Subject: [OpenIndiana-discuss] Browser update/alternative for OI_151?
Message-ID: <1340499846.85930.YahooMailClassic@web161204.mail.bf1.yahoo.com>

I'm encountering an increasing number of websites which complain that my browser is out of date.  I'm running OI_151 w/ firefox 0.5.11-0.151.1.  "pkg update" says "No updates available for this image."

google & the wiki didn't offer much hope, though I do see updates for OpenSolaris 11.  Does anyone know if one of those  works on OI?

Am I correct in assuming that the lack of more recent versions of Firefox is due to it not being compilable on OI?  Is there a more recent or alternative  browser option?  I don't think I use any plugins (e.g. I removed flash).  

I just want a basic browser.  I'd like secure, but I realize that's not realistic.   

I'm *very* tired of version churn on the web:-(

Thanks,
Reg


From yuri.pankov at gmail.com  Sun Jun 24 01:10:32 2012
From: yuri.pankov at gmail.com (Yuri Pankov)
Date: Sun, 24 Jun 2012 05:10:32 +0400
Subject: [OpenIndiana-discuss] Browser update/alternative for OI_151?
In-Reply-To: <1340499846.85930.YahooMailClassic@web161204.mail.bf1.yahoo.com>
References: <1340499846.85930.YahooMailClassic@web161204.mail.bf1.yahoo.com>
Message-ID: <4FE66908.30300@gmail.com>

On Sat, 23 Jun 2012 18:04:06 -0700 (PDT), Reginald Beardsley wrote:
> I'm encountering an increasing number of websites which complain that my browser is out of date.  I'm running OI_151 w/ firefox 0.5.11-0.151.1.  "pkg update" says "No updates available for this image."
>
> google & the wiki didn't offer much hope, though I do see updates for OpenSolaris 11.  Does anyone know if one of those  works on OI?
>
> Am I correct in assuming that the lack of more recent versions of Firefox is due to it not being compilable on OI?  Is there a more recent or alternative  browser option?  I don't think I use any plugins (e.g. I removed flash).
>
> I just want a basic browser.  I'd like secure, but I realize that's not realistic.
>
> I'm *very* tired of version churn on the web:-(
http://openindiana.org/pipermail/openindiana-discuss/2012-June/008320.html


From dave.koelmeyer at davekoelmeyer.co.nz  Sun Jun 24 01:11:17 2012
From: dave.koelmeyer at davekoelmeyer.co.nz (Dave Koelmeyer)
Date: Sun, 24 Jun 2012 13:11:17 +1200
Subject: [OpenIndiana-discuss] Browser update/alternative for OI_151?
In-Reply-To: <1340499846.85930.YahooMailClassic@web161204.mail.bf1.yahoo.com>
References: <1340499846.85930.YahooMailClassic@web161204.mail.bf1.yahoo.com>
Message-ID: <4FE66935.1020104@davekoelmeyer.co.nz>

On 06/24/12 01:04 PM, Reginald Beardsley wrote:
> I'm encountering an increasing number of websites which complain that my browser is out of date.  I'm running OI_151 w/ firefox 0.5.11-0.151.1.  "pkg update" says "No updates available for this image."
>
> google & the wiki didn't offer much hope, though I do see updates for OpenSolaris 11.  Does anyone know if one of those  works on OI?
>

Hi Reginald,

You can get the latest Firefox for Solaris (runs on OpenIndiana fine) from:

http://releases.mozilla.org/pub/mozilla.org/firefox/releases/13.0.1/contrib/

Substitute the version number in the URL as necessary :)

Cheers,

-- 
Dave Koelmeyer
http://www.davekoelmeyer.co.nz



From pulaskite at yahoo.com  Sun Jun 24 01:43:54 2012
From: pulaskite at yahoo.com (Reginald Beardsley)
Date: Sat, 23 Jun 2012 18:43:54 -0700 (PDT)
Subject: [OpenIndiana-discuss] Browser update/alternative for OI_151?
In-Reply-To: <4FE66935.1020104@davekoelmeyer.co.nz>
Message-ID: <1340502234.26062.YahooMailClassic@web161203.mail.bf1.yahoo.com>

Yuri & Dave,


Seems to work fine. 

Many thanks,
Reg


From yuri.pankov at gmail.com  Sun Jun 24 04:24:16 2012
From: yuri.pankov at gmail.com (Yuri Pankov)
Date: Sun, 24 Jun 2012 08:24:16 +0400
Subject: [OpenIndiana-discuss] ACPI errors
In-Reply-To: <CAD0Ztp1TPJMqXVw3s7v5x_3G4iNh4LB=oCjpgsE2SuiQk4DSLA@mail.gmail.com>
References: <FF7867E8B89EAE4891E7A47C724A50910657B0@MBX2010-K01.ad.fz-juelich.de>
	<FF7867E8B89EAE4891E7A47C724A5091067376@MBX2010-K01.ad.fz-juelich.de>
	<CAD0Ztp1TPJMqXVw3s7v5x_3G4iNh4LB=oCjpgsE2SuiQk4DSLA@mail.gmail.com>
Message-ID: <4FE69670.6090600@gmail.com>

On Sat, 23 Jun 2012 11:39:00 -0400, Gordon Ross wrote:
> On Fri, Jun 22, 2012 at 10:01 AM, "Weiergr?ber, Oliver H."
> <o.h.weiergraeber at fz-juelich.de> wrote:
>> Hello,
>>
>> while testing OpenIndiana (and Solaris 11) on an HP xw8600 workstation,
>> I noticed messages like this occurring regularly during bootup:
>>
>> ----------------------------------------------------------------------------------------------------------------------------
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 879926 kern.notice] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20100915/dsfield-231)
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 804433 kern.notice] **** Exception AE_ALREADY_EXISTS during execution of method [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80)
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 652514 kern.notice] Method Execution Stack:
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 489567 kern.notice] Method [_OSC] executing: CreateDWordField (CAPB, Local1, CAPD)
> [...]
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 342246 kern.notice] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80), AE_ALREADY_EXISTS (20100915/psparse-632)
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 117524 kern.notice] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
>> ----------------------------------------------------------------------------------------------------------------------------
>>
>> What kind of ACPI problem is indicated here? Anything to worry about? I did notice stability issues on Solaris 11, but not on OpenIndiana, so I guess these are unrelated to the ACPI stuff.
>> The BIOS version is the latest available for this machine.
>>
>> Thanks in advance
>> Oliver
>
> When I was last working on an ACPI update (which I think is what's
> currently in illumos and OI) Yuri Pankov was helping me test the code,
> and observed a problem on his HP laptop that looked something like
> this, if I recall correctly.  He did some further experimenting and
> found that he could make his laptop boot without the ACPI errors by
> attaching the "EC" device a bit later.
>
> He showed me a possible fix, which I asked him to do some more work
> on, but then he ran out of time or something.  Maybe you'd like to
> pick up his changes and try them?

ACPICA 20100915 isn't the latest version available at the moment (at 
least in illumos tree), which means that you are missing some fixes 
Gordon did. Please try upgrading your OpenIndiana installation first and 
check if it helps.



From michelle at msknight.com  Sun Jun 24 07:01:50 2012
From: michelle at msknight.com (michelle)
Date: Sun, 24 Jun 2012 08:01:50 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
Message-ID: <4FE6BB5E.5030604@msknight.com>

Hi Folks,

Sorry to come to you with a long and convoluted problem.

Situation - home-type standard PC, 4gig of RAM, running two SSDs in a 
mirrored root raid pool. Three 2tb hard drives in a raidz.

System is...

              OpenIndiana Development oi_151.1.4 X86 (powered by illumos)
         Copyright 2011 Oracle and/or its affiliates. All rights reserved.
                         Use is subject to license terms.
                            Assembled 22 April 2012

I have an external, "toaster" which takes two hard drives, one is 
connected via e-sata; the other is running via USB (although for this 
instance, there was no drive in teh socket) because I've had a long 
running battle to try and get an affordable (to me) e-sata card that 
will give me another e-sata channel.

The ZFS set was getting full; something like only 50gig free. I was 
starting file copies off the server to an external drive via an SMB 
client, and going to bed, to wake up and find the process had frozen. 
Diagnosis led me to the server, which appeared to hang on any log on 
attempt. It even didn't listen to the power button properly.

Eventually, it was a dirty, hard down.

On coming up again at 07:13 , it gave this...

Jun 24 07:01:55 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:01:55 jaguar This may result in reduced system performance.
Jun 24 07:01:55 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:01:55 jaguar This may result in reduced system performance.
Jun 24 07:10:25 jaguar power: [ID 199196 kern.notice] NOTICE: Power 
Button pressed 3 times, cancelling all requests
Jun 24 07:10:43 jaguar suspend: [ID 221072 daemon.notice] System is 
being shut down.
Jun 24 07:10:43 jaguar poweroff: [ID 330035 auth.crit] initiated by mich 
on /dev/console
Jun 24 07:13:20 jaguar genunix: [ID 108120 kern.notice] ^MOpenIndiana 
Build oi_151a4 64-bit (illumos 13676:98ca40df9171)
Jun 24 07:13:20 jaguar genunix: [ID 107366 kern.notice] SunOS Release 
5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
Jun 24 07:13:20 jaguar genunix: [ID 864463 kern.notice] All rights 
reserved. Use is subject to license terms.
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: lgpg
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: tsc
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: msr
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: mtrr
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: pge
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: de
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: cmov
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: mmx
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: mca
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: pae
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: cv8
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: pat
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: sep
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: sse
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: sse2
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: htt
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: asysc
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: nx
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: sse3
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: cx16
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: cmp
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: tscp
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: mwait
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: cpuid
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: ssse3
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: sse4_1
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: sse4_2
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: clfsh
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: 64
Jun 24 07:13:20 jaguar unix: [ID 223955 kern.info] x86_feature: vmx
Jun 24 07:13:20 jaguar unix: [ID 168242 kern.info] mem = 3923444K 
(0xef77d000)
Jun 24 07:13:20 jaguar acpica: [ID 233941 kern.notice] ACPI: RSDP f70c0 
00014 (v0 GBT   )
Jun 24 07:13:20 jaguar acpica: [ID 329277 kern.notice] ACPI: RSDT 
d77e3040 00040 (v1 GBT    GBTUACPI 42302E31 GBTU 01010101)
Jun 24 07:13:20 jaguar acpica: [ID 229170 kern.notice] ACPI: FACP 
d77e30c0 00074 (v1 GBT    GBTUACPI 42302E31 GBTU 01010101)
Jun 24 07:13:20 jaguar acpica: [ID 764759 kern.notice] ACPI: DSDT 
d77e3180 055B4 (v1 GBT    GBTUACPI 00001000 MSFT 0100000C)
Jun 24 07:13:20 jaguar acpica: [ID 347281 kern.notice] ACPI: FACS 
d77e0000 00040
Jun 24 07:13:20 jaguar acpica: [ID 193408 kern.notice] ACPI: HPET 
d77e8880 00038 (v1 GBT    GBTUACPI 42302E31 GBTU 00000098)
Jun 24 07:13:20 jaguar acpica: [ID 265575 kern.notice] ACPI: MCFG 
d77e8900 0003C (v1 GBT    GBTUACPI 42302E31 GBTU 01010101)
Jun 24 07:13:20 jaguar acpica: [ID 254724 kern.notice] ACPI: EUDS 
d77e8940 004D0 (v1 GBT             00000000      00000000)
Jun 24 07:13:20 jaguar acpica: [ID 403521 kern.notice] ACPI: TAMG 
d77e8e10 00A4A (v1 GBT    GBT   B0 5455312E BG?? 53450101)
Jun 24 07:13:20 jaguar acpica: [ID 651266 kern.notice] ACPI: APIC 
d77e8780 000BC (v1 GBT    GBTUACPI 42302E31 GBTU 01010101)
Jun 24 07:13:20 jaguar acpica: [ID 186916 kern.notice] ACPI: SSDT 
d77e9880 01BF8 (v1  INTEL PPM RCM  80000001 INTL 20061109)
Jun 24 07:13:20 jaguar unix: [ID 190185 kern.info] SMBIOS v2.4 loaded 
(1190 bytes)
Jun 24 07:13:20 jaguar unix: [ID 972737 kern.info] Skipping psm: xpv_psm
Jun 24 07:13:20 jaguar rootnex: [ID 466748 kern.info] root nexus = i86pc
Jun 24 07:13:20 jaguar iommulib: [ID 321598 kern.info] NOTICE: 
iommulib_nexus_register: rootnex-1: Succesfully registered NEXUS i86pc 
nexops=fffffffffbd13720
Jun 24 07:13:20 jaguar rootnex: [ID 349649 kern.info] pseudo0 at root
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] pseudo0 is /pseudo
Jun 24 07:13:20 jaguar rootnex: [ID 349649 kern.info] scsi_vhci0 at root
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] scsi_vhci0 is 
/scsi_vhci
Jun 24 07:13:20 jaguar pci_autoconfig: [ID 139057 kern.info] NOTICE: 
reprogram io-range on ppb[0/1c/0]: 0x1000 ~ 0x1fff
Jun 24 07:13:20 jaguar pci_autoconfig: [ID 596873 kern.info] NOTICE: 
reprogram mem-range on ppb[0/1c/0]: 0xd7800000 ~ 0xd78fffff
Jun 24 07:13:20 jaguar pci_autoconfig: [ID 596873 kern.info] NOTICE: 
reprogram mem-range on ppb[0/1c/5]: 0xd7900000 ~ 0xd79fffff
Jun 24 07:13:20 jaguar pci_autoconfig: [ID 595143 kern.info] NOTICE: add 
io-range on subtractive ppb[0/1e/0]: 0x2000 ~ 0x2fff
Jun 24 07:13:20 jaguar genunix: [ID 596552 kern.info] Reading Intel 
IOMMU boot options
Jun 24 07:13:20 jaguar rootnex: [ID 349649 kern.info] npe0 at root: 
space 0 offset 0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] npe0 is /pci at 0,0
Jun 24 07:13:20 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
isa at 1f, isa0
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 0 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 1 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 2 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 3 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 4 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 5 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 6 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 615120 kern.info] NOTICE: apic: 
local nmi: 7 0x0 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 419660 kern.info] pcplusmp: irq 0x9 
vector 0x80 ioapic 0x2 intin 0x9 is bound to cpu 1
Jun 24 07:13:20 jaguar pcplusmp: [ID 419660 kern.info] pcplusmp: irq 0xb 
vector 0xd1 ioapic 0x2 intin 0xb is bound to cpu 2
Jun 24 07:13:20 jaguar amd_iommu: [ID 251261 kern.info] NOTICE: 
amd_iommu: No AMD IOMMU ACPI IVRS table
Jun 24 07:13:20 jaguar pseudo: [ID 129642 kern.info] pseudo-device: acpippm0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] acpippm0 is 
/pseudo/acpippm at 0
Jun 24 07:13:20 jaguar pseudo: [ID 129642 kern.info] pseudo-device: ppm0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] ppm0 is /pseudo/ppm at 0
Jun 24 07:13:20 jaguar ahci: [ID 405770 kern.info] NOTICE: ahci0: hba 
AHCI version = 1.30
Jun 24 07:13:20 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pciclass,010601 (ahci) instance 0 irq 0x18 vector 0x40 ioapic 0xff intin 
0xff is bound to cpu 3
Jun 24 07:13:20 jaguar sata: [ID 663010 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2 :
Jun 24 07:13:20 jaguar sata: [ID 761595 kern.info]     SATA disk device 
at port 0
Jun 24 07:13:20 jaguar sata: [ID 846691 kern.info]     model INTEL 
SSDSA2M040G2GC
Jun 24 07:13:20 jaguar sata: [ID 693010 kern.info]     firmware 2CV102HB
Jun 24 07:13:20 jaguar sata: [ID 163988 kern.info]     serial number 
CVGB949301PH040GGN
Jun 24 07:13:20 jaguar sata: [ID 594940 kern.info]     supported features:
Jun 24 07:13:20 jaguar sata: [ID 981177 kern.info]      48-bit LBA, DMA, 
Native Command Queueing, SMART, SMART self-test
Jun 24 07:13:20 jaguar sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     Supported queue 
depth 32
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     capacity = 
78165360 sectors
Jun 24 07:13:20 jaguar scsi: [ID 583861 kern.info] sd0 at ahci0: target 
0 lun 0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] sd0 is 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 0,0
Jun 24 07:13:20 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 0,0 (sd0) online
Jun 24 07:13:20 jaguar sata: [ID 663010 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2 :
Jun 24 07:13:20 jaguar sata: [ID 761595 kern.info]     SATA disk device 
at port 1
Jun 24 07:13:20 jaguar sata: [ID 846691 kern.info]     model INTEL 
SSDSA2M040G2GC
Jun 24 07:13:20 jaguar sata: [ID 693010 kern.info]     firmware 2CV102HB
Jun 24 07:13:20 jaguar sata: [ID 163988 kern.info]     serial number 
CVGB949301PC040GGN
Jun 24 07:13:20 jaguar sata: [ID 594940 kern.info]     supported features:
Jun 24 07:13:20 jaguar sata: [ID 981177 kern.info]      48-bit LBA, DMA, 
Native Command Queueing, SMART, SMART self-test
Jun 24 07:13:20 jaguar sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     Supported queue 
depth 32
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     capacity = 
78163247 sectors
Jun 24 07:13:20 jaguar scsi: [ID 583861 kern.info] sd2 at ahci0: target 
1 lun 0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] sd2 is 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 1,0
Jun 24 07:13:20 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 1,0 (sd2) online
Jun 24 07:13:20 jaguar sata: [ID 663010 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2 :
Jun 24 07:13:20 jaguar sata: [ID 761595 kern.info]     SATA disk device 
at port 2
Jun 24 07:13:20 jaguar sata: [ID 846691 kern.info]     model ST32000542AS
Jun 24 07:13:20 jaguar sata: [ID 693010 kern.info]     firmware CC34
Jun 24 07:13:20 jaguar sata: [ID 163988 kern.info]     serial 
number             5XW17ARW
Jun 24 07:13:20 jaguar sata: [ID 594940 kern.info]     supported features:
Jun 24 07:13:20 jaguar sata: [ID 981177 kern.info]      48-bit LBA, DMA, 
Native Command Queueing, SMART, SMART self-test
Jun 24 07:13:20 jaguar sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     Supported queue 
depth 32
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     capacity = 
3907029168 sectors
Jun 24 07:13:20 jaguar scsi: [ID 583861 kern.info] sd3 at ahci0: target 
2 lun 0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] sd3 is 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 2,0
Jun 24 07:13:20 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 2,0 (sd3) online
Jun 24 07:13:20 jaguar sata: [ID 663010 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2 :
Jun 24 07:13:20 jaguar sata: [ID 761595 kern.info]     SATA disk device 
at port 3
Jun 24 07:13:20 jaguar sata: [ID 846691 kern.info]     model WDC 
WD20EARS-00MVWB0
Jun 24 07:13:20 jaguar sata: [ID 693010 kern.info]     firmware 51.0AB51
Jun 24 07:13:20 jaguar sata: [ID 163988 kern.info]     serial 
number      WD-WMAZA0555575
Jun 24 07:13:20 jaguar sata: [ID 594940 kern.info]     supported features:
Jun 24 07:13:20 jaguar sata: [ID 981177 kern.info]      48-bit LBA, DMA, 
Native Command Queueing, SMART, SMART self-test
Jun 24 07:13:20 jaguar sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     Supported queue 
depth 32
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     capacity = 
3907029168 sectors
Jun 24 07:13:20 jaguar scsi: [ID 583861 kern.info] sd4 at ahci0: target 
3 lun 0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] sd4 is 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 3,0
Jun 24 07:13:20 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 3,0 (sd4) online
Jun 24 07:13:20 jaguar sata: [ID 663010 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2 :
Jun 24 07:13:20 jaguar sata: [ID 761595 kern.info]     SATA disk device 
at port 4
Jun 24 07:13:20 jaguar sata: [ID 846691 kern.info]     model WDC 
WD20EARS-00MVWB0
Jun 24 07:13:20 jaguar sata: [ID 693010 kern.info]     firmware 51.0AB51
Jun 24 07:13:20 jaguar sata: [ID 163988 kern.info]     serial 
number      WD-WMAZA0484508
Jun 24 07:13:20 jaguar sata: [ID 594940 kern.info]     supported features:
Jun 24 07:13:20 jaguar sata: [ID 981177 kern.info]      48-bit LBA, DMA, 
Native Command Queueing, SMART, SMART self-test
Jun 24 07:13:20 jaguar sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     Supported queue 
depth 32
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     capacity = 
3907029168 sectors
Jun 24 07:13:20 jaguar scsi: [ID 583861 kern.info] sd5 at ahci0: target 
4 lun 0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] sd5 is 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 4,0
Jun 24 07:13:20 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 4,0 (sd5) online
Jun 24 07:13:20 jaguar sata: [ID 663010 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2 :
Jun 24 07:13:20 jaguar sata: [ID 761595 kern.info]     SATA disk device 
at port 5
Jun 24 07:13:20 jaguar sata: [ID 846691 kern.info]     model SAMSUNG 
HD154UI
Jun 24 07:13:20 jaguar sata: [ID 693010 kern.info]     firmware 1AG01118
Jun 24 07:13:20 jaguar sata: [ID 163988 kern.info]     serial number 
S1Y6J90SB10084
Jun 24 07:13:20 jaguar sata: [ID 594940 kern.info]     supported features:
Jun 24 07:13:20 jaguar sata: [ID 981177 kern.info]      48-bit LBA, DMA, 
Native Command Queueing, SMART, SMART self-test
Jun 24 07:13:20 jaguar sata: [ID 643337 kern.info]     SATA Gen2 
signaling speed (3.0Gbps)
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     Supported queue 
depth 32
Jun 24 07:13:20 jaguar sata: [ID 349649 kern.info]     capacity = 
2930277168 sectors
Jun 24 07:13:20 jaguar scsi: [ID 583861 kern.info] sd6 at ahci0: target 
5 lun 0
Jun 24 07:13:20 jaguar genunix: [ID 936769 kern.info] sd6 is 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 5,0
Jun 24 07:13:20 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2/disk at 5,0 (sd6) online
Jun 24 07:13:20 jaguar zfs: [ID 249136 kern.info] imported version 0 
pool rpool using 28
Jun 24 07:13:20 jaguar genunix: [ID 308332 kern.info] root on 
rpool/ROOT/openindiana-3 fstype zfs
Jun 24 07:13:21 jaguar rootnex: [ID 349649 kern.info] acpinex0 at root
Jun 24 07:13:21 jaguar genunix: [ID 936769 kern.info] acpinex0 is /fw
Jun 24 07:13:21 jaguar acpinex: [ID 328922 kern.info] acpinex: cpu at 0, 
cpudrv0
Jun 24 07:13:21 jaguar genunix: [ID 408114 kern.info] /fw/cpu at 0 
(cpudrv0) online
Jun 24 07:13:21 jaguar pseudo: [ID 129642 kern.info] pseudo-device: dld0
Jun 24 07:13:21 jaguar genunix: [ID 936769 kern.info] dld0 is /pseudo/dld at 0
Jun 24 07:13:21 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pciclass,0c0320 (ehci) instance 0 irq 0x12 vector 0x81 ioapic 0x2 intin 
0x12 is bound to cpu 0
Jun 24 07:13:22 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5006 at 1a,7, ehci0
Jun 24 07:13:22 jaguar genunix: [ID 936769 kern.info] ehci0 is 
/pci at 0,0/pci1458,5006 at 1a,7
Jun 24 07:13:22 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pciclass,0c0320 (ehci) instance 1 irq 0x17 vector 0x82 ioapic 0x2 intin 
0x17 is bound to cpu 1
Jun 24 07:13:23 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5006 at 1d,7, ehci1
Jun 24 07:13:23 jaguar genunix: [ID 936769 kern.info] ehci1 is 
/pci at 0,0/pci1458,5006 at 1d,7
Jun 24 07:13:23 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pciclass,0c0300 (uhci) instance 0 irq 0x10 vector 0x83 ioapic 0x2 intin 
0x10 is bound to cpu 2
Jun 24 07:13:23 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5004 at 1a, uhci0
Jun 24 07:13:23 jaguar genunix: [ID 936769 kern.info] uhci0 is 
/pci at 0,0/pci1458,5004 at 1a
Jun 24 07:13:23 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pciclass,0c0300 (uhci) instance 1 irq 0x15 vector 0x84 ioapic 0x2 intin 
0x15 is bound to cpu 3
Jun 24 07:13:23 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5004 at 1a,1, uhci1
Jun 24 07:13:23 jaguar genunix: [ID 936769 kern.info] uhci1 is 
/pci at 0,0/pci1458,5004 at 1a,1
Jun 24 07:13:23 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5004 at 1a,2, uhci2
Jun 24 07:13:23 jaguar genunix: [ID 936769 kern.info] uhci2 is 
/pci at 0,0/pci1458,5004 at 1a,2
Jun 24 07:13:24 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5004 at 1d, uhci3
Jun 24 07:13:24 jaguar genunix: [ID 936769 kern.info] uhci3 is 
/pci at 0,0/pci1458,5004 at 1d
Jun 24 07:13:24 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pciclass,0c0300 (uhci) instance 4 irq 0x13 vector 0x85 ioapic 0x2 intin 
0x13 is bound to cpu 0
Jun 24 07:13:24 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5004 at 1d,1, uhci4
Jun 24 07:13:24 jaguar genunix: [ID 936769 kern.info] uhci4 is 
/pci at 0,0/pci1458,5004 at 1d,1
Jun 24 07:13:24 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,5004 at 1d,2, uhci5
Jun 24 07:13:24 jaguar genunix: [ID 936769 kern.info] uhci5 is 
/pci at 0,0/pci1458,5004 at 1d,2
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu0: x86 (chipid 0x0 
GenuineIntel 20655 family 6 model 37 step 5 clock 3067 MHz)
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu0: Intel(r) 
Core(tm) i3 CPU         540  @ 3.07GHz
Jun 24 07:13:24 jaguar acpinex: [ID 328922 kern.info] acpinex: cpu at 1, 
cpudrv1
Jun 24 07:13:24 jaguar genunix: [ID 408114 kern.info] /fw/cpu at 1 
(cpudrv1) online
Jun 24 07:13:24 jaguar acpinex: [ID 328922 kern.info] acpinex: cpu at 2, 
cpudrv2
Jun 24 07:13:24 jaguar genunix: [ID 408114 kern.info] /fw/cpu at 2 
(cpudrv2) online
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu2: x86 (chipid 0x0 
GenuineIntel 20655 family 6 model 37 step 5 clock 3067 MHz)
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu2: Intel(r) 
Core(tm) i3 CPU         540  @ 3.07GHz
Jun 24 07:13:24 jaguar unix: [ID 557947 kern.info] cpu2 initialization 
complete - online
Jun 24 07:13:24 jaguar acpinex: [ID 328922 kern.info] acpinex: cpu at 3, 
cpudrv3
Jun 24 07:13:24 jaguar genunix: [ID 408114 kern.info] /fw/cpu at 3 
(cpudrv3) online
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu1: x86 (chipid 0x0 
GenuineIntel 20655 family 6 model 37 step 5 clock 3067 MHz)
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu3: x86 (chipid 0x0 
GenuineIntel 20655 family 6 model 37 step 5 clock 3067 MHz)
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu1: Intel(r) 
Core(tm) i3 CPU         540  @ 3.07GHz
Jun 24 07:13:24 jaguar unix: [ID 950921 kern.info] cpu3: Intel(r) 
Core(tm) i3 CPU         540  @ 3.07GHz
Jun 24 07:13:24 jaguar unix: [ID 557947 kern.info] cpu1 initialization 
complete - online
Jun 24 07:13:24 jaguar unix: [ID 557947 kern.info] cpu3 initialization 
complete - online
Jun 24 07:13:24 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci8086,3b42 at 1c, pcieb1
Jun 24 07:13:24 jaguar genunix: [ID 936769 kern.info] pcieb1 is 
/pci at 0,0/pci8086,3b42 at 1c
Jun 24 07:13:24 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci8086,3b4a at 1c,4, pcieb2
Jun 24 07:13:24 jaguar genunix: [ID 936769 kern.info] pcieb2 is 
/pci at 0,0/pci8086,3b4a at 1c,4
Jun 24 07:13:24 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci8086,3b4c at 1c,5, pcieb3
Jun 24 07:13:24 jaguar genunix: [ID 936769 kern.info] pcieb3 is 
/pci at 0,0/pci8086,3b4c at 1c,5
Jun 24 07:13:25 jaguar usba: [ID 912658 kern.info] USB 2.0 device 
(usb5e3,608) operating at hi speed (USB 2.x) on USB 2.0 root hub: hub at 1, 
hubd3 at bus address 2
Jun 24 07:13:25 jaguar usba: [ID 349649 kern.info]     USB2.0 Hub
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] hubd3 is 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 1
Jun 24 07:13:25 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 1 (hubd3) online
Jun 24 07:13:25 jaguar usba: [ID 912658 kern.info] USB 2.0 device 
(usb5e3,608) operating at hi speed (USB 2.x) on USB 2.0 root hub: hub at 6, 
hubd1 at bus address 3
Jun 24 07:13:25 jaguar usba: [ID 349649 kern.info]     USB2.0 Hub
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] hubd1 is 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6
Jun 24 07:13:25 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6 (hubd1) online
Jun 24 07:13:25 jaguar usba: [ID 912658 kern.info] USB 1.10 device 
(usb4b4,333) operating at low speed (USB 1.x) on USB 2.0 external hub: 
mouse at 1, hid5 at bus address 4
Jun 24 07:13:25 jaguar usba: [ID 349649 kern.info]     Cypress Semi. 
Optical Mouse for U+P
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] hid5 is 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/mouse at 1
Jun 24 07:13:25 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/mouse at 1 (hid5) online
Jun 24 07:13:25 jaguar usba: [ID 912658 kern.info] USB 1.10 device 
(usbd3d,1) operating at low speed (USB 1.x) on USB 2.0 external hub: 
device at 2, usb_mid2 at bus address 5
Jun 24 07:13:25 jaguar usba: [ID 349649 kern.info]     USBPS2
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] usb_mid2 is 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/device at 2
Jun 24 07:13:25 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/device at 2 (usb_mid2) online
Jun 24 07:13:25 jaguar usba: [ID 912658 kern.info] USB 1.10 interface 
(usbifd3d,1.config1.0) operating at low speed (USB 1.x) on USB 2.0 
external hub: keyboard at 0, hid6 at bus address 5
Jun 24 07:13:25 jaguar usba: [ID 349649 kern.info]     USBPS2
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] hid6 is 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/device at 2/keyboard at 0
Jun 24 07:13:25 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
stmf_sbd0
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] stmf_sbd0 is 
/pseudo/stmf_sbd at 0
Jun 24 07:13:25 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/device at 2/keyboard at 0 (hid6) online
Jun 24 07:13:25 jaguar usba: [ID 912658 kern.info] USB 1.10 interface 
(usbifd3d,1.config1.1) operating at low speed (USB 1.x) on USB 2.0 
external hub: mouse at 1, hid7 at bus address 5
Jun 24 07:13:25 jaguar usba: [ID 349649 kern.info]     USBPS2
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] hid7 is 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/device at 2/mouse at 1
Jun 24 07:13:25 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 6/device at 2/mouse at 1 (hid7) online
Jun 24 07:13:25 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci8086,244e at 1e, pci_pci0
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] pci_pci0 is 
/pci at 0,0/pci8086,244e at 1e
Jun 24 07:13:25 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pciclass,0c0010 (hci1394) instance 0 irq 0x11 vector 0x86 ioapic 0x2 
intin 0x11 is bound to cpu 1
Jun 24 07:13:25 jaguar pci_pci: [ID 370704 kern.info] PCI-device: 
pci1458,1000 at 7, hci13940
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] hci13940 is 
/pci at 0,0/pci8086,244e at 1e/pci1458,1000 at 7
Jun 24 07:13:25 jaguar pseudo: [ID 129642 kern.info] pseudo-device: audio0
Jun 24 07:13:25 jaguar genunix: [ID 936769 kern.info] audio0 is 
/pseudo/audio at 0
Jun 24 07:13:26 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: 
pci10ec,8168 (rge) instance 0 irq 0x19 vector 0x60 ioapic 0xff intin 
0xff is bound to cpu 2
Jun 24 07:13:26 jaguar rge: [ID 801725 kern.info] NOTICE: rge0: Using 
MSI interrupt type
Jun 24 07:13:26 jaguar mac: [ID 469746 kern.info] NOTICE: rge0 registered
Jun 24 07:13:27 jaguar pseudo: [ID 129642 kern.info] pseudo-device: zfs0
Jun 24 07:13:27 jaguar genunix: [ID 936769 kern.info] zfs0 is /pseudo/zfs at 0
Jun 24 07:13:27 jaguar nwamd[76]: [ID 605049 daemon.error] 1: 
nwamd_set_unset_link_properties: dladm_set_linkprop failed: operation 
not supported
Jun 24 07:13:30 jaguar mac: [ID 435574 kern.info] NOTICE: rge0 link up, 
1000 Mbps, full duplex
Jun 24 07:13:33 jaguar genunix: [ID 227219 kern.info] This Solaris 
instance has UUID 351542cb-5131-c7ac-9876-e2c340b173a7
Jun 24 07:13:33 jaguar genunix: [ID 454863 kern.info] dump on 
/dev/zvol/dsk/rpool/dump size 1979 MB
Jun 24 07:13:34 jaguar npe: [ID 236367 kern.info] PCI Express-device: 
pci1458,a002 at 1b, audiohd0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] audiohd0 is 
/pci at 0,0/pci1458,a002 at 1b
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: pm0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] pm0 is /pseudo/pm at 0
Jun 24 07:13:34 jaguar rootnex: [ID 349649 kern.info] iscsi0 at root
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] iscsi0 is /iscsi
Jun 24 07:13:34 jaguar rootnex: [ID 349649 kern.info] xsvc0 at root: 
space 0 offset 0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] xsvc0 is /xsvc at 0,0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: power0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] power0 is 
/pseudo/power at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: srn0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] srn0 is /pseudo/srn at 0
Jun 24 07:13:34 jaguar /usr/lib/power/powerd: [ID 387247 daemon.error] 
Able to open /dev/srn
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] devinfo0 is 
/pseudo/devinfo at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] pseudo1 is 
/pseudo/zconsnex at 1
Jun 24 07:13:34 jaguar acpinex: [ID 328922 kern.info] acpinex: sb at 0, 
acpinex1
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] acpinex1 is /fw/sb at 0
Jun 24 07:13:34 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: asy 
(asy) instance 0 irq 0x4 vector 0xb0 ioapic 0x2 intin 0x4 is bound to cpu 3
Jun 24 07:13:34 jaguar isa: [ID 202937 kern.info] ISA-device: asy0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] asy0 is 
/pci at 0,0/isa at 1f/asy at 1,3f8
Jun 24 07:13:34 jaguar isa: [ID 202937 kern.info] ISA-device: pit_beep0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] pit_beep0 is 
/pci at 0,0/isa at 1f/pit_beep
Jun 24 07:13:34 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:13:34 jaguar This may result in reduced system performance.
Jun 24 07:13:34 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:13:34 jaguar This may result in reduced system performance.
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: llc10
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] llc10 is 
/pseudo/llc1 at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] lofi0 is 
/pseudo/lofi at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
ramdisk1024
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] ramdisk1024 is 
/pseudo/ramdisk at 1024
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] ucode0 is 
/pseudo/ucode at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
nvidia255
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] nvidia255 is 
/pseudo/nvidia at 255
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: dcpc0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] dcpc0 is 
/pseudo/dcpc at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: dtrace0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] dtrace0 is 
/pseudo/dtrace at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
fasttrap0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] fasttrap0 is 
/pseudo/fasttrap at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
lockstat0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] lockstat0 is 
/pseudo/lockstat at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: profile0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] profile0 is 
/pseudo/profile at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
systrace0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] systrace0 is 
/pseudo/systrace at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] fcsm0 is 
/pseudo/fcsm at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fct0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] fct0 is /pseudo/fct at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: stmf0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] stmf0 is 
/pseudo/stmf at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: pool0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] pool0 is 
/pseudo/pool at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: bpf0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] bpf0 is /pseudo/bpf at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] winlock0 is 
/pseudo/winlock at 0
Jun 24 07:13:34 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Jun 24 07:13:34 jaguar genunix: [ID 936769 kern.info] fssnap0 is 
/pseudo/fssnap at 0
Jun 24 07:13:34 jaguar ipf: [ID 774698 kern.info] IP Filter: v4.1.9, 
running.
Jun 24 07:13:35 jaguar pseudo: [ID 129642 kern.info] pseudo-device: nsmb0
Jun 24 07:13:35 jaguar genunix: [ID 936769 kern.info] nsmb0 is 
/pseudo/nsmb at 0
Jun 24 07:13:36 jaguar console-kit-daemon[516]: [ID 702911 
daemon.warning] WARNING: signal "open_session_request" (from 
"OpenSessionRequest") exported but not found in object class "CkSeat"
Jun 24 07:13:36 jaguar console-kit-daemon[516]: [ID 702911 
daemon.warning] WARNING: signal "close_session_request" (from 
"CloseSessionRequest") exported but not found in object class "CkSeat"
Jun 24 07:13:36 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:13:36 jaguar This may result in reduced system performance.
Jun 24 07:13:36 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:13:36 jaguar This may result in reduced system performance.

---

...then I determined to unplug the external USB hard drive and got this...

---

Jun 24 07:20:52 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:20:52 jaguar This may result in reduced system performance.
Jun 24 07:20:52 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:20:52 jaguar This may result in reduced system performance.
Jun 24 07:45:43 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: 
ahci port 3 has task file error
Jun 24 07:45:43 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery
Jun 24 07:45:43 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 07:45:43 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed
Jun 24 07:46:04 jaguar genunix: [ID 408114 kern.info] 
/pci at 0,0/pci1458,5006 at 1a,7/hub at 1 (hubd3) removed
Jun 24 07:46:04 jaguar rootnex: [ID 349649 kern.info] xsvc0 at root: 
space 0 offset 0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] xsvc0 is /xsvc at 0,0
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/aszeszo.fastdev01.uk.openindiana.org/masterconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/aszeszo.fastdev01.uk.openindiana.org/zoneconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/trisk.fastdev01.uk.openindiana.org/masterconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/trisk.fastdev01.uk.openindiana.org/zoneconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/transcode.fastdev01.uk.openindiana.org/zoneconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/transcode.fastdev01.uk.openindiana.org/masterconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/tomww.fastdev01.uk.openindiana.org/zoneconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/tomww.fastdev01.uk.openindiana.org/masterconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/python.fastdev01.uk.openindiana.org/zoneconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/python.fastdev01.uk.openindiana.org/masterconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/jds.fastdev01.uk.openindiana.org/zoneconsole: No such file or 
directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/jds.fastdev01.uk.openindiana.org/masterconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/sfw.fastdev01.uk.openindiana.org/zoneconsole: No such file or 
directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/sfw.fastdev01.uk.openindiana.org/masterconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for /dev/zcons/jdsbuild/zoneconsole: 
No such file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/jdsbuild/masterconsole: No such file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/onnv.fastdev01.uk.openindiana.org/masterconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/onnv.fastdev01.uk.openindiana.org/zoneconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/g11n.fastdev01.uk.openindiana.org/masterconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/g11n.fastdev01.uk.openindiana.org/zoneconsole: No such file 
or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/alasdair.fastdev01.uk.openindiana.org/zoneconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/alasdair.fastdev01.uk.openindiana.org/masterconsole: No such 
file or directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/test01.alasdair.openindiana.org/zoneconsole: No such file or 
directory
Jun 24 07:46:04 jaguar devfsadmd[255]: [ID 317882 daemon.error] 
build_devlink_list: readlink failed for 
/dev/zcons/test01.alasdair.openindiana.org/masterconsole: No such file 
or directory
Jun 24 07:46:04 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:46:04 jaguar This may result in reduced system performance.
Jun 24 07:46:04 jaguar unix: [ID 954099 kern.info] NOTICE: IRQ16 is 
being shared by drivers with different interrupt levels.
Jun 24 07:46:04 jaguar This may result in reduced system performance.
Jun 24 07:46:04 jaguar pcplusmp: [ID 805372 kern.info] pcplusmp: asy 
(asy) instance 0 irq 0x4 vector 0xb0 ioapic 0x2 intin 0x4 is bound to cpu 0
Jun 24 07:46:04 jaguar isa: [ID 202937 kern.info] ISA-device: asy0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] asy0 is 
/pci at 0,0/isa at 1f/asy at 1,3f8
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: llc10
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] llc10 is 
/pseudo/llc1 at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] lofi0 is 
/pseudo/lofi at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
ramdisk1024
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] ramdisk1024 is 
/pseudo/ramdisk at 1024
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] ucode0 is 
/pseudo/ucode at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
nvidia255
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] nvidia255 is 
/pseudo/nvidia at 255
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: dcpc0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] dcpc0 is 
/pseudo/dcpc at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
fasttrap0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] fasttrap0 is 
/pseudo/fasttrap at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
lockstat0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] lockstat0 is 
/pseudo/lockstat at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: profile0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] profile0 is 
/pseudo/profile at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: 
systrace0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] systrace0 is 
/pseudo/systrace at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] fcsm0 is 
/pseudo/fcsm at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fct0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] fct0 is /pseudo/fct at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: stmf0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] stmf0 is 
/pseudo/stmf at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: bpf0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] bpf0 is /pseudo/bpf at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] winlock0 is 
/pseudo/winlock at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] fssnap0 is 
/pseudo/fssnap at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: pm0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] pm0 is /pseudo/pm at 0
Jun 24 07:46:04 jaguar pseudo: [ID 129642 kern.info] pseudo-device: nsmb0
Jun 24 07:46:04 jaguar genunix: [ID 936769 kern.info] nsmb0 is 
/pseudo/nsmb at 0


---

... and it has stopped complaining for a few minutes now.

However, the terminal was giving me...

"Jun 24 07:06:04 jaguar devfsadmd[255]: build_devlink_list:readkubj 
fauked fir /dev/zcons/test01.alasdair.openindiana.org/masterconsule: No 
such file or directory

I'm also unsure of the event at 07:13:27 - nwamd[76]: [ID 605049 
daemon.error] 1: nwamd_set_unset_link_properties: dladm_set_linkprop 
failed: operation not supported

Could the lack of free space on the ZFS set also have caused a problem, 
or is it likely that the weight of another problem, possibly the USB 
external drive connection, caused it to keel over?



From minikola at gmail.com  Sun Jun 24 12:11:18 2012
From: minikola at gmail.com (Nikola M.)
Date: Sun, 24 Jun 2012 14:11:18 +0200
Subject: [OpenIndiana-discuss] High availability/Clustering for
 OpenIndiana 2010.09
In-Reply-To: <997910.3792.qm@web111312.mail.gq1.yahoo.com>
References: <997910.3792.qm@web111312.mail.gq1.yahoo.com>
Message-ID: <4FE703E6.8040203@gmail.com>

On 09/15/10 05:34 PM, ken mays wrote:
> Hello,
>
> HA/Clustering solutions like a 128-node cluster for distributed computing and computational efforts (cloud or internal) are very possible.
>
> This is something to "showcase" in the upcoming weeks.
>
> ~ Ken Mays
>
Hi, what happend with this HA/Clustering resurrection in 
Openindiana/Illumos ?



From awg1 at gmx.com  Sun Jun 24 14:28:22 2012
From: awg1 at gmx.com (Adam Gold)
Date: Sun, 24 Jun 2012 15:28:22 +0100
Subject: [OpenIndiana-discuss] recognizing disks
Message-ID: <6F8FE2A0-600B-437D-8C65-0D9BBA550664@gmx.com>

Hi there.  I'm a linux user and have recently decided to switch to OpenIndiana using a x86_64 server.  Somewhat embarrassingly I'm seem to be falling at one of the early hurdles.  My server has 1 SSD where the O/S has been successfully installed and 4 X 3TB hard drives managed by an LSI RAID controller.  I have configured the hard drives as JBOD so I can use ZFS with all its capabilities.

Having booted up for the first time I ran 'format -e' but the 4 hard drives were not detected.  Likewise when using 'cfgadm -alv' and 'devfsadm' + 'format' there was no sign of any unconfigured drives.  Just to be sure there wasn't any legacy data/meta-data I booted to a rescue disk and erased the GPT labels at the beginning and end of the 3TB disks using 'dd'.  Again no luck.

These drives have always showed up automatically under linux so I'm wondering if I'm making some very obvious starting error with the new O/S, perhaps to do with labelling (although now there really are no labels) or something.  I'm posting in the hope that this may be quickly apparent to veteran users (and apologies for the relatively trivial level of the inquiry).  Thanks in advance for any responses.

From mike.laspina at laspina.ca  Sun Jun 24 16:24:08 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Sun, 24 Jun 2012 11:24:08 -0500
Subject: [OpenIndiana-discuss] recognizing disks
In-Reply-To: <6F8FE2A0-600B-437D-8C65-0D9BBA550664@gmx.com>
References: <6F8FE2A0-600B-437D-8C65-0D9BBA550664@gmx.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D470C@MS1.laspina.ca>

Hi Adam,

Possibly the LSI controller was not matched to a driver. Check the
controller model and verify it is on the HCL.

Run: 

pfexec prtconf | grep driver 

to observer any devices that are not bound to a driver.


http://illumos.org/hcl/

Typically I have found that the some RAID mode firmware within LSI cards
and other vendors is not always compatible or matched to a driver.
For example I have an IBM (LSI 1068) branded adaptor. It works fine when
I load the Initiator/Target mode firmware image but not when it's
running the RAID firmware image.

Regards,
Mike

http://blog.laspina.ca/ 


-----Original Message-----
From: Adam Gold [mailto:awg1 at gmx.com] 
Sent: Sunday, June 24, 2012 9:28 AM
To: openindiana-discuss at openindiana.org
Subject: [OpenIndiana-discuss] recognizing disks

Hi there.  I'm a linux user and have recently decided to switch to
OpenIndiana using a x86_64 server.  Somewhat embarrassingly I'm seem to
be falling at one of the early hurdles.  My server has 1 SSD where the
O/S has been successfully installed and 4 X 3TB hard drives managed by
an LSI RAID controller.  I have configured the hard drives as JBOD so I
can use ZFS with all its capabilities.

Having booted up for the first time I ran 'format -e' but the 4 hard
drives were not detected.  Likewise when using 'cfgadm -alv' and
'devfsadm' + 'format' there was no sign of any unconfigured drives.
Just to be sure there wasn't any legacy data/meta-data I booted to a
rescue disk and erased the GPT labels at the beginning and end of the
3TB disks using 'dd'.  Again no luck.

These drives have always showed up automatically under linux so I'm
wondering if I'm making some very obvious starting error with the new
O/S, perhaps to do with labelling (although now there really are no
labels) or something.  I'm posting in the hope that this may be quickly
apparent to veteran users (and apologies for the relatively trivial
level of the inquiry).  Thanks in advance for any responses.
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From jsowoc at gmail.com  Sun Jun 24 16:44:33 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Sun, 24 Jun 2012 10:44:33 -0600
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE6BB5E.5030604@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
Message-ID: <CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>

On Sun, Jun 24, 2012 at 1:01 AM, michelle <michelle at msknight.com> wrote:
> Situation - home-type standard PC, 4gig of RAM, running two SSDs in a
> mirrored root raid pool. Three 2tb hard drives in a raidz.
>
> System is...
>
> ? ? ? ? ? ? OpenIndiana Development oi_151.1.4 X86 (powered by illumos)
[...]
>
> I have an external, "toaster" which takes two hard drives, one is connected
> via e-sata; the other is running via USB (although for this instance, there
> was no drive in teh socket) because I've had a long running battle to try
> and get an affordable (to me) e-sata card that will give me another e-sata
> channel.

So it's a 2-bay RAID enclosure with either USB or eSATA connections.
One of the two bays are occupied, and how is the enclosure being
connected?


> The ZFS set was getting full; something like only 50gig free.

You probably have two zpools - one is the mirrored "rpool", while the
other is your data pool, say, "tank". Am I understanding that it's
"tank" that has 50 GB (out of 4TB) free, while "rpool" does not have
any problems?


> I was starting
> file copies off the server to an external drive via an SMB client, and going
> to bed, to wake up and find the process had frozen. Diagnosis led me to the
> server, which appeared to hang on any log on attempt. It even didn't listen
> to the power button properly.

Is this external drive the RAID enclosure discussed above, that you
connected via Ethernet and it shows up as an SMB device, or is this on
a separate computer?


My thoughts are:

1) if "rpool" is not full, then the system should not freeze.
Depending on any snapshots, even removing files from "tank" may fail
and if you do it via SMB, as opposed to over a local command line, you
won't know why. Could you try logging on to the system, and copying
the files from the server to a client, so you see any local error
messages on the command line?

2) if, for some reason, data loss crept in, ZFS will refuse to return
bad data. Could you run a "zpool scrub" on each of the pools and then
verify that they are healthy?


> Could the lack of free space on the ZFS set also have caused a problem, or
> is it likely that the weight of another problem, possibly the USB external
> drive connection, caused it to keel over?

Not sure if it will help, but could you give details on what the
enclosure is (brand/model), and what motherboard/USB controller are on
the server?


Jan


From michelle at msknight.com  Sun Jun 24 17:00:35 2012
From: michelle at msknight.com (michelle)
Date: Sun, 24 Jun 2012 18:00:35 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
Message-ID: <4FE747B3.8060604@msknight.com>

The motherboard is a Gigabyte GA-H55M-UD2H and has five SATA sockets, 
two IDE and one E-sata.

The SATA are, I believe, Intel.

The mb has five internal sata - two are rpool which are SSDs with plenty 
of space on them.

The other three are given over to a "tank" mounted at /mirror.

The external toaster is a Sharkoom Quickport Duo II, where drive  1 is 
connected via E-sata and, when I connect the second, it is via USB 
because I only have one e-sata port.

I believe that disconnecting the USB has resulted in stopping the IRQ 
resource problem, but now I am having this...

Jun 24 15:59:46 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery
Jun 24 15:59:46 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 15:59:46 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed
Jun 24 15:59:46 jaguar ahci: [ID 811322 kern.info] NOTICE: ahci0: 
ahci_tran_reset_dport port 3 reset device
Jun 24 15:59:51 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: 
ahci port 3 has task file error
Jun 24 15:59:51 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery
Jun 24 15:59:51 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 15:59:51 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed
Jun 24 15:59:54 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: 
ahci port 3 has task file error
Jun 24 15:59:54 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery
Jun 24 15:59:54 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 15:59:54 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed
Jun 24 16:00:00 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: 
ahci port 3 has task file error
Jun 24 16:00:00 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery
Jun 24 16:00:00 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 16:00:00 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed


The set is usually automatically scrubbed once a month.

I have removed about 200 gig of data and it seems to be stable-ish.

I'll begin another scrub of the tank now. It will likely take 10 hours.



On 24/06/12 17:44, Jan Owoc wrote:
> On Sun, Jun 24, 2012 at 1:01 AM, michelle<michelle at msknight.com>  wrote:
>> Situation - home-type standard PC, 4gig of RAM, running two SSDs in a
>> mirrored root raid pool. Three 2tb hard drives in a raidz.
>>
>> System is...
>>
>>              OpenIndiana Development oi_151.1.4 X86 (powered by illumos)
> [...]
>> I have an external, "toaster" which takes two hard drives, one is connected
>> via e-sata; the other is running via USB (although for this instance, there
>> was no drive in teh socket) because I've had a long running battle to try
>> and get an affordable (to me) e-sata card that will give me another e-sata
>> channel.
> So it's a 2-bay RAID enclosure with either USB or eSATA connections.
> One of the two bays are occupied, and how is the enclosure being
> connected?
>
>
>> The ZFS set was getting full; something like only 50gig free.
> You probably have two zpools - one is the mirrored "rpool", while the
> other is your data pool, say, "tank". Am I understanding that it's
> "tank" that has 50 GB (out of 4TB) free, while "rpool" does not have
> any problems?
>
>
>> I was starting
>> file copies off the server to an external drive via an SMB client, and going
>> to bed, to wake up and find the process had frozen. Diagnosis led me to the
>> server, which appeared to hang on any log on attempt. It even didn't listen
>> to the power button properly.
> Is this external drive the RAID enclosure discussed above, that you
> connected via Ethernet and it shows up as an SMB device, or is this on
> a separate computer?
>
>
> My thoughts are:
>
> 1) if "rpool" is not full, then the system should not freeze.
> Depending on any snapshots, even removing files from "tank" may fail
> and if you do it via SMB, as opposed to over a local command line, you
> won't know why. Could you try logging on to the system, and copying
> the files from the server to a client, so you see any local error
> messages on the command line?
>
> 2) if, for some reason, data loss crept in, ZFS will refuse to return
> bad data. Could you run a "zpool scrub" on each of the pools and then
> verify that they are healthy?
>
>
>> Could the lack of free space on the ZFS set also have caused a problem, or
>> is it likely that the weight of another problem, possibly the USB external
>> drive connection, caused it to keel over?
> Not sure if it will help, but could you give details on what the
> enclosure is (brand/model), and what motherboard/USB controller are on
> the server?
>
>
> Jan
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From awg1 at gmx.com  Sun Jun 24 17:15:23 2012
From: awg1 at gmx.com (Adam Gold)
Date: Sun, 24 Jun 2012 18:15:23 +0100
Subject: [OpenIndiana-discuss] recognizing disks
In-Reply-To: <8F607366E3C0F9499212649291E0BD640D470C@MS1.laspina.ca>
References: <6F8FE2A0-600B-437D-8C65-0D9BBA550664@gmx.com>
	<8F607366E3C0F9499212649291E0BD640D470C@MS1.laspina.ca>
Message-ID: <1A919C53-698B-43F5-A026-9539289442E7@gmx.com>

Mike,

Thanks a lot for the response.  The controller model is LSI 9240-8i.  I ran the command and received the following output:

*************
 pci15d9,6 (driver not attached)
        pci8086,3408 (driver not attached)
        pci8086,340a (driver not attached)
        pci8086,340e (driver not attached)
            pci1000,9240 (driver not attached)
        pci8086,342d (driver not attached)
        pci8086,342e (driver not attached)
        pci8086,3422 (driver not attached)
        pci8086,3438 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
                    input, instance #4 (driver not attached)
            motherboard (driver not attached)
            asy, instance #0 (driver not attached)
            asy, instance #1 (driver not attached)
            motherboard (driver not attached)
            ide (driver not attached)
        pci15d9,6 (driver not attached)
            ide (driver not attached)
    ioapics (driver not attached)
        ioapic, instance #0 (driver not attached)
    used-resources (driver not attached)
    agpgart, instance #0 (driver not attached)
*************

I'm guessing it's one of the pci drivers - any pointers (or questions I can answer to help narrow it down).  Also, am I correct in saying the loading of the Initiator/Target mode firmware image should be done in the BIOS before the O/S has loaded?

Thanks for your help.

Regards,

Adam


On 24 Jun 2012, at 17:24, Mike La Spina wrote:

> Hi Adam,
> 
> Possibly the LSI controller was not matched to a driver. Check the
> controller model and verify it is on the HCL.
> 
> Run: 
> 
> pfexec prtconf | grep driver 
> 
> to observer any devices that are not bound to a driver.
> 
> 
> http://illumos.org/hcl/
> 
> Typically I have found that the some RAID mode firmware within LSI cards
> and other vendors is not always compatible or matched to a driver.
> For example I have an IBM (LSI 1068) branded adaptor. It works fine when
> I load the Initiator/Target mode firmware image but not when it's
> running the RAID firmware image.
> 
> Regards,
> Mike
> 
> http://blog.laspina.ca/ 
> 
> 
> -----Original Message-----
> From: Adam Gold [mailto:awg1 at gmx.com] 
> Sent: Sunday, June 24, 2012 9:28 AM
> To: openindiana-discuss at openindiana.org
> Subject: [OpenIndiana-discuss] recognizing disks
> 
> Hi there.  I'm a linux user and have recently decided to switch to
> OpenIndiana using a x86_64 server.  Somewhat embarrassingly I'm seem to
> be falling at one of the early hurdles.  My server has 1 SSD where the
> O/S has been successfully installed and 4 X 3TB hard drives managed by
> an LSI RAID controller.  I have configured the hard drives as JBOD so I
> can use ZFS with all its capabilities.
> 
> Having booted up for the first time I ran 'format -e' but the 4 hard
> drives were not detected.  Likewise when using 'cfgadm -alv' and
> 'devfsadm' + 'format' there was no sign of any unconfigured drives.
> Just to be sure there wasn't any legacy data/meta-data I booted to a
> rescue disk and erased the GPT labels at the beginning and end of the
> 3TB disks using 'dd'.  Again no luck.
> 
> These drives have always showed up automatically under linux so I'm
> wondering if I'm making some very obvious starting error with the new
> O/S, perhaps to do with labelling (although now there really are no
> labels) or something.  I'm posting in the hope that this may be quickly
> apparent to veteran users (and apologies for the relatively trivial
> level of the inquiry).  Thanks in advance for any responses.
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



From mike.laspina at laspina.ca  Sun Jun 24 18:29:43 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Sun, 24 Jun 2012 13:29:43 -0500
Subject: [OpenIndiana-discuss] recognizing disks
In-Reply-To: <1A919C53-698B-43F5-A026-9539289442E7@gmx.com>
References: <6F8FE2A0-600B-437D-8C65-0D9BBA550664@gmx.com><8F607366E3C0F9499212649291E0BD640D470C@MS1.laspina.ca>
	<1A919C53-698B-43F5-A026-9539289442E7@gmx.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D470D@MS1.laspina.ca>

Adam,

As I suspected it did not find a driver match. There is a Solaris driver
available from LSI for that card.
            
pci1000,9240 (driver not attached)

Try
http://www.lsi.com/channel/products/storagecomponents/Pages/MegaRAIDSAS9
240-8i.aspx
Or
http://www.byte.nl/blog/2011/01/04/how-to-install-opensolaris-openindian
a-on-an-m1015-lsi-9240-raid-controller/

Regards,
Mike
 


-----Original Message-----
From: Adam Gold [mailto:awg1 at gmx.com] 
Sent: Sunday, June 24, 2012 12:15 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] recognizing disks

Mike,

Thanks a lot for the response.  The controller model is LSI 9240-8i.  I
ran the command and received the following output:

*************
 pci15d9,6 (driver not attached)
        pci8086,3408 (driver not attached)
        pci8086,340a (driver not attached)
        pci8086,340e (driver not attached)
            pci1000,9240 (driver not attached)
        pci8086,342d (driver not attached)
        pci8086,342e (driver not attached)
        pci8086,3422 (driver not attached)
        pci8086,3438 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
                    input, instance #4 (driver not attached)
            motherboard (driver not attached)
            asy, instance #0 (driver not attached)
            asy, instance #1 (driver not attached)
            motherboard (driver not attached)
            ide (driver not attached)
        pci15d9,6 (driver not attached)
            ide (driver not attached)
    ioapics (driver not attached)
        ioapic, instance #0 (driver not attached)
    used-resources (driver not attached)
    agpgart, instance #0 (driver not attached)
*************

I'm guessing it's one of the pci drivers - any pointers (or questions I
can answer to help narrow it down).  Also, am I correct in saying the
loading of the Initiator/Target mode firmware image should be done in
the BIOS before the O/S has loaded?

Thanks for your help.

Regards,

Adam


On 24 Jun 2012, at 17:24, Mike La Spina wrote:

> Hi Adam,
> 
> Possibly the LSI controller was not matched to a driver. Check the 
> controller model and verify it is on the HCL.
> 
> Run: 
> 
> pfexec prtconf | grep driver
> 
> to observer any devices that are not bound to a driver.
> 
> 
> http://illumos.org/hcl/
> 
> Typically I have found that the some RAID mode firmware within LSI 
> cards and other vendors is not always compatible or matched to a
driver.
> For example I have an IBM (LSI 1068) branded adaptor. It works fine 
> when I load the Initiator/Target mode firmware image but not when it's

> running the RAID firmware image.
> 
> Regards,
> Mike
> 
> http://blog.laspina.ca/
> 
> 
> -----Original Message-----
> From: Adam Gold [mailto:awg1 at gmx.com]
> Sent: Sunday, June 24, 2012 9:28 AM
> To: openindiana-discuss at openindiana.org
> Subject: [OpenIndiana-discuss] recognizing disks
> 
> Hi there.  I'm a linux user and have recently decided to switch to 
> OpenIndiana using a x86_64 server.  Somewhat embarrassingly I'm seem 
> to be falling at one of the early hurdles.  My server has 1 SSD where 
> the O/S has been successfully installed and 4 X 3TB hard drives 
> managed by an LSI RAID controller.  I have configured the hard drives 
> as JBOD so I can use ZFS with all its capabilities.
> 
> Having booted up for the first time I ran 'format -e' but the 4 hard 
> drives were not detected.  Likewise when using 'cfgadm -alv' and 
> 'devfsadm' + 'format' there was no sign of any unconfigured drives.
> Just to be sure there wasn't any legacy data/meta-data I booted to a 
> rescue disk and erased the GPT labels at the beginning and end of the 
> 3TB disks using 'dd'.  Again no luck.
> 
> These drives have always showed up automatically under linux so I'm 
> wondering if I'm making some very obvious starting error with the new 
> O/S, perhaps to do with labelling (although now there really are no
> labels) or something.  I'm posting in the hope that this may be 
> quickly apparent to veteran users (and apologies for the relatively 
> trivial level of the inquiry).  Thanks in advance for any responses.
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From mike.laspina at laspina.ca  Sun Jun 24 19:10:05 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Sun, 24 Jun 2012 14:10:05 -0500
Subject: [OpenIndiana-discuss] recognizing disks
In-Reply-To: <1A919C53-698B-43F5-A026-9539289442E7@gmx.com>
References: <6F8FE2A0-600B-437D-8C65-0D9BBA550664@gmx.com><8F607366E3C0F9499212649291E0BD640D470C@MS1.laspina.ca>
	<1A919C53-698B-43F5-A026-9539289442E7@gmx.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D470E@MS1.laspina.ca>

Adam,

There is a possibility that the existing mega_sas driver will work
correctly out of the box. Can't verify it for you but there are some
simple ways to invoke a detection and or direct binding.

The Initiator/Target mode can be applied using a utility from LSI. It
can also be applied from a Linux/Windows OS etc. 

1: Add the alias to /etc/driver_alias

Edit the file and directly after this line:

	driver name=mega_sas class=scsi \

Add the following pci id strings - most likely the first one:
	
	alias=pci1000,0073.9240.1000 \
	alias=pci1000,0073.3035.1054 \
	alias=pci1000,0073.1054.1000 \
	alias=pci1000,0073.1458.1002 \


2: Or directly binding it with drv_add

	pfexec add_drv -i '"pci1000,73"' mega_sas

-----Original Message-----
From: Adam Gold [mailto:awg1 at gmx.com] 
Sent: Sunday, June 24, 2012 12:15 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] recognizing disks

Mike,

Thanks a lot for the response.  The controller model is LSI 9240-8i.  I
ran the command and received the following output:

*************
 pci15d9,6 (driver not attached)
        pci8086,3408 (driver not attached)
        pci8086,340a (driver not attached)
        pci8086,340e (driver not attached)
            pci1000,9240 (driver not attached)
        pci8086,342d (driver not attached)
        pci8086,342e (driver not attached)
        pci8086,3422 (driver not attached)
        pci8086,3438 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
        pci15d9,6 (driver not attached)
                    input, instance #4 (driver not attached)
            motherboard (driver not attached)
            asy, instance #0 (driver not attached)
            asy, instance #1 (driver not attached)
            motherboard (driver not attached)
            ide (driver not attached)
        pci15d9,6 (driver not attached)
            ide (driver not attached)
    ioapics (driver not attached)
        ioapic, instance #0 (driver not attached)
    used-resources (driver not attached)
    agpgart, instance #0 (driver not attached)
*************

I'm guessing it's one of the pci drivers - any pointers (or questions I
can answer to help narrow it down).  Also, am I correct in saying the
loading of the Initiator/Target mode firmware image should be done in
the BIOS before the O/S has loaded?

Thanks for your help.

Regards,

Adam


On 24 Jun 2012, at 17:24, Mike La Spina wrote:

> Hi Adam,
> 
> Possibly the LSI controller was not matched to a driver. Check the 
> controller model and verify it is on the HCL.
> 
> Run: 
> 
> pfexec prtconf | grep driver
> 
> to observer any devices that are not bound to a driver.
> 
> 
> http://illumos.org/hcl/
> 
> Typically I have found that the some RAID mode firmware within LSI 
> cards and other vendors is not always compatible or matched to a
driver.
> For example I have an IBM (LSI 1068) branded adaptor. It works fine 
> when I load the Initiator/Target mode firmware image but not when it's

> running the RAID firmware image.
> 
> Regards,
> Mike
> 
> http://blog.laspina.ca/
> 
> 
> -----Original Message-----
> From: Adam Gold [mailto:awg1 at gmx.com]
> Sent: Sunday, June 24, 2012 9:28 AM
> To: openindiana-discuss at openindiana.org
> Subject: [OpenIndiana-discuss] recognizing disks
> 
> Hi there.  I'm a linux user and have recently decided to switch to 
> OpenIndiana using a x86_64 server.  Somewhat embarrassingly I'm seem 
> to be falling at one of the early hurdles.  My server has 1 SSD where 
> the O/S has been successfully installed and 4 X 3TB hard drives 
> managed by an LSI RAID controller.  I have configured the hard drives 
> as JBOD so I can use ZFS with all its capabilities.
> 
> Having booted up for the first time I ran 'format -e' but the 4 hard 
> drives were not detected.  Likewise when using 'cfgadm -alv' and 
> 'devfsadm' + 'format' there was no sign of any unconfigured drives.
> Just to be sure there wasn't any legacy data/meta-data I booted to a 
> rescue disk and erased the GPT labels at the beginning and end of the 
> 3TB disks using 'dd'.  Again no luck.
> 
> These drives have always showed up automatically under linux so I'm 
> wondering if I'm making some very obvious starting error with the new 
> O/S, perhaps to do with labelling (although now there really are no
> labels) or something.  I'm posting in the hope that this may be 
> quickly apparent to veteran users (and apologies for the relatively 
> trivial level of the inquiry).  Thanks in advance for any responses.
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From awg1 at gmx.com  Sun Jun 24 19:24:06 2012
From: awg1 at gmx.com (Adam Gold)
Date: Sun, 24 Jun 2012 20:24:06 +0100
Subject: [OpenIndiana-discuss] recognizing disks
In-Reply-To: <8F607366E3C0F9499212649291E0BD640D470E@MS1.laspina.ca>
References: <6F8FE2A0-600B-437D-8C65-0D9BBA550664@gmx.com><8F607366E3C0F9499212649291E0BD640D470C@MS1.laspina.ca>
	<1A919C53-698B-43F5-A026-9539289442E7@gmx.com>
	<8F607366E3C0F9499212649291E0BD640D470E@MS1.laspina.ca>
Message-ID: <903A4A94-B3B1-4F0C-AA4A-612C1AE42A98@gmx.com>

Thanks Mike.  I will try this first, it not I'll go the more "drastic" route!

Adam


On 24 Jun 2012, at 20:10, Mike La Spina wrote:

> Adam,
> 
> There is a possibility that the existing mega_sas driver will work
> correctly out of the box. Can't verify it for you but there are some
> simple ways to invoke a detection and or direct binding.
> 
> The Initiator/Target mode can be applied using a utility from LSI. It
> can also be applied from a Linux/Windows OS etc. 
> 
> 1: Add the alias to /etc/driver_alias
> 
> Edit the file and directly after this line:
> 
> 	driver name=mega_sas class=scsi \
> 
> Add the following pci id strings - most likely the first one:
> 	
> 	alias=pci1000,0073.9240.1000 \
> 	alias=pci1000,0073.3035.1054 \
> 	alias=pci1000,0073.1054.1000 \
> 	alias=pci1000,0073.1458.1002 \
> 
> 
> 2: Or directly binding it with drv_add
> 
> 	pfexec add_drv -i '"pci1000,73"' mega_sas
> 
> -----Original Message-----
> From: Adam Gold [mailto:awg1 at gmx.com] 
> Sent: Sunday, June 24, 2012 12:15 PM
> To: Discussion list for OpenIndiana
> Subject: Re: [OpenIndiana-discuss] recognizing disks
> 
> Mike,
> 
> Thanks a lot for the response.  The controller model is LSI 9240-8i.  I
> ran the command and received the following output:
> 
> *************
> pci15d9,6 (driver not attached)
>        pci8086,3408 (driver not attached)
>        pci8086,340a (driver not attached)
>        pci8086,340e (driver not attached)
>            pci1000,9240 (driver not attached)
>        pci8086,342d (driver not attached)
>        pci8086,342e (driver not attached)
>        pci8086,3422 (driver not attached)
>        pci8086,3438 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>        pci15d9,6 (driver not attached)
>                    input, instance #4 (driver not attached)
>            motherboard (driver not attached)
>            asy, instance #0 (driver not attached)
>            asy, instance #1 (driver not attached)
>            motherboard (driver not attached)
>            ide (driver not attached)
>        pci15d9,6 (driver not attached)
>            ide (driver not attached)
>    ioapics (driver not attached)
>        ioapic, instance #0 (driver not attached)
>    used-resources (driver not attached)
>    agpgart, instance #0 (driver not attached)
> *************
> 
> I'm guessing it's one of the pci drivers - any pointers (or questions I
> can answer to help narrow it down).  Also, am I correct in saying the
> loading of the Initiator/Target mode firmware image should be done in
> the BIOS before the O/S has loaded?
> 
> Thanks for your help.
> 
> Regards,
> 
> Adam
> 
> 
> On 24 Jun 2012, at 17:24, Mike La Spina wrote:
> 
>> Hi Adam,
>> 
>> Possibly the LSI controller was not matched to a driver. Check the 
>> controller model and verify it is on the HCL.
>> 
>> Run: 
>> 
>> pfexec prtconf | grep driver
>> 
>> to observer any devices that are not bound to a driver.
>> 
>> 
>> http://illumos.org/hcl/
>> 
>> Typically I have found that the some RAID mode firmware within LSI 
>> cards and other vendors is not always compatible or matched to a
> driver.
>> For example I have an IBM (LSI 1068) branded adaptor. It works fine 
>> when I load the Initiator/Target mode firmware image but not when it's
> 
>> running the RAID firmware image.
>> 
>> Regards,
>> Mike
>> 
>> http://blog.laspina.ca/
>> 
>> 
>> -----Original Message-----
>> From: Adam Gold [mailto:awg1 at gmx.com]
>> Sent: Sunday, June 24, 2012 9:28 AM
>> To: openindiana-discuss at openindiana.org
>> Subject: [OpenIndiana-discuss] recognizing disks
>> 
>> Hi there.  I'm a linux user and have recently decided to switch to 
>> OpenIndiana using a x86_64 server.  Somewhat embarrassingly I'm seem 
>> to be falling at one of the early hurdles.  My server has 1 SSD where 
>> the O/S has been successfully installed and 4 X 3TB hard drives 
>> managed by an LSI RAID controller.  I have configured the hard drives 
>> as JBOD so I can use ZFS with all its capabilities.
>> 
>> Having booted up for the first time I ran 'format -e' but the 4 hard 
>> drives were not detected.  Likewise when using 'cfgadm -alv' and 
>> 'devfsadm' + 'format' there was no sign of any unconfigured drives.
>> Just to be sure there wasn't any legacy data/meta-data I booted to a 
>> rescue disk and erased the GPT labels at the beginning and end of the 
>> 3TB disks using 'dd'.  Again no luck.
>> 
>> These drives have always showed up automatically under linux so I'm 
>> wondering if I'm making some very obvious starting error with the new 
>> O/S, perhaps to do with labelling (although now there really are no
>> labels) or something.  I'm posting in the hope that this may be 
>> quickly apparent to veteran users (and apologies for the relatively 
>> trivial level of the inquiry).  Thanks in advance for any responses.
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
>> 
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



From michelle at msknight.com  Mon Jun 25 06:30:55 2012
From: michelle at msknight.com (michelle)
Date: Mon, 25 Jun 2012 07:30:55 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE747B3.8060604@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com>
Message-ID: <4FE8059F.9040206@msknight.com>

Came back to it this morning, there had been errors. However, now the 
system has crashed.

It was responding to console, but when I asked for a zpool status, the 
terminal froze.

I had another terminal that was already logged on, and gave an init 6, 
but the server didn't respond. It's just sitting there.

---

The end result was that I had to hit the power again.

Reboot and log on gave zpool result of...

mich at jaguar:~# zpool status
   pool: data
  state: ONLINE
   scan: scrub in progress since Sun Jun 24 18:00:28 2012
     1.38T scanned out of 5.03T at 177K/s, (scan is slow, no estimated time)
     3.22M repaired, 27.53% done
config:

         NAME        STATE     READ WRITE CKSUM
         data        ONLINE       0     0     0
           raidz1-0  ONLINE       0     0     0
             c2t2d0  ONLINE       0     0     0
             c2t3d0  ONLINE       0     0     0  (repairing)
             c2t4d0  ONLINE       0     0     0

errors: No known data errors

   pool: rpool
  state: ONLINE
   scan: scrub repaired 0 in 0h1m with 0 errors on Sat Jun  9 00:01:26 2012
config:

         NAME          STATE     READ WRITE CKSUM
         rpool         ONLINE       0     0     0
           mirror-0    ONLINE       0     0     0
             c2t0d0s0  ONLINE       0     0     0
             c2t1d0s0  ONLINE       0     0     0

errors: No known data errors

.. and this is the messages at about the time of the crash...

Jun 24 21:20:55 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed
Jun 24 21:20:58 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: 
ahci port 3 has task file error
Jun 24 21:20:58 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery
Jun 24 21:20:58 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 21:21:00 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed
Jun 24 21:21:27 jaguar sata: [ID 801845 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2:
Jun 24 21:21:27 jaguar  SATA port 3 error
Jun 24 21:21:27 jaguar sata: [ID 801845 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2:
Jun 24 21:21:27 jaguar  SATA port 3 error
Jun 24 21:21:27 jaguar sata: [ID 801845 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2:
Jun 24 21:21:27 jaguar  SATA port 3 error
Jun 24 21:21:27 jaguar sata: [ID 801845 kern.info] 
/pci at 0,0/pci1458,b005 at 1f,2:
Jun 24 21:21:27 jaguar  SATA port 3 error
Jun 24 21:21:42 jaguar fmd: [ID 377184 daemon.error] SUNW-MSG-ID: 
ZFS-8000-FD, TYPE: Fault, VER: 1, SEVERITY: Major
Jun 24 21:21:42 jaguar EVENT-TIME: Sun Jun 24 21:21:42 BST 2012
Jun 24 21:21:42 jaguar PLATFORM: H55M-UD2H, CSN: -, HOSTNAME: jaguar
Jun 24 21:21:42 jaguar SOURCE: zfs-diagnosis, REV: 1.0
Jun 24 21:21:42 jaguar EVENT-ID: fbae1f99-ef10-ca46-c308-958e66bd0ddb
Jun 24 21:21:42 jaguar DESC: The number of I/O errors associated with a 
ZFS device exceeded
Jun 24 21:21:42 jaguar       acceptable levels.  Refer to 
http://illumos.org/msg/ZFS-8000-FD for more information.
Jun 24 21:21:42 jaguar AUTO-RESPONSE: The device has been offlined and 
marked as faulted.  An attempt
Jun 24 21:21:42 jaguar       will be made to activate a hot spare if 
available.
Jun 24 21:21:42 jaguar IMPACT: Fault tolerance of the pool may be 
compromised.
Jun 24 21:21:42 jaguar REC-ACTION: Run 'zpool status -x' and replace the 
bad device.
Jun 24 21:21:55 jaguar ahci: [ID 517647 kern.warning] WARNING: ahci0: 
watchdog port 3 satapkt 0xffffff020f879888 timed out
Jun 25 07:24:04 jaguar genunix: [ID 108120 kern.notice] ^MOpenIndiana 
Build oi_151a4 64-bit (illumos 13676:98ca40df9171)
Jun 25 07:24:04 jaguar genunix: [ID 107366 kern.notice] SunOS Release 
5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
Jun 25 07:24:04 jaguar genunix: [ID 864463 kern.notice] All rights 
reserved. Use is subject to license terms.
Jun 25 07:24:04 jaguar unix: [ID 223955 kern.info] x86_feature: lgpg

On the face of this, a drive failure has taken the system down.

I'm going to have to check the connections,



From o.h.weiergraeber at fz-juelich.de  Mon Jun 25 07:17:34 2012
From: o.h.weiergraeber at fz-juelich.de (=?iso-8859-1?Q?=22Weiergr=E4ber=2C_Oliver_H=2E=22?=)
Date: Mon, 25 Jun 2012 07:17:34 +0000
Subject: [OpenIndiana-discuss] ACPI errors
In-Reply-To: <4FE69670.6090600@gmail.com>
References: <FF7867E8B89EAE4891E7A47C724A50910657B0@MBX2010-K01.ad.fz-juelich.de>
	<FF7867E8B89EAE4891E7A47C724A5091067376@MBX2010-K01.ad.fz-juelich.de>
	<CAD0Ztp1TPJMqXVw3s7v5x_3G4iNh4LB=oCjpgsE2SuiQk4DSLA@mail.gmail.com>,
	<4FE69670.6090600@gmail.com>
Message-ID: <FF7867E8B89EAE4891E7A47C724A50910676AB@MBX2010-K01.ad.fz-juelich.de>

Thanks a lot for the quick replies. According to Update manager, my system is up to date,
so it seems the latest fixes you mentioned did not make it (yet) into OpenIndiana.
Is there a chance this will happen in the neat future?

Best regards,
Oliver


________________________________________
From: Yuri Pankov [yuri.pankov at gmail.com]
Sent: Sunday, June 24, 2012 6:24 AM
To: openindiana-discuss
Subject: Re: [OpenIndiana-discuss] ACPI errors

On Sat, 23 Jun 2012 11:39:00 -0400, Gordon Ross wrote:
> On Fri, Jun 22, 2012 at 10:01 AM, "Weiergr?ber, Oliver H."
> <o.h.weiergraeber at fz-juelich.de> wrote:
>> Hello,
>>
>> while testing OpenIndiana (and Solaris 11) on an HP xw8600 workstation,
>> I noticed messages like this occurring regularly during bootup:
>>
>> ----------------------------------------------------------------------------------------------------------------------------
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 879926 kern.notice] ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS (20100915/dsfield-231)
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 804433 kern.notice] **** Exception AE_ALREADY_EXISTS during execution of method [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80)
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 652514 kern.notice] Method Execution Stack:
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 489567 kern.notice] Method [_OSC] executing: CreateDWordField (CAPB, Local1, CAPD)
> [...]
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 342246 kern.notice] ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80), AE_ALREADY_EXISTS (20100915/psparse-632)
>> May 17 21:13:48 mymachine.mydomain acpica: [ID 117524 kern.notice] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
>> ----------------------------------------------------------------------------------------------------------------------------
>>
>> What kind of ACPI problem is indicated here? Anything to worry about? I did notice stability issues on Solaris 11, but not on OpenIndiana, so I guess these are unrelated to the ACPI stuff.
>> The BIOS version is the latest available for this machine.
>>
>> Thanks in advance
>> Oliver
>
> When I was last working on an ACPI update (which I think is what's
> currently in illumos and OI) Yuri Pankov was helping me test the code,
> and observed a problem on his HP laptop that looked something like
> this, if I recall correctly.  He did some further experimenting and
> found that he could make his laptop boot without the ACPI errors by
> attaching the "EC" device a bit later.
>
> He showed me a possible fix, which I asked him to do some more work
> on, but then he ran out of time or something.  Maybe you'd like to
> pick up his changes and try them?

ACPICA 20100915 isn't the latest version available at the moment (at
least in illumos tree), which means that you are missing some fixes
Gordon did. Please try upgrading your OpenIndiana installation first and
check if it helps.


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Kennen Sie schon unseren neuen Film? http://www.fz-juelich.de/film
Kennen Sie schon unsere app? http://www.fz-juelich.de/app


From milan.jurik at xylab.cz  Mon Jun 25 07:40:35 2012
From: milan.jurik at xylab.cz (Milan Jurik)
Date: Mon, 25 Jun 2012 09:40:35 +0200
Subject: [OpenIndiana-discuss] ACPI errors
In-Reply-To: <FF7867E8B89EAE4891E7A47C724A50910676AB@MBX2010-K01.ad.fz-juelich.de>
References: <FF7867E8B89EAE4891E7A47C724A50910657B0@MBX2010-K01.ad.fz-juelich.de>
	<FF7867E8B89EAE4891E7A47C724A5091067376@MBX2010-K01.ad.fz-juelich.de>
	<CAD0Ztp1TPJMqXVw3s7v5x_3G4iNh4LB=oCjpgsE2SuiQk4DSLA@mail.gmail.com>,
	<4FE69670.6090600@gmail.com>
	<FF7867E8B89EAE4891E7A47C724A50910676AB@MBX2010-K01.ad.fz-juelich.de>
Message-ID: <8ff0233656e279e6afc93795a5e5d968@xylab.cz>

Hi,

could you start system terminal and send output of:

uname -a

and

pkg publisher

to this list?

Best regards,

Milan

On 25.06.2012 09:17, Weiergr?ber, Oliver H. wrote:
> Thanks a lot for the quick replies. According to Update manager, my
> system is up to date,
> so it seems the latest fixes you mentioned did not make it (yet) into
> OpenIndiana.
> Is there a chance this will happen in the neat future?
>
> Best regards,
> Oliver
>
>
> ________________________________________
> From: Yuri Pankov [yuri.pankov at gmail.com]
> Sent: Sunday, June 24, 2012 6:24 AM
> To: openindiana-discuss
> Subject: Re: [OpenIndiana-discuss] ACPI errors
>
> On Sat, 23 Jun 2012 11:39:00 -0400, Gordon Ross wrote:
>> On Fri, Jun 22, 2012 at 10:01 AM, "Weiergr?ber, Oliver H."
>> <o.h.weiergraeber at fz-juelich.de> wrote:
>>> Hello,
>>>
>>> while testing OpenIndiana (and Solaris 11) on an HP xw8600 
>>> workstation,
>>> I noticed messages like this occurring regularly during bootup:
>>>
>>> 
>>> ----------------------------------------------------------------------------------------------------------------------------
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 879926 kern.notice] 
>>> ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS 
>>> (20100915/dsfield-231)
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 804433 kern.notice] 
>>> **** Exception AE_ALREADY_EXISTS during execution of method 
>>> [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80)
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 652514 kern.notice] 
>>> Method Execution Stack:
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 489567 kern.notice] 
>>> Method [_OSC] executing: CreateDWordField (CAPB, Local1, CAPD)
>> [...]
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 342246 kern.notice] 
>>> ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node 
>>> ffffff02d59a8e80), AE_ALREADY_EXISTS (20100915/psparse-632)
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 117524 kern.notice] 
>>> ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS 
>>> error
>>> 
>>> ----------------------------------------------------------------------------------------------------------------------------
>>>
>>> What kind of ACPI problem is indicated here? Anything to worry 
>>> about? I did notice stability issues on Solaris 11, but not on 
>>> OpenIndiana, so I guess these are unrelated to the ACPI stuff.
>>> The BIOS version is the latest available for this machine.
>>>
>>> Thanks in advance
>>> Oliver
>>
>> When I was last working on an ACPI update (which I think is what's
>> currently in illumos and OI) Yuri Pankov was helping me test the 
>> code,
>> and observed a problem on his HP laptop that looked something like
>> this, if I recall correctly.  He did some further experimenting and
>> found that he could make his laptop boot without the ACPI errors by
>> attaching the "EC" device a bit later.
>>
>> He showed me a possible fix, which I asked him to do some more work
>> on, but then he ran out of time or something.  Maybe you'd like to
>> pick up his changes and try them?
>
> ACPICA 20100915 isn't the latest version available at the moment (at
> least in illumos tree), which means that you are missing some fixes
> Gordon did. Please try upgrading your OpenIndiana installation first 
> and
> check if it helps.
>
>



From aneurin.price at gmail.com  Mon Jun 25 14:18:47 2012
From: aneurin.price at gmail.com (Aneurin Price)
Date: Mon, 25 Jun 2012 15:18:47 +0100
Subject: [OpenIndiana-discuss] 'pkg image-update' and BEs
Message-ID: <CAHb+SPDN8=YPmX73t7fPrZ9BY6igwV72QZZUh3C9Ee9-h70cSg@mail.gmail.com>

Hi folks,

I have a basic newbie question: can somebody help me to understand how
exactly the boot environments created by 'pkg image-update' work?

Lets say I start with the BE 'mysystem'. My initial expectation -
obviously incorrect - was that performing the update would take a
snapshot (call it 'mysystem-1'), and create a corresponding BE, then
apply the relevant updates to the *currently active* BE. Then I would
immediately have access to updates that don't require a restart (new
application software versions etc.); I can reboot to get the new
kernel version, or I can reboot and choose the mysystem-1 BE if
anything went wrong.

In short, I was expecting the operation to be roughly equivalent to
snapshot creation, followed by 'apt-get dist-upgrade'.

That obviously isn't the case, but I can't find a clear explanation
anywhere of how the process actually works. From observation it
appears to be the following: a snapshot and corresponding BE are
created, and the update process is applied to that *new* BE. Thus
newly installed updates aren't available until rebooting into that new
BE. The current BE effectively acts as the 'backup' snapshot, so any
other changes to the system (applied to the running environment) not
only won't apply to the new BE, but are basically modifying the
backup. Hence, updating should be the *very last* thing to do before a
reboot, and rebooting ASAP after performing the update is *extremely*
important.

Is that understanding correct?

Assuming so, is it possible to make pkg behave more like my initial
expectation? I suppose I could create a snapshot myself using beadm,
then tell pkg not to create a new environment, but is that likely to
bite me in some nasty way? I'd like a better understanding of why the
system works the way it does before trying to fight it :P.

Thanks for your time.

(PS: Apologies if this list is inappropriate for basic questions like
this; let me know if that's the case.)


From jimklimov at cos.ru  Mon Jun 25 14:40:12 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Mon, 25 Jun 2012 18:40:12 +0400
Subject: [OpenIndiana-discuss] 'pkg image-update' and BEs
In-Reply-To: <CAHb+SPDN8=YPmX73t7fPrZ9BY6igwV72QZZUh3C9Ee9-h70cSg@mail.gmail.com>
References: <CAHb+SPDN8=YPmX73t7fPrZ9BY6igwV72QZZUh3C9Ee9-h70cSg@mail.gmail.com>
Message-ID: <4FE8784C.1000706@cos.ru>

2012-06-25 18:18, Aneurin Price wrote:> Hi folks,
 >
 > I have a basic newbie question: can somebody help me to understand how
 > exactly the boot environments created by 'pkg image-update' work?

Hello, I might make a few mistakes (and welcome corrections then),
but here's the way I see it (and in short - your understanding
matches mine):

There are some packages which are marked as requiring (suggesting)
creation of either a backup BE or a new BE; you can also enforce
or disable creation of these via "pkg(5)" command-line options.
There are also many packages which do not dictate creation of BEs
(backup or new) during their installation, leaving that to chance
(the user's choice and/or what other co-installed packages might
dictate).

Backup BEs are snapshots taken just before the installation, and
in my practice they seemed to stay snapshots (not directly easily
bootable - but you can make a ZFS clone filesystem based on the
snapshot, in order to boot into the backup BE). Modifications are
applied to the current BE; this is a mode for changes which are
not expected (by package authors or sysadmins) to cause troubles.

New BEs are just that - a snapshot is created of your current BE,
a clone is made from this snapshot, and the modifications are
applied to this clone. Your currently active BE remains intact,
and if you apply any changes to it (manually) after creating a
new cloned BE - these changes will be unseen in the new BE and
its descendants. As you say, in this case a reboot should be
scheduled and done soon, to avoid surprises.

I think that the "new BE" upgrade mode is more geared towards
lower-level upgrades, such as the kernel, drivers and system
tools; (re-)enabling many of these would either require a reboot
or equivalent shutdown of services and reloading of drivers at
least, and a fast-reboot is cleaner to test everything.

That said, if you're installing some userland application
software which wants a new BE but you know it doesn't really
require that, *I think* it is safe to optionally backup/clone
your current BE, and install the package into the current BE
requesting that a new one should not be made by pkg(5).


 > Lets say I start with the BE 'mysystem'. My initial expectation -
> obviously incorrect - was that performing the update would take a
> snapshot (call it 'mysystem-1'), and create a corresponding BE, then
> apply the relevant updates to the *currently active* BE. Then I would
> immediately have access to updates that don't require a restart (new
> application software versions etc.); I can reboot to get the new
> kernel version, or I can reboot and choose the mysystem-1 BE if
> anything went wrong.
>
> In short, I was expecting the operation to be roughly equivalent to
> snapshot creation, followed by 'apt-get dist-upgrade'.
>
> That obviously isn't the case, but I can't find a clear explanation
> anywhere of how the process actually works. From observation it
> appears to be the following: a snapshot and corresponding BE are
> created, and the update process is applied to that *new* BE. Thus
> newly installed updates aren't available until rebooting into that new
> BE. The current BE effectively acts as the 'backup' snapshot, so any
> other changes to the system (applied to the running environment) not
> only won't apply to the new BE, but are basically modifying the
> backup. Hence, updating should be the *very last* thing to do before a
> reboot, and rebooting ASAP after performing the update is *extremely*
> important.
>
> Is that understanding correct?
>
> Assuming so, is it possible to make pkg behave more like my initial
> expectation? I suppose I could create a snapshot myself using beadm,
> then tell pkg not to create a new environment, but is that likely to
> bite me in some nasty way? I'd like a better understanding of why the
> system works the way it does before trying to fight it :P.
>
> Thanks for your time.
>
> (PS: Apologies if this list is inappropriate for basic questions like
> this; let me know if that's the case.)

HTH,
//Jim Klimov



From michaelsprivate at gmail.com  Mon Jun 25 14:44:21 2012
From: michaelsprivate at gmail.com (Michael Schuster)
Date: Mon, 25 Jun 2012 16:44:21 +0200
Subject: [OpenIndiana-discuss] 'pkg image-update' and BEs
In-Reply-To: <CAHb+SPDN8=YPmX73t7fPrZ9BY6igwV72QZZUh3C9Ee9-h70cSg@mail.gmail.com>
References: <CAHb+SPDN8=YPmX73t7fPrZ9BY6igwV72QZZUh3C9Ee9-h70cSg@mail.gmail.com>
Message-ID: <CADqw_gJtZpKwFNtC8bQ+auLmgD3FTJan0uVjW9NY8gZErxNcTQ@mail.gmail.com>

Hi Aneurin,

I'd expect one of the design goals of the whole image-update process was to
work with as little interruption as possible (we had this in live upgrade
as well, so the historical precedent is fairly clear, IMO anyway): you
could run your update, watch it finish, analyse logs etc., all while the
machine (think "big server") was up and running *completely unchanged*.
Only when/if you're satisfied that the update did what you expected it to
do, you could (schedule a) reboot. IMO that's a much safer approach than
what you describe.

cheers
Michael

On Mon, Jun 25, 2012 at 4:18 PM, Aneurin Price <aneurin.price at gmail.com>wrote:

> Hi folks,
>
> I have a basic newbie question: can somebody help me to understand how
> exactly the boot environments created by 'pkg image-update' work?
>
> Lets say I start with the BE 'mysystem'. My initial expectation -
> obviously incorrect - was that performing the update would take a
> snapshot (call it 'mysystem-1'), and create a corresponding BE, then
> apply the relevant updates to the *currently active* BE. Then I would
> immediately have access to updates that don't require a restart (new
> application software versions etc.); I can reboot to get the new
> kernel version, or I can reboot and choose the mysystem-1 BE if
> anything went wrong.
>
> In short, I was expecting the operation to be roughly equivalent to
> snapshot creation, followed by 'apt-get dist-upgrade'.
>
> That obviously isn't the case, but I can't find a clear explanation
> anywhere of how the process actually works. From observation it
> appears to be the following: a snapshot and corresponding BE are
> created, and the update process is applied to that *new* BE. Thus
> newly installed updates aren't available until rebooting into that new
> BE. The current BE effectively acts as the 'backup' snapshot, so any
> other changes to the system (applied to the running environment) not
> only won't apply to the new BE, but are basically modifying the
> backup. Hence, updating should be the *very last* thing to do before a
> reboot, and rebooting ASAP after performing the update is *extremely*
> important.
>
> Is that understanding correct?
>
> Assuming so, is it possible to make pkg behave more like my initial
> expectation? I suppose I could create a snapshot myself using beadm,
> then tell pkg not to create a new environment, but is that likely to
> bite me in some nasty way? I'd like a better understanding of why the
> system works the way it does before trying to fight it :P.
>
> Thanks for your time.
>
> (PS: Apologies if this list is inappropriate for basic questions like
> this; let me know if that's the case.)
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
Michael Schuster
http://recursiveramblings.wordpress.com/

From aneurin.price at gmail.com  Mon Jun 25 15:24:31 2012
From: aneurin.price at gmail.com (Aneurin Price)
Date: Mon, 25 Jun 2012 16:24:31 +0100
Subject: [OpenIndiana-discuss] 'pkg image-update' and BEs
In-Reply-To: <CADqw_gJtZpKwFNtC8bQ+auLmgD3FTJan0uVjW9NY8gZErxNcTQ@mail.gmail.com>
References: <CAHb+SPDN8=YPmX73t7fPrZ9BY6igwV72QZZUh3C9Ee9-h70cSg@mail.gmail.com>
	<CADqw_gJtZpKwFNtC8bQ+auLmgD3FTJan0uVjW9NY8gZErxNcTQ@mail.gmail.com>
Message-ID: <CAHb+SPD+d=7etWHVce=g+ncn_UwKP93PVeX4oC3u0DppeED3Vg@mail.gmail.com>

On 25 June 2012 15:44, Michael Schuster <michaelsprivate at gmail.com> wrote:
> Hi Aneurin,
>
> I'd expect one of the design goals of the whole image-update process was to
> work with as little interruption as possible (we had this in live upgrade
> as well, so the historical precedent is fairly clear, IMO anyway): you
> could run your update, watch it finish, analyse logs etc., all while the
> machine (think "big server") was up and running *completely unchanged*.
> Only when/if you're satisfied that the update did what you expected it to
> do, you could (schedule a) reboot. IMO that's a much safer approach than
> what you describe.

Ah, that way of working is new to me, but it does make a lot of sense.

Thank you both for your quick replies - it seems a lot clearer now,
especially with the distinction between a backup BE and a new BE.


From michelle at msknight.com  Mon Jun 25 18:08:02 2012
From: michelle at msknight.com (michelle)
Date: Mon, 25 Jun 2012 19:08:02 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8059F.9040206@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
Message-ID: <4FE8A902.6000406@msknight.com>

OK - my back is up against the wall.

mich at jaguar:~# zpool status
   pool: data
  state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
         Sufficient replicas exist for the pool to continue functioning in a
         degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
         repaired.
   scan: scrub repaired 7.10M in 24h30m with 0 errors on Mon Jun 25 
18:30:48 2012
config:

         NAME        STATE     READ WRITE CKSUM
         data        DEGRADED     0     0     0
           raidz1-0  DEGRADED     0     0     0
             c2t2d0  ONLINE       0     0     0
             c2t3d0  FAULTED      0   102     0  too many errors
             c2t4d0  ONLINE       0     0     0

errors: No known data errors


The cables appear fine, so I'm dealing with either a controller issue, 
or a hard drive issue, I don't know how to interpret those earlier 
"messages" messages.

I need help please to make the right call, before I potentially loose 
4tb of files.




From udo.grabowski at kit.edu  Mon Jun 25 18:21:08 2012
From: udo.grabowski at kit.edu (Udo Grabowski (IMK))
Date: Mon, 25 Jun 2012 20:21:08 +0200
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8A902.6000406@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com>
Message-ID: <4FE8AC14.60609@kit.edu>

On 06/25/12 08:08 PM, michelle wrote:
> OK - my back is up against the wall.
>
> mich at jaguar:~# zpool status
>    pool: data
>   state: DEGRADED
> status: One or more devices are faulted in response to persistent errors.
>          Sufficient replicas exist for the pool to continue functioning
> in a
>          degraded state.
> action: Replace the faulted device, or use 'zpool clear' to mark the device
>          repaired.
>    scan: scrub repaired 7.10M in 24h30m with 0 errors on Mon Jun 25
> 18:30:48 2012
> config:
>
>          NAME        STATE     READ WRITE CKSUM
>          data        DEGRADED     0     0     0
>            raidz1-0  DEGRADED     0     0     0
>              c2t2d0  ONLINE       0     0     0
>              c2t3d0  FAULTED      0   102     0  too many errors
>              c2t4d0  ONLINE       0     0     0
>
> errors: No known data errors
>
>
> The cables appear fine, so I'm dealing with either a controller issue,
> or a hard drive issue, I don't know how to interpret those earlier
> "messages" messages.
>
> I need help please to make the right call, before I potentially loose
> 4tb of files.
>

Probably a failing drive - use fmdump -eV for the scsi errors,
the dev links in /dev/rdsk/c2t3d0 gives you the device path to look
for. Use iostat -Exn to get the Smart Errors for that drive,
/var/adm/messages probably has some details, fmadm faulty
messages will convince your support (if you have one) to replace
the drive.
-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026




From edwardlotus at gmail.com  Mon Jun 25 18:34:23 2012
From: edwardlotus at gmail.com (Edward M)
Date: Mon, 25 Jun 2012 11:34:23 -0700
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8A902.6000406@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com>
Message-ID: <4FE8AF2F.1090801@gmail.com>

On 06/25/2012 11:08 AM, michelle wrote:
> The cables appear fine, so I'm dealing with either a controller issue, 
> or a hard drive issue, I don't know how to interpret those earlier 
> "messages" messages. 

     Appers it is HD. Have you looked at this doc titled:

        Too many I/O errors on ZFS device

       reference:
       http://illumos.org/msg/ZFS-8000-FD

    in the action section mentions how to fix, hope it helps.:-)


From skiselkov.ml at gmail.com  Mon Jun 25 18:40:30 2012
From: skiselkov.ml at gmail.com (=?windows-1252?Q?Sa=9Ao_Kiselkov?=)
Date: Mon, 25 Jun 2012 20:40:30 +0200
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8A902.6000406@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com>
Message-ID: <4FE8B09E.6090403@gmail.com>

On 06/25/2012 08:08 PM, michelle wrote:
> OK - my back is up against the wall.
> 
> mich at jaguar:~# zpool status
>   pool: data
>  state: DEGRADED
> status: One or more devices are faulted in response to persistent errors.
>         Sufficient replicas exist for the pool to continue functioning in a
>         degraded state.
> action: Replace the faulted device, or use 'zpool clear' to mark the device
>         repaired.
>   scan: scrub repaired 7.10M in 24h30m with 0 errors on Mon Jun 25
> 18:30:48 2012
> config:
> 
>         NAME        STATE     READ WRITE CKSUM
>         data        DEGRADED     0     0     0
>           raidz1-0  DEGRADED     0     0     0
>             c2t2d0  ONLINE       0     0     0
>             c2t3d0  FAULTED      0   102     0  too many errors
>             c2t4d0  ONLINE       0     0     0
> 
> errors: No known data errors
> 
> 
> The cables appear fine, so I'm dealing with either a controller issue,
> or a hard drive issue, I don't know how to interpret those earlier
> "messages" messages.
> 
> I need help please to make the right call, before I potentially loose
> 4tb of files.

Have you tried running "iostat -En c2t3d0 1" and watching it while
placing load on the machine? I've had bad SAS cabling give me weird ZFS
behavior. Meanwhile, I went a hunt for all sorts of firmware issues, not
realizing it was the physical layer which bit me.

--
Saso


From michelle at msknight.com  Mon Jun 25 18:50:07 2012
From: michelle at msknight.com (michelle)
Date: Mon, 25 Jun 2012 19:50:07 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8B09E.6090403@gmail.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com> <4FE8B09E.6090403@gmail.com>
Message-ID: <4FE8B2DF.3070007@msknight.com>

Well, right now I can't do anything.

I asked it to unmount the data set and it said it was busy.

I checked all my client links and everything was closed, so I asked it 
to export again. It still said it was busy.

I decided to use -f and then it froze.

I logged in to another terminal session and issued an init 0, but the 
box just sits there and refuses to go down.


From michelle at msknight.com  Mon Jun 25 19:31:27 2012
From: michelle at msknight.com (michelle)
Date: Mon, 25 Jun 2012 20:31:27 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8B2DF.3070007@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com> <4FE8B09E.6090403@gmail.com>
	<4FE8B2DF.3070007@msknight.com>
Message-ID: <4FE8BC8F.4050600@msknight.com>

I did a hard reset and moved the drive to another channel.

The fault followed the drive so I'm certain it is the drive, as people 
have said.

The thing that bugs me is that this ZFS fault locked up the OS - and 
that's a real concern.

I think I'm going to need to have a hard think about my options and 
possibly leave OI for FreeNAS, Nexenta or Schillix.



From dswartz at druber.com  Mon Jun 25 19:34:05 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Mon, 25 Jun 2012 15:34:05 -0400
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8BC8F.4050600@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>	<4FE747B3.8060604@msknight.com>
	<4FE8059F.9040206@msknight.com>	<4FE8A902.6000406@msknight.com>
	<4FE8B09E.6090403@gmail.com>	<4FE8B2DF.3070007@msknight.com>
	<4FE8BC8F.4050600@msknight.com>
Message-ID: <4FE8BD2D.7070004@druber.com>

On 6/25/2012 3:31 PM, michelle wrote:
> I did a hard reset and moved the drive to another channel.
>
> The fault followed the drive so I'm certain it is the drive, as people 
> have said.
>
> The thing that bugs me is that this ZFS fault locked up the OS - and 
> that's a real concern.
>
> I think I'm going to need to have a hard think about my options and 
> possibly leave OI for FreeNAS, Nexenta or Schillix.

Given that Nexenta has the same underlying (basically) OS as OI, you may 
be in for a disappointment if you think this will help you.  Can't speak 
to Schillix.


From skiselkov.ml at gmail.com  Mon Jun 25 19:52:03 2012
From: skiselkov.ml at gmail.com (=?windows-1252?Q?Sa=9Ao_Kiselkov?=)
Date: Mon, 25 Jun 2012 21:52:03 +0200
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8BC8F.4050600@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com> <4FE8B09E.6090403@gmail.com>
	<4FE8B2DF.3070007@msknight.com> <4FE8BC8F.4050600@msknight.com>
Message-ID: <4FE8C163.907@gmail.com>

On 06/25/2012 09:31 PM, michelle wrote:
> I did a hard reset and moved the drive to another channel.
> 
> The fault followed the drive so I'm certain it is the drive, as people
> have said.

Then return it for warranty repairs or get a new one. SMART data should
help you get a clearer picture of exactly what's going on too.

> The thing that bugs me is that this ZFS fault locked up the OS - and
> that's a real concern.

You're obviously dealing with very bad hardware behaving in very
unpredictable ways. It is true that ZFS was built to run on inexpensive
hardware, however, the ways in which badly behaving controllers can
screw you over can far exceed ZFS' abilities to cope with that. Also,
"inexpensive" is a flexible term - SAS storage is inexpensive compared
to FC, but nowhere near "on-board SATA ports"-inexpensive.

It is likely that what you're seeing isn't so much the fault of ZFS
itself, but rather the SATA HBA not being able to cope with strange
device behavior (your logs actually tell that story) - don't make the
mistake of thinking all SATA chips can cope with hot-plug or weird bus
errors. Enterprise vendors, even with SATA hardware, test the various
failure modes and make sure things go down in at least a somewhat
predictable manner.

> I think I'm going to need to have a hard think about my options and
> possibly leave OI for FreeNAS, Nexenta or Schillix.

I can't speak for FreeNAS, but Nexenta and Schillix share practically
the same OS kernel underneath, so I don't think you'll get different
behavior from them. As I said, I think it was most probably caused your
on-board SATA HBA anyway, so no matter the OS, badly done hardware tends
to carry over into the software world.

--
Saso


From o.h.weiergraeber at fz-juelich.de  Mon Jun 25 20:11:51 2012
From: o.h.weiergraeber at fz-juelich.de (=?iso-8859-1?Q?=22Weiergr=E4ber=2C_Oliver_H=2E=22?=)
Date: Mon, 25 Jun 2012 20:11:51 +0000
Subject: [OpenIndiana-discuss] ACPI errors
In-Reply-To: <8ff0233656e279e6afc93795a5e5d968@xylab.cz>
References: <FF7867E8B89EAE4891E7A47C724A50910657B0@MBX2010-K01.ad.fz-juelich.de>
	<FF7867E8B89EAE4891E7A47C724A5091067376@MBX2010-K01.ad.fz-juelich.de>
	<CAD0Ztp1TPJMqXVw3s7v5x_3G4iNh4LB=oCjpgsE2SuiQk4DSLA@mail.gmail.com>,
	<4FE69670.6090600@gmail.com>
	<FF7867E8B89EAE4891E7A47C724A50910676AB@MBX2010-K01.ad.fz-juelich.de>,
	<8ff0233656e279e6afc93795a5e5d968@xylab.cz>
Message-ID: <FF7867E8B89EAE4891E7A47C724A509106785D@MBX2010-K01.ad.fz-juelich.de>

Sure, here we go:

(~): uname -a
SunOS mymachine 5.11 oi_151a4 i86pc i386 i86pc Solaris

(~): pkg publisher
PUBLISHER                             TYPE     STATUS   URI
openindiana.org                       origin   online   http://pkg.openindiana.org/dev/
opensolaris.org          (non-sticky, disabled) origin   online   http://pkg.openindiana.org/legacy/
sfe                                   origin   online   http://pkg.openindiana.org/sfe/
sfe-encumbered                        origin   online   http://pkg.openindiana.org/sfe-encumbered/

Hope this helps,
Oliver



________________________________________
From: Milan Jurik [milan.jurik at xylab.cz]
Sent: Monday, June 25, 2012 9:40 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] ACPI errors

Hi,

could you start system terminal and send output of:

uname -a

and

pkg publisher

to this list?

Best regards,

Milan

On 25.06.2012 09:17, Weiergr?ber, Oliver H. wrote:
> Thanks a lot for the quick replies. According to Update manager, my
> system is up to date,
> so it seems the latest fixes you mentioned did not make it (yet) into
> OpenIndiana.
> Is there a chance this will happen in the neat future?
>
> Best regards,
> Oliver
>
>
> ________________________________________
> From: Yuri Pankov [yuri.pankov at gmail.com]
> Sent: Sunday, June 24, 2012 6:24 AM
> To: openindiana-discuss
> Subject: Re: [OpenIndiana-discuss] ACPI errors
>
> On Sat, 23 Jun 2012 11:39:00 -0400, Gordon Ross wrote:
>> On Fri, Jun 22, 2012 at 10:01 AM, "Weiergr?ber, Oliver H."
>> <o.h.weiergraeber at fz-juelich.de> wrote:
>>> Hello,
>>>
>>> while testing OpenIndiana (and Solaris 11) on an HP xw8600
>>> workstation,
>>> I noticed messages like this occurring regularly during bootup:
>>>
>>>
>>> ----------------------------------------------------------------------------------------------------------------------------
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 879926 kern.notice]
>>> ACPI Error: [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS
>>> (20100915/dsfield-231)
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 804433 kern.notice]
>>> **** Exception AE_ALREADY_EXISTS during execution of method
>>> [\_SB_.PCI0._OSC] (Node ffffff02d59a8e80)
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 100000 kern.notice]
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 652514 kern.notice]
>>> Method Execution Stack:
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 489567 kern.notice]
>>> Method [_OSC] executing: CreateDWordField (CAPB, Local1, CAPD)
>> [...]
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 342246 kern.notice]
>>> ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node
>>> ffffff02d59a8e80), AE_ALREADY_EXISTS (20100915/psparse-632)
>>> May 17 21:13:48 mymachine.mydomain acpica: [ID 117524 kern.notice]
>>> ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS
>>> error
>>>
>>> ----------------------------------------------------------------------------------------------------------------------------
>>>
>>> What kind of ACPI problem is indicated here? Anything to worry
>>> about? I did notice stability issues on Solaris 11, but not on
>>> OpenIndiana, so I guess these are unrelated to the ACPI stuff.
>>> The BIOS version is the latest available for this machine.
>>>
>>> Thanks in advance
>>> Oliver
>>
>> When I was last working on an ACPI update (which I think is what's
>> currently in illumos and OI) Yuri Pankov was helping me test the
>> code,
>> and observed a problem on his HP laptop that looked something like
>> this, if I recall correctly.  He did some further experimenting and
>> found that he could make his laptop boot without the ACPI errors by
>> attaching the "EC" device a bit later.
>>
>> He showed me a possible fix, which I asked him to do some more work
>> on, but then he ran out of time or something.  Maybe you'd like to
>> pick up his changes and try them?
>
> ACPICA 20100915 isn't the latest version available at the moment (at
> least in illumos tree), which means that you are missing some fixes
> Gordon did. Please try upgrading your OpenIndiana installation first
> and
> check if it helps.
>
>


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Kennen Sie schon unseren neuen Film? http://www.fz-juelich.de/film
Kennen Sie schon unsere app? http://www.fz-juelich.de/app


From ray at arachelian.com  Mon Jun 25 21:06:07 2012
From: ray at arachelian.com (Ray Arachelian)
Date: Mon, 25 Jun 2012 17:06:07 -0400
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8BC8F.4050600@msknight.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com> <4FE8B09E.6090403@gmail.com>
	<4FE8B2DF.3070007@msknight.com> <4FE8BC8F.4050600@msknight.com>
Message-ID: <4FE8D2BF.3050607@arachelian.com>

On 06/25/2012 03:31 PM, michelle wrote:
> I did a hard reset and moved the drive to another channel.
>
> The fault followed the drive so I'm certain it is the drive, as people
> have said.
>
> The thing that bugs me is that this ZFS fault locked up the OS - and
> that's a real concern.
>
> I think I'm going to need to have a hard think about my options and
> possibly leave OI for FreeNAS, Nexenta or Schillix.
>

My guess is that since all the pools are by default set to have failmode
set to "wait" on failure, it'll wait forever.

Now, changing it to "continue" which will return an error, but it could
lead to worse behavior in some cases.  (You could set it to panic also,
but you'll like that far less.)



From me at cs.Stanford.EDU  Mon Jun 25 21:20:32 2012
From: me at cs.Stanford.EDU (Martin Frost)
Date: Mon, 25 Jun 2012 14:20:32 -0700
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8D2BF.3050607@arachelian.com> (message from Ray Arachelian on
	Mon, 25 Jun 2012 17:06:07 -0400)
Message-ID: <E1SjGi0-0005u1-G5@sunburn.Stanford.EDU>

 > Date: Mon, 25 Jun 2012 17:06:07 -0400
 > From: Ray Arachelian <ray at arachelian.com>
 > OpenPGP: id=E556D4A0
 > 
 > On 06/25/2012 03:31 PM, michelle wrote:
 > > I did a hard reset and moved the drive to another channel.
 > >
 > > The fault followed the drive so I'm certain it is the drive, as people
 > > have said.
 > >
 > > The thing that bugs me is that this ZFS fault locked up the OS - and
 > > that's a real concern.
 > >
 > > I think I'm going to need to have a hard think about my options and
 > > possibly leave OI for FreeNAS, Nexenta or Schillix.
 > >
 > 
 > My guess is that since all the pools are by default set to have failmode
 > set to "wait" on failure, it'll wait forever.
 > 
 > Now, changing it to "continue" which will return an error, but it could
 > lead to worse behavior in some cases.  (You could set it to panic also,
 > but you'll like that far less.)

Why should it return an error when no data has been lost yet, given
the redundancy (which is all that's lost so far)?

Martin


From maybird1776 at yahoo.com  Mon Jun 25 22:50:55 2012
From: maybird1776 at yahoo.com (ken mays)
Date: Mon, 25 Jun 2012 15:50:55 -0700 (PDT)
Subject: [OpenIndiana-discuss] openusb 1.1.6 update
In-Reply-To: <4FE8D2BF.3050607@arachelian.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com> <4FE8B09E.6090403@gmail.com>
	<4FE8B2DF.3070007@msknight.com> <4FE8BC8F.4050600@msknight.com>
	<4FE8D2BF.3050607@arachelian.com>
Message-ID: <1340664655.97323.YahooMailNeo@web111311.mail.gq1.yahoo.com>



Feel free to test the included 32-bit build of openusb 1.1.6 for oi_151a at:.

https://www.illumos.org/issues/2934

An update (or patch) may resolve a few reported issues bugs in USB io transfers.

The original openusb 1.0.1 userland port is maintained upstream. 

~ Ken Mays

From mike.laspina at laspina.ca  Tue Jun 26 00:12:30 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Mon, 25 Jun 2012 19:12:30 -0500
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8BC8F.4050600@msknight.com>
References: <4FE6BB5E.5030604@msknight.com><CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com><4FE747B3.8060604@msknight.com>
	<4FE8059F.9040206@msknight.com><4FE8A902.6000406@msknight.com>
	<4FE8B09E.6090403@gmail.com><4FE8B2DF.3070007@msknight.com>
	<4FE8BC8F.4050600@msknight.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D4713@MS1.laspina.ca>

I have observed the same SATA hard disk error wait behavior over many
operating systems. It's a SATA hardware issue. I have even observed it
on expensive high end storage servers. (HP, IBM, etc.) The SATA disk or
subsystem is trying to correct/recover errors, it should not and just
return the fault back to the caller (ZFS in this case). It can handle
the issue much more diplomatically and will correct the data fault
immediately. Don't blame ZFS, it is well designed, SATA on the other
hand is trying hard to do a bad thing.

-----Original Message-----
From: michelle [mailto:michelle at msknight.com] 
Sent: Monday, June 25, 2012 2:31 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Diagnosis help needed

I did a hard reset and moved the drive to another channel.

The fault followed the drive so I'm certain it is the drive, as people
have said.

The thing that bugs me is that this ZFS fault locked up the OS - and
that's a real concern.

I think I'm going to need to have a hard think about my options and
possibly leave OI for FreeNAS, Nexenta or Schillix.


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From richard.elling at richardelling.com  Tue Jun 26 00:19:45 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Mon, 25 Jun 2012 17:19:45 -0700
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE8D2BF.3050607@arachelian.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com> <4FE8B09E.6090403@gmail.com>
	<4FE8B2DF.3070007@msknight.com> <4FE8BC8F.4050600@msknight.com>
	<4FE8D2BF.3050607@arachelian.com>
Message-ID: <A6DD16B7-EB1B-4F20-90E2-77EC851C26E5@RichardElling.com>

On Jun 25, 2012, at 2:06 PM, Ray Arachelian wrote:

> On 06/25/2012 03:31 PM, michelle wrote:
>> I did a hard reset and moved the drive to another channel.
>> 
>> The fault followed the drive so I'm certain it is the drive, as people
>> have said.
>> 
>> The thing that bugs me is that this ZFS fault locked up the OS - and
>> that's a real concern.
>> 
>> I think I'm going to need to have a hard think about my options and
>> possibly leave OI for FreeNAS, Nexenta or Schillix.
>> 
> 
> My guess is that since all the pools are by default set to have failmode
> set to "wait" on failure, it'll wait forever.

I do not believe this is a case where failmode is used -- the pool state is 
not FAULTED.

In my experience, this is a case where the disk is there, accepting commands,
but not actually responding. Eventually, (by default for most Solaris-derivative)
after 60seconds * 3 retries, something else is attempted, that also fails. Also in
my experience, I see this on consumer-grade drives (qv TLER discussions). 
However, we can't know more until we see the "fmdump -eV" error log descriptive
output.
 -- richard

-- 

ZFS storage and performance consulting at http://www.RichardElling.com








From michelle at msknight.com  Tue Jun 26 00:34:24 2012
From: michelle at msknight.com (michelle)
Date: Tue, 26 Jun 2012 01:34:24 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <A6DD16B7-EB1B-4F20-90E2-77EC851C26E5@RichardElling.com>
References: <4FE6BB5E.5030604@msknight.com>
	<CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com>
	<4FE747B3.8060604@msknight.com> <4FE8059F.9040206@msknight.com>
	<4FE8A902.6000406@msknight.com> <4FE8B09E.6090403@gmail.com>
	<4FE8B2DF.3070007@msknight.com> <4FE8BC8F.4050600@msknight.com>
	<4FE8D2BF.3050607@arachelian.com>
	<A6DD16B7-EB1B-4F20-90E2-77EC851C26E5@RichardElling.com>
Message-ID: <4FE90390.9080103@msknight.com>

Apologies,

This went to an individual rather than back to the group.

----

Thanks for the response.

The thing that set of major alarms in my head is the fact that these 
errors caused OI to freeze up to the degree where it needed to be 
powered off. It would acknowledge the power switch instruction, but 
wouldn't power down.

Messages is full of ...

Jun 24 21:20:58 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: 
ahci port 3 has task file error
Jun 24 21:20:58 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery
Jun 24 21:20:58 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 21:21:00 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed

The fmdump gives loads of ...

Jun 25 2012 17:20:59.709529495 ereport.fs.zfs.probe_failure
nvlist version: 0
         class = ereport.fs.zfs.probe_failure
         ena = 0x9af81a688900c01
         detector = (embedded nvlist)
         nvlist version: 0
                 version = 0x0
                 scheme = zfs
                 pool = 0xb4f18a4cb65803ce
                 vdev = 0xe8c24676aa3c2a12
         (end detector)

         pool = data
         pool_guid = 0xb4f18a4cb65803ce
         pool_context = 0
         pool_failmode = wait
         vdev_guid = 0xe8c24676aa3c2a12
         vdev_type = disk
         vdev_path = /dev/dsk/c2t3d0s0
         vdev_devid = 
id1,sd at SATA_____WDC_WD20EARS-00M_____WD-WMAZA0555575/a
         parent_guid = 0x394c2bd12b4ffcfc
         parent_type = raidz
         prev_state = 0x0
         __ttl = 0x1
         __tod = 0x4fe88feb 0x2a4a8f97

iostat gives...

mich at jaguar:~# iostat -Exn
                     extended device statistics
     r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
     0.1    1.1    3.4    8.4  0.0  0.0    0.5    0.5   0   0 c2t0d0
     0.1    1.1    3.5    8.4  0.0  0.0    0.5    0.5   0   0 c2t1d0
   332.1    6.6 29970.5   65.3  0.1  2.6    0.2    7.7   2  39 c2t2d0
   261.3    6.6 23380.2   61.2  0.5  4.4    1.8   16.3   8  68 c2t3d0
   373.4    7.8 29970.7   65.2  0.1  2.9    0.3    7.6   2  47 c2t4d0
c2t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: INTEL SSDSA2M040 Revision: 02HB Serial No: 
CVGB949301PH040
Size: 40.02GB <40020664320 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 36 Predictive Failure Analysis: 0
c2t1d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: INTEL SSDSA2M040 Revision: 02HB Serial No: 
CVGB949301PC040
Size: 40.02GB <40019582464 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 35 Predictive Failure Analysis: 0
c2t2d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: ST32000542AS     Revision: CC34 Serial No: 
5XW17ARW
Size: 2000.40GB <2000398934016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 36 Predictive Failure Analysis: 0
c2t3d0           Soft Errors: 0 Hard Errors: 795 Transport Errors: 0
Vendor: ATA      Product: WDC WD20EARS-00M Revision: AB51 Serial No: 
WD-WMAZA0555575
Size: 2000.40GB <2000398934016 bytes>
Media Error: 370 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 70 Predictive Failure Analysis: 0
c2t4d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: WDC WD20EARS-00M Revision: AB51 Serial No: 
WD-WMAZA0484508
Size: 2000.40GB <2000398934016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 36 Predictive Failure Analysis: 0



From vishwasd at arkologic.com  Tue Jun 26 00:55:27 2012
From: vishwasd at arkologic.com (Vishwas Durai)
Date: Mon, 25 Jun 2012 17:55:27 -0700
Subject: [OpenIndiana-discuss] Options for a root filesystem
Message-ID: <4FE9087F.4010206@arkologic.com>

Hello all,
I'm wondering what options are available for root filesystem in OI? By 
default,  install  uses ZFS and creates a rpool. But If I'm a ZFS hacker 
and made some changes to some core structures, how does one go about 
debugging that? Is dropping to kmdb and debugging the only available 
(painful) option?
Any experience that you can share with this will be very helpful.
Thanks,
Vish.



From jsowoc at gmail.com  Tue Jun 26 01:00:19 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Mon, 25 Jun 2012 19:00:19 -0600
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <4FE9087F.4010206@arkologic.com>
References: <4FE9087F.4010206@arkologic.com>
Message-ID: <CADCwuEY3KNp9UjDLi+k3vU5A+gWQ-TdSWBjCkGzEmVcfie7Tjg@mail.gmail.com>

On Mon, Jun 25, 2012 at 6:55 PM, Vishwas Durai <vishwasd at arkologic.com> wrote:
> I'm wondering what options are available for root filesystem in OI? By
> default, ?install ?uses ZFS and creates a rpool.

I was about to say, "use UFS", but I found this:
http://openindiana.org/pipermail/openindiana-discuss/2011-June/004488.html

If the thread is correct, then your only option is ZFS. Sorry...

Jan


From gordon.w.ross at gmail.com  Tue Jun 26 02:37:44 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Mon, 25 Jun 2012 22:37:44 -0400
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <CADCwuEY3KNp9UjDLi+k3vU5A+gWQ-TdSWBjCkGzEmVcfie7Tjg@mail.gmail.com>
References: <4FE9087F.4010206@arkologic.com>
	<CADCwuEY3KNp9UjDLi+k3vU5A+gWQ-TdSWBjCkGzEmVcfie7Tjg@mail.gmail.com>
Message-ID: <CAD0Ztp2Hk1NP5mes0-pegdnA7O11hAiZwCogRLq9NwNrqUA-hQ@mail.gmail.com>

UFS root should still work, also NFS root (convenient for ZFS debug work:)

On Mon, Jun 25, 2012 at 9:00 PM, Jan Owoc <jsowoc at gmail.com> wrote:
> On Mon, Jun 25, 2012 at 6:55 PM, Vishwas Durai <vishwasd at arkologic.com> wrote:
>> I'm wondering what options are available for root filesystem in OI? By
>> default, ?install ?uses ZFS and creates a rpool.
>
> I was about to say, "use UFS", but I found this:
> http://openindiana.org/pipermail/openindiana-discuss/2011-June/004488.html
>
> If the thread is correct, then your only option is ZFS. Sorry...
>
> Jan
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss



-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From richard.elling at richardelling.com  Tue Jun 26 03:10:09 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Mon, 25 Jun 2012 20:10:09 -0700
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <CAD0Ztp2Hk1NP5mes0-pegdnA7O11hAiZwCogRLq9NwNrqUA-hQ@mail.gmail.com>
References: <4FE9087F.4010206@arkologic.com>
	<CADCwuEY3KNp9UjDLi+k3vU5A+gWQ-TdSWBjCkGzEmVcfie7Tjg@mail.gmail.com>
	<CAD0Ztp2Hk1NP5mes0-pegdnA7O11hAiZwCogRLq9NwNrqUA-hQ@mail.gmail.com>
Message-ID: <82F2252D-116D-43A6-B86F-43728276E1EA@RichardElling.com>

UFS root certainly works, but not sure if the OI installer makes it easy?
 -- richard

On Jun 25, 2012, at 7:37 PM, Gordon Ross wrote:

> UFS root should still work, also NFS root (convenient for ZFS debug work:)
> 
> On Mon, Jun 25, 2012 at 9:00 PM, Jan Owoc <jsowoc at gmail.com> wrote:
>> On Mon, Jun 25, 2012 at 6:55 PM, Vishwas Durai <vishwasd at arkologic.com> wrote:
>>> I'm wondering what options are available for root filesystem in OI? By
>>> default,  install  uses ZFS and creates a rpool.
>> 
>> I was about to say, "use UFS", but I found this:
>> http://openindiana.org/pipermail/openindiana-discuss/2011-June/004488.html
>> 
>> If the thread is correct, then your only option is ZFS. Sorry...
>> 
>> Jan
>> 
>> _______________________________________________
>> OpenIndiana-discuss mailing list
>> OpenIndiana-discuss at openindiana.org
>> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> 
> 
> -- 
> Gordon Ross <gwr at nexenta.com>
> Nexenta Systems, Inc.  www.nexenta.com
> Enterprise class storage for everyone
> 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

-- 

ZFS storage and performance consulting at http://www.RichardElling.com








From richlowe at richlowe.net  Tue Jun 26 03:12:37 2012
From: richlowe at richlowe.net (Richard Lowe)
Date: Mon, 25 Jun 2012 23:12:37 -0400
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <CAD0Ztp2Hk1NP5mes0-pegdnA7O11hAiZwCogRLq9NwNrqUA-hQ@mail.gmail.com>
References: <4FE9087F.4010206@arkologic.com>
	<CADCwuEY3KNp9UjDLi+k3vU5A+gWQ-TdSWBjCkGzEmVcfie7Tjg@mail.gmail.com>
	<CAD0Ztp2Hk1NP5mes0-pegdnA7O11hAiZwCogRLq9NwNrqUA-hQ@mail.gmail.com>
Message-ID: <CAA7J0x_C=Pz8vScBrHz80+6qB-+mK1tBXGvDt-opmZEg5Fz8pg@mail.gmail.com>

On Mon, Jun 25, 2012 at 10:37 PM, Gordon Ross <gordon.w.ross at gmail.com> wrote:
> UFS root should still work, also NFS root (convenient for ZFS debug work:)
>

As concepts within illumos, yes.

With the full OI distribution, doubtful.

-- Rich


From gordon.w.ross at gmail.com  Tue Jun 26 03:20:40 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Mon, 25 Jun 2012 23:20:40 -0400
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <CAA7J0x_C=Pz8vScBrHz80+6qB-+mK1tBXGvDt-opmZEg5Fz8pg@mail.gmail.com>
References: <4FE9087F.4010206@arkologic.com>
	<CADCwuEY3KNp9UjDLi+k3vU5A+gWQ-TdSWBjCkGzEmVcfie7Tjg@mail.gmail.com>
	<CAD0Ztp2Hk1NP5mes0-pegdnA7O11hAiZwCogRLq9NwNrqUA-hQ@mail.gmail.com>
	<CAA7J0x_C=Pz8vScBrHz80+6qB-+mK1tBXGvDt-opmZEg5Fz8pg@mail.gmail.com>
Message-ID: <CAD0Ztp1N3fHst0gsp9pr5b32RHrBZ7b-zSptC_0v0LF=tDUU+g@mail.gmail.com>

On Mon, Jun 25, 2012 at 11:12 PM, Richard Lowe <richlowe at richlowe.net> wrote:
> On Mon, Jun 25, 2012 at 10:37 PM, Gordon Ross <gordon.w.ross at gmail.com> wrote:
>> UFS root should still work, also NFS root (convenient for ZFS debug work:)
>>
>
> As concepts within illumos, yes.
>
> With the full OI distribution, doubtful.
>
> -- Rich

Last I looked, the install CD (or image for a USB stick) is a UFS image.
It's not hard to set that up for PXE boot over the net, with NFS root.
(We used to do that regularly for network installs in the lab.)

-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From mike.laspina at laspina.ca  Tue Jun 26 04:36:41 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Mon, 25 Jun 2012 23:36:41 -0500
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <4FE90390.9080103@msknight.com>
References: <4FE6BB5E.5030604@msknight.com><CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com><4FE747B3.8060604@msknight.com>
	<4FE8059F.9040206@msknight.com><4FE8A902.6000406@msknight.com>
	<4FE8B09E.6090403@gmail.com><4FE8B2DF.3070007@msknight.com>
	<4FE8BC8F.4050600@msknight.com><4FE8D2BF.3050607@arachelian.com><A6DD16B7-EB1B-4F20-90E2-77EC851C26E5@RichardElling.com>
	<4FE90390.9080103@msknight.com>
Message-ID: <8F607366E3C0F9499212649291E0BD640D4714@MS1.laspina.ca>

The error reported task_file_status = 0x4041 on port 3 is a result of an
ATA response where the PxIS.TFES bit was set. The ahci driver must do a
port reset at that point. The SATA disk failed to perform an operation
and reported it. I suspect this is not a data error and may be more on
the lines of a firmware fault on the SATA controller. So it may well be
a faulty disk in the most unruly way, that is conditional e.g. could be
anything around or on the ATA chain, a bad cable, running to hot,
interference, mobo firmware ... etc.    

-----Original Message-----
From: michelle [mailto:michelle at msknight.com] 
Sent: Monday, June 25, 2012 7:34 PM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Diagnosis help needed

Apologies,

This went to an individual rather than back to the group.

----

Thanks for the response.

The thing that set of major alarms in my head is the fact that these
errors caused OI to freeze up to the degree where it needed to be
powered off. It would acknowledge the power switch instruction, but
wouldn't power down.

Messages is full of ...

Jun 24 21:20:58 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0: 
ahci port 3 has task file error
Jun 24 21:20:58 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0: 
ahci port 3 is trying to do error recovery Jun 24 21:20:58 jaguar ahci:
[ID 693748 kern.warning] WARNING: ahci0: 
ahci port 3 task_file_status = 0x4041
Jun 24 21:21:00 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0: 
error recovery for port 3 succeed

The fmdump gives loads of ...

Jun 25 2012 17:20:59.709529495 ereport.fs.zfs.probe_failure nvlist
version: 0
         class = ereport.fs.zfs.probe_failure
         ena = 0x9af81a688900c01
         detector = (embedded nvlist)
         nvlist version: 0
                 version = 0x0
                 scheme = zfs
                 pool = 0xb4f18a4cb65803ce
                 vdev = 0xe8c24676aa3c2a12
         (end detector)

         pool = data
         pool_guid = 0xb4f18a4cb65803ce
         pool_context = 0
         pool_failmode = wait
         vdev_guid = 0xe8c24676aa3c2a12
         vdev_type = disk
         vdev_path = /dev/dsk/c2t3d0s0
         vdev_devid =
id1,sd at SATA_____WDC_WD20EARS-00M_____WD-WMAZA0555575/a
         parent_guid = 0x394c2bd12b4ffcfc
         parent_type = raidz
         prev_state = 0x0
         __ttl = 0x1
         __tod = 0x4fe88feb 0x2a4a8f97

iostat gives...

mich at jaguar:~# iostat -Exn
                     extended device statistics
     r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
     0.1    1.1    3.4    8.4  0.0  0.0    0.5    0.5   0   0 c2t0d0
     0.1    1.1    3.5    8.4  0.0  0.0    0.5    0.5   0   0 c2t1d0
   332.1    6.6 29970.5   65.3  0.1  2.6    0.2    7.7   2  39 c2t2d0
   261.3    6.6 23380.2   61.2  0.5  4.4    1.8   16.3   8  68 c2t3d0
   373.4    7.8 29970.7   65.2  0.1  2.9    0.3    7.6   2  47 c2t4d0
c2t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: INTEL SSDSA2M040 Revision: 02HB Serial No: 
CVGB949301PH040
Size: 40.02GB <40020664320 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal
Request: 36 Predictive Failure Analysis: 0
c2t1d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: INTEL SSDSA2M040 Revision: 02HB Serial No: 
CVGB949301PC040
Size: 40.02GB <40019582464 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal
Request: 35 Predictive Failure Analysis: 0
c2t2d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: ST32000542AS     Revision: CC34 Serial No: 
5XW17ARW
Size: 2000.40GB <2000398934016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal
Request: 36 Predictive Failure Analysis: 0
c2t3d0           Soft Errors: 0 Hard Errors: 795 Transport Errors: 0
Vendor: ATA      Product: WDC WD20EARS-00M Revision: AB51 Serial No: 
WD-WMAZA0555575
Size: 2000.40GB <2000398934016 bytes>
Media Error: 370 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal
Request: 70 Predictive Failure Analysis: 0
c2t4d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: WDC WD20EARS-00M Revision: AB51 Serial No: 
WD-WMAZA0484508
Size: 2000.40GB <2000398934016 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal
Request: 36 Predictive Failure Analysis: 0


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From michelle at msknight.com  Tue Jun 26 06:52:14 2012
From: michelle at msknight.com (michelle)
Date: Tue, 26 Jun 2012 07:52:14 +0100
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <8F607366E3C0F9499212649291E0BD640D4714@MS1.laspina.ca>
References: <4FE6BB5E.5030604@msknight.com><CADCwuEZz_YnL94s7cej73CsSmGUEKOwDU4_kT9aao7Fj5+zm+A@mail.gmail.com><4FE747B3.8060604@msknight.com>
	<4FE8059F.9040206@msknight.com><4FE8A902.6000406@msknight.com>
	<4FE8B09E.6090403@gmail.com><4FE8B2DF.3070007@msknight.com>
	<4FE8BC8F.4050600@msknight.com><4FE8D2BF.3050607@arachelian.com><A6DD16B7-EB1B-4F20-90E2-77EC851C26E5@RichardElling.com>
	<4FE90390.9080103@msknight.com>
	<8F607366E3C0F9499212649291E0BD640D4714@MS1.laspina.ca>
Message-ID: <4FE95C1E.8020703@msknight.com>

Many thanks to all.

I now have a better understanding of what is happening, why OI locked up 
in the way it did, and that with the exception of FreeNAS (ZFS 15) and 
NAS4Free, (claiming ZFS 28) it will be the same thing with Schillix and 
NexcentaStor.

I've sold some of my possessions in order to buy the remaining 3tb 
drives I need so while they take time to come, I'll try and get a 
machine and try out NAS4Free as the web based control system looks nice 
and central, while there is still CLI.

Thanks once again; now I have the information I need to make some solid 
decisions.


From ray at arachelian.com  Tue Jun 26 10:54:44 2012
From: ray at arachelian.com (Ray Arachelian)
Date: Tue, 26 Jun 2012 06:54:44 -0400
Subject: [OpenIndiana-discuss] Diagnosis help needed
In-Reply-To: <E1SjGi0-0005u1-G5@sunburn.Stanford.EDU>
References: <E1SjGi0-0005u1-G5@sunburn.Stanford.EDU>
Message-ID: <4FE994F4.3050109@arachelian.com>

On 06/25/2012 05:20 PM, Martin Frost wrote:
>  > My guess is that since all the pools are by default set to have failmode
>  > set to "wait" on failure, it'll wait forever.
>  > 
>  > Now, changing it to "continue" which will return an error, but it could
>  > lead to worse behavior in some cases.  (You could set it to panic also,
>  > but you'll like that far less.)
>
> Why should it return an error when no data has been lost yet, given
> the redundancy (which is all that's lost so far)?
>

Exactly my point:  In some cases, such as this, you want it to wait, in
others, where there's no chance of it ever coming back, you don't.



From ma2412 at gmx.de  Tue Jun 26 12:44:19 2012
From: ma2412 at gmx.de (Armin Maier)
Date: Tue, 26 Jun 2012 14:44:19 +0200
Subject: [OpenIndiana-discuss] Problem/Question on mount lofs:
Message-ID: <4FE9AEA3.6060306@gmx.de>

Hello anybody!
I've got a problem centraly sharing ZFS filesystems.
What i want is to create zfs filesystems for different Usergroups and i 
want to share them in a central location.

The idea was to create a "/mountbase" directory and share it with 
"sharemgr" (this is working and i can access the share from my Windows 7 
machine "\\openindiana\zfs$" )
Mount the zfs Filesystems do directories within the "/mountbase" directory:

mkdir /mountbase/zfsfilesys1
mount -F lofs /zfspool/zfsfilesys1 /mountbase/zfsfilesys1

If i browse to the "/mountbase/zfsfilesys1" directory on the console i 
can see all the Contents and everything is fine, but when i open the 
share "\\openindiana\zfs$" i do net see any directories. If i unmount 
the "/mountbase/zfsfilesys1" Directory it appears on the Windows computer.
Does someone know why this happens? Is there a "smbserver" setting which 
has to be set? I do not use samba for sharing, i am using the Solaris 
smb service "svc:/network/smb/server:default".


From udo.grabowski at kit.edu  Tue Jun 26 12:52:17 2012
From: udo.grabowski at kit.edu (Udo Grabowski (IMK))
Date: Tue, 26 Jun 2012 14:52:17 +0200
Subject: [OpenIndiana-discuss] Problem/Question on mount lofs:
In-Reply-To: <4FE9AEA3.6060306@gmx.de>
References: <4FE9AEA3.6060306@gmx.de>
Message-ID: <4FE9B081.3030500@kit.edu>

Simply use the mountpoint property of the zfs filesystem to set
the mountpoint to /mountbase/zfsfilesys1, then set the sharenfs
or sharesmb property of the filesystem to export them. You may
also look at the casesensitivity property for the smb shares.

There's no need to use the sharemgr for this simple scenario.

On 26/06/2012 14:44, Armin Maier wrote:
> Hello anybody!
> I've got a problem centraly sharing ZFS filesystems.
> What i want is to create zfs filesystems for different Usergroups and i want to
> share them in a central location.
>
> The idea was to create a "/mountbase" directory and share it with "sharemgr"
> (this is working and i can access the share from my Windows 7 machine
> "\\openindiana\zfs$" )
> Mount the zfs Filesystems do directories within the "/mountbase" directory:
>
> mkdir /mountbase/zfsfilesys1
> mount -F lofs /zfspool/zfsfilesys1 /mountbase/zfsfilesys1
>
> If i browse to the "/mountbase/zfsfilesys1" directory on the console i can see
> all the Contents and everything is fine, but when i open the share
> "\\openindiana\zfs$" i do net see any directories. If i unmount the
> "/mountbase/zfsfilesys1" Directory it appears on the Windows computer.
> Does someone know why this happens? Is there a "smbserver" setting which has to
> be set? I do not use samba for sharing, i am using the Solaris smb service
> "svc:/network/smb/server:default".

-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026


From roy at karlsbakk.net  Tue Jun 26 13:01:58 2012
From: roy at karlsbakk.net (Roy Sigurd Karlsbakk)
Date: Tue, 26 Jun 2012 15:01:58 +0200 (CEST)
Subject: [OpenIndiana-discuss] Garrett D'Amore on using SATA drives in a SAS
	system
Message-ID: <13852970.4.1340715718558.JavaMail.root@zimbra>

Hi all

Seems Garrett D'Amore from Nexenta has a few things to say about using SATA drives in SAS systems

http://gdamore.blogspot.no/2010/08/why-sas-sata-is-not-such-great-idea.html

The digest is "Just don't do it"?

Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy at karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et element?rt imperativ for alle pedagoger ? unng? eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer p? norsk.


From ma2412 at gmx.de  Tue Jun 26 13:24:28 2012
From: ma2412 at gmx.de (Armin Maier)
Date: Tue, 26 Jun 2012 15:24:28 +0200
Subject: [OpenIndiana-discuss] [!! SPAM] Re: Problem/Question on mount
 lofs:
In-Reply-To: <4FE9B081.3030500@kit.edu>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
Message-ID: <4FE9B80C.9090002@gmx.de>

Hello Udo, i know that mountpoints can be changed and sharing is 
possible for a zfs filesystem, but that is not what i want, in your 
scenario there is a share for each filesystem, i want to have 1 share on 
the server trough wich i can see and browse all zfs filesystems.
Please correct me if i have missunderstood something of your answer.
The more, i tried to mount the filesystem unter "/mountbase":

zfs umount /zfspool/zfsfilesys1
mkdir /mountbase/zfsfilesys1
zfs set mountpoint=/mountbase/zfsfilesys1  /zfspool/zfsfilesys1
zfs mount /zfspool/zfsfilesys1

That worked, but i still cannot access the "zfsfilesys1" folder over the 
network, the folder disappeares after running "zfs mount" command, 
before that command i can see the folder over the network. (/mountbase 
is still shared by sharemgr).




From dswartz at druber.com  Tue Jun 26 13:29:31 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Tue, 26 Jun 2012 09:29:31 -0400
Subject: [OpenIndiana-discuss] Garrett D'Amore on using SATA drives in a
	SASsystem
In-Reply-To: <13852970.4.1340715718558.JavaMail.root@zimbra>
References: <13852970.4.1340715718558.JavaMail.root@zimbra>
Message-ID: <E94E52B28ADF4D7B8AEE060A23E4DCC1@manticore>

Keep in mind this is almost 2 yrs old, though.  I seem to recall a thread
here or there that has pinned the SATA toxicity issues to an mpt driver bug
or somesuch?

-----Original Message-----
From: Roy Sigurd Karlsbakk [mailto:roy at karlsbakk.net] 
Sent: Tuesday, June 26, 2012 9:02 AM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] Garrett D'Amore on using SATA drives in a
SASsystem

Hi all

Seems Garrett D'Amore from Nexenta has a few things to say about using SATA
drives in SAS systems

http://gdamore.blogspot.no/2010/08/why-sas-sata-is-not-such-great-idea.html

The digest is "Just don't do it"


Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy at karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det
er et element?rt imperativ for alle pedagoger ? unng? eksessiv anvendelse av
idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og
relevante synonymer p? norsk.

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss



From udo.grabowski at kit.edu  Tue Jun 26 13:30:15 2012
From: udo.grabowski at kit.edu (Udo Grabowski (IMK))
Date: Tue, 26 Jun 2012 15:30:15 +0200
Subject: [OpenIndiana-discuss] [!! SPAM] Re: Problem/Question on mount
 lofs:
In-Reply-To: <4FE9B80C.9090002@gmx.de>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
	<4FE9B80C.9090002@gmx.de>
Message-ID: <4FE9B967.3020300@kit.edu>

On 26/06/2012 15:24, Armin Maier wrote:
> zfs umount /zfspool/zfsfilesys1
> mkdir /mountbase/zfsfilesys1
> zfs set mountpoint=/mountbase/zfsfilesys1 /zfspool/zfsfilesys1
> zfs mount /zfspool/zfsfilesys1
>
> That worked, but i still cannot access the "zfsfilesys1" folder over the
> network, the folder disappeares after running "zfs mount" command, before that
> command i can see the folder over the network. (/mountbase is still shared by
> sharemgr).

zfs set mountpoint= already mounts, no need to mount it separately
(if the canmount property is set to on).
-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026


From udo.grabowski at kit.edu  Tue Jun 26 13:32:10 2012
From: udo.grabowski at kit.edu (Udo Grabowski (IMK))
Date: Tue, 26 Jun 2012 15:32:10 +0200
Subject: [OpenIndiana-discuss] [!! SPAM] Re: Problem/Question on mount
 lofs:
In-Reply-To: <4FE9B80C.9090002@gmx.de>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
	<4FE9B80C.9090002@gmx.de>
Message-ID: <4FE9B9DA.6080505@kit.edu>

On 26/06/2012 15:24, Armin Maier wrote:

> zfs umount /zfspool/zfsfilesys1
> mkdir /mountbase/zfsfilesys1
> zfs set mountpoint=/mountbase/zfsfilesys1 /zfspool/zfsfilesys1
> zfs mount /zfspool/zfsfilesys1
>
And no need to mkdir  /mountbase/zfsfilesys1, this is also managed
by zfs set mountpoint=
-- 
Dr.Udo Grabowski    Inst.f.Meteorology a.Climate Research IMK-ASF-SAT
www-imk.fzk.de/asf/sat/grabowski/ www.imk-asf.kit.edu/english/sat.php
KIT - Karlsruhe Institute of Technology            http://www.kit.edu
Postfach 3640,76021 Karlsruhe,Germany  T:(+49)721 608-26026 F:-926026


From juzhenliang at gmail.com  Tue Jun 26 16:23:01 2012
From: juzhenliang at gmail.com (=?GB2312?B?V2FyR3JleVvVvba3sanB+l0=?=)
Date: Wed, 27 Jun 2012 00:23:01 +0800
Subject: [OpenIndiana-discuss] IP-dedicated zone (OI b151a4) is not
	ping-able in virtualbox
Message-ID: <CAFp0D57bK74os2NeHGVuwDbFnEWGMEMJJ4jc+6AFTxHkNG2vgw@mail.gmail.com>

Hi, all.

I installed OpenIndiana b151 in virtualbox on MacOSX, there is a zone with
dedicated ip over e1000g1 which connecting to a host-only virtual NIC.
Everything was okay before updating to b151a4. I could access it
everywhere, host OS, global zone, or any other VMs whose NICs are in the
same virtual network.

However, when updating to b151a4, it is not ping-able outside the box,
unless following command is running in the global zone:
tcpdump -i e1000g1.

Since the PCnet-fast virtual network card is not usable in OpenIndiana
b151a4 (It seems that something is not recognized),
I have changed the VNIC hardware to Intel Pro/1000 MT one.

Thanks for helping me solve this problem, or more information needed?

From richard.elling at richardelling.com  Tue Jun 26 17:15:25 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Tue, 26 Jun 2012 10:15:25 -0700
Subject: [OpenIndiana-discuss] Garrett D'Amore on using SATA drives in a
	SASsystem
In-Reply-To: <E94E52B28ADF4D7B8AEE060A23E4DCC1@manticore>
References: <13852970.4.1340715718558.JavaMail.root@zimbra>
	<E94E52B28ADF4D7B8AEE060A23E4DCC1@manticore>
Message-ID: <9810920F-D934-41AE-A9AF-50EC8DFF114E@RichardElling.com>

On Jun 26, 2012, at 6:29 AM, Dan Swartzendruber wrote:

> Keep in mind this is almost 2 yrs old, though.  I seem to recall a thread
> here or there that has pinned the SATA toxicity issues to an mpt driver bug
> or somesuch?

Not really. Search for other OSes and their tales of woe. In some cases, a
bad SATA drive can make the machine fail at POST, well before an OS is 
loaded.

Best results for SATA is direct-connect: no expanders, no extenders.
Next best is SATA with a good-quality SATA/SAS interposer.
Known to be a poor mix: both SATA and SAS devices sharing an expander.

NB, we have seen changes in HBA, expander, and disk firmware all contribute
to happiness or sadness when SATA devices are used in SAS fabrics (STP).
At one time, we tried to keep a list of combinations known for happiness, but
maintaining that list proved to be impractical, due to the constant churn and
unavailability of disk firmware patches from various vendors. Also, do not assume
that you will be able to get a firmware upgrade, even if it exists :-(
 -- richard

-- 

ZFS storage and performance consulting at http://www.RichardElling.com








From dswartz at druber.com  Tue Jun 26 17:36:55 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Tue, 26 Jun 2012 13:36:55 -0400
Subject: [OpenIndiana-discuss] Garrett D'Amore on using SATA drives in
 a	SASsystem
In-Reply-To: <9810920F-D934-41AE-A9AF-50EC8DFF114E@RichardElling.com>
References: <13852970.4.1340715718558.JavaMail.root@zimbra>	<E94E52B28ADF4D7B8AEE060A23E4DCC1@manticore>
	<9810920F-D934-41AE-A9AF-50EC8DFF114E@RichardElling.com>
Message-ID: <4FE9F337.80607@druber.com>

On 6/26/2012 1:15 PM, Richard Elling wrote:
> On Jun 26, 2012, at 6:29 AM, Dan Swartzendruber wrote:
>
>    
>> Keep in mind this is almost 2 yrs old, though.  I seem to recall a thread
>> here or there that has pinned the SATA toxicity issues to an mpt driver bug
>> or somesuch?
>>      
> Not really. Search for other OSes and their tales of woe. In some cases, a
> bad SATA drive can make the machine fail at POST, well before an OS is
> loaded.
>
> Best results for SATA is direct-connect: no expanders, no extenders.
> Next best is SATA with a good-quality SATA/SAS interposer.
> Known to be a poor mix: both SATA and SAS devices sharing an expander.
>
> NB, we have seen changes in HBA, expander, and disk firmware all contribute
> to happiness or sadness when SATA devices are used in SAS fabrics (STP).
> At one time, we tried to keep a list of combinations known for happiness, but
> maintaining that list proved to be impractical, due to the constant churn and
> unavailability of disk firmware patches from various vendors. Also, do not assume
> that you will be able to get a firmware upgrade, even if it exists :-(
>   -- richard
>
>    
To clarify: on hardocp a few months back, there was a discussion on this 
whole issue and there was a cryptic reference to Oracle having 
supposedly root-caused a software/driver bug that was causing a specific 
problem.  I wish I could remember anything more specific than that...


From jimklimov at cos.ru  Tue Jun 26 17:38:26 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 26 Jun 2012 21:38:26 +0400
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <4FE9087F.4010206@arkologic.com>
References: <4FE9087F.4010206@arkologic.com>
Message-ID: <4FE9F392.1010504@cos.ru>

2012-06-26 4:55, Vishwas Durai ?????:
> Hello all,
> I'm wondering what options are available for root filesystem in OI? By
> default,  install  uses ZFS and creates a rpool. But If I'm a ZFS hacker
> and made some changes to some core structures, how does one go about
> debugging that? Is dropping to kmdb and debugging the only available
> (painful) option?
> Any experience that you can share with this will be very helpful.

As I understand, you want your OS stability to be independent
from ZFS stability and code - so you want to use a different
booting method?

I am not sure if booting from UFS is still supported, but it
seems unlikely that anyone would take time to carve it out
either. So you can try creating a separate slice with a UFS
root filesystem in it. You likely won't have working beadm
and backup/alternate BEs in this case, though.

Alternately, you might create LiveUSB images and flash a boot
disk with your alternate ZFS code (see Distro Constructor),
it may also be possible to avoid USB drives and just re-image
a physical partition on your hard disk. This would likely
work faster and avoid surprises of flash write-wearing.

Finally, you can do these experiments in a VM so as to not
corrupt your physical workstation ;)

HTH,
//Jim Klimov


From jimklimov at cos.ru  Tue Jun 26 17:53:34 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 26 Jun 2012 21:53:34 +0400
Subject: [OpenIndiana-discuss] Problem/Question on mount lofs:
In-Reply-To: <4FE9B081.3030500@kit.edu>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
Message-ID: <4FE9F71E.6040205@cos.ru>

> On 26/06/2012 14:44, Armin Maier wrote:
>> Hello anybody!
>> I've got a problem centraly sharing ZFS filesystems.
>> What i want is to create zfs filesystems for different Usergroups and
>> i want to
>> share them in a central location.
>>
>> The idea was to create a "/mountbase" directory and share it with
>> "sharemgr"
>> (this is working and i can access the share from my Windows 7 machine
>> "\\openindiana\zfs$" )
>> Mount the zfs Filesystems do directories within the "/mountbase"
>> directory:
>>
>> mkdir /mountbase/zfsfilesys1
>> mount -F lofs /zfspool/zfsfilesys1 /mountbase/zfsfilesys1
>>
>> If i browse to the "/mountbase/zfsfilesys1" directory on the console i
>> can see
>> all the Contents and everything is fine, but when i open the share
>> "\\openindiana\zfs$" i do net see any directories. If i unmount the
>> "/mountbase/zfsfilesys1" Directory it appears on the Windows computer.
>> Does someone know why this happens? Is there a "smbserver" setting
>> which has to
>> be set? I do not use samba for sharing, i am using the Solaris smb
>> service
>> "svc:/network/smb/server:default".

AFAIK the Solaris kernel CIFS server, which is also used in OI,
does not allow sharing ZFS dataset hierarchies as a single
mountpoint (like you can do with NFS), and the CIFS clients
don't have a means to detect a nested mountpoint and call a
new mount operation for the nested datasets. I am not sure why,
maybe it is a protocol limitation, or a certain vendor's popular
client capability limitation.

SAMBA works around this problem by maintaining its own VFS layer
to map CIFS URLs to local filesystem IDs and inodes within these
filesystems (note that your nested datasets can have identical
inode numbers used to reference unrelated files stored within
these datasets). ZFS and Kernel CIFS/NFS servers don't do that -
they share each FS independently, and have no internal need for
such VFS mappings. That's what I've heard and read...

I might suggest that you do use SAMBA instead for this quest,
or that you try to set up a DFS (Distributed FileSystem) server
which actually serves mountpoint references - I heard rumors
that this can help combine several servers' CIFS shares into
something that looks like a single share for Windows clients.
A DFS server can be made as part of Windows Server for a long
time (Win2000 at least), and I think SAMBA can do that too.

HTH,
//Jim Klimov



From openindiana at tenzer.dk  Tue Jun 26 18:04:51 2012
From: openindiana at tenzer.dk (Jeppe Toustrup)
Date: Tue, 26 Jun 2012 20:04:51 +0200
Subject: [OpenIndiana-discuss] IP-dedicated zone (OI b151a4) is not
 ping-able in virtualbox
In-Reply-To: <CAFp0D57bK74os2NeHGVuwDbFnEWGMEMJJ4jc+6AFTxHkNG2vgw@mail.gmail.com>
References: <CAFp0D57bK74os2NeHGVuwDbFnEWGMEMJJ4jc+6AFTxHkNG2vgw@mail.gmail.com>
Message-ID: <CAJ9NRxVV4ZKE5VTrP2MJ7FQSpnBHeYazEu6JAZThBL7DcSUOkQ@mail.gmail.com>

On Tue, Jun 26, 2012 at 6:23 PM, WarGrey[????] <juzhenliang at gmail.com> wrote:
> I installed OpenIndiana b151 in virtualbox on MacOSX, there is a zone with
> dedicated ip over e1000g1 which connecting to a host-only virtual NIC.
> Everything was okay before updating to b151a4. I could access it
> everywhere, host OS, global zone, or any other VMs whose NICs are in the
> same virtual network.
>
> However, when updating to b151a4, it is not ping-able outside the box,
> unless following command is running in the global zone:
> tcpdump -i e1000g1.

VNICs and VirtualBox doesn't go well together. The reason for this is
that VirtualBox doesn't know anything about the MAC address of the
VNIC, and thus doesn't forward traffic to that MAC address into the
virtual machine.
When you run tcpdump it will set the network interface in promiscuous
mode, which will drop the filtering of traffic intended to other
hosts, and the traffic to the zone will get through.

The best way I have found to solve this, is to create an extra network
interface in the VirtualBox configuration, and then assign that
interface to the zone instead of a VNIC. Then it will work as
expected.

--
Venlig hilsen / Kind regards
Jeppe Toustrup (aka. Tenzer)


From k.nuyt at zonnet.nl  Tue Jun 26 19:27:15 2012
From: k.nuyt at zonnet.nl (Kees Nuyt)
Date: Tue, 26 Jun 2012 21:27:15 +0200
Subject: [OpenIndiana-discuss] IP-dedicated zone (OI b151a4) is not
	ping-able in virtualbox
In-Reply-To: <CAJ9NRxVV4ZKE5VTrP2MJ7FQSpnBHeYazEu6JAZThBL7DcSUOkQ@mail.gmail.com>
References: <CAFp0D57bK74os2NeHGVuwDbFnEWGMEMJJ4jc+6AFTxHkNG2vgw@mail.gmail.com>
	<CAJ9NRxVV4ZKE5VTrP2MJ7FQSpnBHeYazEu6JAZThBL7DcSUOkQ@mail.gmail.com>
Message-ID: <lv2ku7pvi1hm1ie721rfj0f5e7j5b4bm70@dim53.demon.nl>

On Tue, 26 Jun 2012 20:04:51 +0200, you wrote:

>On Tue, Jun 26, 2012 at 6:23 PM, WarGrey[????????] <juzhenliang at gmail.com> wrote:
>> I installed OpenIndiana b151 in virtualbox on MacOSX, there is a zone with
>> dedicated ip over e1000g1 which connecting to a host-only virtual NIC.
>> Everything was okay before updating to b151a4. I could access it
>> everywhere, host OS, global zone, or any other VMs whose NICs are in the
>> same virtual network.
>>
>> However, when updating to b151a4, it is not ping-able outside the box,
>> unless following command is running in the global zone:
>> tcpdump -i e1000g1.
>
>VNICs and VirtualBox doesn't go well together. The reason for this is
>that VirtualBox doesn't know anything about the MAC address of the
>VNIC, and thus doesn't forward traffic to that MAC address into the
>virtual machine.
>When you run tcpdump it will set the network interface in promiscuous
>mode, which will drop the filtering of traffic intended to other
>hosts, and the traffic to the zone will get through.
>
>The best way I have found to solve this, is to create an extra network
>interface in the VirtualBox configuration, and then assign that
>interface to the zone instead of a VNIC. Then it will work as
>expected.

Good hint.

Additionally: NICs are cheap in VirtualBox. Although the GUI only allows
management of up to four, the CLI VBoxManage can manage up to eight
NICs.

http://www.virtualbox.org/manual/ch06.html
http://www.virtualbox.org/manual/ch08.html#idp13727168 

-- 
Regards,

Kees Nuyt



From skiselkov.ml at gmail.com  Tue Jun 26 19:31:03 2012
From: skiselkov.ml at gmail.com (=?UTF-8?B?U2HFoW8gS2lzZWxrb3Y=?=)
Date: Tue, 26 Jun 2012 21:31:03 +0200
Subject: [OpenIndiana-discuss] Garrett D'Amore on using SATA drives in a
 SAS system
In-Reply-To: <13852970.4.1340715718558.JavaMail.root@zimbra>
References: <13852970.4.1340715718558.JavaMail.root@zimbra>
Message-ID: <4FEA0DF7.9030603@gmail.com>

On 06/26/2012 03:01 PM, Roy Sigurd Karlsbakk wrote:
> Hi all
> 
> Seems Garrett D'Amore from Nexenta has a few things to say about using SATA drives in SAS systems
> 
> http://gdamore.blogspot.no/2010/08/why-sas-sata-is-not-such-great-idea.html
> 
> The digest is "Just don't do it"?

Couldn't agree more. Big-name endors (like Sun/Oracle, Dell, HP, etc.)
need to test each SATA firmware revision they ship for storage products
and often modify it to make it behave more normally. Sun (and other
vendors possibly too) put a small interposer board between the SATA
drive and the SAS expander back-plane in enclosures to make sure this
multi-protocol joyride was going well (most of the time).

In my experience, SATA drives just aren't worth it. Looking at e.g.
Seagate Constellation ES.2 drives in SATA vs SAS varieties, the price
difference is only a few dolars (depending on dealer), so it just isn't
worth the gamble. Plus, SAS is dual-port and multi-path often allows for
better use of the new drive's rather large caches (64MB+) by being able
to satisfy a read from cache while a write is going on.

--
Saso


From jimklimov at cos.ru  Tue Jun 26 20:26:14 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 27 Jun 2012 00:26:14 +0400
Subject: [OpenIndiana-discuss] bmc-watchdog SMF dependencies
Message-ID: <4FEA1AE6.30208@cos.ru>

Hello all, I've got a new small matter for generic discussion:

   Some of my systems have hardware watchdogs, either on motherboards
features or in IPMI addons.

   A small intro for newcomers: Watchdogs include a timer that can be
started by BIOS or a watchdog driver in the OS, and the driver should
regularly restart this timer (a trivial driver is just a loop with
long sleeps and a write of a byte into a certain port's address).
If the computer freezes and the driver no longer functions, the
hardware watchdog issues a reset on the motherboard, or a similar
administrative action (if configurable).

   Now, in OpenSolaris (and portable to OI) there is a bmc-watchdog
package for some proprietary hardware implementations, as well as
a newly ported open-source driver is brewing. There is also an SMF
service to wrap the watchdog. From what I see, upon service startup
the HW timer is started, and for the duration of the service uptime
the timer-resets are regularly issued. Upon service shutdown there
are two possible approaches (as I tweaked the method script a lot,
I am not sure what was there originally): either the daemon for
regularly-restarting the timer is just killed (and the timer keeps
ticking), or the timer is also stopped. On my system it happened
to be the former, and during a shutdown which took longer than usual
to proceed (for valid reasons), the box got reset by the timer.

   Now I looked at the SMF manifest, and see that the service only
depends on filesystem/usr. In my practice this meant that upon OS
shutdown, the bmc-watchdog daemon was quickly killed (as nothing
depends on this service) and the timer ticked down to zero - boom!

   Question is: what is a valid way to avoid the watchdog killing
the system upon lengthy shutdowns?

   I came up with a few ideas:
1) Redefine the stop method to not kill the daemon - not good, for
    pedantic reasons at least ;)
2) Redefine the stop method to kill the daemon and stop the timer -
    not good because the box can potentially also freeze during
    shutdown, and in that case we would want it automagically reset;
3) Make milestone/single-user a dependency of bmc-watchdog (I also
    tried to redefine bmc-watchdog instance to have a dependent -
    but this did not get picked up properly) - in this case the
    daemon works until all heavy services in miletone/multi-user
    get shut down properly, and only gets killed then (and the HW
    timer ticks for a few more seconds, until the system is rebooted).

So far I like the idea#3 (alone) best. Are there any reasons not to
do so, or to do something different? Ultimately, I hope, the best
method should end up in the illumos-gate ;)

Thanks,
//Jim Klimov


From jimklimov at cos.ru  Tue Jun 26 20:47:46 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 27 Jun 2012 00:47:46 +0400
Subject: [OpenIndiana-discuss] "shareiscsi" and COMSTAR
Message-ID: <4FEA1FF2.9060402@cos.ru>

Hello all,

   I am revising an older OpenSolaris file-server before an upgrade
to OI, and this server uses COMSTAR to publish some zvols via iSCSI.
As I revised the procedure used to set it up originally, I remember
that the initial OpenSolaris iSCSI stack performed poorer, but only
it was integrated with "zfs set shareiscsi=..." attribute, and part
of migration to COMSTAR was to make sure that these attributes are
set to "off" so that the older iSCSI daemon does not start up when
the pool is imported.

   Questions are:

1) Is COMSTAR still not-integrated with shareiscsi ZFS attributes?
    Or can the pool use the attribute, and the correct (new COMSTAR)
    iSCSI target daemon will fire up?

2) What would be the best way to migrate iSCSI server configuration
    (LUs, views, allowed client lists, etc.) - is it sufficient to
    just export the SMF config of "stmf" service, or do I also need
    some other services and/or files (/etc/iscsi, something else?)

Thanks,
//Jim Klimov



From rennieallen at gmail.com  Tue Jun 26 20:54:15 2012
From: rennieallen at gmail.com (Rennie Allen)
Date: Tue, 26 Jun 2012 13:54:15 -0700
Subject: [OpenIndiana-discuss] bmc-watchdog SMF dependencies
In-Reply-To: <4FEA1AE6.30208@cos.ru>
Message-ID: <CC0F6F30.2686B%rennieallen@gmail.com>

I don't see what is wrong with option #1.  Just leave the watchdog running
until the kernel shuts down the computer. There is no reason the watchdog
should ever stop (that way it offers protection continuously until the
system is otherwise shut off).



On 6/26/12 1:26 PM, "Jim Klimov" <jimklimov at cos.ru> wrote:

>Hello all, I've got a new small matter for generic discussion:
>
>   Some of my systems have hardware watchdogs, either on motherboards
>features or in IPMI addons.
>
>   A small intro for newcomers: Watchdogs include a timer that can be
>started by BIOS or a watchdog driver in the OS, and the driver should
>regularly restart this timer (a trivial driver is just a loop with
>long sleeps and a write of a byte into a certain port's address).
>If the computer freezes and the driver no longer functions, the
>hardware watchdog issues a reset on the motherboard, or a similar
>administrative action (if configurable).
>
>   Now, in OpenSolaris (and portable to OI) there is a bmc-watchdog
>package for some proprietary hardware implementations, as well as
>a newly ported open-source driver is brewing. There is also an SMF
>service to wrap the watchdog. From what I see, upon service startup
>the HW timer is started, and for the duration of the service uptime
>the timer-resets are regularly issued. Upon service shutdown there
>are two possible approaches (as I tweaked the method script a lot,
>I am not sure what was there originally): either the daemon for
>regularly-restarting the timer is just killed (and the timer keeps
>ticking), or the timer is also stopped. On my system it happened
>to be the former, and during a shutdown which took longer than usual
>to proceed (for valid reasons), the box got reset by the timer.
>
>   Now I looked at the SMF manifest, and see that the service only
>depends on filesystem/usr. In my practice this meant that upon OS
>shutdown, the bmc-watchdog daemon was quickly killed (as nothing
>depends on this service) and the timer ticked down to zero - boom!
>
>   Question is: what is a valid way to avoid the watchdog killing
>the system upon lengthy shutdowns?
>
>   I came up with a few ideas:
>1) Redefine the stop method to not kill the daemon - not good, for
>    pedantic reasons at least ;)
>2) Redefine the stop method to kill the daemon and stop the timer -
>    not good because the box can potentially also freeze during
>    shutdown, and in that case we would want it automagically reset;
>3) Make milestone/single-user a dependency of bmc-watchdog (I also
>    tried to redefine bmc-watchdog instance to have a dependent -
>    but this did not get picked up properly) - in this case the
>    daemon works until all heavy services in miletone/multi-user
>    get shut down properly, and only gets killed then (and the HW
>    timer ticks for a few more seconds, until the system is rebooted).
>
>So far I like the idea#3 (alone) best. Are there any reasons not to
>do so, or to do something different? Ultimately, I hope, the best
>method should end up in the illumos-gate ;)
>
>Thanks,
>//Jim Klimov
>
>_______________________________________________
>OpenIndiana-discuss mailing list
>OpenIndiana-discuss at openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss




From jimklimov at cos.ru  Tue Jun 26 21:32:45 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 27 Jun 2012 01:32:45 +0400
Subject: [OpenIndiana-discuss] bmc-watchdog SMF dependencies
In-Reply-To: <CC0F6F30.2686B%rennieallen@gmail.com>
References: <CC0F6F30.2686B%rennieallen@gmail.com>
Message-ID: <4FEA2A7D.80509@cos.ru>

2012-06-27 0:54, Rennie Allen ?????:
> I don't see what is wrong with option #1.  Just leave the watchdog running
> until the kernel shuts down the computer. There is no reason the watchdog
> should ever stop (that way it offers protection continuously until the
> system is otherwise shut off).

Well, there might be reasons for administrative stopping of
the watchdog. Say, to try a different driver or daemon ;)

Of course, in this case the SMF stop might do nothing, and
the daemon can be killed manually by admin - if he knows
what to kill. SMF restarts would be tricky though (a start
method should kill pre-existing daemons and/or do nothing
and "exit 0")?...

Thanks,
//Jim



From richard.elling at richardelling.com  Tue Jun 26 21:36:08 2012
From: richard.elling at richardelling.com (Richard Elling)
Date: Tue, 26 Jun 2012 14:36:08 -0700
Subject: [OpenIndiana-discuss] Garrett D'Amore on using SATA drives in a
	SASsystem
In-Reply-To: <4FE9F337.80607@druber.com>
References: <13852970.4.1340715718558.JavaMail.root@zimbra>	<E94E52B28ADF4D7B8AEE060A23E4DCC1@manticore>
	<9810920F-D934-41AE-A9AF-50EC8DFF114E@RichardElling.com>
	<4FE9F337.80607@druber.com>
Message-ID: <1B4F8C20-B623-4EA3-894D-C0BD24038350@richardelling.com>

On Jun 26, 2012, at 10:36 AM, Dan Swartzendruber wrote:
> On 6/26/2012 1:15 PM, Richard Elling wrote:
>> On Jun 26, 2012, at 6:29 AM, Dan Swartzendruber wrote:
>> 
>>   
>>> Keep in mind this is almost 2 yrs old, though.  I seem to recall a thread
>>> here or there that has pinned the SATA toxicity issues to an mpt driver bug
>>> or somesuch?
>>>     
>> Not really. Search for other OSes and their tales of woe. In some cases, a
>> bad SATA drive can make the machine fail at POST, well before an OS is
>> loaded.
>> 
>> Best results for SATA is direct-connect: no expanders, no extenders.
>> Next best is SATA with a good-quality SATA/SAS interposer.
>> Known to be a poor mix: both SATA and SAS devices sharing an expander.
>> 
>> NB, we have seen changes in HBA, expander, and disk firmware all contribute
>> to happiness or sadness when SATA devices are used in SAS fabrics (STP).
>> At one time, we tried to keep a list of combinations known for happiness, but
>> maintaining that list proved to be impractical, due to the constant churn and
>> unavailability of disk firmware patches from various vendors. Also, do not assume
>> that you will be able to get a firmware upgrade, even if it exists :-(
>>  -- richard
>> 
>>   
> To clarify: on hardocp a few months back, there was a discussion on this whole issue and there was a cryptic reference to Oracle having supposedly root-caused a software/driver bug that was causing a specific problem.  I wish I could remember anything more specific than that?

I can recall no less than 5 times this was claimed to be fixed. Yet, problems persist.
IMHO the root cause is that the specifications are just loose enough that perfect
interoperability under all failure modes between SAS, STP, and SATA will take
many years, perhaps decades, to "fix"

For example, with one disk vendor, after 12 months of trouble, we were finally 
able to get enough traces and data for them to isolate a race condition they had
been fighting for years. Great work team! Then they EOLed the product without
producing a GA firmware upgrade. I know these devices do not work well under
STP and will never recommend them to be used with expanders. Fortunately, 
they are EOL, so as time flies by we should see fewer and fewer of them.
 -- richard

-- 

ZFS storage and performance consulting at http://www.RichardElling.com








From jay at frelled.us  Tue Jun 26 23:09:32 2012
From: jay at frelled.us (Jay Heyl)
Date: Tue, 26 Jun 2012 16:09:32 -0700
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <4FE9087F.4010206@arkologic.com>
References: <4FE9087F.4010206@arkologic.com>
Message-ID: <CAACKFo=GCWbtm4Oux1Bu7CWVpsvgcJ3=grVqDAt52=TW1bQCnw@mail.gmail.com>

On Mon, Jun 25, 2012 at 5:55 PM, Vishwas Durai <vishwasd at arkologic.com>wrote:

> Hello all,
> I'm wondering what options are available for root filesystem in OI? By
> default,  install  uses ZFS and creates a rpool. But If I'm a ZFS hacker
> and made some changes to some core structures, how does one go about
> debugging that? Is dropping to kmdb and debugging the only available
> (painful) option?


Trust me, you do NOT want to be modifying the file system code used on your
live system. Leave your base system running with the release code and use a
virtual machine as your sand box. Actually, use a COPY of a nicely
configured virtual machine. If you mess up, correcting your mistake is a
simple matter of making another copy of the virtual machine. Unless you
enjoy installing/restoring your development machine...

  -- Jay

From john at xaccel.net  Tue Jun 26 23:51:16 2012
From: john at xaccel.net (John T. Bittner)
Date: Tue, 26 Jun 2012 23:51:16 +0000
Subject: [OpenIndiana-discuss] ZFS and AVS guru
Message-ID: <EFCDF2C6785A7B478B3A77A6E7C363699AC09C28@mail.xaccel.net>

I am working on setting up 2 SAN to replicate via AVS. I think I get the idea of how to set this up but have a few questions.
The 2 sans I build have 15 drives SAS drives + 2 Cache SSD's and 2 Log SSD's.

The question I have is do you replicate the SSD's ?
Do you need a bitmap for all the drives or can I use one for the zpool.

Looking for a ZFS and AVS guru to work with me for about an hour.  Willing to pay.

Anyone interested please email me direct at john at xaccel.net

Thanks

John Bittner
Xaccel Networks.






From mike.laspina at laspina.ca  Wed Jun 27 00:51:09 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Tue, 26 Jun 2012 19:51:09 -0500
Subject: [OpenIndiana-discuss] "shareiscsi" and COMSTAR
In-Reply-To: <4FEA1FF2.9060402@cos.ru>
References: <4FEA1FF2.9060402@cos.ru>
Message-ID: <8F607366E3C0F9499212649291E0BD640D4715@MS1.laspina.ca>

Hi Jim,

>1) Is COMSTAR still not-integrated with shareiscsi ZFS attributes?
>    Or can the pool use the attribute, and the correct (new COMSTAR)
>    iSCSI target daemon will fire up?

COMSTAR is not integrated with ZFS and it will ignore the ZFS props.
What is the release of the old host OS?
I strongly suggest you record the old iqn target names and the LU's they
are mapped to, as well the LU GUID is helpful.
Snapshots on zvols are your friends! 


>2) What would be the best way to migrate iSCSI server configuration
>    (LUs, views, allowed client lists, etc.) - is it sufficient to
>    just export the SMF config of "stmf" service, or do I also need
>    some other services and/or files (/etc/iscsi, something else?)

This really depends on your current configuration .. can you provide
some specifics of the existing targets/initiators?

Mike

http://blog.laspina.ca
 

Thanks,
//Jim Klimov


_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


From juzhenliang at gmail.com  Wed Jun 27 01:10:07 2012
From: juzhenliang at gmail.com (WarGrey Ju)
Date: Wed, 27 Jun 2012 09:10:07 +0800
Subject: [OpenIndiana-discuss] IP-dedicated zone (OI b151a4) is not
 ping-able in virtualbox
In-Reply-To: <lv2ku7pvi1hm1ie721rfj0f5e7j5b4bm70@dim53.demon.nl>
References: <CAFp0D57bK74os2NeHGVuwDbFnEWGMEMJJ4jc+6AFTxHkNG2vgw@mail.gmail.com>
	<CAJ9NRxVV4ZKE5VTrP2MJ7FQSpnBHeYazEu6JAZThBL7DcSUOkQ@mail.gmail.com>
	<lv2ku7pvi1hm1ie721rfj0f5e7j5b4bm70@dim53.demon.nl>
Message-ID: <CAFp0D54u7LPOYTWdy=7KD+YoMotiUkwEMhdO08d6x9+dJkOr9A@mail.gmail.com>

Okay, thanks for your replies.

But this workaround is not very good, since the topology of my virtual
network has been changed both on physically and logically.

I want to know when will they get together well? the previous versions are
okay.
Before that, I will not use zones any more to deploy my services as if I am
using a linux box.

or, are there any providers can serve people the solaris/illumos hosting
and servers?

I need a real machine to develop, deploy and research on,
finally I wish I can make some contributions for the project.

From rennieallen at gmail.com  Wed Jun 27 01:44:20 2012
From: rennieallen at gmail.com (Rennie Allen)
Date: Tue, 26 Jun 2012 18:44:20 -0700
Subject: [OpenIndiana-discuss] Options for a root filesystem
In-Reply-To: <CAACKFo=GCWbtm4Oux1Bu7CWVpsvgcJ3=grVqDAt52=TW1bQCnw@mail.gmail.com>
Message-ID: <CC0FB2EC.268C5%rennieallen@gmail.com>

+1 what Jay says.

Also, I don't think that dropping to mdb is all that painful.  It is one
of the best debuggers around.



On 6/26/12 4:09 PM, "Jay Heyl" <jay at frelled.us> wrote:

>On Mon, Jun 25, 2012 at 5:55 PM, Vishwas Durai
><vishwasd at arkologic.com>wrote:
>
>> Hello all,
>> I'm wondering what options are available for root filesystem in OI? By
>> default,  install  uses ZFS and creates a rpool. But If I'm a ZFS hacker
>> and made some changes to some core structures, how does one go about
>> debugging that? Is dropping to kmdb and debugging the only available
>> (painful) option?
>
>
>Trust me, you do NOT want to be modifying the file system code used on
>your
>live system. Leave your base system running with the release code and use
>a
>virtual machine as your sand box. Actually, use a COPY of a nicely
>configured virtual machine. If you mess up, correcting your mistake is a
>simple matter of making another copy of the virtual machine. Unless you
>enjoy installing/restoring your development machine...
>
>  -- Jay
>_______________________________________________
>OpenIndiana-discuss mailing list
>OpenIndiana-discuss at openindiana.org
>http://openindiana.org/mailman/listinfo/openindiana-discuss




From gordon.w.ross at gmail.com  Wed Jun 27 05:28:26 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Wed, 27 Jun 2012 01:28:26 -0400
Subject: [OpenIndiana-discuss] Problem/Question on mount lofs:
In-Reply-To: <4FE9F71E.6040205@cos.ru>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
	<4FE9F71E.6040205@cos.ru>
Message-ID: <CAD0Ztp23NLY8re5gjSwTs2uLDs2T-daHKvCi1xmiXHkKReX+=Q@mail.gmail.com>

On Tue, Jun 26, 2012 at 1:53 PM, Jim Klimov <jimklimov at cos.ru> wrote:
>> On 26/06/2012 14:44, Armin Maier wrote:
>>>
>>> Hello anybody!
>>> I've got a problem centraly sharing ZFS filesystems.
>>> What i want is to create zfs filesystems for different Usergroups and
>>> i want to share them in a central location.
[...]
>>> If i browse to the "/mountbase/zfsfilesys1" directory on the console i
>>> can see
>>> all the Contents and everything is fine, but when i open the share
>>> "\\openindiana\zfs$" i do net see any directories. If i unmount the
>>> "/mountbase/zfsfilesys1" Directory it appears on the Windows computer.
>>> Does someone know why this happens? Is there a "smbserver" setting
>>> which has to
>>> be set? I do not use samba for sharing, i am using the Solaris smb
>>> service
>>> "svc:/network/smb/server:default".

> AFAIK the Solaris kernel CIFS server, which is also used in OI,
> does not allow sharing ZFS dataset hierarchies as a single
> mountpoint (like you can do with NFS), and the CIFS clients
> don't have a means to detect a nested mountpoint and call a
> new mount operation for the nested datasets. I am not sure why,
> maybe it is a protocol limitation, or a certain vendor's popular
> client capability limitation.

The native SMB service currently does not share recursively.
(That was a design choice - an unpopular one - more below.)
When you set sharesmb=... on some ZFS data set, none of
the ZFS data sets that might exist below it are visible to SMB.
Bug or feature?  You decide...

We at Nexenta implemented an option to allow such "child"
file systems under a share to be exposed by the share.
Unfortunately, I don't think it ever got pushed up-stream
to the illumos gate.  I guess you'd be in favor?

-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From gordon.w.ross at gmail.com  Wed Jun 27 05:34:25 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Wed, 27 Jun 2012 01:34:25 -0400
Subject: [OpenIndiana-discuss] bmc-watchdog SMF dependencies
In-Reply-To: <4FEA1AE6.30208@cos.ru>
References: <4FEA1AE6.30208@cos.ru>
Message-ID: <CAD0Ztp38MkWrh0OzwMNi_OuEWSHoa=EDvkfzWVhg08u0EOESXA@mail.gmail.com>

On Tue, Jun 26, 2012 at 4:26 PM, Jim Klimov <jimklimov at cos.ru> wrote:
> Hello all, I've got a new small matter for generic discussion:

> ?Now, in OpenSolaris (and portable to OI) there is a bmc-watchdog
> package for some proprietary hardware implementations, as well as
> a newly ported open-source driver is brewing. There is also an SMF
> service to wrap the watchdog. From what I see, upon service startup
> the HW timer is started, and for the duration of the service uptime
> the timer-resets are regularly issued. Upon service shutdown there
> are two possible approaches (as I tweaked the method script a lot,
> I am not sure what was there originally): either the daemon for
> regularly-restarting the timer is just killed (and the timer keeps
> ticking), or the timer is also stopped. On my system it happened
> to be the former, and during a shutdown which took longer than usual
> to proceed (for valid reasons), the box got reset by the timer.
>
> ?Now I looked at the SMF manifest, and see that the service only
> depends on filesystem/usr. In my practice this meant that upon OS
> shutdown, the bmc-watchdog daemon was quickly killed (as nothing
> depends on this service) and the timer ticked down to zero - boom!
>
> ?Question is: what is a valid way to avoid the watchdog killing
> the system upon lengthy shutdowns?
>
> ?I came up with a few ideas:
> 1) Redefine the stop method to not kill the daemon - not good, for
> ? pedantic reasons at least ;)
> 2) Redefine the stop method to kill the daemon and stop the timer -
> ? not good because the box can potentially also freeze during
> ? shutdown, and in that case we would want it automagically reset;
> 3) Make milestone/single-user a dependency of bmc-watchdog (I also
> ? tried to redefine bmc-watchdog instance to have a dependent -
> ? but this did not get picked up properly) - in this case the
> ? daemon works until all heavy services in miletone/multi-user
> ? get shut down properly, and only gets killed then (and the HW
> ? timer ticks for a few more seconds, until the system is rebooted).

4)  Run your watchdog reset program outside of the SMF contract,
     for the service i.e. "ctrun -l none bmc-watchdog"
     so it will not be killed when the service is stopped.


-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From jimklimov at cos.ru  Wed Jun 27 09:55:44 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 27 Jun 2012 13:55:44 +0400
Subject: [OpenIndiana-discuss] "shareiscsi" and COMSTAR
In-Reply-To: <8F607366E3C0F9499212649291E0BD640D4715@MS1.laspina.ca>
References: <4FEA1FF2.9060402@cos.ru>
	<8F607366E3C0F9499212649291E0BD640D4715@MS1.laspina.ca>
Message-ID: <4FEAD8A0.50009@cos.ru>

2012-06-27 4:51, Mike La Spina wrote:
> Hi Jim,
>
>> 1) Is COMSTAR still not-integrated with shareiscsi ZFS attributes?
>>     Or can the pool use the attribute, and the correct (new COMSTAR)
>>     iSCSI target daemon will fire up?
>
> COMSTAR is not integrated with ZFS and it will ignore the ZFS props.

Well, that was the case a couple of years ago when we played with
the newly released COMSTAR. We did not know whether the progress
marched on (to integrate ZFS with COMSTAR) - hence the questions ;)

> What is the release of the old host OS?

SXCE snv_117... Well, it may be more than a couple of years :)

> I strongly suggest you record the old iqn target names and the LU's they
> are mapped to, as well the LU GUID is helpful.

Probably so, if only to check that the SMF/file-based config
migration attempt went well.

> Snapshots on zvols are your friends!

Unfortunately, they are not. The OS upgrade is part of the box's
migration to larger new drives, and so far it is very restrained
on free disk space in the pool. ZVOL snapshots reserve the zvol
size so as to guarantee the ability to rewrite the whole zvol
contents safely, and the box can not afford that much wasted
space. Ability to do these snapshots is indeed one of the many
reasons for the overall upgrade (HW+SW).

>
>
>> 2) What would be the best way to migrate iSCSI server configuration
>>     (LUs, views, allowed client lists, etc.) - is it sufficient to
>>     just export the SMF config of "stmf" service, or do I also need
>>     some other services and/or files (/etc/iscsi, something else?)
>
> This really depends on your current configuration .. can you provide
> some specifics of the existing targets/initiators?

The targets are now a few zvols on the snv_117 box, served by
COMSTAR (svc:/system/stmf:default, svc:/network/iscsi/target:default).
The service svc:/network/iscsi/initiator:default is also online,
but it was AFAIK used for testing and does not normally attach
remote LUNs.

Initiators that I know of are from free ESXi hosts, I'm uncertain
about the version.

//Jim


From jim at cos.ru  Wed Jun 27 10:24:20 2012
From: jim at cos.ru (Jim Klimov)
Date: Wed, 27 Jun 2012 14:24:20 +0400
Subject: [OpenIndiana-discuss] IP-dedicated zone (OI b151a4) is not
 ping-able in virtualbox
In-Reply-To: <CAFp0D54u7LPOYTWdy=7KD+YoMotiUkwEMhdO08d6x9+dJkOr9A@mail.gmail.com>
References: <CAFp0D57bK74os2NeHGVuwDbFnEWGMEMJJ4jc+6AFTxHkNG2vgw@mail.gmail.com>
	<CAJ9NRxVV4ZKE5VTrP2MJ7FQSpnBHeYazEu6JAZThBL7DcSUOkQ@mail.gmail.com>
	<lv2ku7pvi1hm1ie721rfj0f5e7j5b4bm70@dim53.demon.nl>
	<CAFp0D54u7LPOYTWdy=7KD+YoMotiUkwEMhdO08d6x9+dJkOr9A@mail.gmail.com>
Message-ID: <4FEADF54.6090505@cos.ru>

2012-06-27 5:10, WarGrey Ju wrote:
> Okay, thanks for your replies.
>
> But this workaround is not very good, since the topology of my virtual
> network has been changed both on physically and logically.
>
> I want to know when will they get together well? the previous versions are
> okay.
> Before that, I will not use zones any more to deploy my services as if I am
> using a linux box.

I think there may be a bit of misunderstanding around here:

1) VirtualBox as a hypervisor does only capture the ethernet
    frames destined for the MAC address of its virtual adapter
    and forwards these frames into the VM, at least it is so
    in the Bridged Mode where the VM's NICs are exposed to
    the external LAN. This works differently on different host
    OSes, and for OpenSolaris hosting there is a documented
    requirement to use dedicated Solaris VNICs for each VM NIC.
    It does work differently on Solaris 10 (no VNICs) though,
    and I am not certain how - perhaps promiscuous mode is used?
    I am not sure why it worked for you before - seemingly it
    shouldn't have ;) Maybe you did have promiscuous networking
    enabled all the time somehow?

    Also you might want to explore different networking modes
    for VirtualBox - such as its NAT or host-only network
    (which I think you've also tried using already).

2) Local zones on your OI VM can use "exclusive" or "shared"
    networking. In exclusive more you dedicate a NIC in the
    guest OS to the zone (perhaps by creating a VNIC, or by
    using a VirtualBox NIC). In shared mode you basically
    create an alias IP address on an existing NIC - and use
    its MAC address, so that can work with VirtualBox well.

3) It is possible to create a "host-only LAN" within OI,
    where one of the zones (usually global) would NAT the
    local zones (with exclusive IP stacks) to/from external
    LAN, using its one external NIC and one IP/MAC-address.
    See my instructions here:
 
http://wiki.illumos.org/display/~jimklimov/Using+host-only+networking+to+get+from+build+zones+and+test+VMs+to+the+Internet

> or, are there any providers can serve people the solaris/illumos hosting
> and servers?

You could ask Joyent, from those I know via Internet reading :)
Maybe other big illumos contributors have similar services?..

> I need a real machine to develop, deploy and research on,
> finally I wish I can make some contributions for the project.

That is most positive ;)

HTH,
//Jim Klimov


From jimklimov at cos.ru  Wed Jun 27 10:30:20 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 27 Jun 2012 14:30:20 +0400
Subject: [OpenIndiana-discuss] Problem/Question on mount lofs:
In-Reply-To: <CAD0Ztp23NLY8re5gjSwTs2uLDs2T-daHKvCi1xmiXHkKReX+=Q@mail.gmail.com>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
	<4FE9F71E.6040205@cos.ru>
	<CAD0Ztp23NLY8re5gjSwTs2uLDs2T-daHKvCi1xmiXHkKReX+=Q@mail.gmail.com>
Message-ID: <4FEAE0BC.6040604@cos.ru>

2012-06-27 9:28, Gordon Ross wrote:
> We at Nexenta implemented an option to allow such "child"
> file systems under a share to be exposed by the share.
> Unfortunately, I don't think it ever got pushed up-stream
> to the illumos gate.  I guess you'd be in favor?

And the CIFS clients (windows, linux, etc.) can mount this
child in the sub-path of a share? I.e. these two datasets:
\\SERVER\share        == tank/export/share
\\SERVER\share\child  == tank/export/share/child

This is certainly an interesting option, I'd be in favor of
seeing it generally available - both as really useful, and
as a match for NFS service capabilities :)
For example, some userhomes are split into several datasets
for misc. reasons, and can't be easily accessed from Windows :(

So far my tests with explicit sharing of child datasets into
the namespace of a parent (a'la sharesmb=name=share\\child)
failed, and accesses from windows into \\SERVER\share\child
returned "Access denied" errors.

//Jim Klimov


From ma2412 at gmx.de  Wed Jun 27 11:01:27 2012
From: ma2412 at gmx.de (Armin Maier)
Date: Wed, 27 Jun 2012 13:01:27 +0200
Subject: [OpenIndiana-discuss] [!! SPAM] Re: Problem/Question on mount
 lofs:
In-Reply-To: <CAD0Ztp23NLY8re5gjSwTs2uLDs2T-daHKvCi1xmiXHkKReX+=Q@mail.gmail.com>
References: <4FE9AEA3.6060306@gmx.de>
	<4FE9B081.3030500@kit.edu><4FE9F71E.6040205@cos.ru>
	<CAD0Ztp23NLY8re5gjSwTs2uLDs2T-daHKvCi1xmiXHkKReX+=Q@mail.gmail.com>
Message-ID: <4FEAE807.8080206@gmx.de>

On 27.06.2012 07:28, Gordon Ross wrote:
>> AFAIK the Solaris kernel CIFS server, which is also used in OI,
>> does not allow sharing ZFS dataset hierarchies as a single
>> mountpoint (like you can do with NFS), and the CIFS clients
>> don't have a means to detect a nested mountpoint and call a
>> new mount operation for the nested datasets. I am not sure why,
>> maybe it is a protocol limitation, or a certain vendor's popular
>> client capability limitation.
> The native SMB service currently does not share recursively.
> (That was a design choice - an unpopular one - more below.)
> When you set sharesmb=... on some ZFS data set, none of
> the ZFS data sets that might exist below it are visible to SMB.
> Bug or feature?  You decide...
>
> We at Nexenta implemented an option to allow such "child"
> file systems under a share to be exposed by the share.
> Unfortunately, I don't think it ever got pushed up-stream
> to the illumos gate.  I guess you'd be in favor?
>
I do not understand the phrase :

When you set sharesmb=... on some ZFS data set, none of
the ZFS data sets that might exist below it are visible to SMB.
Bug or feature?  You decide...

I interpret it like if sharesmb= is set to off on every zfs filesystem 
the smb server should display filesystems which might exist below, but 
that is definiteley not so.
I also was looking for dfs support like Windows has build in, but smb 
server seams to not support that. Samba is no alternative for me since i 
am using windows conform ACL on the zfs filesystem and openindiana is 
joind to domain and uses the windows users and groups, i dont want to 
play around with winbind samba and permissions since the smb server of 
opensolaris works very simple and much easier than a samba configuration 
i think.


From aneurin.price at gmail.com  Wed Jun 27 11:41:04 2012
From: aneurin.price at gmail.com (Aneurin Price)
Date: Wed, 27 Jun 2012 12:41:04 +0100
Subject: [OpenIndiana-discuss] KVM guests hang at boot on oi_151a4
Message-ID: <CAHb+SPCQstkkih3uw99=tuuyqt+neQAVo22uyXsbtJ_zDFGDUA@mail.gmail.com>

Hello all,

I have a machine which was running some KVM guests successfully on
oi_151a3, but no longer since updating to oi_151a4.

I've tried a Windows 8 VM - when I connect to the qemu VNC display I
just get a black screen, which I believe indicates it's hanging at the
beginning of the Windows boot process. I've also tried booting
pxelinux - that successfully gets the boot image via TFTP, but hangs
immediately after that point. Both of these work fine with oi_151a3
using the same configuration.

When it happens, one CPU core is permanently pegged at 100%, and
kvmstat gives output like the following:

   pid vcpu |  exits :  haltx   irqx  irqwx    iox  mmiox |   irqs   emul   eptv
   757    0 | 396890 :      0      6     18     18      0 |     18      0      0
   757    1 |      0 :      0      0      0      0      0 |      0      0      0

Has anyone else seen anything like this?

I'm not certain what information I can provide which might be of
relevance, and I'm not sure what my next step should be in trying to
debug this; perhaps somebody can give me some pointers?

Thanks for your time,
Nye


From matt.connolly.au at gmail.com  Wed Jun 27 12:12:26 2012
From: matt.connolly.au at gmail.com (Matt Connolly)
Date: Wed, 27 Jun 2012 22:12:26 +1000
Subject: [OpenIndiana-discuss] EveryCity OpenWebStack for php 5.3
Message-ID: <9D9934BB-5E38-41EC-AB61-8A8EFF6B12C6@gmail.com>

I just came across the EveryCity OpenWebStack repository for SmartOS / Solaris 10.

http://smartos.pkg.ec/en/index.shtml

Has anyone tried this for OpenIndiana?

In particular I have need for php 5.3 and compiling from source looks quite difficult.


-Matt



From t12nslookup at gmail.com  Wed Jun 27 12:28:18 2012
From: t12nslookup at gmail.com (Jonathan Adams)
Date: Wed, 27 Jun 2012 13:28:18 +0100
Subject: [OpenIndiana-discuss] KVM guests hang at boot on oi_151a4
In-Reply-To: <CAHb+SPCQstkkih3uw99=tuuyqt+neQAVo22uyXsbtJ_zDFGDUA@mail.gmail.com>
References: <CAHb+SPCQstkkih3uw99=tuuyqt+neQAVo22uyXsbtJ_zDFGDUA@mail.gmail.com>
Message-ID: <CAKr4wiSgAYKPG=CS75jXzcSJjYGxCWes9L54peTkf_6ncXh0hw@mail.gmail.com>

mine stopped working after u2 ... there is a "fix" on this issue:

https://www.illumos.org/issues/2626

# pkg uninstall driver/i86pc/kvm system/qemu system/qemu/kvm
# pkg install system/qemu at 0.15.0,5.11-0.151.1.2:20120209T223057Z \
system/qemu/kvm at 0.0.1.20110813,5.11-0.151.1.2:20120209T223223Z \
driver/i86pc/kvm at 0.0.1.20110820,5.11-0.151.1.2:20120209T214555Z

Hope it helps.

Jon

On 27 June 2012 12:41, Aneurin Price <aneurin.price at gmail.com> wrote:
> Hello all,
>
> I have a machine which was running some KVM guests successfully on
> oi_151a3, but no longer since updating to oi_151a4.
>
> I've tried a Windows 8 VM - when I connect to the qemu VNC display I
> just get a black screen, which I believe indicates it's hanging at the
> beginning of the Windows boot process. I've also tried booting
> pxelinux - that successfully gets the boot image via TFTP, but hangs
> immediately after that point. Both of these work fine with oi_151a3
> using the same configuration.
>
> When it happens, one CPU core is permanently pegged at 100%, and
> kvmstat gives output like the following:
>
> ? pid vcpu | ?exits : ?haltx ? irqx ?irqwx ? ?iox ?mmiox | ? irqs ? emul ? eptv
> ? 757 ? ?0 | 396890 : ? ? ?0 ? ? ?6 ? ? 18 ? ? 18 ? ? ?0 | ? ? 18 ? ? ?0 ? ? ?0
> ? 757 ? ?1 | ? ? ?0 : ? ? ?0 ? ? ?0 ? ? ?0 ? ? ?0 ? ? ?0 | ? ? ?0 ? ? ?0 ? ? ?0
>
> Has anyone else seen anything like this?
>
> I'm not certain what information I can provide which might be of
> relevance, and I'm not sure what my next step should be in trying to
> debug this; perhaps somebody can give me some pointers?
>
> Thanks for your time,
> Nye
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss


From ppkomatsu at gmail.com  Wed Jun 27 13:22:41 2012
From: ppkomatsu at gmail.com (Pepe Komatsu)
Date: Wed, 27 Jun 2012 08:22:41 -0500
Subject: [OpenIndiana-discuss] MegaRAID 9261-8i
Message-ID: <CAK8SrzqiEREr9m-51RGixr9bJNOLTavb582oX4X+rt_YB3msHQ@mail.gmail.com>

Someone have experience with LSI MegaRAID 9261-8i and OI?

-- 
Ricardo Komatsu
IT Consultant

From skiselkov.ml at gmail.com  Wed Jun 27 13:35:47 2012
From: skiselkov.ml at gmail.com (=?windows-1252?Q?Sa=9Ao_Kiselkov?=)
Date: Wed, 27 Jun 2012 15:35:47 +0200
Subject: [OpenIndiana-discuss] MegaRAID 9261-8i
In-Reply-To: <CAK8SrzqiEREr9m-51RGixr9bJNOLTavb582oX4X+rt_YB3msHQ@mail.gmail.com>
References: <CAK8SrzqiEREr9m-51RGixr9bJNOLTavb582oX4X+rt_YB3msHQ@mail.gmail.com>
Message-ID: <4FEB0C33.3030102@gmail.com>

On 06/27/2012 03:22 PM, Pepe Komatsu wrote:
> Someone have experience with LSI MegaRAID 9261-8i and OI?

Seeing that it's a LSI SAS 2108-based card, I recommend avoiding it if
possible, since there's no JBOD (initiator-target) mode available on the
firmware running in these chips. I recommend you go for something based
around the LSI SAS 2008 (e.g. the 9210-8i)

Other than that, support for the SAS 2108 should be hassle free.

--
Saso


From skiselkov.ml at gmail.com  Wed Jun 27 13:37:33 2012
From: skiselkov.ml at gmail.com (=?windows-1252?Q?Sa=9Ao_Kiselkov?=)
Date: Wed, 27 Jun 2012 15:37:33 +0200
Subject: [OpenIndiana-discuss] MegaRAID 9261-8i
In-Reply-To: <4FEB0C33.3030102@gmail.com>
References: <CAK8SrzqiEREr9m-51RGixr9bJNOLTavb582oX4X+rt_YB3msHQ@mail.gmail.com>
	<4FEB0C33.3030102@gmail.com>
Message-ID: <4FEB0C9D.10108@gmail.com>

On 06/27/2012 03:35 PM, Sa?o Kiselkov wrote:
> around the LSI SAS 2008 (e.g. the 9210-8i)

Minor correction, I meant the 9211-8i. The 9210-8i isn't available in
retail channels.

Cheers,
--
Saso


From aneurin.price at gmail.com  Wed Jun 27 14:02:43 2012
From: aneurin.price at gmail.com (Aneurin Price)
Date: Wed, 27 Jun 2012 15:02:43 +0100
Subject: [OpenIndiana-discuss] KVM guests hang at boot on oi_151a4
In-Reply-To: <CAKr4wiSgAYKPG=CS75jXzcSJjYGxCWes9L54peTkf_6ncXh0hw@mail.gmail.com>
References: <CAHb+SPCQstkkih3uw99=tuuyqt+neQAVo22uyXsbtJ_zDFGDUA@mail.gmail.com>
	<CAKr4wiSgAYKPG=CS75jXzcSJjYGxCWes9L54peTkf_6ncXh0hw@mail.gmail.com>
Message-ID: <CAHb+SPAmKFp02ute6b84K7=15Dm57rWBRo5hcrpcxfDg9eS_fA@mail.gmail.com>

On 27 June 2012 13:28, Jonathan Adams <t12nslookup at gmail.com> wrote:
> mine stopped working after u2 ... there is a "fix" on this issue:
>
> https://www.illumos.org/issues/2626
>
> # pkg uninstall driver/i86pc/kvm system/qemu system/qemu/kvm
> # pkg install system/qemu at 0.15.0,5.11-0.151.1.2:20120209T223057Z \
> system/qemu/kvm at 0.0.1.20110813,5.11-0.151.1.2:20120209T223223Z \
> driver/i86pc/kvm at 0.0.1.20110820,5.11-0.151.1.2:20120209T214555Z
>

Interesting; I don't think that's the same problem - the basic
symptoms sound similar, but I'm not getting any error message as in
that report. Also, it doesn't seem to affect the same versions.

Based on that bug thread, I've tried different version combinations of
driver/i86pc/kvm, system/qemu, and system/qemu/kvm.

The result is that driver/i86pc/kvm and system/qemu don't show the
problem in any version I've tried, but it manifests when upgrading
system/qemu/kvm from 0.0.1.20110813-0.151.1.2 to
0.0.1.20120229-0.151.1.3 or later.

I've also tested using parameters like Piotr Jasiukajtis gave as
working configuration for him - same problem.

I can keep system/qemu/kvm at the working version for now, but
obviously that's not a solution long-term. Any ideas?


From dswartz at druber.com  Wed Jun 27 14:05:49 2012
From: dswartz at druber.com (Dan Swartzendruber)
Date: Wed, 27 Jun 2012 10:05:49 -0400
Subject: [OpenIndiana-discuss] quasi-hang hot-plugging sata drive?
Message-ID: <D251AF7CB65A4CC4BDC69F26ADC3319C@manticore>

OI 151a4.  3x2 mirrored data pool with single SAS drive for root.  Hot
plugged 1TB sata drive and started backing up to it using zfs send | zfs
recv.  That was chugging along nicely. I then hot-plugged a 160GB sata 2,5
drive in a 2.5/3.5 adapter to make sure it will fit correctly when I get my
l2arc SSD.  I ran devfsadm -Cv to make sure everything was clean.  That
command hung.  Unplugged the drive and no change.  Eventually things came
back and I got a prompt, but it seems like any command I type that does disk
activity (like zfs list) also hangs.  While trying to figure *that* out, my
wife comes downstairs and asks me 'what the **** is going on?  my
telecommuting session is totally gone!'  I had to power-cycle the box to get
it back.  Even worse, I kept getting errors about 'zfs mount -a' not working
because one of the windows shares directories was not empty, so the whole
mount process would blow up.  I finally had to 'zfs delete' on that share to
recover.  I kept seeing messages about:

 

Jun 27 09:16:09 nas devfsadmd[402]: [ID 937045 daemon.error] failed to
lookup dev name for
/pci at 0,0/pci8086,2779 at 1/pci1000,3040 at 0/iport at f/disk at w5000cca59bf478a0,0

 

I did 'devfsadm -Cv' and it purged a bunch of crap and now I am back up.  I
am guessing it did NOT like the 160GB drive I plugged in?  This was NOT a
fun way to start the day :(  Any thoughts on what went wrong?


From t12nslookup at gmail.com  Wed Jun 27 14:18:52 2012
From: t12nslookup at gmail.com (Jonathan Adams)
Date: Wed, 27 Jun 2012 15:18:52 +0100
Subject: [OpenIndiana-discuss] KVM guests hang at boot on oi_151a4
In-Reply-To: <CAHb+SPAmKFp02ute6b84K7=15Dm57rWBRo5hcrpcxfDg9eS_fA@mail.gmail.com>
References: <CAHb+SPCQstkkih3uw99=tuuyqt+neQAVo22uyXsbtJ_zDFGDUA@mail.gmail.com>
	<CAKr4wiSgAYKPG=CS75jXzcSJjYGxCWes9L54peTkf_6ncXh0hw@mail.gmail.com>
	<CAHb+SPAmKFp02ute6b84K7=15Dm57rWBRo5hcrpcxfDg9eS_fA@mail.gmail.com>
Message-ID: <CAKr4wiRrDtaWeeydL3MGXmeHeysqcBxcYgDXiUKqpzK448BRYw@mail.gmail.com>

On 27 June 2012 15:02, Aneurin Price <aneurin.price at gmail.com> wrote:
> I can keep system/qemu/kvm at the working version for now, but
> obviously that's not a solution long-term. Any ideas?

I, myself, am waiting on that issue thread for an answer ... hopefully
someone else can reproduce it and find the fault.

I'll pass on any ideas I have when I get them :)

Jon


From gordon.w.ross at gmail.com  Wed Jun 27 20:31:45 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Wed, 27 Jun 2012 16:31:45 -0400
Subject: [OpenIndiana-discuss] Problem/Question on mount lofs:
In-Reply-To: <4FEAE0BC.6040604@cos.ru>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
	<4FE9F71E.6040205@cos.ru>
	<CAD0Ztp23NLY8re5gjSwTs2uLDs2T-daHKvCi1xmiXHkKReX+=Q@mail.gmail.com>
	<4FEAE0BC.6040604@cos.ru>
Message-ID: <CAD0Ztp1_+u5gtQNyk1k=5Cv-X47+dEk3jxpd6LiVwPsn7n31uA@mail.gmail.com>

On Wed, Jun 27, 2012 at 6:30 AM, Jim Klimov <jimklimov at cos.ru> wrote:
>
> And the CIFS clients (windows, linux, etc.) can mount this
> child in the sub-path of a share? I.e. these two datasets:
> \\SERVER\share ? ? ? ?== tank/export/share
> \\SERVER\share\child ?== tank/export/share/child

No, just one share: \\server\share
but share/child is accessible when it was not before.

-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From jimklimov at cos.ru  Wed Jun 27 21:15:43 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Thu, 28 Jun 2012 01:15:43 +0400
Subject: [OpenIndiana-discuss] Problem/Question on mount lofs:
In-Reply-To: <CAD0Ztp1_+u5gtQNyk1k=5Cv-X47+dEk3jxpd6LiVwPsn7n31uA@mail.gmail.com>
References: <4FE9AEA3.6060306@gmx.de> <4FE9B081.3030500@kit.edu>
	<4FE9F71E.6040205@cos.ru>
	<CAD0Ztp23NLY8re5gjSwTs2uLDs2T-daHKvCi1xmiXHkKReX+=Q@mail.gmail.com>
	<4FEAE0BC.6040604@cos.ru>
	<CAD0Ztp1_+u5gtQNyk1k=5Cv-X47+dEk3jxpd6LiVwPsn7n31uA@mail.gmail.com>
Message-ID: <4FEB77FF.6030004@cos.ru>

2012-06-28 0:31, Gordon Ross ?????:
> On Wed, Jun 27, 2012 at 6:30 AM, Jim Klimov <jimklimov at cos.ru> wrote:
>>
>> And the CIFS clients (windows, linux, etc.) can mount this
>> child in the sub-path of a share? I.e. these two datasets:
>> \\SERVER\share        == tank/export/share
>> \\SERVER\share\child  == tank/export/share/child
>
> No, just one share: \\server\share
> but share/child is accessible when it was not before.
>

I stand by my assessment that this would be a cool addition
to upstream illumos for general public's benefit! ;)

Thanks,
//Jim Klimov


From drs.grid at gmail.com  Thu Jun 28 01:26:50 2012
From: drs.grid at gmail.com (drsgrid)
Date: Wed, 27 Jun 2012 18:26:50 -0700
Subject: [OpenIndiana-discuss] Static routes
Message-ID: <CAOFhruY-znwp0xK=6Eb+Sqxzab=uMS51X3SX4CqO+hZJ3BjnJA@mail.gmail.com>

Im not a full time admin but im trying to use rsync across 10GE (or even
1GE -as a starting point) from one openindana box to another. Both machines
are also connected to a broader network to receive updates (eth0)  but im
trying to use a xover cable for eth1 so i can rsync across and not take up
a lot of bandwith on the broader network. From my reading think I need to
setup a static route on eth1.   All my ip addresses are static: -

machineA(eth0)=192.168.0.100, machineA(eth1)=192.168.10.2
machineB(eth0)=192.168.0.108, machineB(eth1)=192.168.10.1

how do i setup the machines so that i can do an rsync across the
192.168.10.x domain so as not to disturb bandwith on the 192.168.0.x domain?

From sardonic.smiles at gmail.com  Thu Jun 28 03:29:03 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Wed, 27 Jun 2012 23:29:03 -0400
Subject: [OpenIndiana-discuss] Static routes
In-Reply-To: <CAOFhruY-znwp0xK=6Eb+Sqxzab=uMS51X3SX4CqO+hZJ3BjnJA@mail.gmail.com>
References: <CAOFhruY-znwp0xK=6Eb+Sqxzab=uMS51X3SX4CqO+hZJ3BjnJA@mail.gmail.com>
Message-ID: <CAPVmm=buG7gkHLJt9zxHajNWmtmZ5_r1+EjpYSrg+EMVBam1PQ@mail.gmail.com>

Set the IP, and a subnet mask; leave routing alone.

For example, I have 192.168.2.x/24 as my internet facing connection. The
direct link between a windows server and my OI box is 192.168.20.x/30. So
the Windows box is .1 and the OI box is .2. No static routes needed. Just
let the two OS's handle it. All traffic properly goes where it should.
On Jun 27, 2012 9:27 PM, "drsgrid" <drs.grid at gmail.com> wrote:

> Im not a full time admin but im trying to use rsync across 10GE (or even
> 1GE -as a starting point) from one openindana box to another. Both machines
> are also connected to a broader network to receive updates (eth0)  but im
> trying to use a xover cable for eth1 so i can rsync across and not take up
> a lot of bandwith on the broader network. From my reading think I need to
> setup a static route on eth1.   All my ip addresses are static: -
>
> machineA(eth0)=192.168.0.100, machineA(eth1)=192.168.10.2
> machineB(eth0)=192.168.0.108, machineB(eth1)=192.168.10.1
>
> how do i setup the machines so that i can do an rsync across the
> 192.168.10.x domain so as not to disturb bandwith on the 192.168.0.x
> domain?
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>

From yuri.pankov at gmail.com  Thu Jun 28 03:34:33 2012
From: yuri.pankov at gmail.com (Yuri Pankov)
Date: Thu, 28 Jun 2012 07:34:33 +0400
Subject: [OpenIndiana-discuss] Static routes
In-Reply-To: <CAOFhruY-znwp0xK=6Eb+Sqxzab=uMS51X3SX4CqO+hZJ3BjnJA@mail.gmail.com>
References: <CAOFhruY-znwp0xK=6Eb+Sqxzab=uMS51X3SX4CqO+hZJ3BjnJA@mail.gmail.com>
Message-ID: <4FEBD0C9.1090405@gmail.com>

On Wed, 27 Jun 2012 18:26:50 -0700, drsgrid wrote:
> Im not a full time admin but im trying to use rsync across 10GE (or even
> 1GE -as a starting point) from one openindana box to another. Both machines
> are also connected to a broader network to receive updates (eth0)  but im
> trying to use a xover cable for eth1 so i can rsync across and not take up
> a lot of bandwith on the broader network. From my reading think I need to
> setup a static route on eth1.   All my ip addresses are static: -
> 
> machineA(eth0)=192.168.0.100, machineA(eth1)=192.168.10.2
> machineB(eth0)=192.168.0.108, machineB(eth1)=192.168.10.1
> 
> how do i setup the machines so that i can do an rsync across the
> 192.168.10.x domain so as not to disturb bandwith on the 192.168.0.x domain?
While interface names (eth0, eth1) look suspicious... :-) This has
nothing to do with routing, just tell rsync to bind to correct
interface/IP address (I hope there's an option).


From mike.laspina at laspina.ca  Thu Jun 28 03:37:14 2012
From: mike.laspina at laspina.ca (Mike La Spina)
Date: Wed, 27 Jun 2012 22:37:14 -0500
Subject: [OpenIndiana-discuss] "shareiscsi" and COMSTAR
In-Reply-To: <4FEAD8A0.50009@cos.ru>
References: <4FEA1FF2.9060402@cos.ru><8F607366E3C0F9499212649291E0BD640D4715@MS1.laspina.ca>
	<4FEAD8A0.50009@cos.ru>
Message-ID: <8F607366E3C0F9499212649291E0BD640D4718@MS1.laspina.ca>



2012-06-27 4:51, Mike La Spina wrote:
>> Hi Jim,
>>
>>> 1) Is COMSTAR still not-integrated with shareiscsi ZFS attributes?
>>>     Or can the pool use the attribute, and the correct (new COMSTAR)
>>>     iSCSI target daemon will fire up?
>>
>> COMSTAR is not integrated with ZFS and it will ignore the ZFS props.
>
>Well, that was the case a couple of years ago when we played with the
newly released COMSTAR. We did not know whether the progress marched on
(to integrate ZFS >with COMSTAR) - hence the questions ;)
>
>> What is the release of the old host OS?
>
>
>SXCE snv_117... Well, it may be more than a couple of years :)

Yes very early COMSTAR code :)

>>
>> I strongly suggest you record the old iqn target names and the LU's 
>> they are mapped to, as well the LU GUID is helpful.
>
>Probably so, if only to check that the SMF/file-based config migration
attempt went well.
>
>> Snapshots on zvols are your friends!
>
>Unfortunately, they are not. The OS upgrade is part of the box's
migration to larger new drives, and so far it is very restrained on free
disk space in the pool. >ZVOL snapshots reserve the zvol size so as to
guarantee the ability to rewrite the whole zvol contents safely, and the
box can not afford that much wasted space. >Ability to do these
snapshots is indeed one of the many reasons for the overall upgrade
(HW+SW).

Then I would at minimum suggest a VM VMFS file level backup outside the
storage host scope.

Other option is to thin it out and free up that unused space then
snapshot it.
zfs set refreservation=none pool/esx/vol0
 
>>
>>
>>> 2) What would be the best way to migrate iSCSI server configuration
>>>     (LUs, views, allowed client lists, etc.) - is it sufficient to
>>>     just export the SMF config of "stmf" service, or do I also need
>>>     some other services and/or files (/etc/iscsi, something else?)
>>
>> This really depends on your current configuration .. can you provide 
>> some specifics of the existing targets/initiators?
>
>The targets are now a few zvols on the snv_117 box, served by COMSTAR
(svc:/system/stmf:default, svc:/network/iscsi/target:default).
>The service svc:/network/iscsi/initiator:default is also online, but it
was AFAIK used for testing and does not normally attach remote LUNs.
>
>Initiators that I know of are from free ESXi hosts, I'm uncertain about
the version.

It's fairly strait forward. You have two possible options.

1) Backup the manifest method.
"It will migrate every property and attribute, be it good or bad for the
new COMSTAR code"
"Suggest you look at and keep a diff on the manifest files"
"I have used this successfully from snv_134 to snv_148""

On the old host:
svccfg export -a stmf > stmf.cfg

note the -a parm "It will include the LU info and other elements."

if your moving the pool vdevs or creating a clean OS image with
importing (otherwise in-place = done)

On the new host:
svccfg export -a stmf > original-stmf.cfg 
svcadm disable stmf
svccfg delete stmf
svccfg import stmf.cfg
svcadm refresh stmf
svcadm enable stmf

2) Recreate the stmf properties method.
"Need to ensure your LU numbers are correct before the ESX host scans
them or you may have serious VMFS problems" 
"Ensures a healthy clean stmf manifest"  
"If you have more than one interface with an IP bound you should define
which IP(s) should be associated to the target using a portal group."

itadm create-tpg tpg1 ip? (assign the appropriate interfaces)
itadm create-target previous.target.iqn.name -t tpg1
itadm create-initatitor esx.iqn.initiator.name
stmfadm create-hg esx1
stmfadm add-hg-member -g esx1 esx.iqn.initiator.name

stmfadm import-lu /dev/zvol/rdsk/sp/store0/vol0
stmfadm add-view -n lu# lu-naa

...

Regards,
Mike



From dave.koelmeyer at davekoelmeyer.co.nz  Thu Jun 28 07:18:34 2012
From: dave.koelmeyer at davekoelmeyer.co.nz (Dave Koelmeyer)
Date: Thu, 28 Jun 2012 19:18:34 +1200
Subject: [OpenIndiana-discuss] OpenIndiana and application keychain
	access
In-Reply-To: <5aa3d542-c01f-c48a-91d5-8c955beb0e9b@me.com>
References: <5aa3d542-c01f-c48a-91d5-8c955beb0e9b@me.com>
Message-ID: <4FEC054A.2030202@davekoelmeyer.co.nz>

On 04/27/11 01:34 PM, Dave Koelmeyer wrote:
> Hi All,
>
> More of an OpenSolaris query originally, as I've always had this 
> problem, but still have it on oi_?147 x86. In certain applications 
> such as Pidgin and the bundled vncserver,. I have saved my password 
> (for various chat accounts in the former, and for password 
> authentication for client connections for the latter).
>
> However, these are apparently not unlocked by the login keychain, 
> consequently on every desktop login to the system I am prompted to 
> supply a password to unlock the keychain on launching these particular 
> applications.
>
> Does anyone know how to "shut this up" so to speak, while still being 
> able to have saved credentials in Pidgin etc.?

Thought I'd try again - I still see this on oi_151a, surely someone else 
has? Any suggested fixes welcome - having vncserver refuse to unlock on 
login is driving me around the bend.

Cheers,

-- 
Dave Koelmeyer
http://www.davekoelmeyer.co.nz



From jmcentee at stirling-dynamics.com  Thu Jun 28 13:57:45 2012
From: jmcentee at stirling-dynamics.com (John McEntee)
Date: Thu, 28 Jun 2012 14:57:45 +0100
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
	regularly hangs.
In-Reply-To: <8F607366E3C0F9499212649291E0BD640D46E9@MS1.laspina.ca>
References: <001501cd48a2$984e9100$c8ebb300$@com><8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>	<007001cd4942$9ffb7b20$dff27160$@com>
	<8F607366E3C0F9499212649291E0BD640D46E9@MS1.laspina.ca>
Message-ID: <017e01cd5535$ff356750$fda035f0$@com>

Ok, and update on my progress as I have not fixed it yet.

The domain controller the OpenIndiana server is connected to  had problems
with the file replication, I cleared the cache and it fixed that problem.
The occurrence of the CIFS server on OpenIndiana dropped dramatically, but
still exist. I found and ran the Microsoft environment IT health check tool,
that had problems contacting another domain controller, stopping the tool
from running (WMI errors), if fixed those and now the toll runs fine with no
significant errors. (complains about the network config of couple of
pre-production exchange servers). This seems to have reduced the hangs even
more.

This week most the users are on a training course so it is not being heavily
used either, but I have a couple of users doing a tcpdump/snoop/wireshark to
a ringbuffer so I can hopefully get a packet trace.

What I have noticed is an ulimit -a returns

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
file size               (blocks, -f) unlimited
open files                      (-n) 256
pipe size            (512 bytes, -p) 10
stack size              (kbytes, -s) 10240
cpu time               (seconds, -t) unlimited
max user processes              (-u) 29995
virtual memory          (kbytes, -v) unlimited


Is the open files going to cause CIFS a problem, 256 seems a bit low, could
easily hit that limit if it is shared amongst all the users.


I also have 2 scripts running every minute via cron (from a linux box). One
copies a 10 MB file via cifs the other via nfs, neither have been delayed
for more than 5 seconds, normally completes with 1 second. These are done to
their own zfs file systems at the moment, but I can foresee having to point
them at the production filesystem if it does not detect the freezes that the
users report.

John

-----Original Message-----
From: Mike La Spina [mailto:mike.laspina at laspina.ca] 
Sent: 14 June 2012 04:43
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Access to ZFS viz CIFS fromwindows
regularlyhangs.


> Does the suspend event only occur on SMB clients or does it impact the
other storage clients when triggered by the Windows clients?

It does not seem to effect the vmware hosted machines via nfs. Next time it
hangs I will try a nfs transfer to it.
- If this is correct its a further indication of an AD/SMB issue, but not
verified at this point.

> Any domain controller event errors?

Yes there are, I will go and resolve this first before I go any further.

- Highly suspect this is where you need to focus.
- This error is suspicious and does look like a issue on the domain. 
- Jun 12 11:26:07 ringwood smbd[6032]: [ID 702911 daemon.notice]
smbd_dc_update: stirling-dynamics.com: located red
- Jun 12 11:34:17 ringwood smbd[6032]: [ID 702911 daemon.error]
smbrdr_exchange[4]: failed (INVALID_HANDLE)
- I would look further back in time and see if it correlates with the
suspended access event. That would define a clear resolution path.

> dmsg output?

Attached - is this the correct etiquette?

- Jun 11 21:38:18 ringwood fmd: [ID 377184 daemon.error] SUNW-MSG-ID:
SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
- Jun 11 21:38:18 ringwood EVENT-TIME: Mon Jun 11 21:38:18 BST 2012
- Jun 11 21:38:18 ringwood PLATFORM: S5520HC, CSN: ............,
HOSTNAME: ringwood
- Jun 11 21:38:18 ringwood SOURCE: software-diagnosis, REV: 0.1
- Jun 11 21:38:18 ringwood EVENT-ID:
cc9f2029-a779-cbd2-e425-8ffbaa19f639
- Jun 11 21:38:18 ringwood DESC: A service failed - a method is failing in a
retryable manner but too often.
- Jun 11 21:38:18 ringwood   Refer to http://sun.com/msg/SMF-8000-YX for
more information.
- Jun 11 21:38:18 ringwood AUTO-RESPONSE: The service has been placed into
the maintenance state.
- Jun 11 21:38:18 ringwood IMPACT: svc:/application/time-slider:default
is unavailable.

- The time slider snapshot service failed? Or was it stopped manually?

> fmdump -eV output?

Also attached.
- Nothing remarkable

> uname -a output?

SunOS ringwood 5.11 oi_148 i86pc i386 i86pc Solaris

> Have you attempted a packet capture of the event?
> snoop -o smb-client.cap <clientip>

Not yet, It could be caputureing for 4 hours before it happens, I will
resolve the AD domain issue first.
- Good approach. 4 hours of packet tracing is hard to digest! It would
certainly need to be truncated down to the trigger event. 

- Mike



_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly confidential
and are solely for the person(s) at the e-mail address(es) above. If you are
not an addressee, you may not disclose, distribute, copy or use this e-mail,
and we request that you send an e-mail to admin at stirling-dynamics.com and
delete this e-mail.  Stirling Dynamics Ltd. accepts no legal liability for
the contents of this e-mail including any errors, interception or
interference, as internet communications are not secure.  Any views or
opinions presented are solely those of the author and do not necessarily
represent those of Stirling Dynamics Ltd. Registered In England No. 2092114
Registered
Office: 26 Regent Street, Clifton, Bristol. BS8 4HG VAT no. GB 464 6551
29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.

_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss


_______________________________________________________________________

The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to admin at stirling-dynamics.com and delete this e-mail.  Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure.  Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. Registered In England No. 2092114 Registered Office: 26 Regent Street, Clifton, Bristol. BS8 4HG
VAT no. GB 464 6551 29
_______________________________________________________________________

This e-mail has been scanned for all viruses MessageLabs.


From jimklimov at cos.ru  Thu Jun 28 14:13:55 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Thu, 28 Jun 2012 18:13:55 +0400
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
 regularly hangs.
In-Reply-To: <017e01cd5535$ff356750$fda035f0$@com>
References: <001501cd48a2$984e9100$c8ebb300$@com>
	<8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>
	<007001cd4942$9ffb7b20$dff27160$@com>
	<8F607366E3C0F9499212649291E0BD640D46E9@MS1.laspina.ca>
	<017e01cd5535$ff356750$fda035f0$@com>
Message-ID: <4FEC66A3.1070403@cos.ru>

2012-06-28 17:57, John McEntee wrote:
> What I have noticed is an ulimit -a returns
>
> core file size          (blocks, -c) unlimited
> data seg size           (kbytes, -d) unlimited
> file size               (blocks, -f) unlimited
> open files                      (-n) 256
> pipe size            (512 bytes, -p) 10
> stack size              (kbytes, -s) 10240
> cpu time               (seconds, -t) unlimited
> max user processes              (-u) 29995
> virtual memory          (kbytes, -v) unlimited
>
>
> Is the open files going to cause CIFS a problem, 256 seems a bit low, could
> easily hit that limit if it is shared amongst all the users.

Note that the limits are per-process (wherever there are OS limits,
they are usually unreachably high), and these represent what limits
your shell has - from system defaults and/or its profile. While a
root user can raise the limits, unprivileged users can only lower
them.

For processes started with initscripts (and this likely holds true
for SMF method scripts) the non-standard ulimits were set in the
script. This might be the case, say, for a script which starts your
Samba server, or more frequently for webservers and J2EE appservers
(each network socket needs a file descriptor). Lack of descriptors
should manifest in the logs or stderr as inability to open files.

I am not sure if this is relevant for Kernel CIFS at all, but you
can try to tune its SMF start method, and/or see if similar settings
can be done with "projects", privileges and other Solaris stuff.

HTH,
//Jim Klimov


From carlsonj at workingcode.com  Thu Jun 28 15:01:21 2012
From: carlsonj at workingcode.com (James Carlson)
Date: Thu, 28 Jun 2012 11:01:21 -0400
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from
 windows	regularly hangs.
In-Reply-To: <017e01cd5535$ff356750$fda035f0$@com>
References: <001501cd48a2$984e9100$c8ebb300$@com><8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>	<007001cd4942$9ffb7b20$dff27160$@com>	<8F607366E3C0F9499212649291E0BD640D46E9@MS1.laspina.ca>
	<017e01cd5535$ff356750$fda035f0$@com>
Message-ID: <4FEC71C1.4010609@workingcode.com>

John McEntee wrote:
> Is the open files going to cause CIFS a problem, 256 seems a bit low, could
> easily hit that limit if it is shared amongst all the users.

"man ulimit" and "man getrlimit" for details.  That's a limit on the
number of file descriptors open in any one user process.  It has nothing
to do with the kernel, and shouldn't have anything to do with CIFS.

The default is 256 in order to keep binary compatibility with
fileno(3C).  That library "function" was once (very long ago) defined as
a macro that read a uchar_t directly from the FILE * pointer.  In the
modern implementation, it is a function, and allows a huge number of
open files, but if you were running ancient SunOS binaries, you would
want to be able to avoid problems.

In any event, 256 is darned large for most reasonable applications,
where pfiles will show a few dozen open descriptors.  You can bump it up
if you like; the normal maximum is 64K.  I would recommend bumping it up
*only* when launching programs that really need to have a large number
of descriptors open at once, such as single-process web servers.
Otherwise, a malfunctioning program can really bog things down.  (I'd
expect that most such programs already use setrlimit(2) to do something
reasonable here ...)

-- 
James Carlson         42.703N 71.076W         <carlsonj at workingcode.com>


From dkjar at elmira.edu  Thu Jun 28 15:31:25 2012
From: dkjar at elmira.edu (Daniel Kjar)
Date: Thu, 28 Jun 2012 11:31:25 -0400
Subject: [OpenIndiana-discuss] can't mirror these disks
Message-ID: <4FEC78CD.3030600@elmira.edu>

Anyone have a clue why?  This is on 151a4

dsk at bio1:/# zpool attach home c8t0d0 c8t1d0
cannot attach c8t1d0 to c8t0d0: devices have different sector alignment
c8t1do:

ascii name  = <ATA-ST1500DM003-9YN1-CC4C-1.36TB>
bytes/sector    =  512
sectors = 2930277167
accessible sectors = 2930277134
Part      Tag    Flag     First Sector          Size          Last Sector
   0        usr    wm               256         1.36TB 2930260750
   1 unassigned    wm                 0            0 0
   2 unassigned    wm                 0            0 0
   3 unassigned    wm                 0            0 0
   4 unassigned    wm                 0            0 0
   5 unassigned    wm                 0            0 0
   6 unassigned    wm                 0            0 0
   8   reserved    wm        2930260751         8.00MB 2930277134

c8t0d0:

Volume name = <        >
ascii name  = <ATA-ST31500541AS-CC34-1.36TB>
bytes/sector    =  512
sectors = 2930277167
accessible sectors = 2930277134
Part      Tag    Flag     First Sector          Size          Last Sector
   0        usr    wm               256         1.36TB 2930260750
   1 unassigned    wm                 0            0 0
   2 unassigned    wm                 0            0 0
   3 unassigned    wm                 0            0 0
   4 unassigned    wm                 0            0 0
   5 unassigned    wm                 0            0 0
   6 unassigned    wm                 0            0 0
   8   reserved    wm        2930260751         8.00MB 2930277134





-- 
Dr. Daniel Kjar
Assistant Professor of Biology
Division of Mathematics and Natural Sciences
Elmira College
1 Park Place
Elmira, NY 14901
607-735-1826
http://faculty.elmira.edu/dkjar

"...humans send their young men to war; ants send their old ladies"
	-E. O. Wilson




From jsowoc at gmail.com  Thu Jun 28 16:37:30 2012
From: jsowoc at gmail.com (Jan Owoc)
Date: Thu, 28 Jun 2012 10:37:30 -0600
Subject: [OpenIndiana-discuss] can't mirror these disks
In-Reply-To: <4FEC78CD.3030600@elmira.edu>
References: <4FEC78CD.3030600@elmira.edu>
Message-ID: <CADCwuEYuN1HwWRO6UBCDqLCdDXm=AMGq+5hW22c6Bzeui2SX-Q@mail.gmail.com>

On Thu, Jun 28, 2012 at 9:31 AM, Daniel Kjar <dkjar at elmira.edu> wrote:
> Anyone have a clue why? ?This is on 151a4
>
> dsk at bio1:/# zpool attach home c8t0d0 c8t1d0
> cannot attach c8t1d0 to c8t0d0: devices have different sector alignment
> c8t1do:
>
> ascii name ?= <ATA-ST1500DM003-9YN1-CC4C-1.36TB>
[...]
> ascii name ?= <ATA-ST31500541AS-CC34-1.36TB>

I had this error when one of my drives had 512b native sectors and the
other had 4k native sectors. I don't think I was able to do a mirror
either direction (i.e. you installed to 512b and are trying to mirror
onto 4k, and I think I also tried installing on 4k and mirroring to
512b with the same error you have).

A quick Internet search reveals that the "...DM003" has 4k sectors
natively [1] while "...541AS" has 512b sectors natively [2].

[1] http://www.seagate.com/staticfiles/support/docs/manual/desktop/Barracuda%207200.14/100686584d.pdf
[2] http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%20LP/100564361a.pdf
(look for Table 1 ~page 10-11)

I wasn't able to find a solution, so I now have a non-mirrored root
pool. Does anyone know how to override this sector alignment issue?

Jan


From jimklimov at cos.ru  Thu Jun 28 17:02:57 2012
From: jimklimov at cos.ru (Jim Klimov)
Date: Thu, 28 Jun 2012 21:02:57 +0400
Subject: [OpenIndiana-discuss] can't mirror these disks
In-Reply-To: <CADCwuEYuN1HwWRO6UBCDqLCdDXm=AMGq+5hW22c6Bzeui2SX-Q@mail.gmail.com>
References: <4FEC78CD.3030600@elmira.edu>
	<CADCwuEYuN1HwWRO6UBCDqLCdDXm=AMGq+5hW22c6Bzeui2SX-Q@mail.gmail.com>
Message-ID: <4FEC8E41.8070107@cos.ru>

2012-06-28 20:37, Jan Owoc wrote:
> I wasn't able to find a solution, so I now have a non-mirrored root
> pool. Does anyone know how to override this sector alignment issue?

Apparently, only by creating a new rpool on the 4KB drive
and zfs-sending data to it from the 512b drive. The idea
was discussed in detail a few times in the past few weeks
on this list and/or on zfs-discuss.

What is strange to me is the news that ZFS would refuse to
attach a 512b disk as a mirror to a 4KB TLVDEV (the rpool).
I did not test this myself, but it sounds like a bug - a
512b disk should certainly receive 4KB writes safely and
quickly (the opposite is not necessarily true) ;)

Did you certainly test that it doesn't work? If so - I think
some noise is due on the lists ;)

Also, for a bit more safety against data corruptions on a
single-disk rpool, you might want to use "copies=2" (or =3)
and rewrite the data to the pool (i.e. zfs-send|zfs-recv
within the pool) - in this case the userdata blocks would
be cloned like metadata is, and corruption (or mis-read)
of a single sector would not cause big problems.
Saved me on my home NAS quite a few times - nearly every
scrub finds a few CKSUM errors on the old root disk :)

HTH,
//Jim Klimov


From dkjar at elmira.edu  Thu Jun 28 19:32:44 2012
From: dkjar at elmira.edu (Daniel Kjar)
Date: Thu, 28 Jun 2012 15:32:44 -0400
Subject: [OpenIndiana-discuss] can't mirror these disks
In-Reply-To: <4FEC8E41.8070107@cos.ru>
References: <4FEC78CD.3030600@elmira.edu>
	<CADCwuEYuN1HwWRO6UBCDqLCdDXm=AMGq+5hW22c6Bzeui2SX-Q@mail.gmail.com>
	<4FEC8E41.8070107@cos.ru>
Message-ID: <4FECB15C.8070100@elmira.edu>

This is not good news.  I guess i will do the send and move to the newer 
disk and get another new disk for that mirrored pool.



On 06/28/12 01:02 PM, Jim Klimov wrote:
> 2012-06-28 20:37, Jan Owoc wrote:
>> I wasn't able to find a solution, so I now have a non-mirrored root
>> pool. Does anyone know how to override this sector alignment issue?
>
> Apparently, only by creating a new rpool on the 4KB drive
> and zfs-sending data to it from the 512b drive. The idea
> was discussed in detail a few times in the past few weeks
> on this list and/or on zfs-discuss.
>
> What is strange to me is the news that ZFS would refuse to
> attach a 512b disk as a mirror to a 4KB TLVDEV (the rpool).
> I did not test this myself, but it sounds like a bug - a
> 512b disk should certainly receive 4KB writes safely and
> quickly (the opposite is not necessarily true) ;)
>
> Did you certainly test that it doesn't work? If so - I think
> some noise is due on the lists ;)
>
> Also, for a bit more safety against data corruptions on a
> single-disk rpool, you might want to use "copies=2" (or =3)
> and rewrite the data to the pool (i.e. zfs-send|zfs-recv
> within the pool) - in this case the userdata blocks would
> be cloned like metadata is, and corruption (or mis-read)
> of a single sector would not cause big problems.
> Saved me on my home NAS quite a few times - nearly every
> scrub finds a few CKSUM errors on the old root disk :)
>
> HTH,
> //Jim Klimov
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

-- 
Dr. Daniel Kjar
Assistant Professor of Biology
Division of Mathematics and Natural Sciences
Elmira College
1 Park Place
Elmira, NY 14901
607-735-1826
http://faculty.elmira.edu/dkjar

"...humans send their young men to war; ants send their old ladies"
	-E. O. Wilson






From gordon.w.ross at gmail.com  Thu Jun 28 19:36:57 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 28 Jun 2012 15:36:57 -0400
Subject: [OpenIndiana-discuss] Access to ZFS viz CIFS from windows
 regularly hangs.
In-Reply-To: <017e01cd5535$ff356750$fda035f0$@com>
References: <001501cd48a2$984e9100$c8ebb300$@com>
	<8F607366E3C0F9499212649291E0BD640D46E8@MS1.laspina.ca>
	<007001cd4942$9ffb7b20$dff27160$@com>
	<8F607366E3C0F9499212649291E0BD640D46E9@MS1.laspina.ca>
	<017e01cd5535$ff356750$fda035f0$@com>
Message-ID: <CAD0Ztp2ryBTROdOaxi529CB8h-Dh0UbqSBdBmga7bX2Eg_qNLQ@mail.gmail.com>

On Thu, Jun 28, 2012 at 9:57 AM, John McEntee
<jmcentee at stirling-dynamics.com> wrote:
> Ok, and update on my progress as I have not fixed it yet.
> [...]
>
> I also have 2 scripts running every minute via cron (from a linux box). One
> copies a 10 MB file via cifs the other via nfs, neither have been delayed
> for more than 5 seconds, normally completes with 1 second. These are done to
> their own zfs file systems at the moment, but I can foresee having to point
> them at the production filesystem if it does not detect the freezes that the
> users report.
>
> John

You'll need to gather some data when the slowdown happens.
I would start at the network with a snoop capture that shows
both the clients involved and the AD server in use.

There are some cases where the SMB server currently
needs to go talk to an AD server to find out the name for
the account represented by some SID, etc. and that can
cause temporary pauses like you see.  If it's anything
like that, the network trace will show it happening.

-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From heinz at licenser.net  Thu Jun 28 20:24:43 2012
From: heinz at licenser.net (Heinz N. Gies)
Date: Thu, 28 Jun 2012 22:24:43 +0200
Subject: [OpenIndiana-discuss] Erlang and Solaris SMF's
Message-ID: <A8928933-7F15-4199-9A77-D493D2D31F05@licenser.net>

I am sure someone has asked this before but I googled for the last hour and have found nothing but a discussion that didn't provide a answer.

My problem is that I want to run a erlang otp release as a SMF service, now the monitoring does not work properly, what I discovered from the discussion mentioned is that it seems the problem that solaris things the release is still running since the epmd is still up and good even so the application might not.

What would be the best solution for this? My first guess was to create a empd service but that kind of gets ugly once you've more then one erlang release running.

Regards,
Heinz
--
Heinz N. Gies
heinz at licenser.net
http://licenser.net



From me at cs.Stanford.EDU  Thu Jun 28 21:08:01 2012
From: me at cs.Stanford.EDU (Martin Frost)
Date: Thu, 28 Jun 2012 14:08:01 -0700
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS over CIFS
Message-ID: <E1SkLwX-0003dM-Ia@sunburn.Stanford.EDU>

I'm running oi_148 as a fileserver, exporting via NFS and the
kernel CIFS service for ZFS.

But Windows users (XP and probably all Windows versions) are unable to
write files from any MS Office applications into the shares from ZFS.
They always get: "Access denied.  Contact your administrator."  Same
result whether they're trying to overwrite a file or write a new file.

Any ideas what's causing that?  This is driving me crazy.  I've
seen the same problem under Linux with Samba, where disabling
locking seemed to help.

After that error, the users save the file to the local disk and copy
it over the CIFS connection into the ZFS system successfully.  So they
clearly have write access into ZFS from Windows, and the filesystem
has lots of free space, but Office can't write any files to ZFS.  I
assume this is some sort of locking problem.  I have nbmand=on, which
is what I've read it should be set to for CIFS sharing.

The directories and files they're trying to edit are owned by the
actual user (defined by matching passwd and smbpasswd entries on the
OI machine) and have 700 permissions and full_set ACLS:

	       owner@:rwxpdDaARWcCos:fd-----:allow
	    everyone@:rwxpdDaARWcCos:fd-----:deny

Some relevant services:

online         Feb_11   svc:/network/shares/group:smb
online         Mar_01   svc:/network/smb/server:default
online         Feb_27   svc:/network/nfs/status:default
online         Feb_27   svc:/network/nfs/rquota:default
online         Feb_27   svc:/network/nfs/nlockmgr:default
online         May_08   svc:/network/nfs/mapid:default
online         May_09   svc:/network/nfs/server:default
online         May_09   svc:/network/nfs/cbd:default

Here are most properties of the filesystem:

NAME         PROPERTY         VALUE              SOURCE
gname/thefs  mounted          yes                -
gname/thefs  reservation      none               default
gname/thefs  mountpoint       /gname/thefs       default
gname/thefs  sharenfs         sec=sys,rw=gname   local
gname/thefs  checksum         on                 default
gname/thefs  compression      gzip               inherited from gname
gname/thefs  atime            off                inherited from gname
gname/thefs  devices          on                 default
gname/thefs  exec             on                 default
gname/thefs  readonly         off                default
gname/thefs  zoned            off                default
gname/thefs  aclinherit       passthrough        local
gname/thefs  canmount         on                 default
gname/thefs  xattr            on                 default
gname/thefs  version          5                  -
gname/thefs  utf8only         off                -
gname/thefs  normalization    none               -
gname/thefs  casesensitivity  mixed              -
gname/thefs  vscan            off                default
gname/thefs  nbmand           on                 local
gname/thefs  sharesmb         name=thefs         local
gname/thefs  refquota         none               default
gname/thefs  refreservation   none               default
gname/thefs  logbias          latency            default
gname/thefs  dedup            off                default
gname/thefs  mlslabel         none               default
gname/thefs  sync             standard           default

Thanks for any suggestions!

Martin


From gordon.w.ross at gmail.com  Thu Jun 28 22:14:53 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 28 Jun 2012 18:14:53 -0400
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS over
	CIFS
In-Reply-To: <E1SkLwX-0003dM-Ia@sunburn.Stanford.EDU>
References: <E1SkLwX-0003dM-Ia@sunburn.Stanford.EDU>
Message-ID: <CAD0Ztp0L7DUwhoLwxBrpyrRb5t4yHqmAyKe63y_eCRuXqc7K+g@mail.gmail.com>

On Thu, Jun 28, 2012 at 5:08 PM, Martin Frost <me at cs.stanford.edu> wrote:
> I'm running oi_148 as a fileserver, exporting via NFS and the
> kernel CIFS service for ZFS.
>
> But Windows users (XP and probably all Windows versions) are unable to
> write files from any MS Office applications into the shares from ZFS.
> They always get: "Access denied. ?Contact your administrator." ?Same
> result whether they're trying to overwrite a file or write a new file.
>
> Any ideas what's causing that? ?This is driving me crazy. ?I've
> seen the same problem under Linux with Samba, where disabling
> locking seemed to help.
>
> After that error, the users save the file to the local disk and copy
> it over the CIFS connection into the ZFS system successfully. ?So they
> clearly have write access into ZFS from Windows, and the filesystem
> has lots of free space, but Office can't write any files to ZFS. ?I
> assume this is some sort of locking problem. ?I have nbmand=on, which
> is what I've read it should be set to for CIFS sharing.
>
> The directories and files they're trying to edit are owned by the
> actual user (defined by matching passwd and smbpasswd entries on the
> OI machine) and have 700 permissions and full_set ACLS:
>
> ? ? ? ? ? ? ? owner@:rwxpdDaARWcCos:fd-----:allow
> ? ? ? ? ? ?everyone@:rwxpdDaARWcCos:fd-----:deny

You are always a member of the "everyone" group, so that deny ACE is
killing your access.


-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From me at cs.Stanford.EDU  Fri Jun 29 01:17:42 2012
From: me at cs.Stanford.EDU (Martin Frost)
Date: Thu, 28 Jun 2012 18:17:42 -0700
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS
	over	CIFS
In-Reply-To: <CAD0Ztp0L7DUwhoLwxBrpyrRb5t4yHqmAyKe63y_eCRuXqc7K+g@mail.gmail.com>
	(message from Gordon Ross on Thu, 28 Jun 2012 18:14:53 -0400)
Message-ID: <E1SkPqA-0000AB-Vo@sunburn.Stanford.EDU>

 > Date: Thu, 28 Jun 2012 18:14:53 -0400
 > From: Gordon Ross <gordon.w.ross at gmail.com>
 > 
 > On Thu, Jun 28, 2012 at 5:08 PM, Martin Frost <me at cs.stanford.edu> wrote:
 > > I'm running oi_148 as a fileserver, exporting via NFS and the
 > > kernel CIFS service for ZFS.
 > >
 > > But Windows users (XP and probably all Windows versions) are unable to
 > > write files from any MS Office applications into the shares from ZFS.
 > > They always get: "Access denied.  Contact your administrator."  Same
 > > result whether they're trying to overwrite a file or write a new file.
 > >
 > > Any ideas what's causing that?  This is driving me crazy.  I've
 > > seen the same problem under Linux with Samba, where disabling
 > > locking seemed to help.
 > >
 > > After that error, the users save the file to the local disk and copy
 > > it over the CIFS connection into the ZFS system successfully.  So they
 > > clearly have write access into ZFS from Windows, and the filesystem
 > > has lots of free space, but Office can't write any files to ZFS.  I
 > > assume this is some sort of locking problem.  I have nbmand=on, which
 > > is what I've read it should be set to for CIFS sharing.
 > >
 > > The directories and files they're trying to edit are owned by the
 > > actual user (defined by matching passwd and smbpasswd entries on the
 > > OI machine) and have 700 permissions and full_set ACLS:
 > >
 > >               owner@:rwxpdDaARWcCos:fd-----:allow
 > >            everyone@:rwxpdDaARWcCos:fd-----:deny
 > 
 > You are always a member of the "everyone" group, so that deny ACE is
 > killing your access.

Sorry, that's wrong.  The first ACL wins, allowing the owner in.

Otherwise, the owner wouldn't have been able to copy the file to ZFS
over CIFS after Word failed to write it there directly.

It's only Word and Excel (and probably other Office apps) that are
getting Access Denied.

Martin


From sardonic.smiles at gmail.com  Fri Jun 29 01:57:56 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Thu, 28 Jun 2012 21:57:56 -0400
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS over
	CIFS
In-Reply-To: <E1SkLwX-0003dM-Ia@sunburn.Stanford.EDU>
References: <E1SkLwX-0003dM-Ia@sunburn.Stanford.EDU>
Message-ID: <CAPVmm=Z+xQZ7ikRPowBd3o20Po9fm+Jtgr7CuB_6RxCAg-kHTQ@mail.gmail.com>

But wouldn't that prevent normal writes as well?

I had the same issue with server 2008r2 and xp clients. That was an smb2.0
issue. I don't know what version of smb the cifs server on OI uses though.

Can you try with other (non-XP/2003) clients?
On Jun 28, 2012 5:08 PM, "Martin Frost" <me at cs.stanford.edu> wrote:

> I'm running oi_148 as a fileserver, exporting via NFS and the
> kernel CIFS service for ZFS.
>
> But Windows users (XP and probably all Windows versions) are unable to
> write files from any MS Office applications into the shares from ZFS.
> They always get: "Access denied.  Contact your administrator."  Same
> result whether they're trying to overwrite a file or write a new file.
>
> Any ideas what's causing that?  This is driving me crazy.  I've
> seen the same problem under Linux with Samba, where disabling
> locking seemed to help.
>
> After that error, the users save the file to the local disk and copy
> it over the CIFS connection into the ZFS system successfully.  So they
> clearly have write access into ZFS from Windows, and the filesystem
> has lots of free space, but Office can't write any files to ZFS.  I
> assume this is some sort of locking problem.  I have nbmand=on, which
> is what I've read it should be set to for CIFS sharing.
>
> The directories and files they're trying to edit are owned by the
> actual user (defined by matching passwd and smbpasswd entries on the
> OI machine) and have 700 permissions and full_set ACLS:
>
>               owner@:rwxpdDaARWcCos:fd-----:allow
>            everyone@:rwxpdDaARWcCos:fd-----:deny
>
> Some relevant services:
>
> online         Feb_11   svc:/network/shares/group:smb
> online         Mar_01   svc:/network/smb/server:default
> online         Feb_27   svc:/network/nfs/status:default
> online         Feb_27   svc:/network/nfs/rquota:default
> online         Feb_27   svc:/network/nfs/nlockmgr:default
> online         May_08   svc:/network/nfs/mapid:default
> online         May_09   svc:/network/nfs/server:default
> online         May_09   svc:/network/nfs/cbd:default
>
> Here are most properties of the filesystem:
>
> NAME         PROPERTY         VALUE              SOURCE
> gname/thefs  mounted          yes                -
> gname/thefs  reservation      none               default
> gname/thefs  mountpoint       /gname/thefs       default
> gname/thefs  sharenfs         sec=sys,rw=gname   local
> gname/thefs  checksum         on                 default
> gname/thefs  compression      gzip               inherited from gname
> gname/thefs  atime            off                inherited from gname
> gname/thefs  devices          on                 default
> gname/thefs  exec             on                 default
> gname/thefs  readonly         off                default
> gname/thefs  zoned            off                default
> gname/thefs  aclinherit       passthrough        local
> gname/thefs  canmount         on                 default
> gname/thefs  xattr            on                 default
> gname/thefs  version          5                  -
> gname/thefs  utf8only         off                -
> gname/thefs  normalization    none               -
> gname/thefs  casesensitivity  mixed              -
> gname/thefs  vscan            off                default
> gname/thefs  nbmand           on                 local
> gname/thefs  sharesmb         name=thefs         local
> gname/thefs  refquota         none               default
> gname/thefs  refreservation   none               default
> gname/thefs  logbias          latency            default
> gname/thefs  dedup            off                default
> gname/thefs  mlslabel         none               default
> gname/thefs  sync             standard           default
>
> Thanks for any suggestions!
>
> Martin
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>

From gordon.w.ross at gmail.com  Fri Jun 29 02:49:40 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 28 Jun 2012 22:49:40 -0400
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS over
	CIFS
In-Reply-To: <E1SkPqA-0000AB-Vo@sunburn.Stanford.EDU>
References: <CAD0Ztp0L7DUwhoLwxBrpyrRb5t4yHqmAyKe63y_eCRuXqc7K+g@mail.gmail.com>
	<E1SkPqA-0000AB-Vo@sunburn.Stanford.EDU>
Message-ID: <CAD0Ztp37tS2YPN97fRQcKK6yG+2BNJjhRq0fzx1mMb1VuBk3OQ@mail.gmail.com>

On Thu, Jun 28, 2012 at 9:17 PM, Martin Frost <me at cs.stanford.edu> wrote:
> ?> Date: Thu, 28 Jun 2012 18:14:53 -0400
> ?> From: Gordon Ross <gordon.w.ross at gmail.com>
> ?>
> ?> On Thu, Jun 28, 2012 at 5:08 PM, Martin Frost <me at cs.stanford.edu> wrote:
> ?> > I'm running oi_148 as a fileserver, exporting via NFS and the
> ?> > kernel CIFS service for ZFS.
> ?> >
> ?> > But Windows users (XP and probably all Windows versions) are unable to
> ?> > write files from any MS Office applications into the shares from ZFS.
> ?> > They always get: "Access denied. ?Contact your administrator." ?Same
> ?> > result whether they're trying to overwrite a file or write a new file.
> ?> >
> ?> > Any ideas what's causing that? ?This is driving me crazy. ?I've
> ?> > seen the same problem under Linux with Samba, where disabling
> ?> > locking seemed to help.
> ?> >
> ?> > After that error, the users save the file to the local disk and copy
> ?> > it over the CIFS connection into the ZFS system successfully. ?So they
> ?> > clearly have write access into ZFS from Windows, and the filesystem
> ?> > has lots of free space, but Office can't write any files to ZFS. ?I
> ?> > assume this is some sort of locking problem. ?I have nbmand=on, which
> ?> > is what I've read it should be set to for CIFS sharing.
> ?> >
> ?> > The directories and files they're trying to edit are owned by the
> ?> > actual user (defined by matching passwd and smbpasswd entries on the
> ?> > OI machine) and have 700 permissions and full_set ACLS:
> ?> >
> ?> > ? ? ? ? ? ? ? owner@:rwxpdDaARWcCos:fd-----:allow
> ?> > ? ? ? ? ? ?everyone@:rwxpdDaARWcCos:fd-----:deny
> ?>
> ?> You are always a member of the "everyone" group, so that deny ACE is
> ?> killing your access.
>
> Sorry, that's wrong. ?The first ACL wins, allowing the owner in.

Not according to:
http://msdn.microsoft.com/en-us/library/cc246052(v=prot.13).aspx
Quoting:  "An explicit deny will always override all other permissions."

> Otherwise, the owner wouldn't have been able to copy the file to ZFS
> over CIFS after Word failed to write it there directly.

During the copy, you might have different permissions (i.e. as creator).

-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From ong.yu.phing at group.ong-ong.com  Fri Jun 29 03:04:38 2012
From: ong.yu.phing at group.ong-ong.com (Ong Yu-Phing)
Date: Fri, 29 Jun 2012 11:04:38 +0800
Subject: [OpenIndiana-discuss] Static routes (OpenIndiana-discuss Digest, Vol 23,
 Issue 42)
In-Reply-To: <CAOFhruY-znwp0xK=6Eb+Sqxzab=uMS51X3SX4CqO+hZJ3BjnJA@mail.gmail.com>
References: <mailman.9525.1340891867.9998.openindiana-discuss@openindiana.org>
	<mailman.9525.1340891867.9998.openindiana-discuss.{ee5d15ff-361d-4f7a-83b8-7ef16bd05ffb}.0@openindiana.org>
	<CAOFhruY-znwp0xK=6Eb+Sqxzab=uMS51X3SX4CqO+hZJ3BjnJA@mail.gmail.com>
Message-ID: <4FED1B46.4050407@group.ong-ong.com>

Assuming that your subnet mask is 255.255.255.0, this means your two 
subnets are separate (192.168.0.0/24 and 192.168.10.0/24).

Then accessing 192.168.10.2 and 192.168.10.1 would be on a separate 
media (your crossover cable; although a modern switch, not hub, would 
also do, since they do point-to-point links, e.g. the HP 2510g's I use 
have 96Gbps capacity across 48ports.  If you are really paranoid about 
any data leakage, you can also VLAN them)

So all you need to do is an rsync using the IP rather than hostname (or 
create an entry in the hosts file for the private IP:
192.168.0.100 machineA
192.168.10.2 privateA
)

e.g. from machine A, rsync -av user at 192.168.10.1:/whatever

On 28/06/2012 09:26, drsgrid wrote:
> Im not a full time admin but im trying to use rsync across 10GE (or even
> 1GE -as a starting point) from one openindana box to another. Both machines
> are also connected to a broader network to receive updates (eth0)  but im
> trying to use a xover cable for eth1 so i can rsync across and not take up
> a lot of bandwith on the broader network. From my reading think I need to
> setup a static route on eth1.   All my ip addresses are static: -
>
> machineA(eth0)=192.168.0.100, machineA(eth1)=192.168.10.2
> machineB(eth0)=192.168.0.108, machineB(eth1)=192.168.10.1
>
> how do i setup the machines so that i can do an rsync across the
> 192.168.10.x domain so as not to disturb bandwith on the 192.168.0.x domain?
>
>




From ong.yu.phing at group.ong-ong.com  Fri Jun 29 03:17:38 2012
From: ong.yu.phing at group.ong-ong.com (Ong Yu-Phing)
Date: Fri, 29 Jun 2012 11:17:38 +0800
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS over
 CIFS (OpenIndiana-discuss Digest, Vol 23, Issue 43)
In-Reply-To: <E1SkLwX-0003dM-Ia@sunburn.Stanford.EDU>
References: <mailman.9551.1340917685.9998.openindiana-discuss@openindiana.org>
	<mailman.9551.1340917685.9998.openindiana-discuss.{500b287e-b280-4006-966e-24af254cdf4c}.0@openindiana.org>
	<E1SkLwX-0003dM-Ia@sunburn.Stanford.EDU>
Message-ID: <4FED1E52.7080407@group.ong-ong.com>

In my environment I have 3 OI_148's integrated into two different ADs, 
with the majority of users being Windows users.  They don't see any 
issues like this.  They are heavy users of cad, design tools like 
photoshop/sketchup etc, as well as MS office/libreoffice, ~12TB of data 
all up (and 30+snapshots per filesystem).

Are you sharing via NFS, or are the Windows users accessing via the ZFS 
sharesmb=thsfs?

In my situation, I don't have both NFS and sharesmb turned on 
simultaneously, nor do I have compression enabled, not sure if these 
make a difference.

My nbmand is off, though, as I'm not using both NFS and CIFS.  Maybe 
this is your problem, since it specifically deals with locking 
(http://docs.oracle.com/cd/E19082-01/820-2429/configurecrossprotocollockingtask/index.html), 
specifically "When the nbmand mount option is not set, the Solaris CIFS 
service will enforce mandatory share reservations and byte-range locking 
internally for all CIFS clients. However, without nbmand set, there is 
only limited coordination with NFS and local processes."?

On 29/06/2012 05:08, Martin Frost wrote:
> I'm running oi_148 as a fileserver, exporting via NFS and the
> kernel CIFS service for ZFS.
>
> But Windows users (XP and probably all Windows versions) are unable to
> write files from any MS Office applications into the shares from ZFS.
> They always get: "Access denied.  Contact your administrator."  Same
> result whether they're trying to overwrite a file or write a new file.
>
> Any ideas what's causing that?  This is driving me crazy.  I've
> seen the same problem under Linux with Samba, where disabling
> locking seemed to help.
>
> After that error, the users save the file to the local disk and copy
> it over the CIFS connection into the ZFS system successfully.  So they
> clearly have write access into ZFS from Windows, and the filesystem
> has lots of free space, but Office can't write any files to ZFS.  I
> assume this is some sort of locking problem.  I have nbmand=on, which
> is what I've read it should be set to for CIFS sharing.
>
> The directories and files they're trying to edit are owned by the
> actual user (defined by matching passwd and smbpasswd entries on the
> OI machine) and have 700 permissions and full_set ACLS:
>
> 	       owner@:rwxpdDaARWcCos:fd-----:allow
> 	    everyone@:rwxpdDaARWcCos:fd-----:deny
>
> Some relevant services:
>
> online         Feb_11   svc:/network/shares/group:smb
> online         Mar_01   svc:/network/smb/server:default
> online         Feb_27   svc:/network/nfs/status:default
> online         Feb_27   svc:/network/nfs/rquota:default
> online         Feb_27   svc:/network/nfs/nlockmgr:default
> online         May_08   svc:/network/nfs/mapid:default
> online         May_09   svc:/network/nfs/server:default
> online         May_09   svc:/network/nfs/cbd:default
>
> Here are most properties of the filesystem:
>
> NAME         PROPERTY         VALUE              SOURCE
> gname/thefs  mounted          yes                -
> gname/thefs  reservation      none               default
> gname/thefs  mountpoint       /gname/thefs       default
> gname/thefs  sharenfs         sec=sys,rw=gname   local
> gname/thefs  checksum         on                 default
> gname/thefs  compression      gzip               inherited from gname
> gname/thefs  atime            off                inherited from gname
> gname/thefs  devices          on                 default
> gname/thefs  exec             on                 default
> gname/thefs  readonly         off                default
> gname/thefs  zoned            off                default
> gname/thefs  aclinherit       passthrough        local
> gname/thefs  canmount         on                 default
> gname/thefs  xattr            on                 default
> gname/thefs  version          5                  -
> gname/thefs  utf8only         off                -
> gname/thefs  normalization    none               -
> gname/thefs  casesensitivity  mixed              -
> gname/thefs  vscan            off                default
> gname/thefs  nbmand           on                 local
> gname/thefs  sharesmb         name=thefs         local
> gname/thefs  refquota         none               default
> gname/thefs  refreservation   none               default
> gname/thefs  logbias          latency            default
> gname/thefs  dedup            off                default
> gname/thefs  mlslabel         none               default
> gname/thefs  sync             standard           default
>
> Thanks for any suggestions!
>
> Martin
>
>
>




From sardonic.smiles at gmail.com  Fri Jun 29 03:19:04 2012
From: sardonic.smiles at gmail.com (Robbie Crash)
Date: Thu, 28 Jun 2012 23:19:04 -0400
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS over
	CIFS
In-Reply-To: <CAD0Ztp37tS2YPN97fRQcKK6yG+2BNJjhRq0fzx1mMb1VuBk3OQ@mail.gmail.com>
References: <CAD0Ztp0L7DUwhoLwxBrpyrRb5t4yHqmAyKe63y_eCRuXqc7K+g@mail.gmail.com>
	<E1SkPqA-0000AB-Vo@sunburn.Stanford.EDU>
	<CAD0Ztp37tS2YPN97fRQcKK6yG+2BNJjhRq0fzx1mMb1VuBk3OQ@mail.gmail.com>
Message-ID: <CAPVmm=ZbT+GgX9b6+37ygHQ8M1TUAgtfXrBi86mUqo3m2cFcWA@mail.gmail.com>

The explicit deny would apply to creator/owner if that were the case. Also,
it's not a 1:1 NTFS ACL mapping to the ZFS ACL. IIRC, the permissions all
show up as special permissions, for only one or two generic users.

If Windows thought that there was an explicit deny, it wouldn't open the
file, and since those are inherited permissions, likely couldn't open the
directory itself.

Try running process explorer on the Windows box to see if it has closed the
file handles.

Also, what version of Office?
On Jun 28, 2012 10:50 PM, "Gordon Ross" <gordon.w.ross at gmail.com> wrote:

> On Thu, Jun 28, 2012 at 9:17 PM, Martin Frost <me at cs.stanford.edu> wrote:
> >  > Date: Thu, 28 Jun 2012 18:14:53 -0400
> >  > From: Gordon Ross <gordon.w.ross at gmail.com>
> >  >
> >  > On Thu, Jun 28, 2012 at 5:08 PM, Martin Frost <me at cs.stanford.edu>
> wrote:
> >  > > I'm running oi_148 as a fileserver, exporting via NFS and the
> >  > > kernel CIFS service for ZFS.
> >  > >
> >  > > But Windows users (XP and probably all Windows versions) are unable
> to
> >  > > write files from any MS Office applications into the shares from
> ZFS.
> >  > > They always get: "Access denied.  Contact your administrator."  Same
> >  > > result whether they're trying to overwrite a file or write a new
> file.
> >  > >
> >  > > Any ideas what's causing that?  This is driving me crazy.  I've
> >  > > seen the same problem under Linux with Samba, where disabling
> >  > > locking seemed to help.
> >  > >
> >  > > After that error, the users save the file to the local disk and copy
> >  > > it over the CIFS connection into the ZFS system successfully.  So
> they
> >  > > clearly have write access into ZFS from Windows, and the filesystem
> >  > > has lots of free space, but Office can't write any files to ZFS.  I
> >  > > assume this is some sort of locking problem.  I have nbmand=on,
> which
> >  > > is what I've read it should be set to for CIFS sharing.
> >  > >
> >  > > The directories and files they're trying to edit are owned by the
> >  > > actual user (defined by matching passwd and smbpasswd entries on the
> >  > > OI machine) and have 700 permissions and full_set ACLS:
> >  > >
> >  > >               owner@:rwxpdDaARWcCos:fd-----:allow
> >  > >            everyone@:rwxpdDaARWcCos:fd-----:deny
> >  >
> >  > You are always a member of the "everyone" group, so that deny ACE is
> >  > killing your access.
> >
> > Sorry, that's wrong.  The first ACL wins, allowing the owner in.
>
> Not according to:
> http://msdn.microsoft.com/en-us/library/cc246052(v=prot.13).aspx
> Quoting:  "An explicit deny will always override all other permissions."
>
> > Otherwise, the owner wouldn't have been able to copy the file to ZFS
> > over CIFS after Word failed to write it there directly.
>
> During the copy, you might have different permissions (i.e. as creator).
>
> --
> Gordon Ross <gwr at nexenta.com>
> Nexenta Systems, Inc.  www.nexenta.com
> Enterprise class storage for everyone
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>

From gordon.w.ross at gmail.com  Sat Jun 30 05:12:17 2012
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Sat, 30 Jun 2012 01:12:17 -0400
Subject: [OpenIndiana-discuss] Hitachi 4 TB disks + HP Microserver + OI
 151 + ZFS
In-Reply-To: <CAD0Ztp06nUZ7=PDRaGk_mXZsOaRvJgv4p3X9AtVx6dnRFF_OnA@mail.gmail.com>
References: <26304643.8.1335720526938.JavaMail.root@zimbra>
	<BE1C00AC-FABD-413A-9DF5-5D0987885B18@delphix.com>
	<76DFB222-A1D4-4DC9-B12F-821A20E99ECE@RichardElling.com>
	<CAD0Ztp3=aVXMufohybLzAu9zHVC_n8=wQEd8NqyWWuioHEzppw@mail.gmail.com>
	<912F60BC-6041-4C21-88DB-C1087B235AE6@RichardElling.com>
	<CAEGK5+=EaAT+AZjmQ8NQzqjAnw-9nSPnHoV=uaXDqpccUj4bLQ@mail.gmail.com>
	<4FA0E14D.4010204@gmail.com>
	<602CD275-8FD0-4BFF-87B8-02934920E0C6@RichardElling.com>
	<CAD0Ztp06nUZ7=PDRaGk_mXZsOaRvJgv4p3X9AtVx6dnRFF_OnA@mail.gmail.com>
Message-ID: <CAD0Ztp1q9KuVnvcL-FmRJ2MBLhU85jryoe0LCs+iNADemP3rug@mail.gmail.com>

On Wed, May 2, 2012 at 3:07 PM, Gordon Ross <gordon.w.ross at gmail.com> wrote:
> On Wed, May 2, 2012 at 2:47 PM, Richard Elling
> <richard.elling at richardelling.com> wrote:
>> On May 2, 2012, at 12:25 AM, Mark wrote:
>>
>>> There are two issues.
>>>
>>> The first is correct partition alignment, the second ashift value.
>>>
>>> In "theory", I haven't tested this yet, manually creating the slices with a start position to sector 64 and using slices instead of whole disks for the zpool devices, and creating with an ashift of 12 may produce the desired outcome.
>>
>> Default starting offset for slice 0 is sector 256 for 512-byte sector disks.
>> You shouldn't have to manually touch these unless you are running an
>> ancient (circa 2006-2007) version of Solaris where the default offset was 34.
>
> Yes, but be warned: the format command will try to make fdisk partitions
> that are aligned on "cyninder" boundaries, which are usually odd numbers
> of sectors. ?I have a fix for that here: ?http://yalms.org/cr/zfs-blksize/
> (the first three files. ?ignore the zfs part for now)
>
> Gordon

For those interested, I have a review out for this work on illumos-dev.
http://www.yalms.org/cr/illumos-2949/
Please comment over there.

Thanks,
-- 
Gordon Ross <gwr at nexenta.com>
Nexenta Systems, Inc. ?www.nexenta.com
Enterprise class storage for everyone


From me at cs.Stanford.EDU  Sat Jun 30 23:00:37 2012
From: me at cs.Stanford.EDU (Martin Frost)
Date: Sat, 30 Jun 2012 16:00:37 -0700
Subject: [OpenIndiana-discuss] Office apps unable to write to ZFS
	over	CIFS
In-Reply-To: <CAPVmm=ZbT+GgX9b6+37ygHQ8M1TUAgtfXrBi86mUqo3m2cFcWA@mail.gmail.com>
	(message from Robbie Crash on Thu, 28 Jun 2012 23:19:04 -0400)
Message-ID: <E1Sl6eb-0001Gp-MY@sunburn.Stanford.EDU>

Thanks to all for the replies.  The Oracle Solaris documentation here:

  http://docs.oracle.com/cd/E19253-01/819-5461/ftyxi/index.html

says:

    The primary rules of ACL access on a ZFS file follow:

    * ZFS processes ACL entries in the order they are listed
	in the ACL, from the top down.

    * After an allow permission has been granted, it cannot be denied
	by a subsequent ACL deny entry in the same ACL permission set.

And my 'allow' was deliberately placed before the 'deny':

              owner@:rwxpdDaARWcCos:fd-----:allow
           everyone@:rwxpdDaARWcCos:fd-----:deny

And indeed *Windows* is allowing the owner to write files in such
directories in the OI ZFS filesystem.

But Office under Windows does not allow that, though it does allow
reading files there (despite the "deny" of all read permissions for
everyone@, which of course the above documention says should be
ignored, as should the denial of write access).

(Office on MacOS X doesn't have this problem.  It's happy to write
such files despite the second line saying 'deny', though if the 'deny'
is the first line, Office on MacOS X does properly fail to read or
write the file.)

If I remove the "everyone@:...:deny", Office under Windows lets the
owner write the file.  It appears that non-owners still cannot read or
write such files, despite my having removed the "everyone@:...:deny",
so I'm satisfied that things are still protected as needed.

So Windows and Office on Windows -- both created by Microsoft --
interpret these ACLs differently.  Oh well.

Thanks again for your help.

Martin

 > Date: Thu, 28 Jun 2012 23:19:04 -0400
 > From: Robbie Crash <sardonic.smiles at gmail.com>
 > 
 > The explicit deny would apply to creator/owner if that were the
 > case. Also, it's not a 1:1 NTFS ACL mapping to the ZFS ACL. IIRC,
 > the permissions all show up as special permissions, for only one or
 > two generic users.
 > 
 > If Windows thought that there was an explicit deny, it wouldn't
 > open the file, and since those are inherited permissions, likely
 > couldn't open the directory itself.
 > 
 > Try running process explorer on the Windows box to see if it has
 > closed the file handles.
 > 
 > Also, what version of Office?
 > 
 > On Jun 28, 2012 10:50 PM, "Gordon Ross" <gordon.w.ross at gmail.com> wrote:
 > 
 > > On Thu, Jun 28, 2012 at 9:17 PM, Martin Frost <me at cs.stanford.edu> wrote:
 > > >  > Date: Thu, 28 Jun 2012 18:14:53 -0400
 > > >  > From: Gordon Ross <gordon.w.ross at gmail.com>
 > > >  >
 > > >  > On Thu, Jun 28, 2012 at 5:08 PM, Martin Frost <me at cs.stanford.edu>
 > > wrote:
 > > >  > > I'm running oi_148 as a fileserver, exporting via NFS and the
 > > >  > > kernel CIFS service for ZFS.
 > > >  > >
 > > >  > > But Windows users (XP and probably all Windows versions)
 > > >  > > are unable to write files from any MS Office applications
 > > >  > > into the shares from ZFS.  They always get: "Access
 > > >  > > denied.  Contact your administrator."  Same result whether
 > > >  > > they're trying to overwrite a file or write a new file.
 > > >  > >
 > > >  > > Any ideas what's causing that?  This is driving me crazy.
 > > >  > > I've seen the same problem under Linux with Samba, where
 > > >  > > disabling locking seemed to help.
 > > >  > >
 > > >  > > After that error, the users save the file to the local
 > > >  > > disk and copy it over the CIFS connection into the ZFS
 > > >  > > system successfully.  So they clearly have write access
 > > >  > > into ZFS from Windows, and the filesystem has lots of free
 > > >  > > space, but Office can't write any files to ZFS.  I assume
 > > >  > > this is some sort of locking problem.  I have nbmand=on,
 > > >  > > which is what I've read it should be set to for CIFS
 > > >  > > sharing.
 > > >  > >
 > > >  > > The directories and files they're trying to edit are owned
 > > >  > > by the actual user (defined by matching passwd and
 > > >  > > smbpasswd entries on the OI machine) and have 700
 > > >  > > permissions and full_set ACLS:
 > > >  > >
 > > >  > >               owner@:rwxpdDaARWcCos:fd-----:allow
 > > >  > >            everyone@:rwxpdDaARWcCos:fd-----:deny
 > > >  >
 > > >  > You are always a member of the "everyone" group, so that
 > > >  > deny ACE is killing your access.
 > > >
 > > > Sorry, that's wrong.  The first ACL wins, allowing the owner in.
 > >
 > > Not according to:
 > > http://msdn.microsoft.com/en-us/library/cc246052(v=prot.13).aspx
 > > Quoting:  "An explicit deny will always override all other permissions."
 > >
 > > > Otherwise, the owner wouldn't have been able to copy the file
 > > > to ZFS over CIFS after Word failed to write it there directly.
 > >
 > > During the copy, you might have different permissions (i.e. as creator).