From hp at pawaq.at  Wed Jun  1 10:21:43 2016
From: hp at pawaq.at (Harald Paier)
Date: Wed, 1 Jun 2016 12:21:43 +0200 (CEST)
Subject: [OmniOS-discuss] zpool import with iSCSI vdevs hangs on
	ioctl-syscall w/cmd 5a06
Message-ID: <1763128364.15396.1464776503960.JavaMail.zimbra@pawaq.at>

Hello, 

I find strange behavior of zpool import when accessing a pool via iscsi: It either completes quickly, takes 61-72 s or 121-127 s. 
Using dtrace I found 2 ioctl syscalls (fd = 3, cmd = 5a06, arg = 804237c) which either return quickly (< 10 s) or take about 60 s. 
I have no idea what ioctl command 5a06 is supposed to do or even where to look for that information. 

While the ioctl command hangs there is no CPU load on both head and backends (idle 99-100%). 

I don't think there is any dependency on the number of devices in the pool, because there are always 2 ioctl-5a06 syscalls. 
Also during zpool import a lot of SCSI errors are reported in fmdump, but I do not see any difference whether or not the affected ioctls run normally. No SCSI errors occur during the hanging ioctls. 
The reported errors are either generic write errors (key 0x3 asc 0xc ascq 0x0) or bus resets (key 0x6 asc 0x29 ascq 0x0). 
There are no SCSI errors once the pool is imported and used for normal IO. 

On the backends there are no errors reported in fmdump and no problems with long running syscalls. 

I also tried the following without any success: 
- Run the tests in both stable (r151014) and bloody (20160422) release. 
- Configure target-params timeout of the initiator to 3 seconds 
- Reconfigure io_time and retries of the sd driver to 3 s / 1 retry. 

Any help to find/resolve the root cause of those sysctl hangs would be greatly appreciated. 

Kind Regards 
harald 


My test setups are: 
A: VMware Workstation 12 (laptop with i7 at 2.5GHz, 16GB RAM, fast SSD disk): 
- 3 backends with 768MB RAM, 1 vCPU, stable release (r151014) 
- 1 head with 2GB RAM, 1 vCPU, stable release (r151014) 
- 1 alternative head with 2GB RAM, 1 vCPU, bloody release (20160422) 
B: VMware ESXi 6 (server with E5620 at 2.4GHz, 24GB RAM, RAID 0 over 3 300GB 15K SAS disks) 
- 3 backends with 1GB RAM, 1 vCPU, stable release (r151014) 
- 1 head with 6GB RAM, 2 vCPU, stable release (r151014) 

Each backend presents 2 virtual disks as LUNs. 
On the head I have created a zpool consiting of 2 raidz1 vdevs spanning the backends: 
pool: pool1 
id: 12810568181218589176 
state: ONLINE 
status: Some supported features are not enabled on the pool. 
action: The pool can be imported using its name or numeric identifier, though 
some features will not be available without an explicit 'zpool upgrade'. 
config: 

pool1 ONLINE 
raidz1-0 ONLINE 
c3t600144F03AB7625F00005723BE320001d0 ONLINE 
c3t600144F03AB7625F00005723BEFB0001d0 ONLINE 
c3t600144F03AB7625F00005723BF1E0001d0 ONLINE 
raidz1-1 ONLINE 
c3t600144F03AB7625F00005723BE320002d0 ONLINE 
c3t600144F03AB7625F00005723BEFB0002d0 ONLINE 
c3t600144F03AB7625F00005723BF1E0002d0 ONLINE 

There is no iSCSI authentication configured, no host or target groups are used. 

I did run zpool import in a loop on both virtual setups using the following script: 

for i in {1..100}; do 
sudo dtrace -n ' 
syscall::ioctl:entry 
/pid == $target/ 
{ 
self->ts = timestamp; 
} 

syscall::ioctl:return 
/pid == $target && self->ts/ 
{ 
@time = sum(timestamp - self->ts); 
self->ts = 0; 
} 

END 
{ 
printa(@time); 
}' -c "zpool import" 
sleep 30; 
done 

After 100 test runs on 2 test setups I got 3 groups of runtimes: 
- below 16 sec 
- between 61 and 72 sec 
- between 121 and 127 sec 

Setup A B 
Result <=16 s +1 min +2 min <=16 s +1 min +2 min 
Count 36 49 15 53 38 9 
Min 5.8 61.0 121.6 1.0 61.2 121.8 
Max 15.9 71.9 126.9 11.2 71.3 127.0 
Avg 10.8 66.6 122.4 4.2 65.3 123.1 
StDev 0.9 0.9 0.7 2.7 2.1 1.1 

Setup B is on faster hardware and does suffer less often from the problem. 
But still there is something going very wrong here. 

So I used dtrace to find out where the additional 1 or 2 minutes come from: 

sudo dtrace -qn ' 
BEGIN 
{ 
printf("\n"); 
} 
syscall::ioctl:entry 
/pid == $target/ 
{ 
self->ts = timestamp; 
self->arg0 = arg0; 
self->arg1 = arg1; 
self->arg2 = arg2; 
} 

syscall::ioctl:return 
/pid == $target && self->ts/ 
{ 
printf("time = %Y, fd = %d, cmd = %lx, arg = %lx, runtime %d s\n", 
walltimestamp, self->arg0, self->arg1, self->arg2, (timestamp - self->ts) / 1000000000); 
@time[probefunc] = lquantize((timestamp - self->ts) / 1000000000, 0, 180, 60); 
self->ts = 0; 
} 

END 
{ 
printa(@time); 
}' -c "zpool import" 



Example 1 (normal run): 

fmdump output: 
May 26 14:11:24.4887 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:11:24.5464 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:11:24.5464 ereport.io.scsi.cmd.disk.recovered 
May 26 14:11:24.8359 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:11:24.8366 ereport.io.scsi.cmd.disk.dev.serr 
May 26 14:11:24.8366 ereport.io.scsi.cmd.disk.dev.serr 
May 26 14:11:24.8366 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:11:24.8395 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:11:24.8397 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:11:24.9291 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:11:24.8366 ereport.io.scsi.cmd.disk.recovered 
May 26 14:11:24.8366 ereport.io.scsi.cmd.disk.recovered 
May 26 14:11:24.8366 ereport.io.scsi.cmd.disk.recovered 
May 26 14:11:29.8392 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:11:29.8392 ereport.io.scsi.cmd.disk.dev.rqs.merr 

dtrace output: 
time = 2016 May 26 14:11:19, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 403, arg = fe2ce9cc, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 9, cmd = 403, arg = fe1cf9cc, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:11:19, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:11:24, fd = 3, cmd = 5a06, arg = 804237c, runtime 5 s 
time = 2016 May 26 14:11:29, fd = 3, cmd = 5a06, arg = 804237c, runtime 5 s 
time = 2016 May 26 14:11:29, fd = 1, cmd = 5401, arg = 8042bbe, runtime 0 s 
time = 2016 May 26 14:11:29, fd = 3, cmd = 5a3f, arg = 80429d0, runtime 0 s 

ioctl 
value ------------- Distribution ------------- count 
< 0 | 0 
0 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 40 
60 | 0 



Example 2 (2 additional minutes): 

fmdump output: 
May 26 14:13:27.6296 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:13:27.6395 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:13:27.6400 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:13:28.4369 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:13:28.4369 ereport.io.scsi.cmd.disk.recovered 
May 26 14:14:27.8696 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:14:27.9694 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:14:27.9695 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:14:28.2196 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:14:28.2230 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:14:28.2235 ereport.io.scsi.cmd.disk.dev.serr 
May 26 14:14:28.2235 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:14:28.2256 ereport.io.scsi.cmd.disk.dev.serr 
May 26 14:14:28.3194 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:14:28.4767 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:14:28.4767 ereport.io.scsi.cmd.disk.recovered 
May 26 14:14:28.2256 ereport.io.scsi.cmd.disk.recovered 
May 26 14:14:28.2256 ereport.io.scsi.cmd.disk.recovered 
May 26 14:14:28.2235 ereport.io.scsi.cmd.disk.recovered 
May 26 14:14:33.2385 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:14:33.3183 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:15:28.8692 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:15:28.9333 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:15:28.9333 ereport.io.scsi.cmd.disk.recovered 

dtrace output: 
time = 2016 May 26 14:13:27, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 403, arg = fe2ce9cc, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 9, cmd = 403, arg = fe1cf9cc, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:13:27, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:14:28, fd = 3, cmd = 5a06, arg = 804237c, runtime 60 s 
time = 2016 May 26 14:15:29, fd = 3, cmd = 5a06, arg = 804237c, runtime 61 s 
time = 2016 May 26 14:15:29, fd = 1, cmd = 5401, arg = 8042bbe, runtime 0 s 
time = 2016 May 26 14:15:29, fd = 3, cmd = 5a3f, arg = 80429d0, runtime 0 s 

ioctl 
value ------------- Distribution ------------- count 
< 0 | 0 
0 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 38 
60 |@@ 2 
120 | 0 



Example 3 (1 addional minute in first 0x5a06-ioctl): 

fmdump output: 
May 26 14:19:16.6490 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:19:16.7392 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:19:16.7393 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:19:16.7400 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:19:16.7401 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:20:17.0794 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:20:17.1439 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:20:17.1439 ereport.io.scsi.cmd.disk.recovered 
May 26 14:20:17.4295 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:20:17.4303 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:20:17.4390 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:20:17.4457 ereport.io.scsi.cmd.disk.tran 
May 26 14:20:17.4457 ereport.io.scsi.cmd.disk.tran 
May 26 14:20:17.5292 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:20:17.4457 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:20:17.5394 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:20:17.4457 ereport.io.scsi.cmd.disk.recovered 
May 26 14:20:17.4457 ereport.io.scsi.cmd.disk.recovered 
May 26 14:20:17.6890 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:20:17.6890 ereport.io.scsi.cmd.disk.recovered 
May 26 14:20:22.4392 ereport.io.scsi.cmd.disk.dev.rqs.merr 

dtrace output: 
time = 2016 May 26 14:19:16, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 403, arg = fe2ce9cc, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 9, cmd = 403, arg = fe1cf9cc, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:19:16, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:20:17, fd = 3, cmd = 5a06, arg = 804237c, runtime 60 s 
time = 2016 May 26 14:20:22, fd = 3, cmd = 5a06, arg = 804237c, runtime 5 s 
time = 2016 May 26 14:20:22, fd = 1, cmd = 5401, arg = 8042bbe, runtime 0 s 
time = 2016 May 26 14:20:22, fd = 3, cmd = 5a3f, arg = 80429d0, runtime 0 s 

ioctl 
value ------------- Distribution ------------- count 
< 0 | 0 
0 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 39 
60 |@ 1 
120 | 0 



Example 4 (1 addional minute in second 0x5a06-ioctl): 

fmdump output: 
May 26 14:23:12.8093 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:12.8099 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:12.8099 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:17.8093 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:17.8094 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:17.9194 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:17.9383 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:23:17.9383 ereport.io.scsi.cmd.disk.recovered 
May 26 14:23:18.2694 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:18.2893 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:18.2898 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:23:18.8060 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:23:18.8060 ereport.io.scsi.cmd.disk.recovered 
May 26 14:23:23.3696 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:24:18.8897 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:24:18.9897 ereport.io.scsi.cmd.disk.dev.rqs.merr 
May 26 14:24:19.0218 ereport.io.scsi.cmd.disk.dev.rqs.derr 
May 26 14:24:19.0218 ereport.io.scsi.cmd.disk.recovered 

dtrace output: 
time = 2016 May 26 14:23:12, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 403, arg = fe2ce9cc, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 403, arg = fe1cf974, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 42a, arg = fe1cf9d0, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 417, arg = fe2ceb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 403, arg = fe2ce974, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 42a, arg = fe2ce9d0, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 412, arg = fe1cf9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 417, arg = fe1cfb58, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 9, cmd = 403, arg = fe1cf9cc, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 8, cmd = 412, arg = fe2ce9b8, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:23:12, fd = 3, cmd = 5a05, arg = 80422f0, runtime 0 s 
time = 2016 May 26 14:23:18, fd = 3, cmd = 5a06, arg = 804237c, runtime 5 s 
time = 2016 May 26 14:24:19, fd = 3, cmd = 5a06, arg = 804237c, runtime 61 s 
time = 2016 May 26 14:24:19, fd = 1, cmd = 5401, arg = 8042bbe, runtime 0 s 
time = 2016 May 26 14:24:19, fd = 3, cmd = 5a3f, arg = 80429d0, runtime 0 s 

ioctl 
value ------------- Distribution ------------- count 
< 0 | 0 
0 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ 39 
60 |@ 1 
120 | 0 






Configure target-params timeout of the initiator to 3 seconds: 

sysadm at head1:/export/home/sysadm$ pfexec iscsiadm list target-param -v 
Target: iqn.2010-08.org.illumos:02:74d64faf-ebe7-e811-c715-f427f6bd76f9 
Alias: backend3 
Bi-directional Authentication: disabled 
Authentication Type: NONE 
Login Parameters (Default/Configured): 
Data Sequence In Order: yes/- 
Data PDU In Order: yes/- 
Default Time To Retain: 20/- 
Default Time To Wait: 2/- 
Error Recovery Level: 0/- 
First Burst Length: 65536/- 
Immediate Data: yes/- 
Initial Ready To Transfer (R2T): yes/- 
Max Burst Length: 262144/- 
Max Outstanding R2T: 1/- 
Max Receive Data Segment Length: 8192/- 
Max Connections: 1/- 
Header Digest: NONE/- 
Data Digest: NONE/- 
Tunable Parameters (Default/Configured): 
Session Login Response Time: 60/3 
Maximum Connection Retry Time: 180/3 
Login Retry Time Interval: 60/3 
Configured Sessions: 1 

Target: iqn.2010-08.org.illumos:02:43ccef91-f911-4c16-c4df-8d99967c3a29 
Alias: backend2 
Bi-directional Authentication: disabled 
Authentication Type: NONE 
Login Parameters (Default/Configured): 
Data Sequence In Order: yes/- 
Data PDU In Order: yes/- 
Default Time To Retain: 20/- 
Default Time To Wait: 2/- 
Error Recovery Level: 0/- 
First Burst Length: 65536/- 
Immediate Data: yes/- 
Initial Ready To Transfer (R2T): yes/- 
Max Burst Length: 262144/- 
Max Outstanding R2T: 1/- 
Max Receive Data Segment Length: 8192/- 
Max Connections: 1/- 
Header Digest: NONE/- 
Data Digest: NONE/- 
Tunable Parameters (Default/Configured): 
Session Login Response Time: 60/3 
Maximum Connection Retry Time: 180/3 
Login Retry Time Interval: 60/3 
Configured Sessions: 1 

Target: iqn.2010-08.org.illumos:02:3e79a87e-125f-c11c-ef19-e30aa9d5fd54 
Alias: backend1 
Bi-directional Authentication: disabled 
Authentication Type: NONE 
Login Parameters (Default/Configured): 
Data Sequence In Order: yes/- 
Data PDU In Order: yes/- 
Default Time To Retain: 20/- 
Default Time To Wait: 2/- 
Error Recovery Level: 0/- 
First Burst Length: 65536/- 
Immediate Data: yes/- 
Initial Ready To Transfer (R2T): yes/- 
Max Burst Length: 262144/- 
Max Outstanding R2T: 1/- 
Max Receive Data Segment Length: 8192/- 
Max Connections: 1/- 
Header Digest: NONE/- 
Data Digest: NONE/- 
Tunable Parameters (Default/Configured): 
Session Login Response Time: 60/3 
Maximum Connection Retry Time: 180/3 
Login Retry Time Interval: 60/3 
Configured Sessions: 1 



Configure io_time and retries for the sd driver: 

echo 'set sd:sd_io_time=3' >> /etc/system 
echo 'sd-config-list = "SUN COMSTAR", "retries-timeout:1";' >> /kernel/drv/sd.conf 
shutdown -i6 -g0 -y 





	Harald Paier 
PAWAQ GmbH 
+43 1 2365078 10 
hp at pawaq.at - www.pawaq.com 
	


Lerchenfelder Stra?e 36/2 - 1080 Wien - Austria - Fn312475y - ATU64308378 - office at pawaq.at - www.pawaq.com 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/593a8c8e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo_pawaq_mail.png
Type: image/png
Size: 4964 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/593a8c8e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PARTNER_SOLUTION_PROVIDER_ENT.png
Type: image/png
Size: 2551 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/593a8c8e/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PARTNER_SERVICE_PROVIDER_PRO.png
Type: image/png
Size: 4564 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/593a8c8e/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: VCP-DCV-s.png
Type: image/png
Size: 3722 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/593a8c8e/attachment-0007.png>

From matej at zunaj.si  Wed Jun  1 11:26:19 2016
From: matej at zunaj.si (=?utf-8?Q?Matej_=C5=BDerovnik?=)
Date: Wed, 1 Jun 2016 13:26:19 +0200
Subject: [OmniOS-discuss] [discuss] COMSTAR hanging
In-Reply-To: <A2FA4C34-5DA9-4922-812A-C4B312BAAA1D@zunaj.si>
References: <0C7A62FA-5D1C-42A4-B171-FAA3AC34AC3D@4amlunch.net>
	<CAAYoGd_dU4E48PikupiD6TrV85urhHiXGx692mA8E=jAYMia-A@mail.gmail.com>
	<97F9575A-C086-4862-B5CA-BA2893E48C08@4amlunch.net>
	<A16F5BDE-472C-4D8D-A654-0FB5A84A9B15@zunaj.si>
	<6D6F42AE-611E-4C7C-88AE-23543CA66DA4@4amlunch.net>
	<B99F52AF-6272-47FE-B4E6-F0DAB6766E1C@omniti.com>
	<2F515DC7-7803-4814-99D1-06AE3E3A196C@4amlunch.net>
	<52C14C1A-80F1-4B5D-AE7D-9999AB1B758F@omniti.com>
	<D2B5448A.36011D%dave-lists@pooserville.com>
	<90EFFEAE-2967-49C7-80F1-AB82E95CB52E@zunaj.si>
	<11A7C643-506B-441D-B320-79C75B8EAFCE@4amlunch.net>
	<65DC5816D4BEE043885A89FD54E273FC6CF6BC33@MAIL101.Ellipseinc.com>
	<FCB546AB-F8CC-4CAC-803C-DB931B2FAE99@4amlunch.net>
	<D7A63329-1098-4B06-85FE-FB175E0A6B1A@zunaj.si>
	<CF9A59F1-58EB-4533-B06B-F5A1D4393536@4amlunch.net>
	<FDBF00AC-6865-49EE-B1BF-75E9D9264BF2@4amlunch.net>
	<867309FA36CA349E.2808DEE6-8CB2-4717-B123-26F8E9BF10C5@mail.outlook.com>
	<867309FA36CA349E.A61AF59B-1738-47A9-8918-7281B3A691CA@mail.outlook.com>
	<ECF358AE-ABC9-4F43-819B-1EC88BCDDF23@4amlunch.net>
	<867309FA36CA349E.0C1F93E3-1045-4C65-9084-870490D3BF34@mail.outlook.com>
	<A2FA4C34-5DA9-4922-812A-C4B312BAAA1D@zunaj.si>
Message-ID: <F5FFE500-55AC-4100-B101-6046154165AF@zunaj.si>

Hey there,

I was a bit too quick with the solution. It crashed a few days later.

What I discovered is that the number of iSCSI sessions starts climbing (one client opens tons of sessions) and when the number of sessions reaches a certain number, target crashes. When me and Dan looked at the memory dump, the client with open sessions is the one holding the lock, so that even stmf/target won?t restart (via svcadm restart).




On the graph we can see the number of sessions rising until it crashes. Number of TCP sessions stays the same.

Matej


> On 13 Apr 2016, at 16:07, Matej ?erovnik <matej at zunaj.si> wrote:
> 
> Hey there,
> 
> we were having the same problems with an old storage with SATA drives and a new one with SAS drives and all HW from Nexenta HCL list, so everything should work. Yet iSCSI target died every 2-6 days nonetheless. With the help of memory dump and Dan, it looks like, we managed to solve the issue.
> 
> In my case, one of the threads was waiting for memory to free. I remembered I hadn?t set max ARC sizeon my system, so it was possible for ARC to eat all my free memory and could not release it quick enough. After settings max ARC size, everything works for the last month. I still can?t say if this really fixed the problem or not, but so far so good:)
> 
> Matej
> 
> 
>> On 13 Jan 2016, at 05:52, John Barfield <john.barfield at bissinc.com <mailto:john.barfield at bissinc.com>> wrote:
>> 
>> Oh I didnt catch that detail. 
>> 
>> Okay well nevermind :)
>> 
>> 
>> Sent from Outlook Mobile <https://aka.ms/qtex0l>
>> 
>> 
>> 
>> On Tue, Jan 12, 2016 at 8:21 PM -0800, "Brian Hechinger" <wonko at 4amlunch.net <mailto:wonko at 4amlunch.net>> wrote:
>> 
>> In my case the SATA disks aren?t on the 1068E.
>> 
>> -brian
>> 
>>> On Jan 12, 2016, at 11:19 PM, John Barfield <john.barfield at bissinc.com <mailto:john.barfield at bissinc.com>> wrote:
>>> 
>>> BTW I left off that it has the same LSI controller chipset
>>> 
>>> Sent from Outlook Mobile <https://aka.ms/qtex0l>
>>> _____________________________
>>> From: John Barfield <john.barfield at bissinc.com <mailto:john.barfield at bissinc.com>>
>>> Sent: Tuesday, January 12, 2016 10:17 PM
>>> Subject: Re: [OmniOS-discuss] [discuss] COMSTAR hanging
>>> To: <discuss at lists.illumos.org <mailto:discuss at lists.illumos.org>>, omnios-discuss <omnios-discuss at lists.omniti.com <mailto:omnios-discuss at lists.omniti.com>>
>>> 
>>> 
>>> My input may or may not be valid but Im going to throw it out there anyway :)
>>> 
>>> do you have any Mpt disconnect errors in /var/adm/messages? 
>>> 
>>> Also do you have smartmontools installed? 
>>> 
>>> I ran into similiar issues just booting a sunfire x4540 recently off of OmniOS live, i/o would just hang while probing device nodes.
>>> 
>>> I found the drive that was acting up and pulled it. 
>>> 
>>> All of a sudden everything miraculously worked amazing. 
>>> 
>>> I compiled smartmontools after I got it to boot and found 10 drives out of 48 with bad sectors in prefail state.
>>> 
>>> I dont know if this happens with SAS drives or not but Im using SATA and saw this was a common issue in old opensolaris threads. 
>>> 
>>> -barfield 
>>> 
>>> Sent from Outlook Mobile <https://aka.ms/qtex0l>
>>> 
>>> 
>>> 
>>> On Tue, Jan 12, 2016 at 8:08 PM -0800, "Brian Hechinger" <wonko at 4amlunch.net <mailto:wonko at 4amlunch.net>> wrote: 
>>> 
>>> In the meantime I?ve removed the SLOG and L2ARC just in case. I don?t think that?s it though. At least will have some sort of data point to work with here. :) 
>>> 
>>> -brian 
>>> 
>>> > On Jan 12, 2016, at 10:55 PM, Brian Hechinger <wonko at 4amlunch.net <mailto:wonko at 4amlunch.net>> wrote: 
>>> > 
>>> > Ok, it has happened. 
>>> > 
>>> > Checking this here, the pool seems to be fine. I can read and write files. 
>>> > 
>>> > except ?zpool status? is now currently hanging. I can still read/write from the pool, however. 
>>> > 
>>> > I can telnet to port 3260, but restarting target services has hung. 
>>> > 
>>> > root at basket1:/tank/Share# svcs -a | grep stmf 
>>> > online         Jan_05   svc:/system/stmf:default 
>>> > root at basket1:/tank/Share# svcs -a | grep target 
>>> > disabled       Jan_05   svc:/system/fcoe_target:default 
>>> > online         Jan_05   svc:/network/iscsi/target:default 
>>> > online         Jan_05   svc:/system/ibsrp/target:default 
>>> > root at basket1:/tank/Share# svcadm restart /system/ibsrp/target 
>>> > root at basket1:/tank/Share# svcadm restart /network/iscsi/target 
>>> > root at basket1:/tank/Share# svcadm restart /system/stmf 
>>> > root at basket1:/tank/Share# svcs -a | grep target 
>>> > disabled       Jan_05   svc:/system/fcoe_target:default 
>>> > online*        22:43:03 svc:/system/ibsrp/target:default 
>>> > online*        22:43:13 svc:/network/iscsi/target:default 
>>> > root at basket1:/tank/Share# svcs -a | grep stmf 
>>> > online*        22:43:18 svc:/system/stmf:default 
>>> > root at basket1:/tank/Share# 
>>> > 
>>> > I?m doing a crash dump reboot. I?ll post the output somewhere. 
>>> > 
>>> > The output of echo '$<threadlist' | mdb -k is attached. 
>>> > 
>>> > <threadlist.out> 
>>> > 
>>> >> On Jan 8, 2016, at 3:11 PM, Matej Zerovnik <matej at zunaj.si <mailto:matej at zunaj.si>> wrote: 
>>> >> 
>>> >> Is the pool usable during comstar hang? 
>>> >> Can you write and read from the pool (test both, in my case, when pool froze, I wasn?t able to write to the pool, but I could read). 
>>> >> 
>>> >> Again, this might not be connected with Comstar, but in my case, Comstar and pool hang were exchanging. 
>>> >> 
>>> >> Matej 
>>> >> 
>>> >>> On 08 Jan 2016, at 20:11, Brian Hechinger <wonko at 4amlunch.net <mailto:wonko at 4amlunch.net>> wrote: 
>>> >>> 
>>> >>> Yeah, I?m using the 1068E to boot from (this has been supported since before Illumos) but that doesn?t have anything accessed by COMSTAR. 
>>> >>> 
>>> >>> It?s the ICH10R SATA that hosts the disks that COMSTAR shares out space from. 
>>> >>> 
>>> >>> -brian 
>>> >>> 
>>> >>>> On Jan 8, 2016, at 1:31 PM, Richard Jahnel <rjahnel at ellipseinc.com <mailto:rjahnel at ellipseinc.com>> wrote: 
>>> >>>> 
>>> >>>> First off, love SuperMicro good choice IMHO. 
>>> >>>> 
>>> >>>> This board has two on board controllers. 
>>> >>>> 
>>> >>>> LSI SAS1068E (not 100% sure there are working illumos drivers for this one) 
>>> >>>> 
>>> >>>> And 
>>> >>>> 
>>> >>>> Intel ICH10R SATA (So I'm guessing your using this one.) 
>>> >>>> 
>>> >>>> -----Original Message----- 
>>> >>>> From: OmniOS-discuss [ mailto:omnios-discuss-bounces at lists.omniti.com <mailto:omnios-discuss-bounces at lists.omniti.com>] On Behalf Of Brian Hechinger 
>>> >>>> Sent: Friday, January 08, 2016 12:16 PM 
>>> >>>> To: Matej Zerovnik <matej at zunaj.si <mailto:matej at zunaj.si>> 
>>> >>>> Cc: omnios-discuss <omnios-discuss at lists.omniti.com <mailto:omnios-discuss at lists.omniti.com>> 
>>> >>>> Subject: Re: [OmniOS-discuss] [discuss] COMSTAR hanging 
>>> >>>> 
>>> >>>> 
>>> >>>>> Which controller exactly do you have? 
>>> >>>> 
>>> >>>> Whatever ACHI stuff is built into the motherboard. Motherboard is X8DTL-3F. 
>>> >>>> 
>>> >>>>> Do you know firmware version? 
>>> >>>> 
>>> >>>> I?m assuming this is linked to the BIOS version? 
>>> >>>> 
>>> >>>>> Which hard drives? 
>>> >>>> 
>>> >>>> Hitachi-HUA723030ALA640-MKAOAA50-2.73TB 
>>> >>>> 
>>> >>>>> It might not tell much, but it?s good to have as much information as possible. 
>>> >>>>> 
>>> >>>>> When comstar hangs, can you telnet to the iSCSI port? 
>>> >>>>> What does svcs says, is the service running? 
>>> >>>>> What happens in you try to restart it? 
>>> >>>>> How do you restart it? 
>>> >>>> 
>>> >>>> I?ll try all these things next time. 
>>> >>>> 
>>> >>>>> In my case, svcs reported service running, but when I tried to telnet, there was no connection as well as there was no listening port opened when checking with 'netstat -an'. If I tried to restart target and stmf service, but stmf service got stucked in online* state and would not start. Reboot was the only solution in my case, but as I said, latest 014 release is working OK (but then again, load got reduced). 
>>> >>>> 
>>> >>>> All good info. Thanks! 
>>> >>>> 
>>> >>>> -brian 
>>> >>>> 
>>> >>>>> 
>>> >>>>> Matej 
>>> >>>>> 
>>> >>>>>> On 08 Jan 2016, at 17:50, Dave Pooser <dave-oo at pooserville.com <mailto:dave-oo at pooserville.com>> wrote: 
>>> >>>>>> 
>>> >>>>>>>> On Jan 8, 2016, at 11:22 AM, Brian Hechinger <wonko at 4amlunch.net <mailto:wonko at 4amlunch.net>> wrote: 
>>> >>>>>>>> 
>>> >>>>>>>> No, ZFS raid10 
>>> >>>>>>> 
>>> >>>>>>> Saw the HW-RAID term, and got concerned.  That's what, raidz2 in ZFS-ese? 
>>> >>>>>> 
>>> >>>>>> It's a zpool with multiple mirror vdevs. 
>>> >>>>>> 
>>> >>>>>> -- 
>>> >>>>>> Dave Pooser 
>>> >>>>>> Cat-Herder-in-Chief, Pooserville.com <http://pooserville.com/> 
>>> >>>>>> 
>>> >>>>>> 
>>> >>>>>> _______________________________________________ 
>>> >>>>>> OmniOS-discuss mailing list 
>>> >>>>>> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com> 
>>> >>>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss <http://lists.omniti.com/mailman/listinfo/omnios-discuss> 
>>> >>>>> 
>>> >>>>> _______________________________________________ 
>>> >>>>> OmniOS-discuss mailing list 
>>> >>>>> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com> 
>>> >>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss <http://lists.omniti.com/mailman/listinfo/omnios-discuss> 
>>> >>>> 
>>> >>>> _______________________________________________ 
>>> >>>> OmniOS-discuss mailing list 
>>> >>>> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com> 
>>> >>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss <http://lists.omniti.com/mailman/listinfo/omnios-discuss> 
>>> >>> 
>>> >> 
>>> > 
>>> 
>>> 
>>> 
>>> http://www.listbox.com <http://www.listbox.com/> 
>>> illumos-discuss | Archives <https://www.listbox.com/member/archive/182180/=now>  <https://www.listbox.com/member/archive/rss/182180/26677440-40b316d8> | Modify <https://www.listbox.com/member/?member_id=26677440&id_secret=26677440-8fd7f4fe> Your Subscription	 <http://www.listbox.com/>
>>> 
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com>
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss <http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>> 
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com>
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/ec44d641/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: iscsi-sessions.png
Type: image/png
Size: 25575 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/ec44d641/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3468 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160601/ec44d641/attachment-0001.bin>

From Josh.Barton at usurf.usu.edu  Thu Jun  2 23:43:58 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Thu, 2 Jun 2016 23:43:58 +0000
Subject: [OmniOS-discuss] GRUB after omni install
Message-ID: <45d8f5a3067c43358f4fbd4973788b5c@Ek.usurf.usu.edu>

After installing omnios on a brand new supermicro machine and rebooting all I get is GRUB _ with no ability to type or do anything. Any thoughts on how to fix this and what might have caused it? Thanks!

Josh Barton
USU Research Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160602/76dd7476/attachment.html>

From Fred_Liu at issi.com  Fri Jun  3 01:07:00 2016
From: Fred_Liu at issi.com (Fred Liu)
Date: Fri, 3 Jun 2016 01:07:00 +0000
Subject: [OmniOS-discuss] GRUB after omni install
In-Reply-To: <45d8f5a3067c43358f4fbd4973788b5c@Ek.usurf.usu.edu>
References: <45d8f5a3067c43358f4fbd4973788b5c@Ek.usurf.usu.edu>
Message-ID: <41D8AF3D9B6AA27A.B9CEC024-0CE6-4BE1-9268-002BF2F36875@mail.outlook.com>

you may try reinstalling grub by "grubinstall"

Fred

Get Outlook for iOS<https://aka.ms/o0ukef>

_____________________________
From: Josh Barton <josh.barton at usurf.usu.edu<mailto:josh.barton at usurf.usu.edu>>
Sent: ???, ?? 3, 2016 7:47 ??
Subject: [OmniOS-discuss] GRUB after omni install
To: <omnios-discuss at lists.omniti.com<mailto:omnios-discuss at lists.omniti.com>>


After installing omnios on a brand new supermicro machine and rebooting all I get isGRUB _ with no ability to type or do anything. Any thoughts on how to fix this and what might have caused it? Thanks!

Josh Barton
USU Research Foundation


After installing omnios on a brand new supermicro machine and rebooting all I get is GRUB _ with no ability to type or do anything. Any thoughts on how to fix this and what might have caused it? Thanks!

Josh Barton
USU Research Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160603/3dfe5e48/attachment.html>

From henson at acm.org  Fri Jun  3 01:09:45 2016
From: henson at acm.org (Paul B. Henson)
Date: Thu, 2 Jun 2016 18:09:45 -0700
Subject: [OmniOS-discuss] GRUB after omni install
In-Reply-To: <45d8f5a3067c43358f4fbd4973788b5c@Ek.usurf.usu.edu>
References: <45d8f5a3067c43358f4fbd4973788b5c@Ek.usurf.usu.edu>
Message-ID: <009701d1bd34$9e7dd210$db797630$@acm.org>

> From: Josh Barton
> Sent: Thursday, June 02, 2016 4:44 PM
> 
> After installing omnios on a brand new supermicro machine and rebooting
all
> I get is GRUB _ with no ability to type or do anything. Any thoughts on
how to
> fix this and what might have caused it? Thanks!

This is generally an indication that the stage 1 bootloader on the MBR was
unable to load the stage 1.5 bootloader from disk. Could you provide a few
more details on the system? What motherboard? What do you have the disk
connected to? What type/size of disk is it? How do you have it configured in
the BIOS?

It's possible either there was an error when the bootloader was installed,
in which case simply reinstalling the bootloader might resolve the issue, or
there is some incompatibility with your system that is causing the failure.

You can boot off of the install media to a shell, but I don't recall if you
can reinstall grub from it? You would need to import/mount your rpool, and
then the command would be something along the lines of:

installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c0t0d0s0

using the appropriate disk target of course.




From stephan.budach at JVM.DE  Fri Jun  3 13:20:50 2016
From: stephan.budach at JVM.DE (Stephan Budach)
Date: Fri, 3 Jun 2016 15:20:50 +0200
Subject: [OmniOS-discuss] ixgbe: breaking aggr on 10GbE X540-T2
In-Reply-To: <DDDC4D69-75C1-4B13-9DE8-EF20D8074632@omniti.com>
References: <5730818B.6020909@jvm.de>
	<8485B303-9706-42C4-B1B1-EAF6DAC949A3@omniti.com>
	<5730D110.5080305@jvm.de>
	<91D2ADD2-19BB-422B-9723-1E7F34DB43FA@omniti.com>
	<5733192A.60506@jvm.de>
	<0F866400-B276-4E81-A6CB-DB071A277F5F@omniti.com>
	<57335E9F.6080404@jvm.de>
	<3F300861-3541-4D3E-82D5-13FD061B8D9B@omniti.com>
	<573B0EC8.9090007@jvm.de>
	<DDDC4D69-75C1-4B13-9DE8-EF20D8074632@omniti.com>
Message-ID: <90e5048d-55a8-707d-4721-7e064ea2e054@jvm.de>

Hi Dale,

Am 17.05.16 um 20:55 schrieb Dale Ghent:
> On May 17, 2016, at 8:30 AM, Stephan Budach <stephan.budach at JVM.DE> wrote:
>
>> I have checked all of my ixgbe interfaces and they all report that now flow controll is in place, as you can see:
>>
>> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe0
>> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
>> ixgbe0       flowctrl        rw   no no             no,tx,rx,bi
>> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe1
>> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
>> ixgbe1       flowctrl        rw   no no             no,tx,rx,bi
>> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe2
>> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
>> ixgbe2       flowctrl        rw   no no             no,tx,rx,bi
>> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe3
>> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
>> ixgbe3       flowctrl        rw   no no             no,tx,rx,bi
>>
>> I then checked the ports on the Nexus switches and found out, that they do have outbound-flowcontrol enabled, but that is the case on any of those Nexus ports, including those, where this issue doesn't exist.
> Optimally you would have flow control turned off on both sides, as the switch still expects the ixgbe NIC to respond appropriately. To be honest, the only time to use ethernet flow control is if you are operating the interfaces for higher-level protocols which do not provide any sort of direct flow control themselves, such as FCoE. If the vast majority of traffic is TCP, leave it to the TCP stack to manage any local congestion on the link.
>
> /dale
I just wanted to wrap this up? I recently swapped that old Sun server 
with a new Supermicro X10-type, which has 4 10 GbE NICs on board, 
installed OmniOS r018 and my RSF-1 cluster software on it. Configured my 
two LACP aggregations and there hasn't been any issue since.
So, either it's something on the old server - it's a Sun Fire X4170M2 - 
or something on the Intel cards.

Cheers,
Stephan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160603/2d785b4c/attachment.html>

From fabio at fabiorabelo.wiki.br  Fri Jun  3 13:42:10 2016
From: fabio at fabiorabelo.wiki.br (=?UTF-8?Q?F=C3=A1bio_Rabelo?=)
Date: Fri, 3 Jun 2016 10:42:10 -0300
Subject: [OmniOS-discuss] ixgbe: breaking aggr on 10GbE X540-T2
In-Reply-To: <90e5048d-55a8-707d-4721-7e064ea2e054@jvm.de>
References: <5730818B.6020909@jvm.de>
	<8485B303-9706-42C4-B1B1-EAF6DAC949A3@omniti.com>
	<5730D110.5080305@jvm.de>
	<91D2ADD2-19BB-422B-9723-1E7F34DB43FA@omniti.com>
	<5733192A.60506@jvm.de>
	<0F866400-B276-4E81-A6CB-DB071A277F5F@omniti.com>
	<57335E9F.6080404@jvm.de>
	<3F300861-3541-4D3E-82D5-13FD061B8D9B@omniti.com>
	<573B0EC8.9090007@jvm.de>
	<DDDC4D69-75C1-4B13-9DE8-EF20D8074632@omniti.com>
	<90e5048d-55a8-707d-4721-7e064ea2e054@jvm.de>
Message-ID: <CAEekY65qKAw=M8Lp86hOjL=20CdXTNPh3xtU_Emcq2A-kZomrw@mail.gmail.com>

Hi to all

A question:

This are the board you used ?

https://www.supermicro.com/products/motherboard/Xeon/C600/X10DRi-T4_.cfm

If so, this board uses Intel X540, and this issue are only with Intel
X550 chips !


F?bio Rabelo

2016-06-03 10:20 GMT-03:00 Stephan Budach <stephan.budach at jvm.de>:
> Hi Dale,
>
> Am 17.05.16 um 20:55 schrieb Dale Ghent:
>
> On May 17, 2016, at 8:30 AM, Stephan Budach <stephan.budach at JVM.DE> wrote:
>
> I have checked all of my ixgbe interfaces and they all report that now flow
> controll is in place, as you can see:
>
> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe0
> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
> ixgbe0       flowctrl        rw   no no             no,tx,rx,bi
> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe1
> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
> ixgbe1       flowctrl        rw   no no             no,tx,rx,bi
> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe2
> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
> ixgbe2       flowctrl        rw   no no             no,tx,rx,bi
> root at zfsha01colt:/root# dladm show-linkprop -p flowctrl ixgbe3
> LINK         PROPERTY        PERM VALUE DEFAULT        POSSIBLE
> ixgbe3       flowctrl        rw   no no             no,tx,rx,bi
>
> I then checked the ports on the Nexus switches and found out, that they do
> have outbound-flowcontrol enabled, but that is the case on any of those
> Nexus ports, including those, where this issue doesn't exist.
>
> Optimally you would have flow control turned off on both sides, as the
> switch still expects the ixgbe NIC to respond appropriately. To be honest,
> the only time to use ethernet flow control is if you are operating the
> interfaces for higher-level protocols which do not provide any sort of
> direct flow control themselves, such as FCoE. If the vast majority of
> traffic is TCP, leave it to the TCP stack to manage any local congestion on
> the link.
>
> /dale
>
> I just wanted to wrap this up? I recently swapped that old Sun server with a
> new Supermicro X10-type, which has 4 10 GbE NICs on board, installed OmniOS
> r018 and my RSF-1 cluster software on it. Configured my two LACP
> aggregations and there hasn't been any issue since.
> So, either it's something on the old server - it's a Sun Fire X4170M2 - or
> something on the Intel cards.
>
> Cheers,
> Stephan
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From stephan.budach at JVM.DE  Fri Jun  3 15:08:20 2016
From: stephan.budach at JVM.DE (Stephan Budach)
Date: Fri, 3 Jun 2016 17:08:20 +0200
Subject: [OmniOS-discuss] ixgbe: breaking aggr on 10GbE X540-T2
In-Reply-To: <CAEekY65qKAw=M8Lp86hOjL=20CdXTNPh3xtU_Emcq2A-kZomrw@mail.gmail.com>
References: <5730818B.6020909@jvm.de>
	<8485B303-9706-42C4-B1B1-EAF6DAC949A3@omniti.com>
	<5730D110.5080305@jvm.de>
	<91D2ADD2-19BB-422B-9723-1E7F34DB43FA@omniti.com>
	<5733192A.60506@jvm.de>
	<0F866400-B276-4E81-A6CB-DB071A277F5F@omniti.com>
	<57335E9F.6080404@jvm.de>
	<3F300861-3541-4D3E-82D5-13FD061B8D9B@omniti.com>
	<573B0EC8.9090007@jvm.de>
	<DDDC4D69-75C1-4B13-9DE8-EF20D8074632@omniti.com>
	<90e5048d-55a8-707d-4721-7e064ea2e054@jvm.de>
	<CAEekY65qKAw=M8Lp86hOjL=20CdXTNPh3xtU_Emcq2A-kZomrw@mail.gmail.com>
Message-ID: <ae9ad3d6-457f-d8e0-7ef6-98caea2b0a87@jvm.de>

Am 03.06.16 um 15:42 schrieb F?bio Rabelo:
> Hi to all
>
> A question:
>
> This are the board you used ?
>
> https://www.supermicro.com/products/motherboard/Xeon/C600/X10DRi-T4_.cfm
>
> If so, this board uses Intel X540, and this issue are only with Intel
> X550 chips !
>
>
> F?bio Rabelo
Yes, this is the board I got. Actually, it's a  X10DRi-T4+

Cheers,
Stephan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160603/d0dc0aa0/attachment-0001.html>

From garrett at damore.org  Fri Jun  3 19:48:17 2016
From: garrett at damore.org (Garrett D'Amore)
Date: Fri, 3 Jun 2016 12:48:17 -0700
Subject: [OmniOS-discuss] [developer] ENABLE_PERL64
In-Reply-To: <49246DD3-ADAE-4F17-A8F8-AD6B7570CDC7@racktopsystems.com>
References: <5751CD8B.1090100@free.fr>
	<49246DD3-ADAE-4F17-A8F8-AD6B7570CDC7@racktopsystems.com>
Message-ID: <9194F3A7-5568-415A-9B1D-06EDBFFFE103@damore.org>

I just wish we could excise all perl from the gate.  Its an unending source of headaches. 

Sent from my iPhone

> On Jun 3, 2016, at 12:25 PM, Andy Stormont <astormont at racktopsystems.com> wrote:
> 
> Hi Richard,
> 
> There?s a cleaner way to handle optional compiles: do it on the dependency line:
> 
>> install: $(ROOTPERLEXT) $(ROOTPERLMOD)
>> $(ENABLE_PERL64)install: $(ROOTPERLEXT64) $(ROOTPERLMOD64)
> 
> That way you don?t need to prefix all of the 64bit variable with $(ENABLE_PERL64).
> 
> - Andy
> 
> 
>> On 3 Jun 2016, at 19:33, Richard PALO <richard.palo at free.fr> wrote:
>> 
>> Rather frustrated on omnios after 'onu' to vanilla upstream (that is, non illumos-omnios based) 
>> gate builds because of the native omnios multi arch perl environment.
>> 
>> What typically happens is, for example, intrd chokes with:
>>> Can't locate Sun/Solaris/Kstat.pm in @INC (@INC contains: /usr/perl5/site_perl/5.16.1/i86pc-solaris-thread-multi-64 /usr/perl5/site_perl/5.16.1 /usr/perl5/vendor_perl/5.16.1/i86pc-solaris-thread-multi-64 /usr/perl5/vendor_perl/5.16.1 /usr/perl5/5.16.1/lib/i86pc-solaris-thread-multi-64 /usr/perl5/5.16.1/lib .) at /usr/lib/intrd line 66.
>> 
>> so attached is an attempt to get the gate to build supporting optional multiarch based upon an
>> adaptation of illumos-omnios/master.
>> 
>> To build with this via bldenv.sh, I updated my illumos.sh with:
>>> export PERL_VERSION=5.16.1
>>> export PERL_ARCH=i86pc-solaris-thread-multi-64int
>>> export PERL_PKGVERS=
>>> export ENABLE_PERL64=
>>> export PERL_ARCH64=i86pc-solaris-thread-multi-64
>> 
>> where the last two are the only changes thus far for omnios users building the gate.
>> 
>> with 'sh bldenv.sh -d illumos.sh' and cd usr/src/cmd/perl  I can now
>>> dmake clobber ; dmake install
>> cleanly with, or without the ENABLE_PERL64= environment variables.
>> 
>> It would be cool to see how hipster or others fare with this...
>> 
>> I would like to mention that since both hipster and omnios have at least perl 5.16.1,
>> I believe there is perhaps only smartos that still has something prior in illumos-extra.
>> Perhaps this is a good time to set PERL_VERSION by default to 5.16.1 or, better, to 5.22
>> 
>> So? Thanks in advance for feedback.
>> I'm running on this now.
>> --
>> 
>> Richard PALO
>> 
>> <0001-ENABLE_PERL64-multiarch-builds.patch>
> 
> 
> 
> -------------------------------------------
> illumos-developer
> Archives: https://www.listbox.com/member/archive/182179/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/182179/21239177-3604570e
> Modify Your Subscription: https://www.listbox.com/member/?member_id=21239177&id_secret=21239177-2d0c9337
> Powered by Listbox: http://www.listbox.com

From danmcd at omniti.com  Fri Jun  3 19:49:18 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 3 Jun 2016 15:49:18 -0400
Subject: [OmniOS-discuss] [developer] ENABLE_PERL64
In-Reply-To: <9194F3A7-5568-415A-9B1D-06EDBFFFE103@damore.org>
References: <5751CD8B.1090100@free.fr>
	<49246DD3-ADAE-4F17-A8F8-AD6B7570CDC7@racktopsystems.com>
	<9194F3A7-5568-415A-9B1D-06EDBFFFE103@damore.org>
Message-ID: <04A2C5A5-37AB-4243-B72B-90B722BEF2B5@omniti.com>


> On Jun 3, 2016, at 3:48 PM, Garrett D'Amore <garrett at damore.org> wrote:
> 
> I just wish we could excise all perl from the gate.  Its an unending source of headaches. 

Someone wanna pitch the final N innings of this?

	http://cr.illumos.org/~webrev/0xffea/intrd-kernel-04/

Dan


From garrett at damore.org  Fri Jun  3 20:08:47 2016
From: garrett at damore.org (Garrett D'Amore)
Date: Fri, 3 Jun 2016 13:08:47 -0700
Subject: [OmniOS-discuss] [developer] ENABLE_PERL64
In-Reply-To: <04A2C5A5-37AB-4243-B72B-90B722BEF2B5@omniti.com>
References: <5751CD8B.1090100@free.fr>
	<49246DD3-ADAE-4F17-A8F8-AD6B7570CDC7@racktopsystems.com>
	<9194F3A7-5568-415A-9B1D-06EDBFFFE103@damore.org>
	<04A2C5A5-37AB-4243-B72B-90B722BEF2B5@omniti.com>
Message-ID: <76EE53DB-3D53-4E51-BFA5-5C50B1CC6957@damore.org>

i dont recall seeing this before.  what is the status and history and how can i help?

Sent from my iPhone

> On Jun 3, 2016, at 12:49 PM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> 
>> On Jun 3, 2016, at 3:48 PM, Garrett D'Amore <garrett at damore.org> wrote:
>> 
>> I just wish we could excise all perl from the gate.  Its an unending source of headaches.
> 
> Someone wanna pitch the final N innings of this?
> 
>    http://cr.illumos.org/~webrev/0xffea/intrd-kernel-04/
> 
> Dan
> 
> 
> 
> -------------------------------------------
> illumos-developer
> Archives: https://www.listbox.com/member/archive/182179/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/182179/21239177-3604570e
> Modify Your Subscription: https://www.listbox.com/member/?member_id=21239177&id_secret=21239177-2d0c9337
> Powered by Listbox: http://www.listbox.com

From richard at netbsd.org  Sat Jun  4 11:10:49 2016
From: richard at netbsd.org (Richard PALO)
Date: Sat, 04 Jun 2016 13:10:49 +0200
Subject: [OmniOS-discuss] [developer] ENABLE_PERL64
In-Reply-To: <12A7C1D0-A4F9-4120-BE0D-21524DD7F50E@gmail.com>
References: <5751CD8B.1090100@free.fr>
	<49246DD3-ADAE-4F17-A8F8-AD6B7570CDC7@racktopsystems.com>
	<9194F3A7-5568-415A-9B1D-06EDBFFFE103@damore.org>
	<5751EE64.50800@free.fr>
	<7ED4FD1D-3EC7-44E0-B8E7-C60F4F9D479B@damore.org>
	<12A7C1D0-A4F9-4120-BE0D-21524DD7F50E@gmail.com>
Message-ID: <5752B739.5080804@netbsd.org>

Le 04/06/16 09:27, Adam ?tevko a ?crit :
> Hello,
> 
> and what about projadd/projmod/projdel/Sun::Solaris::Project?
> 
> We have kstat rewritten in C, however this wasn?t done for projadd/projmod/projdel. Removing them from gate without proper replacement will cause headaches.
> 

the following use these routines:
> richard at omnis:/home/richard/src/illumos-gate$ git grep -l Sun::Solaris::  |grep -Ev 'man|contrib\/Sun'
> usr/src/cmd/abi/appcert/scripts/AppcertUtil.pm
> usr/src/cmd/abi/appcert/scripts/abi_index.pl
> usr/src/cmd/abi/appcert/scripts/appcert.pl
> usr/src/cmd/abi/appcert/scripts/symcheck.pl
> usr/src/cmd/abi/appcert/scripts/symprof.pl
> usr/src/cmd/abi/appcert/scripts/symreport.pl
> usr/src/cmd/auditrecord/auditrecord.pl
> usr/src/cmd/auditrecord/mkmsg.pl
> usr/src/cmd/intrd/intrd.pl
> usr/src/cmd/lgrpinfo/lgrpinfo.pl
> usr/src/cmd/pginfo/pginfo.pl
> usr/src/cmd/pgstat/pgstat.pl
> usr/src/cmd/projadd/projadd.pl
> usr/src/cmd/projadd/projdel.pl
> usr/src/cmd/projadd/projmod.pl
> usr/src/cmd/sgs/lari/lari.pl
> usr/src/cmd/stat/arcstat/arcstat.pl

where, as Garrett said, only intrd uses internally Sun::Solaris::Intrs

Seems to me while it would be great to blast ::Intrs when the 'C' version of intrd commits, 
omnios users using 'onu' are still at risk with all these perl dependencies existing where the
multi arch perl/contrib is not done, either in the gate or natively in omnios-build.

This is the reason for at least an interim solution proposed by ENABLE_PERL64=
-- 
Richard PALO


From garrett at damore.org  Sat Jun  4 15:00:08 2016
From: garrett at damore.org (Garrett D'Amore)
Date: Sat, 4 Jun 2016 08:00:08 -0700
Subject: [OmniOS-discuss] [developer] ENABLE_PERL64
In-Reply-To: <5752B739.5080804@netbsd.org>
References: <5751CD8B.1090100@free.fr>
	<49246DD3-ADAE-4F17-A8F8-AD6B7570CDC7@racktopsystems.com>
	<9194F3A7-5568-415A-9B1D-06EDBFFFE103@damore.org>
	<5751EE64.50800@free.fr>
	<7ED4FD1D-3EC7-44E0-B8E7-C60F4F9D479B@damore.org>
	<12A7C1D0-A4F9-4120-BE0D-21524DD7F50E@gmail.com>
	<5752B739.5080804@netbsd.org>
Message-ID: <A5270CAE-79A6-4380-99DC-05BEF195F16E@damore.org>

we could fix then others too. It probably is not that much effort. :)

Sent from my iPhone

> On Jun 4, 2016, at 4:10 AM, Richard PALO <richard at netbsd.org> wrote:
> 
> Le 04/06/16 09:27, Adam ?tevko a ?crit :
>> Hello,
>> 
>> and what about projadd/projmod/projdel/Sun::Solaris::Project?
>> 
>> We have kstat rewritten in C, however this wasn?t done for projadd/projmod/projdel. Removing them from gate without proper replacement will cause headaches.
> 
> the following use these routines:
>> richard at omnis:/home/richard/src/illumos-gate$ git grep -l Sun::Solaris::  |grep -Ev 'man|contrib\/Sun'
>> usr/src/cmd/abi/appcert/scripts/AppcertUtil.pm
>> usr/src/cmd/abi/appcert/scripts/abi_index.pl
>> usr/src/cmd/abi/appcert/scripts/appcert.pl
>> usr/src/cmd/abi/appcert/scripts/symcheck.pl
>> usr/src/cmd/abi/appcert/scripts/symprof.pl
>> usr/src/cmd/abi/appcert/scripts/symreport.pl
>> usr/src/cmd/auditrecord/auditrecord.pl
>> usr/src/cmd/auditrecord/mkmsg.pl
>> usr/src/cmd/intrd/intrd.pl
>> usr/src/cmd/lgrpinfo/lgrpinfo.pl
>> usr/src/cmd/pginfo/pginfo.pl
>> usr/src/cmd/pgstat/pgstat.pl
>> usr/src/cmd/projadd/projadd.pl
>> usr/src/cmd/projadd/projdel.pl
>> usr/src/cmd/projadd/projmod.pl
>> usr/src/cmd/sgs/lari/lari.pl
>> usr/src/cmd/stat/arcstat/arcstat.pl
> 
> where, as Garrett said, only intrd uses internally Sun::Solaris::Intrs
> 
> Seems to me while it would be great to blast ::Intrs when the 'C' version of intrd commits, 
> omnios users using 'onu' are still at risk with all these perl dependencies existing where the
> multi arch perl/contrib is not done, either in the gate or natively in omnios-build.
> 
> This is the reason for at least an interim solution proposed by ENABLE_PERL64=
> -- 
> Richard PALO
> 

From danmcd at omniti.com  Mon Jun  6 18:47:53 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 6 Jun 2016 14:47:53 -0400
Subject: [OmniOS-discuss] SECURITY AND FEATURE UPDATES for OmniOS LTS, Stable,
	and old-Stable
Message-ID: <FD4BAABC-DA92-408D-BDDA-AACD52079B27@omniti.com>

Please "pkg update" on your OmniOS r151014, r151016, or r151018 machines at your earliest convenience.

The following security fixes are on ALL THREE:

	? libxml update to 2.9.4
	? DTrace stability fixes (illumos 7033-7035)
	? setid binaries disallow ld.so.1's $ORIGIN (illumos 6987)
	? ZFS no longer bleeds zvol entries into non-global zones (illumos 7019,7020)
	? NTP to 4.2.8p8
	? expat to 2.1.1 (with CVE 2016-0718 fix)

The following other fixes are on r151014 and r151018:

	? missing MCFG table should lead to I/O PCIe config access (illumos 6859)
	? allow sendfile() on AF_UNIX sockets (illumos 6861)
	? ZFS-helper: kernel virtual memory fragmentation leads to hang (illumos 6914)
	? STMF kstat free is using an improper size for kmem_free(). (illumos 6938)
	? Driver support for Solarflare 10G and 40G ethernet

The following are new to r151014, but are already on r151018:

	? Timezone, USB, and PCI data files updates. (Now matches r151018)
	? Driver support for vmxnet3s
	? MSI-X support fixed for virtio
	? The debug.illumos pkg(5) variant.

Each release's release notes have been updated, and install media for r151014 and r151018 have been updated as well.

Bloody will be getting an IPS-only update by the end of the day.  Watch for that in a separate mail.

Thank you, and happy updating!
Dan


From danmcd at omniti.com  Mon Jun  6 20:08:34 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 6 Jun 2016 16:08:34 -0400
Subject: [OmniOS-discuss] Bloody update - June 6th,
	plus small LX porting update
Message-ID: <02E50B85-6139-45ED-BA30-E6109F2304D0@omniti.com>

I've updated only on the http://pkg.omniti.com/omnios/bloody/ repo the bloody image.

The last merge with illumos-gate was a2f72b6.  All of the omnios-build non-illumos changes are equal to those in r151018.

I will be less frequent with these because of my attempt to port LX to OmniOS:

	https://github.com/danmcd/io-lx-public/

That's my public repo.  You can feel free to pull from it.  I will announce drastic overhauls to it on this list if I do something like burn-it-to-the-ground (again).

Thanks,
Dan


From danmcd at omniti.com  Mon Jun  6 20:09:23 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 6 Jun 2016 16:09:23 -0400
Subject: [OmniOS-discuss] Bloody update - June 6th,
	plus small LX porting update
In-Reply-To: <02E50B85-6139-45ED-BA30-E6109F2304D0@omniti.com>
References: <02E50B85-6139-45ED-BA30-E6109F2304D0@omniti.com>
Message-ID: <023D95F8-3246-4AFB-8B6B-3CF24F34427A@omniti.com>


> On Jun 6, 2016, at 4:08 PM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> I've updated only on the http://pkg.omniti.com/omnios/bloody/ repo the bloody image.

Shoot --> please wait 30 minutes.  I pressed "send" in the middle of "pkgrecv....".

Sorry,
Dan


From davide.poletto at gmail.com  Mon Jun  6 22:04:20 2016
From: davide.poletto at gmail.com (Davide Poletto)
Date: Tue, 7 Jun 2016 00:04:20 +0200
Subject: [OmniOS-discuss] OmniOS 151014 LTS (omnios-b13298f) pkg update -v
 shows an osnet-incorporation related message.
Message-ID: <CANKMAMaoiBPfexWma_kyebmyNC90KM3zBtqExQ0ThYpBq_u9Cw@mail.gmail.com>

Hi all,

On a OmniOS 151014 LTS (updated today from *omnios-aab7656* April 2016 to
*omnios-b13298f* June 2016) I was performing a *post update post reboot* *pkg
update -v* just to check if all packages were OK and I receive:

root at nas01:/root# pkg update -v
Creating Plan (Running solver): -
pkg update: No solution was found to satisfy constraints
Plan Creation: Package solver has not found a solution to update to latest
available versions.
This may indicate an overly constrained set of packages are installed.

latest incorporations:

  pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11
,5.11-0.151014:20160603T031035Z
Dependency analysis is unable to determine exact cause.
Try specifying expected results to obtain more detailed error messages.

Is there anything I should check or be worry about?

Here the *pkg update -v* done where the system was at (updated)
*omnios-aab7656*:

root at nas01:/root# pkg update -v
           Packages to install:         2
            Packages to update:       303
     Estimated space available:  33.70 GB
Estimated space to be consumed: 495.43 MB
       Create boot environment:       Yes
     Activate boot environment:       Yes
Create backup boot environment:        No
          Rebuild boot archive:       Yes

Changed packages:
omnios
  driver/network/sfxge
    None -> 0.5.11-0.151014:20160603T031058Z
  driver/network/vmxnet3s
    None -> 0.5.11-0.151014:20160603T031058Z
  SUNWcs
    0.5.11-0.151014:20160420T161518Z -> 0.5.11-0.151014:20160603T031037Z
  SUNWcsd
    0.5.11-0.151014:20160420T161518Z -> 0.5.11-0.151014:20160603T031037Z
  compatibility/ucb
    0.5.11-0.151014:20160420T161531Z -> 0.5.11-0.151014:20160603T031050Z
  developer/debug/mdb
    0.5.11-0.151014:20160420T161531Z -> 0.5.11-0.151014:20160603T031051Z
  developer/dtrace
    0.5.11-0.151014:20160420T161531Z -> 0.5.11-0.151014:20160603T031051Z
  developer/linker
    0.5.11-0.151014:20160420T161531Z -> 0.5.11-0.151014:20160603T031051Z
  diagnostic/cpu-counters
    0.5.11-0.151014:20160420T161532Z -> 0.5.11-0.151014:20160603T031051Z
  diagnostic/latencytop
    0.5.11-0.151014:20160420T161532Z -> 0.5.11-0.151014:20160603T031051Z
  diagnostic/powertop
    0.5.11-0.151014:20160420T161532Z -> 0.5.11-0.151014:20160603T031051Z
  driver/audio
    0.5.11-0.151014:20160420T161532Z -> 0.5.11-0.151014:20160603T031052Z
  driver/crypto/dca
    0.5.11-0.151014:20160420T161532Z -> 0.5.11-0.151014:20160603T031052Z
  driver/crypto/tpm
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031052Z
  driver/firewire
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031052Z
  driver/graphics/agpgart
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031052Z
  driver/graphics/atiatom
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031052Z
  driver/graphics/drm
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031053Z
  driver/i86pc/fipe
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031053Z
  driver/i86pc/ioat
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031053Z
  driver/i86pc/platform
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031053Z
  driver/misc/virtio
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031053Z
  driver/network/afe
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031053Z
  driver/network/amd8111s
    0.5.11-0.151014:20160420T161533Z -> 0.5.11-0.151014:20160603T031053Z
  driver/network/atge
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031053Z
  driver/network/bfe
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/bge
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/bnx
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/bnxe
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/bpf
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/chxge
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/dmfe
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/e1000g
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/elxl
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/emlxs
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/eoib
    0.5.11-0.151014:20160420T161534Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/fcip
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031054Z
  driver/network/fcp
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/fcsm
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/fp
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/hermon
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/hme
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/hxge
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/ib
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/ibdma
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/ibp
    0.5.11-0.151014:20160420T161535Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/igb
    0.5.11-0.151014:20160420T161536Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/iprb
    0.5.11-0.151014:20160420T161536Z -> 0.5.11-0.151014:20160603T031055Z
  driver/network/ixgb
    0.5.11-0.151014:20160420T161536Z -> 0.5.11-0.151014:20160603T031056Z
  driver/network/ixgbe
    0.5.11-0.151014:20160420T161536Z -> 0.5.11-0.151014:20160603T031056Z
  driver/network/mxfe
    0.5.11-0.151014:20160420T161536Z -> 0.5.11-0.151014:20160603T031056Z
  driver/network/myri10ge
    0.5.11-0.151014:20160420T161536Z -> 0.5.11-0.151014:20160603T031056Z
  driver/network/nge
    0.5.11-0.151014:20160420T161536Z -> 0.5.11-0.151014:20160603T031056Z
  driver/network/ntxn
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031056Z
  driver/network/nxge
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/ofk
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/pcn
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/platform
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/qlc
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/rds
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/rdsv3
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/rge
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/rpcib
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/rtls
    0.5.11-0.151014:20160420T161537Z -> 0.5.11-0.151014:20160603T031057Z
  driver/network/sdp
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/sdpib
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/sfe
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/tavor
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/usbecm
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/vioif
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/vr
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/xge
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/network/yge
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031058Z
  driver/pcmcia
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031059Z
  driver/serial/usbftdi
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031059Z
  driver/serial/usbsacm
    0.5.11-0.151014:20160420T161538Z -> 0.5.11-0.151014:20160603T031059Z
  driver/serial/usbser
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/serial/usbser_edge
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/serial/usbsksp
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/serial/usbsksp/usbs49_fw
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/serial/usbsprl
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/aac
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/adpu320
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/ahci
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/amr
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/arcmsr
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/ata
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/bcm_sata
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/blkdev
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/cpqary3
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/glm
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/lsimega
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031059Z
  driver/storage/marvell88sx
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/mega_sas
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/mpt_sas
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/mr_sas
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/nv_sata
    0.5.11-0.151014:20160420T161539Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/pmcs
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/sbp2
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/scsa1394
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/sdcard
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/ses
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/si3124
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/smp
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/storage/vioblk
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/usb
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/usb/ugen
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  driver/xvm/pv
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031100Z
  entire
    11-0.151014:20160104T154618Z -> 11-0.151014:20160602T180308Z
  incorporation/jeos/illumos-gate
    11-0.151014:20151112T205755Z -> 11-0.151014:20160602T180308Z
  install/beadm
    0.5.11-0.151014:20160420T161540Z -> 0.5.11-0.151014:20160603T031101Z
  library/expat
    2.1.0-0.151014:20150402T213301Z -> 2.1.1-0.151014:20160602T180327Z
  library/libtecla
    1.6.0-0.151014:20160420T161540Z -> 1.6.0-0.151014:20160603T031101Z
  library/libxml2
    2.9.3-0.151014:20160506T213935Z -> 2.9.4-0.151014:20160602T180301Z
  library/security/tcp-wrapper
    7.6-0.151014:20160420T161541Z -> 7.6-0.151014:20160603T031101Z
  locale/af
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/ar
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/as
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/az
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/be
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/bg
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/bg-extra
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/bn
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/bo
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/bs
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/ca
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031102Z
  locale/ca-extra
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031101Z
  locale/cs
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031102Z
  locale/cs-extra
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031102Z
  locale/da
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031102Z
  locale/da-extra
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031102Z
  locale/de
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031102Z
  locale/de-extra
    0.5.11-0.151014:20160420T161541Z -> 0.5.11-0.151014:20160603T031102Z
  locale/el
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/el-extra
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/en
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/en-extra
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/es
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/es-extra
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/et
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/fi
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/fi-extra
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/fil
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/fr
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/fr-extra
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/ga
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/gu
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031102Z
  locale/he
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/hi
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/hr
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/hr-extra
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/hu
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/hu-extra
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/hy
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/id
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/ii
    0.5.11-0.151014:20160420T161542Z -> 0.5.11-0.151014:20160603T031103Z
  locale/is
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/is-extra
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/it
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/it-extra
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/ja
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/ka
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/kk
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/km
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/kn
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/ko
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/kok
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/lt
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/lt-extra
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/lv
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/lv-extra
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031103Z
  locale/mk
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/mk-extra
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/ml
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/mn
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/mr
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/ms
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/mt
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/nb
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/ne
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/nl
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/nl-extra
    0.5.11-0.151014:20160420T161543Z -> 0.5.11-0.151014:20160603T031104Z
  locale/nn
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/or
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/pa
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/pl
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/pl-extra
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/pt
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/pt-extra
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/ro
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/ru
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/ru-extra
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/sa
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/si
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/sk
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031104Z
  locale/sl
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/sq
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/sq-extra
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/sr
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/sv
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/sv-extra
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/ta
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/te
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/th
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/th-extra
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/tr
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/tr-extra
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/ug
    0.5.11-0.151014:20160420T161544Z -> 0.5.11-0.151014:20160603T031105Z
  locale/uk
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  locale/ur
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  locale/vi
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  locale/zh_cn
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  locale/zh_hk
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  locale/zh_mo
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  locale/zh_sg
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  locale/zh_tw
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  naming/ldap
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031105Z
  network/bridging
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031106Z
  network/ftp
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031106Z
  network/ipfilter
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031106Z
  network/iscsi/initiator
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031106Z
  network/iscsi/iser
    0.5.11-0.151014:20160420T161545Z -> 0.5.11-0.151014:20160603T031106Z
  network/ssh
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031106Z
  network/ssh/ssh-key
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031106Z
  network/telnet
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031106Z
  package/svr4
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031106Z
  runtime/perl/module/sun-solaris
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031107Z
  service/fault-management
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031107Z
  service/file-system/nfs
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031107Z
  service/file-system/smb
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031107Z
  service/hal
    0.5.11-0.151014:20160420T161546Z -> 0.5.11-0.151014:20160603T031107Z
  service/network/dns/mdns
    0.5.11-0.151014:20160420T161547Z -> 0.5.11-0.151014:20160603T031107Z
  service/network/network-clients
    0.5.11-0.151014:20160420T161547Z -> 0.5.11-0.151014:20160603T031108Z
  service/network/ntp
    4.2.8.7-0.151014:20160503T142738Z -> 4.2.8.8-0.151014:20160606T145645Z
  service/network/ssh
    0.5.11-0.151014:20160420T161547Z -> 0.5.11-0.151014:20160603T031108Z
  service/picl
    0.5.11-0.151014:20160420T161548Z -> 0.5.11-0.151014:20160603T031108Z
  service/resource-pools
    0.5.11-0.151014:20160420T161548Z -> 0.5.11-0.151014:20160603T031108Z
  service/resource-pools/poold
    0.5.11-0.151014:20160420T161548Z -> 0.5.11-0.151014:20160603T031108Z
  service/security/gss
    0.5.11-0.151014:20160420T161548Z -> 0.5.11-0.151014:20160603T031108Z
  service/security/kerberos-5
    0.5.11-0.151014:20160420T161548Z -> 0.5.11-0.151014:20160603T031108Z
  service/storage/fibre-channel/fc-fabric
    0.5.11-0.151014:20160420T161548Z -> 0.5.11-0.151014:20160603T031109Z
  service/storage/removable-media
    0.5.11-0.151014:20160420T161548Z -> 0.5.11-0.151014:20160603T031109Z
  storage/stmf
    0.5.11-0.151014:20160420T161549Z -> 0.5.11-0.151014:20160603T031110Z
  storage/svm
    0.5.11-0.151014:20160420T161549Z -> 0.5.11-0.151014:20160603T031110Z
  system/accounting/legacy
    0.5.11-0.151014:20160420T161549Z -> 0.5.11-0.151014:20160603T031110Z
  system/boot/grub
    0.97-0.151014:20160420T161549Z -> 0.97-0.151014:20160603T031110Z
  system/boot/real-mode
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031110Z
  system/boot/wanboot
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031110Z
  system/boot/wanboot/internal
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031110Z
  system/data/hardware-registry
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031110Z
  system/data/keyboard/keytables
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031110Z
  system/data/terminfo
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031111Z
  system/extended-system-utilities
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031111Z
  system/file-system/autofs
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031111Z
  system/file-system/nfs
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031111Z
  system/file-system/smb
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031111Z
  system/file-system/udfs
    0.5.11-0.151014:20160420T161550Z -> 0.5.11-0.151014:20160603T031111Z
  system/file-system/zfs
    0.5.11-0.151014:20160420T161551Z -> 0.5.11-0.151014:20160603T031111Z
  system/flash/fwflash
    0.5.11-0.151014:20160420T161551Z -> 0.5.11-0.151014:20160603T031111Z
  system/fru-id
    0.5.11-0.151014:20160420T161551Z -> 0.5.11-0.151014:20160603T031112Z
  system/fru-id/platform
    0.5.11-0.151014:20160420T161551Z -> 0.5.11-0.151014:20160603T031112Z
  system/ipc
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/cpu-counters
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/dtrace/providers
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/dynamic-reconfiguration/i86pc
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/platform
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/power
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/secure-rpc
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/security/gss
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/suspend-resume
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/kernel/ultra-wideband
    0.5.11-0.151014:20160420T161552Z -> 0.5.11-0.151014:20160603T031113Z
  system/library
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/library/libdiskmgt
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/libfcoe
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/math
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/platform
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/policykit
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/processor
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/security/gss
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/security/gss/diffie-hellman
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/security/gss/spnego
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/security/libsasl
    0.5.11-0.151014:20160420T161553Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/storage/fibre-channel/hbaapi
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/storage/fibre-channel/libsun_fc
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031114Z
  system/library/storage/ima
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/library/storage/ima/header-ima
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/library/storage/libmpapi
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/library/storage/libmpscsi_vhci
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/library/storage/scsi-plugins
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/man
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/management/snmp/sea/sea-config
    0.5.11-0.151014:20160420T161554Z -> 0.5.11-0.151014:20160603T031115Z
  system/network
    0.5.11-0.151014:20160420T161556Z -> 0.5.11-0.151014:20160603T031117Z
  system/network/mailwrapper
    0.5.11-0.151014:20160420T161555Z -> 0.5.11-0.151014:20160603T031116Z
  system/network/nis
    0.5.11-0.151014:20160420T161555Z -> 0.5.11-0.151014:20160603T031116Z
  system/network/routing
    0.5.11-0.151014:20160420T161555Z -> 0.5.11-0.151014:20160603T031116Z
  system/network/udapl
    0.5.11-0.151014:20160420T161555Z -> 0.5.11-0.151014:20160603T031116Z
  system/network/udapl/udapl-tavor
    0.5.11-0.151014:20160420T161555Z -> 0.5.11-0.151014:20160603T031116Z
  system/scheduler/fss
    0.5.11-0.151014:20160420T161556Z -> 0.5.11-0.151014:20160603T031117Z
  system/storage/fibre-channel/port-utility
    0.5.11-0.151014:20160420T161556Z -> 0.5.11-0.151014:20160603T031117Z
  system/storage/luxadm
    0.5.11-0.151014:20160420T161556Z -> 0.5.11-0.151014:20160603T031117Z
  system/xopen/xcu4
    0.5.11-0.151014:20160420T161557Z -> 0.5.11-0.151014:20160603T031118Z
  system/zones
    0.5.11-0.151014:20160420T161557Z -> 0.5.11-0.151014:20160603T031118Z
  text/doctools
    0.5.11-0.151014:20160420T161557Z -> 0.5.11-0.151014:20160603T031118Z
  text/locale
    0.5.11-0.151014:20160420T161557Z -> 0.5.11-0.151014:20160603T031118Z
DOWNLOAD                                PKGS         FILES    XFER (MB)
SPEED
Completed                            305/305     2581/2581    85.3/85.3
449k/s

PHASE                                          ITEMS
Removing old actions                         538/538
Installing new actions                       917/917
Updating modified actions                  3654/3654
Updating package state database                 Done
Updating package cache                       303/303
Updating image state                            Done
Creating fast lookup database                   Done
Reading search index                            Done
Building new search index                    402/402

A clone of omnios-r151014-10 exists and has been updated and activated.
On the next boot the Boot Environment omnios-r151014-11 will be
mounted on '/'.  Reboot when ready to switch to this updated BE.


---------------------------------------------------------------------------
NOTE: Please review release notes posted at:

http://omnios.omniti.com/ReleaseNotes
---------------------------------------------------------------------------

Then I checked:

root at nas01:/root# pkg verify
pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11
,5.11-0.151014:20160603T031035Z
pkg verify: no packages matching
'pkg://omnios/consolidation/osnet/osnet-incorporation at 0.5.11,5.11-0.151014:20160603T031035Z'
installed
root at nas01:/root# pkg list entire
NAME (PUBLISHER)
VERSION                    IFO
entire
11-0.151014                i--
root at nas01:/root# pkg list -Hv entire
pkg://omnios/entire at 11-0.151014:20160602T180308Z
i--
root at nas01:/root# pkg publisher
PUBLISHER                   TYPE     STATUS P LOCATION
omnios                      origin   online F
http://pkg.omniti.com/omnios/r151014/
uulm.mawi                   origin   online F
http://scott.mathematik.uni-ulm.de/release/
root at nas01:/root# pkgrepo list -Hs http://pkg.omniti.com/omnios/r151014/
entire at 11-0.151014:20160602T180308Z
omnios    entire
11-0.151014:20160602T180308Z
root at nas01:/root# pkg list -af osnet-incorporation at 0.5.11
,5.11-0.151014:20160603T031035Z
NAME (PUBLISHER)
VERSION                    IFO
consolidation/osnet/osnet-incorporation
0.5.11-0.151014            ---

Does it mean that I must install the osnet-incorporation package?

Davide.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/56e0ed1a/attachment-0001.html>

From skeltonr at btconnect.com  Mon Jun  6 22:13:06 2016
From: skeltonr at btconnect.com (Richard Skelton)
Date: Mon, 06 Jun 2016 23:13:06 +0100
Subject: [OmniOS-discuss] Need a way to set the drive locater leds for a
	9300-16i HBA
Message-ID: <5755F572.80303@btconnect.com>

Hi,
I now have a 9300-16i HBA working with OmniOS r151018-ae3141d but need a
way to set the drive locater leds.
I have downloaded SAS3IRCU_P12.zip but sas3ircu LIST shows no
controllers :-(



root at skelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# ./sas3ircu LIST
Avago Technologies SAS3 IR Configuration Utility.
Version 13.00.00.00 (2016.03.08)
Copyright (c) 2009-2016 Avago Technologies. All rights reserved.

SAS3IRCU: No Controllers Found.
root at bskelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# truss ./sas3ircu LIST
execve("sas3ircu", 0x08047CE0, 0x08047CEC)  argc = 2
sysinfo(SI_MACHINE, "i86pc", 257)               = 6
mmap(0x00000000, 32, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFB0000
mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFA0000
mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF90000
mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF80000
memcntl(0xFEFB5000, 48396, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
memcntl(0x08050000, 22240, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
getcwd("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel", 1014) = 0
resolvepath("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", "/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 1023) = 52
stat64("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 0x08047974) = 0
open("/var/ld/ld.config", O_RDONLY)             Err#2 ENOENT
sysconfig(_CONFIG_PAGESIZE)                     = 4096
stat64("/usr/sfw/lib/libdevinfo.so.1", 0x08047194) Err#2 ENOENT
stat64("/lib/libdevinfo.so.1", 0x08047194)      = 0
resolvepath("/lib/libdevinfo.so.1", "/lib/libdevinfo.so.1", 1023) = 20
open("/lib/libdevinfo.so.1", O_RDONLY)          = 3
mmapobj(3, MMOBJ_INTERPRET, 0xFEF80AA8, 0x08047200, 0x00000000) = 0
close(3)                                        = 0
memcntl(0xFEF50000, 26820, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
stat64("/usr/sfw/lib/libc.so.1", 0x08047194)    Err#2 ENOENT
stat64("/lib/libc.so.1", 0x08047194)            = 0
resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14
open("/lib/libc.so.1", O_RDONLY)                = 3
mmapobj(3, MMOBJ_INTERPRET, 0xFEFFDDD0, 0x08047200, 0x00000000) = 0
close(3)                                        = 0
mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEDE0000
memcntl(0xFEDF0000, 254776, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEDD0000
getcontext(0x080477B4)
getrlimit(RLIMIT_STACK, 0x080477AC)             = 0
getpid()                                        = 1657 [1656]
lwp_private(0, 1, 0xFEDD2A40)                   = 0x000001C3
setustack(0xFEDD2AA0)
lwp_cond_broadcast(0xFEDE00FC)                  = 0
lwp_cond_broadcast(0xFEF80C8C)                  = 0
lwp_cond_broadcast(0xFEF805FC)                  = 0
sysi86(SI86FPSTART, 0xFEF46E6C, 0x0000133F, 0x00001F80) = 0x00000001
ioctl(1, TCGETA, 0x08046D9E)                    = 0
fstat64(1, 0x08046CE0)                          = 0
Avago Technologies SAS3 IR Configuration Utility.
write(1, " A v a g o   T e c h n o".., 50)      = 50
Version 13.00.00.00 (2016.03.08)
write(1, " V e r s i o n   1 3 . 0".., 34)      = 34
Copyright (c) 2009-2016 Avago Technologies. All rights reserved.

write(1, " C o p y r i g h t   ( c".., 67)      = 67
brk(0x080912D8)                                 = 0
brk(0x080932D8)                                 = 0
sysconfig(_CONFIG_PAGESIZE)                     = 4096
open("/devices/pseudo/devinfo at 0:devinfo", O_RDONLY) = 3
ioctl(3, DINFOIDENT, 0x00000000)                = 57311
ioctl(3, 0xDF07, 0x08046D1C)                    = 629484
brk(0x080932D8)                                 = 0
brk(0x0812D2D8)                                 = 0
ioctl(3, DINFOUSRLD, 0x08092000)                = 630784
close(3)                                        = 0
sysconfig(_CONFIG_PAGESIZE)                     = 4096
SAS3IRCU: No Controllers Found.
write(1, " S A S 3 I R C U :   N o".., 32)      = 32
_exit(1)


Cheers
Richard.




From danmcd at omniti.com  Tue Jun  7 00:42:12 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 6 Jun 2016 20:42:12 -0400
Subject: [OmniOS-discuss] OmniOS 151014 LTS (omnios-b13298f) pkg update
	-v shows an osnet-incorporation related message.
In-Reply-To: <CANKMAMaoiBPfexWma_kyebmyNC90KM3zBtqExQ0ThYpBq_u9Cw@mail.gmail.com>
References: <CANKMAMaoiBPfexWma_kyebmyNC90KM3zBtqExQ0ThYpBq_u9Cw@mail.gmail.com>
Message-ID: <4939307F-2DE7-481A-920B-36479F2D2A6E@omniti.com>

Ahhh good catch.

I know what happened.  I forgot to update the "entire" and "jeos/illumos-gate" consolidations with the updated Timezone package versions.  Luckily, those are small and easily fixed.  As a side-effect, you will want to update now to also obtain the 2016c timezone info.  What isn't lucky is that I have to rebuild the update media.  Luckily, not as many people are installing LTS *today* from ISO or USB as they are updating their existing deployments.

I have now updated the public repo servers.  I will soon be updating the release media as well.

Here's a machine I have like yours, that also caught this error, but with better post-update results:

r151014(~)[0]% sudo pkg update --no-backup-be
            Packages to update:  4
       Create boot environment: No
Create backup boot environment: No

Planning linked: 0/1 done; 1 working: zone:kvm-only
Linked image 'zone:kvm-only' output:
| Packages to update: 4
`
Planning linked: 1/1 done
DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
Completed                                4/4         32/32      0.2/0.2  1.1M/s

Downloading linked: 0/1 done; 1 working: zone:kvm-only
Downloading linked: 1/1 done
PHASE                                          ITEMS
Removing old actions                             8/8
Installing new actions                         15/15
Updating modified actions                      32/32
Updating package state database                 Done 
Updating package cache                           4/4 
Updating image state                            Done 
Creating fast lookup database                   Done 
Executing linked: 0/1 done; 1 working: zone:kvm-only
Executing linked: 1/1 done

---------------------------------------------------------------------------
NOTE: Please review release notes posted at:

http://omnios.omniti.com/ReleaseNotes
---------------------------------------------------------------------------

r151014(~)[0]% sudo pkg update -nv
No updates available for this image.
Planning linked: 0/1 done; 1 working: zone:kvm-only
Linked image 'zone:kvm-only' output:
| No updates available for this image. (zone:kvm-only)
`
Planning linked: 1/1 done
r151014(~)[4]% 


That's more in line with what should happen.


THANK YOU and good catch!
Dan


From danmcd at omniti.com  Tue Jun  7 00:47:58 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 6 Jun 2016 20:47:58 -0400
Subject: [OmniOS-discuss] LTS users, please read
Message-ID: <5E708963-1C39-44FD-AC6A-B6ABD83A5CB2@omniti.com>

If you haven't updated LTS, skip this mail.

If you've updated LTS TODAY, please run "pkg update --no-backup-be" and you'll receive 4 updates:

	- The actual 2016c timezone update
	- Consolidation updates for entire, jeos/illumos-gate, and osnet-consolidation

Thanks to Davide Poletto for pointing out I forgot to update the 2016c timezone changes in omnios-build for r151014.

I'm re-cutting release media right now, but most users here are existing r151014 deployments.

Thanks, and sorry,
Dan


From danmcd at omniti.com  Tue Jun  7 01:47:38 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 6 Jun 2016 21:47:38 -0400
Subject: [OmniOS-discuss] LTS users, please read
In-Reply-To: <5E708963-1C39-44FD-AC6A-B6ABD83A5CB2@omniti.com>
References: <5E708963-1C39-44FD-AC6A-B6ABD83A5CB2@omniti.com>
Message-ID: <9513BC3A-83C9-47B9-A03E-5FF08E9A5581@omniti.com>


> On Jun 6, 2016, at 8:47 PM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> I'm re-cutting release media right now, but most users here are existing r151014 deployments.

Release media has been updated as well.

Dan


From daleg at omniti.com  Tue Jun  7 01:54:41 2016
From: daleg at omniti.com (Dale Ghent)
Date: Mon, 6 Jun 2016 21:54:41 -0400
Subject: [OmniOS-discuss] Need a way to set the drive locater leds for a
	9300-16i HBA
In-Reply-To: <5755F572.80303@btconnect.com>
References: <5755F572.80303@btconnect.com>
Message-ID: <CBE6594F-08D3-42E2-8B3D-45270B666F3D@omniti.com>


Oracle Solaris and illumos-based distros such as OmniOS have diverged in many places, sometimes subtly. At the end of the day, you're using a tool designed on and for Oracle Solaris, so the lack of expected results elsewhere is not entirely surprising. You may want to try with an older version of the sas3ircu binary.

> On Jun 6, 2016, at 6:13 PM, Richard Skelton <skeltonr at btconnect.com> wrote:
> 
> Hi,
> I now have a 9300-16i HBA working with OmniOS r151018-ae3141d but need a
> way to set the drive locater leds.
> I have downloaded SAS3IRCU_P12.zip but sas3ircu LIST shows no
> controllers :-(
> 
> 
> 
> root at skelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# ./sas3ircu LIST
> Avago Technologies SAS3 IR Configuration Utility.
> Version 13.00.00.00 (2016.03.08)
> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
> 
> SAS3IRCU: No Controllers Found.
> root at bskelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# truss ./sas3ircu LIST
> execve("sas3ircu", 0x08047CE0, 0x08047CEC)  argc = 2
> sysinfo(SI_MACHINE, "i86pc", 257)               = 6
> mmap(0x00000000, 32, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFB0000
> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFA0000
> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF90000
> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF80000
> memcntl(0xFEFB5000, 48396, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
> memcntl(0x08050000, 22240, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
> resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
> getcwd("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel", 1014) = 0
> resolvepath("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", "/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 1023) = 52
> stat64("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 0x08047974) = 0
> open("/var/ld/ld.config", O_RDONLY)             Err#2 ENOENT
> sysconfig(_CONFIG_PAGESIZE)                     = 4096
> stat64("/usr/sfw/lib/libdevinfo.so.1", 0x08047194) Err#2 ENOENT
> stat64("/lib/libdevinfo.so.1", 0x08047194)      = 0
> resolvepath("/lib/libdevinfo.so.1", "/lib/libdevinfo.so.1", 1023) = 20
> open("/lib/libdevinfo.so.1", O_RDONLY)          = 3
> mmapobj(3, MMOBJ_INTERPRET, 0xFEF80AA8, 0x08047200, 0x00000000) = 0
> close(3)                                        = 0
> memcntl(0xFEF50000, 26820, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
> stat64("/usr/sfw/lib/libc.so.1", 0x08047194)    Err#2 ENOENT
> stat64("/lib/libc.so.1", 0x08047194)            = 0
> resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14
> open("/lib/libc.so.1", O_RDONLY)                = 3
> mmapobj(3, MMOBJ_INTERPRET, 0xFEFFDDD0, 0x08047200, 0x00000000) = 0
> close(3)                                        = 0
> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEDE0000
> memcntl(0xFEDF0000, 254776, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
> mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEDD0000
> getcontext(0x080477B4)
> getrlimit(RLIMIT_STACK, 0x080477AC)             = 0
> getpid()                                        = 1657 [1656]
> lwp_private(0, 1, 0xFEDD2A40)                   = 0x000001C3
> setustack(0xFEDD2AA0)
> lwp_cond_broadcast(0xFEDE00FC)                  = 0
> lwp_cond_broadcast(0xFEF80C8C)                  = 0
> lwp_cond_broadcast(0xFEF805FC)                  = 0
> sysi86(SI86FPSTART, 0xFEF46E6C, 0x0000133F, 0x00001F80) = 0x00000001
> ioctl(1, TCGETA, 0x08046D9E)                    = 0
> fstat64(1, 0x08046CE0)                          = 0
> Avago Technologies SAS3 IR Configuration Utility.
> write(1, " A v a g o   T e c h n o".., 50)      = 50
> Version 13.00.00.00 (2016.03.08)
> write(1, " V e r s i o n   1 3 . 0".., 34)      = 34
> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
> 
> write(1, " C o p y r i g h t   ( c".., 67)      = 67
> brk(0x080912D8)                                 = 0
> brk(0x080932D8)                                 = 0
> sysconfig(_CONFIG_PAGESIZE)                     = 4096
> open("/devices/pseudo/devinfo at 0:devinfo", O_RDONLY) = 3
> ioctl(3, DINFOIDENT, 0x00000000)                = 57311
> ioctl(3, 0xDF07, 0x08046D1C)                    = 629484
> brk(0x080932D8)                                 = 0
> brk(0x0812D2D8)                                 = 0
> ioctl(3, DINFOUSRLD, 0x08092000)                = 630784
> close(3)                                        = 0
> sysconfig(_CONFIG_PAGESIZE)                     = 4096
> SAS3IRCU: No Controllers Found.
> write(1, " S A S 3 I R C U :   N o".., 32)      = 32
> _exit(1)
> 
> 
> Cheers
> Richard.
> 
> 
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160606/1dd84a3e/attachment.bin>

From matej at zunaj.si  Tue Jun  7 06:26:54 2016
From: matej at zunaj.si (=?utf-8?Q?Matej_=C5=BDerovnik?=)
Date: Tue, 7 Jun 2016 08:26:54 +0200
Subject: [OmniOS-discuss] Need a way to set the drive locater leds for a
	9300-16i HBA
In-Reply-To: <CBE6594F-08D3-42E2-8B3D-45270B666F3D@omniti.com>
References: <5755F572.80303@btconnect.com>
	<CBE6594F-08D3-42E2-8B3D-45270B666F3D@omniti.com>
Message-ID: <13512510-0111-453A-8B14-81F6FBC782ED@zunaj.si>

Try this util, it works for me: https://github.com/Nexenta/nza-userland/tree/master/nza-userland/components/sas3ircu/usr/sbin

Matej

> On 07 Jun 2016, at 03:54, Dale Ghent <daleg at omniti.com> wrote:
> 
> 
> Oracle Solaris and illumos-based distros such as OmniOS have diverged in many places, sometimes subtly. At the end of the day, you're using a tool designed on and for Oracle Solaris, so the lack of expected results elsewhere is not entirely surprising. You may want to try with an older version of the sas3ircu binary.
> 
>> On Jun 6, 2016, at 6:13 PM, Richard Skelton <skeltonr at btconnect.com> wrote:
>> 
>> Hi,
>> I now have a 9300-16i HBA working with OmniOS r151018-ae3141d but need a
>> way to set the drive locater leds.
>> I have downloaded SAS3IRCU_P12.zip but sas3ircu LIST shows no
>> controllers :-(
>> 
>> 
>> 
>> root at skelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# ./sas3ircu LIST
>> Avago Technologies SAS3 IR Configuration Utility.
>> Version 13.00.00.00 (2016.03.08)
>> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
>> 
>> SAS3IRCU: No Controllers Found.
>> root at bskelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# truss ./sas3ircu LIST
>> execve("sas3ircu", 0x08047CE0, 0x08047CEC)  argc = 2
>> sysinfo(SI_MACHINE, "i86pc", 257)               = 6
>> mmap(0x00000000, 32, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFB0000
>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFA0000
>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF90000
>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF80000
>> memcntl(0xFEFB5000, 48396, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>> memcntl(0x08050000, 22240, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>> resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
>> getcwd("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel", 1014) = 0
>> resolvepath("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", "/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 1023) = 52
>> stat64("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 0x08047974) = 0
>> open("/var/ld/ld.config", O_RDONLY)             Err#2 ENOENT
>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>> stat64("/usr/sfw/lib/libdevinfo.so.1", 0x08047194) Err#2 ENOENT
>> stat64("/lib/libdevinfo.so.1", 0x08047194)      = 0
>> resolvepath("/lib/libdevinfo.so.1", "/lib/libdevinfo.so.1", 1023) = 20
>> open("/lib/libdevinfo.so.1", O_RDONLY)          = 3
>> mmapobj(3, MMOBJ_INTERPRET, 0xFEF80AA8, 0x08047200, 0x00000000) = 0
>> close(3)                                        = 0
>> memcntl(0xFEF50000, 26820, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>> stat64("/usr/sfw/lib/libc.so.1", 0x08047194)    Err#2 ENOENT
>> stat64("/lib/libc.so.1", 0x08047194)            = 0
>> resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14
>> open("/lib/libc.so.1", O_RDONLY)                = 3
>> mmapobj(3, MMOBJ_INTERPRET, 0xFEFFDDD0, 0x08047200, 0x00000000) = 0
>> close(3)                                        = 0
>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEDE0000
>> memcntl(0xFEDF0000, 254776, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>> mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEDD0000
>> getcontext(0x080477B4)
>> getrlimit(RLIMIT_STACK, 0x080477AC)             = 0
>> getpid()                                        = 1657 [1656]
>> lwp_private(0, 1, 0xFEDD2A40)                   = 0x000001C3
>> setustack(0xFEDD2AA0)
>> lwp_cond_broadcast(0xFEDE00FC)                  = 0
>> lwp_cond_broadcast(0xFEF80C8C)                  = 0
>> lwp_cond_broadcast(0xFEF805FC)                  = 0
>> sysi86(SI86FPSTART, 0xFEF46E6C, 0x0000133F, 0x00001F80) = 0x00000001
>> ioctl(1, TCGETA, 0x08046D9E)                    = 0
>> fstat64(1, 0x08046CE0)                          = 0
>> Avago Technologies SAS3 IR Configuration Utility.
>> write(1, " A v a g o   T e c h n o".., 50)      = 50
>> Version 13.00.00.00 (2016.03.08)
>> write(1, " V e r s i o n   1 3 . 0".., 34)      = 34
>> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
>> 
>> write(1, " C o p y r i g h t   ( c".., 67)      = 67
>> brk(0x080912D8)                                 = 0
>> brk(0x080932D8)                                 = 0
>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>> open("/devices/pseudo/devinfo at 0:devinfo", O_RDONLY) = 3
>> ioctl(3, DINFOIDENT, 0x00000000)                = 57311
>> ioctl(3, 0xDF07, 0x08046D1C)                    = 629484
>> brk(0x080932D8)                                 = 0
>> brk(0x0812D2D8)                                 = 0
>> ioctl(3, DINFOUSRLD, 0x08092000)                = 630784
>> close(3)                                        = 0
>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>> SAS3IRCU: No Controllers Found.
>> write(1, " S A S 3 I R C U :   N o".., 32)      = 32
>> _exit(1)
>> 
>> 
>> Cheers
>> Richard.
>> 
>> 
>> 
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3468 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/60154c19/attachment-0001.bin>

From davide.poletto at gmail.com  Tue Jun  7 08:04:39 2016
From: davide.poletto at gmail.com (Davide Poletto)
Date: Tue, 7 Jun 2016 10:04:39 +0200
Subject: [OmniOS-discuss] OmniOS 151014 LTS (omnios-b13298f) pkg update
 -v shows an osnet-incorporation related message.
In-Reply-To: <4939307F-2DE7-481A-920B-36479F2D2A6E@omniti.com>
References: <CANKMAMaoiBPfexWma_kyebmyNC90KM3zBtqExQ0ThYpBq_u9Cw@mail.gmail.com>
	<4939307F-2DE7-481A-920B-36479F2D2A6E@omniti.com>
Message-ID: <CANKMAMbbyDivnaqkKWpoLPx_3V9w0wvxHj=JjeFrQqjMgjQDbA@mail.gmail.com>

Hello Dan!

Oh...I've only been *lucky* because I did the update very early yesterday
late night (CET)!

Thanks for fixing so promptly.

Here it is the pkg update -v now:

root at nas01:/root# pkg update -v
            Packages to update:        4
     Estimated space available: 33.36 GB
Estimated space to be consumed: 24.00 MB
       Create boot environment:       No
Create backup boot environment:      Yes
          Rebuild boot archive:       No

Changed packages:
omnios
  consolidation/osnet/osnet-incorporation
    0.5.11-0.151014:20160420T161515Z -> 0.5.11-0.151014:20160603T031035Z
  entire
    11-0.151014:20160602T180308Z -> 11-0.151014:20160607T003721Z
  incorporation/jeos/illumos-gate
    11-0.151014:20160602T180308Z -> 11-0.151014:20160607T003720Z
  system/data/zoneinfo
    2015.7-0.151014:20160420T161550Z -> 2016.3-0.151014:20160603T031111Z
DOWNLOAD                                PKGS         FILES    XFER (MB)
SPEED
Completed                                4/4         32/32      0.2/0.2
194k/s

PHASE                                          ITEMS
Removing old actions                             8/8
Installing new actions                         15/15
Updating modified actions                      32/32
Updating package state database                 Done
Updating package cache                           4/4
Updating image state                            Done
Creating fast lookup database                   Done
Reading search index                            Done
Updating search index                            4/4

---------------------------------------------------------------------------
NOTE: Please review release notes posted at:

http://omnios.omniti.com/ReleaseNotes
---------------------------------------------------------------------------

Thanks again, Davide.

On Tue, Jun 7, 2016 at 2:42 AM, Dan McDonald <danmcd at omniti.com> wrote:

> Ahhh good catch.
>
> I know what happened.  I forgot to update the "entire" and
> "jeos/illumos-gate" consolidations with the updated Timezone package
> versions.  Luckily, those are small and easily fixed.  As a side-effect,
> you will want to update now to also obtain the 2016c timezone info.  What
> isn't lucky is that I have to rebuild the update media.  Luckily, not as
> many people are installing LTS *today* from ISO or USB as they are updating
> their existing deployments.
>
> I have now updated the public repo servers.  I will soon be updating the
> release media as well.
>
> Here's a machine I have like yours, that also caught this error, but with
> better post-update results:
>
> r151014(~)[0]% sudo pkg update --no-backup-be
>             Packages to update:  4
>        Create boot environment: No
> Create backup boot environment: No
>
> Planning linked: 0/1 done; 1 working: zone:kvm-only
> Linked image 'zone:kvm-only' output:
> | Packages to update: 4
> `
> Planning linked: 1/1 done
> DOWNLOAD                                PKGS         FILES    XFER (MB)
>  SPEED
> Completed                                4/4         32/32      0.2/0.2
> 1.1M/s
>
> Downloading linked: 0/1 done; 1 working: zone:kvm-only
> Downloading linked: 1/1 done
> PHASE                                          ITEMS
> Removing old actions                             8/8
> Installing new actions                         15/15
> Updating modified actions                      32/32
> Updating package state database                 Done
> Updating package cache                           4/4
> Updating image state                            Done
> Creating fast lookup database                   Done
> Executing linked: 0/1 done; 1 working: zone:kvm-only
> Executing linked: 1/1 done
>
> ---------------------------------------------------------------------------
> NOTE: Please review release notes posted at:
>
> http://omnios.omniti.com/ReleaseNotes
> ---------------------------------------------------------------------------
>
> r151014(~)[0]% sudo pkg update -nv
> No updates available for this image.
> Planning linked: 0/1 done; 1 working: zone:kvm-only
> Linked image 'zone:kvm-only' output:
> | No updates available for this image. (zone:kvm-only)
> `
> Planning linked: 1/1 done
> r151014(~)[4]%
>
>
> That's more in line with what should happen.
>
>
> THANK YOU and good catch!
> Dan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/c0e52076/attachment.html>

From sjorge+ml at blackdot.be  Tue Jun  7 11:00:06 2016
From: sjorge+ml at blackdot.be (Jorge Schrauwen)
Date: Tue, 07 Jun 2016 13:00:06 +0200
Subject: [OmniOS-discuss] Community interest in illumos PF port?
In-Reply-To: <CACLsAptC-H3TSCcMguusaye9TOt3diHJqrpddaWQ-D6Fgvan+g@mail.gmail.com>
References: <9064334fe578d975ef3c7823ceed613f@blackdot.be>
	<d5fc3b22d0b5b6666a54873896e94f6c@blackdot.be>
	<CACLsAptC-H3TSCcMguusaye9TOt3diHJqrpddaWQ-D6Fgvan+g@mail.gmail.com>
Message-ID: <92091e57332b008424d301173bf1c45d@blackdot.be>

Hello, 

We promised to send a reply once we gathered some data, so here it is. 

>From what alanc told us Oracle spent well over 2 engineer years working
on their port. This would
require high amount of money for a successfull crowdsourcing campaign. 

27 people including us (Adam and Jorge) responded that we would like to
see pf ported to illumos. 
However, all of us were individuals without a backing company to back
with some serious amount of funds. 

Based on this fact, we conclude that the crowd-sourcing campaign would
likely fail. 

Regards 

Adam and Jorge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/76c408cd/attachment.html>

From gary at genashor.com  Tue Jun  7 14:07:43 2016
From: gary at genashor.com (Gary Gendel)
Date: Tue, 7 Jun 2016 10:07:43 -0400
Subject: [OmniOS-discuss] SECURITY AND FEATURE UPDATES for OmniOS LTS,
 Stable, and old-Stable
In-Reply-To: <FD4BAABC-DA92-408D-BDDA-AACD52079B27@omniti.com>
References: <FD4BAABC-DA92-408D-BDDA-AACD52079B27@omniti.com>
Message-ID: <5756D52F.1010109@genashor.com>

Thanks for the update.  I'm on 151018 and after the update it wouldn't 
boot so I rolled back to the previous BE.  I got a whole lot of PCI 
overflow errors (I think since these were on the console) and then it hung.

I suspect the bge network driver as this has caused me issues in the 
past which was the impetus for my move from OI to OmniOS.  I didn't see 
anything interesting in the kernel logs.  I'd like to try again but 
where can I find information on the proper way to capture the problem so 
I can report it properly.

Gary

On 06/06/2016 02:47 PM, Dan McDonald wrote:
> Please "pkg update" on your OmniOS r151014, r151016, or r151018 machines at your earliest convenience.
>
> The following security fixes are on ALL THREE:
>
> 	? libxml update to 2.9.4
> 	? DTrace stability fixes (illumos 7033-7035)
> 	? setid binaries disallow ld.so.1's $ORIGIN (illumos 6987)
> 	? ZFS no longer bleeds zvol entries into non-global zones (illumos 7019,7020)
> 	? NTP to 4.2.8p8
> 	? expat to 2.1.1 (with CVE 2016-0718 fix)
>
> The following other fixes are on r151014 and r151018:
>
> 	? missing MCFG table should lead to I/O PCIe config access (illumos 6859)
> 	? allow sendfile() on AF_UNIX sockets (illumos 6861)
> 	? ZFS-helper: kernel virtual memory fragmentation leads to hang (illumos 6914)
> 	? STMF kstat free is using an improper size for kmem_free(). (illumos 6938)
> 	? Driver support for Solarflare 10G and 40G ethernet
>
> The following are new to r151014, but are already on r151018:
>
> 	? Timezone, USB, and PCI data files updates. (Now matches r151018)
> 	? Driver support for vmxnet3s
> 	? MSI-X support fixed for virtio
> 	? The debug.illumos pkg(5) variant.
>
> Each release's release notes have been updated, and install media for r151014 and r151018 have been updated as well.
>
> Bloody will be getting an IPS-only update by the end of the day.  Watch for that in a separate mail.
>
> Thank you, and happy updating!
> Dan
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3703 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/46d7b775/attachment-0001.bin>

From daleg at omniti.com  Tue Jun  7 14:50:56 2016
From: daleg at omniti.com (Dale Ghent)
Date: Tue, 7 Jun 2016 10:50:56 -0400
Subject: [OmniOS-discuss] SECURITY AND FEATURE UPDATES for OmniOS LTS,
	Stable, and old-Stable
In-Reply-To: <5756D52F.1010109@genashor.com>
References: <FD4BAABC-DA92-408D-BDDA-AACD52079B27@omniti.com>
	<5756D52F.1010109@genashor.com>
Message-ID: <C42EF447-EDDC-4D3C-8A11-0A5C54A92E1E@omniti.com>


Please do, we would of course be very interested in what the errors are.

You can mount the updated BE and see if the errors made it into the logs before it hung.

/dale

> On Jun 7, 2016, at 10:07 AM, Gary Gendel <gary at genashor.com> wrote:
> 
> Thanks for the update.  I'm on 151018 and after the update it wouldn't boot so I rolled back to the previous BE.  I got a whole lot of PCI overflow errors (I think since these were on the console) and then it hung.
> 
> I suspect the bge network driver as this has caused me issues in the past which was the impetus for my move from OI to OmniOS.  I didn't see anything interesting in the kernel logs.  I'd like to try again but where can I find information on the proper way to capture the problem so I can report it properly.
> 
> Gary
> 
> On 06/06/2016 02:47 PM, Dan McDonald wrote:
>> Please "pkg update" on your OmniOS r151014, r151016, or r151018 machines at your earliest convenience.
>> 
>> The following security fixes are on ALL THREE:
>> 
>> 	? libxml update to 2.9.4
>> 	? DTrace stability fixes (illumos 7033-7035)
>> 	? setid binaries disallow ld.so.1's $ORIGIN (illumos 6987)
>> 	? ZFS no longer bleeds zvol entries into non-global zones (illumos 7019,7020)
>> 	? NTP to 4.2.8p8
>> 	? expat to 2.1.1 (with CVE 2016-0718 fix)
>> 
>> The following other fixes are on r151014 and r151018:
>> 
>> 	? missing MCFG table should lead to I/O PCIe config access (illumos 6859)
>> 	? allow sendfile() on AF_UNIX sockets (illumos 6861)
>> 	? ZFS-helper: kernel virtual memory fragmentation leads to hang (illumos 6914)
>> 	? STMF kstat free is using an improper size for kmem_free(). (illumos 6938)
>> 	? Driver support for Solarflare 10G and 40G ethernet
>> 
>> The following are new to r151014, but are already on r151018:
>> 
>> 	? Timezone, USB, and PCI data files updates. (Now matches r151018)
>> 	? Driver support for vmxnet3s
>> 	? MSI-X support fixed for virtio
>> 	? The debug.illumos pkg(5) variant.
>> 
>> Each release's release notes have been updated, and install media for r151014 and r151018 have been updated as well.
>> 
>> Bloody will be getting an IPS-only update by the end of the day.  Watch for that in a separate mail.
>> 
>> Thank you, and happy updating!
>> Dan
>> 
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/4cd0d6aa/attachment.bin>

From danmcd at omniti.com  Tue Jun  7 15:13:32 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Tue, 7 Jun 2016 11:13:32 -0400
Subject: [OmniOS-discuss] SECURITY AND FEATURE UPDATES for OmniOS LTS,
	Stable, and old-Stable
In-Reply-To: <5756D52F.1010109@genashor.com>
References: <FD4BAABC-DA92-408D-BDDA-AACD52079B27@omniti.com>
	<5756D52F.1010109@genashor.com>
Message-ID: <D87793A1-7257-423E-83F4-974D4FBA2543@omniti.com>


> On Jun 7, 2016, at 10:07 AM, Gary Gendel <gary at genashor.com> wrote:
> 
> Thanks for the update.  I'm on 151018 and after the update it wouldn't boot so I rolled back to the previous BE.  I got a whole lot of PCI overflow errors (I think since these were on the console) and then it hung.

We did include this in the '018 update:

	? missing MCFG table should lead to I/O PCIe config access (illumos 6859)

That may be tripping up bge.

Dan


From skeltonr at btconnect.com  Tue Jun  7 16:47:53 2016
From: skeltonr at btconnect.com (Richard Skelton)
Date: Tue, 07 Jun 2016 17:47:53 +0100
Subject: [OmniOS-discuss] Need a way to set the drive locater leds for a
 9300-16i HBA
In-Reply-To: <13512510-0111-453A-8B14-81F6FBC782ED@zunaj.si>
References: <5755F572.80303@btconnect.com>
	<CBE6594F-08D3-42E2-8B3D-45270B666F3D@omniti.com>
	<13512510-0111-453A-8B14-81F6FBC782ED@zunaj.si>
Message-ID: <5756FAB9.8070709@btconnect.com>

Hi Matej,
Thanks this also works for me with a few warning when I turn on/off the
drive leds:-

root at skelly:/root# ./sas3ircu 0 LOCATE 1:3 ON
LSI Corporation SAS3 IR Configuration Utility.
Version 05.00.00.00 (2014.02.26)
Copyright (c) 2009-2014 LSI Corporation. All rights reserved.

SAS3IRCU: LOCATE command completed successfully.
SAS3IRCU: Command LOCATE Completed Successfully.
SAS3IRCU: Utility Completed Successfully.
root at skelly2:/root# ./sas3ircu 0 LOCATE 1:3 off
LSI Corporation SAS3 IR Configuration Utility.
Version 05.00.00.00 (2014.02.26)
Copyright (c) 2009-2014 LSI Corporation. All rights reserved.

SAS3IRCU: LOCATE command completed successfully.
SAS3IRCU: Command LOCATE Completed Successfully.
SAS3IRCU: Utility Completed Successfully.
root at brssds112:/root#


Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
Jun  7 11:22:54 skelly       FW Upload tce invalid!
root at skelly:/root#




Matej Z(erovnik wrote:
> Try this util, it works for me: https://github.com/Nexenta/nza-userland/tree/master/nza-userland/components/sas3ircu/usr/sbin
>
> Matej
>
>   
>> On 07 Jun 2016, at 03:54, Dale Ghent <daleg at omniti.com> wrote:
>>
>>
>> Oracle Solaris and illumos-based distros such as OmniOS have diverged in many places, sometimes subtly. At the end of the day, you're using a tool designed on and for Oracle Solaris, so the lack of expected results elsewhere is not entirely surprising. You may want to try with an older version of the sas3ircu binary.
>>
>>     
>>> On Jun 6, 2016, at 6:13 PM, Richard Skelton <skeltonr at btconnect.com> wrote:
>>>
>>> Hi,
>>> I now have a 9300-16i HBA working with OmniOS r151018-ae3141d but need a
>>> way to set the drive locater leds.
>>> I have downloaded SAS3IRCU_P12.zip but sas3ircu LIST shows no
>>> controllers :-(
>>>
>>>
>>>
>>> root at skelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# ./sas3ircu LIST
>>> Avago Technologies SAS3 IR Configuration Utility.
>>> Version 13.00.00.00 (2016.03.08)
>>> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
>>>
>>> SAS3IRCU: No Controllers Found.
>>> root at bskelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# truss ./sas3ircu LIST
>>> execve("sas3ircu", 0x08047CE0, 0x08047CEC)  argc = 2
>>> sysinfo(SI_MACHINE, "i86pc", 257)               = 6
>>> mmap(0x00000000, 32, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFB0000
>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFA0000
>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF90000
>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF80000
>>> memcntl(0xFEFB5000, 48396, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>> memcntl(0x08050000, 22240, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>> resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
>>> getcwd("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel", 1014) = 0
>>> resolvepath("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", "/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 1023) = 52
>>> stat64("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 0x08047974) = 0
>>> open("/var/ld/ld.config", O_RDONLY)             Err#2 ENOENT
>>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>>> stat64("/usr/sfw/lib/libdevinfo.so.1", 0x08047194) Err#2 ENOENT
>>> stat64("/lib/libdevinfo.so.1", 0x08047194)      = 0
>>> resolvepath("/lib/libdevinfo.so.1", "/lib/libdevinfo.so.1", 1023) = 20
>>> open("/lib/libdevinfo.so.1", O_RDONLY)          = 3
>>> mmapobj(3, MMOBJ_INTERPRET, 0xFEF80AA8, 0x08047200, 0x00000000) = 0
>>> close(3)                                        = 0
>>> memcntl(0xFEF50000, 26820, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>> stat64("/usr/sfw/lib/libc.so.1", 0x08047194)    Err#2 ENOENT
>>> stat64("/lib/libc.so.1", 0x08047194)            = 0
>>> resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14
>>> open("/lib/libc.so.1", O_RDONLY)                = 3
>>> mmapobj(3, MMOBJ_INTERPRET, 0xFEFFDDD0, 0x08047200, 0x00000000) = 0
>>> close(3)                                        = 0
>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEDE0000
>>> memcntl(0xFEDF0000, 254776, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>> mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEDD0000
>>> getcontext(0x080477B4)
>>> getrlimit(RLIMIT_STACK, 0x080477AC)             = 0
>>> getpid()                                        = 1657 [1656]
>>> lwp_private(0, 1, 0xFEDD2A40)                   = 0x000001C3
>>> setustack(0xFEDD2AA0)
>>> lwp_cond_broadcast(0xFEDE00FC)                  = 0
>>> lwp_cond_broadcast(0xFEF80C8C)                  = 0
>>> lwp_cond_broadcast(0xFEF805FC)                  = 0
>>> sysi86(SI86FPSTART, 0xFEF46E6C, 0x0000133F, 0x00001F80) = 0x00000001
>>> ioctl(1, TCGETA, 0x08046D9E)                    = 0
>>> fstat64(1, 0x08046CE0)                          = 0
>>> Avago Technologies SAS3 IR Configuration Utility.
>>> write(1, " A v a g o   T e c h n o".., 50)      = 50
>>> Version 13.00.00.00 (2016.03.08)
>>> write(1, " V e r s i o n   1 3 . 0".., 34)      = 34
>>> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
>>>
>>> write(1, " C o p y r i g h t   ( c".., 67)      = 67
>>> brk(0x080912D8)                                 = 0
>>> brk(0x080932D8)                                 = 0
>>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>>> open("/devices/pseudo/devinfo at 0:devinfo", O_RDONLY) = 3
>>> ioctl(3, DINFOIDENT, 0x00000000)                = 57311
>>> ioctl(3, 0xDF07, 0x08046D1C)                    = 629484
>>> brk(0x080932D8)                                 = 0
>>> brk(0x0812D2D8)                                 = 0
>>> ioctl(3, DINFOUSRLD, 0x08092000)                = 630784
>>> close(3)                                        = 0
>>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>>> SAS3IRCU: No Controllers Found.
>>> write(1, " S A S 3 I R C U :   N o".., 32)      = 32
>>> _exit(1)
>>>
>>>
>>> Cheers
>>> Richard.
>>>
>>>
>>>
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>>       
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>     
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/d8dfe20c/attachment-0001.html>

From Josh.Barton at usurf.usu.edu  Tue Jun  7 17:53:16 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Tue, 7 Jun 2016 17:53:16 +0000
Subject: [OmniOS-discuss] Only grub after boot
Message-ID: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>

I accidentally detached my topic from the mailing list last week so here I am trying again with more details this time. I have installed OmniOS on a Supermicro system running with 3 LSI 9300 8i controlllers(see hardware list below) but while installation proceeds normally, boot fails at grub, all I see is the word grub with a flashing cursor and I am unable to interact at all. I did notice a warning about i/o requests not being aligned with the 4096 byte disk but after installation I checked the ashift with the live cd and it was 12 as it should be. I have checked to ensure that I am running via AHCI in the BIOS. I even tried re-running installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c1t5000C50d0...s0. Any ideas? Thanks!

Item Number

Item Type

# of Units

CSE-216BAC-R920LPB

Chassis

1.00

LSI 9300-8i

Disk Controller

3.00

 X10DRi-T4+

Motherboard

1.00

Micron/Crucial CT16G4RFD4213

16 GB Ram

12.00

Samsung M393A4K40BB0-CPB

32 GB Ram

8.00

Seagate ST2000NX0243

2TB Drive

12.00

Intel Xeon E5-2637 v3 Quad-core (4 Core) 3.50 GHz Processor

CPU

2.00



I have it set up to boot off the first hard disk of the 12 installed
The first 2 are going to mirrored in ZFS for the os, the remaining 10 will be used to host a postgres database of about 700GB

Josh Barton
USU Research Foundation

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/2f6029d3/attachment.html>

From robertfantini at gmail.com  Tue Jun  7 17:59:34 2016
From: robertfantini at gmail.com (Robert Fantini)
Date: Tue, 7 Jun 2016 13:59:34 -0400
Subject: [OmniOS-discuss] moving rpool from onboard sata to LSI HBA
Message-ID: <CALnM7zk-iztVLDssMN18Tu3s-1Xk-Z9NUkUnPxKK+=BfNhaufg@mail.gmail.com>

Hello

just moving the disks  does not work.

something like a coredump flashed and the system resets.

this is just a test system , so it is not urgent that this gets fixed right
away.


Are there things that can be tried to move rpool from onboard to hba?


best regards, Rob Fantini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/428b177f/attachment.html>

From daleg at omniti.com  Tue Jun  7 18:12:25 2016
From: daleg at omniti.com (Dale Ghent)
Date: Tue, 7 Jun 2016 14:12:25 -0400
Subject: [OmniOS-discuss] moving rpool from onboard sata to LSI HBA
In-Reply-To: <CALnM7zk-iztVLDssMN18Tu3s-1Xk-Z9NUkUnPxKK+=BfNhaufg@mail.gmail.com>
References: <CALnM7zk-iztVLDssMN18Tu3s-1Xk-Z9NUkUnPxKK+=BfNhaufg@mail.gmail.com>
Message-ID: <0B3C9CBC-4F4E-4E6B-8E39-38D542C02BF2@omniti.com>


Boot off a OmniOS ISO or USB image to a shell prompt, import the rpool to a temporary location (such as /mnt) and export it; then try to boot again. This will update the device path in the rpool and GRUB will be able to find the disks again.

/dale

> On Jun 7, 2016, at 1:59 PM, Robert Fantini <robertfantini at gmail.com> wrote:
> 
> Hello
> 
> just moving the disks  does not work.
> 
> something like a coredump flashed and the system resets.
> 
> this is just a test system , so it is not urgent that this gets fixed right away.
> 
> 
> Are there things that can be tried to move rpool from onboard to hba?
> 
> 
> best regards, Rob Fantini
> 
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From matej at zunaj.si  Tue Jun  7 19:30:29 2016
From: matej at zunaj.si (=?utf-8?Q?Matej_=C5=BDerovnik?=)
Date: Tue, 7 Jun 2016 21:30:29 +0200
Subject: [OmniOS-discuss] Need a way to set the drive locater leds for a
	9300-16i HBA
In-Reply-To: <5756FAB9.8070709@btconnect.com>
References: <5755F572.80303@btconnect.com>
	<CBE6594F-08D3-42E2-8B3D-45270B666F3D@omniti.com>
	<13512510-0111-453A-8B14-81F6FBC782ED@zunaj.si>
	<5756FAB9.8070709@btconnect.com>
Message-ID: <A88FF659-86E2-4B7C-9DCC-FC800A9E87E3@zunaj.si>

I have the same errors. If I remember correctly I think I read somewhere that those are only warnings and that we can ignore them.

Matej

> On 07 Jun 2016, at 18:47, Richard Skelton <skeltonr at btconnect.com> wrote:
> 
> Hi Matej,
> Thanks this also works for me with a few warning when I turn on/off the drive leds:-
> root at skelly:/root# ./sas3ircu 0 LOCATE 1:3 ON
> LSI Corporation SAS3 IR Configuration Utility.
> Version 05.00.00.00 (2014.02.26)
> Copyright (c) 2009-2014 LSI Corporation. All rights reserved.
> 
> SAS3IRCU: LOCATE command completed successfully.
> SAS3IRCU: Command LOCATE Completed Successfully.
> SAS3IRCU: Utility Completed Successfully.
> root at skelly2:/root# ./sas3ircu 0 LOCATE 1:3 off
> LSI Corporation SAS3 IR Configuration Utility.
> Version 05.00.00.00 (2014.02.26)
> Copyright (c) 2009-2014 LSI Corporation. All rights reserved.
> 
> SAS3IRCU: LOCATE command completed successfully.
> SAS3IRCU: Command LOCATE Completed Successfully.
> SAS3IRCU: Utility Completed Successfully.
> root at brssds112:/root#
> 
> 
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> Jun  7 11:22:54 skelly scsi: [ID 107833 kern.warning] WARNING: /pci at 7a,0/pci8086,2f06 at 2,2/pci10b5,8724 at 0/pci10b5,8724 at 0/pci1000,3130 at 0 (mpt_sas4):
> Jun  7 11:22:54 skelly       FW Upload tce invalid!
> root at skelly:/root#
> 
> 
> 
> Matej ?erovnik wrote:
>> 
>> Try this util, it works for me: https://github.com/Nexenta/nza-userland/tree/master/nza-userland/components/sas3ircu/usr/sbin <https://github.com/Nexenta/nza-userland/tree/master/nza-userland/components/sas3ircu/usr/sbin>
>> 
>> Matej
>> 
>>   
>>> On 07 Jun 2016, at 03:54, Dale Ghent <daleg at omniti.com> <mailto:daleg at omniti.com> wrote:
>>> 
>>> 
>>> Oracle Solaris and illumos-based distros such as OmniOS have diverged in many places, sometimes subtly. At the end of the day, you're using a tool designed on and for Oracle Solaris, so the lack of expected results elsewhere is not entirely surprising. You may want to try with an older version of the sas3ircu binary.
>>> 
>>>     
>>>> On Jun 6, 2016, at 6:13 PM, Richard Skelton <skeltonr at btconnect.com> <mailto:skeltonr at btconnect.com> wrote:
>>>> 
>>>> Hi,
>>>> I now have a 9300-16i HBA working with OmniOS r151018-ae3141d but need a
>>>> way to set the drive locater leds.
>>>> I have downloaded SAS3IRCU_P12.zip but sas3ircu LIST shows no
>>>> controllers :-(
>>>> 
>>>> 
>>>> 
>>>> root at skelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# ./sas3ircu LIST
>>>> Avago Technologies SAS3 IR Configuration Utility.
>>>> Version 13.00.00.00 (2016.03.08)
>>>> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
>>>> 
>>>> SAS3IRCU: No Controllers Found.
>>>> root at bskelly:/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel# truss ./sas3ircu LIST
>>>> execve("sas3ircu", 0x08047CE0, 0x08047CEC)  argc = 2
>>>> sysinfo(SI_MACHINE, "i86pc", 257)               = 6
>>>> mmap(0x00000000, 32, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFB0000
>>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEFA0000
>>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF90000
>>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEF80000
>>>> memcntl(0xFEFB5000, 48396, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>>> memcntl(0x08050000, 22240, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>>> resolvepath("/usr/lib/ld.so.1", "/lib/ld.so.1", 1023) = 12
>>>> getcwd("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel", 1014) = 0
>>>> resolvepath("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", "/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 1023) = 52
>>>> stat64("/root/SAS3IRCU_P12/sas3ircu_solaris_x86_rel/sas3ircu", 0x08047974) = 0
>>>> open("/var/ld/ld.config", O_RDONLY)             Err#2 ENOENT
>>>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>>>> stat64("/usr/sfw/lib/libdevinfo.so.1", 0x08047194) Err#2 ENOENT
>>>> stat64("/lib/libdevinfo.so.1", 0x08047194)      = 0
>>>> resolvepath("/lib/libdevinfo.so.1", "/lib/libdevinfo.so.1", 1023) = 20
>>>> open("/lib/libdevinfo.so.1", O_RDONLY)          = 3
>>>> mmapobj(3, MMOBJ_INTERPRET, 0xFEF80AA8, 0x08047200, 0x00000000) = 0
>>>> close(3)                                        = 0
>>>> memcntl(0xFEF50000, 26820, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>>> stat64("/usr/sfw/lib/libc.so.1", 0x08047194)    Err#2 ENOENT
>>>> stat64("/lib/libc.so.1", 0x08047194)            = 0
>>>> resolvepath("/lib/libc.so.1", "/lib/libc.so.1", 1023) = 14
>>>> open("/lib/libc.so.1", O_RDONLY)                = 3
>>>> mmapobj(3, MMOBJ_INTERPRET, 0xFEFFDDD0, 0x08047200, 0x00000000) = 0
>>>> close(3)                                        = 0
>>>> mmap(0x00000000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEDE0000
>>>> memcntl(0xFEDF0000, 254776, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
>>>> mmap(0x00010000, 24576, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xFEDD0000
>>>> getcontext(0x080477B4)
>>>> getrlimit(RLIMIT_STACK, 0x080477AC)             = 0
>>>> getpid()                                        = 1657 [1656]
>>>> lwp_private(0, 1, 0xFEDD2A40)                   = 0x000001C3
>>>> setustack(0xFEDD2AA0)
>>>> lwp_cond_broadcast(0xFEDE00FC)                  = 0
>>>> lwp_cond_broadcast(0xFEF80C8C)                  = 0
>>>> lwp_cond_broadcast(0xFEF805FC)                  = 0
>>>> sysi86(SI86FPSTART, 0xFEF46E6C, 0x0000133F, 0x00001F80) = 0x00000001
>>>> ioctl(1, TCGETA, 0x08046D9E)                    = 0
>>>> fstat64(1, 0x08046CE0)                          = 0
>>>> Avago Technologies SAS3 IR Configuration Utility.
>>>> write(1, " A v a g o   T e c h n o".., 50)      = 50
>>>> Version 13.00.00.00 (2016.03.08)
>>>> write(1, " V e r s i o n   1 3 . 0".., 34)      = 34
>>>> Copyright (c) 2009-2016 Avago Technologies. All rights reserved.
>>>> 
>>>> write(1, " C o p y r i g h t   ( c".., 67)      = 67
>>>> brk(0x080912D8)                                 = 0
>>>> brk(0x080932D8)                                 = 0
>>>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>>>> open("/devices/pseudo/devinfo at 0:devinfo", O_RDONLY) = 3
>>>> ioctl(3, DINFOIDENT, 0x00000000)                = 57311
>>>> ioctl(3, 0xDF07, 0x08046D1C)                    = 629484
>>>> brk(0x080932D8)                                 = 0
>>>> brk(0x0812D2D8)                                 = 0
>>>> ioctl(3, DINFOUSRLD, 0x08092000)                = 630784
>>>> close(3)                                        = 0
>>>> sysconfig(_CONFIG_PAGESIZE)                     = 4096
>>>> SAS3IRCU: No Controllers Found.
>>>> write(1, " S A S 3 I R C U :   N o".., 32)      = 32
>>>> _exit(1)
>>>> 
>>>> 
>>>> Cheers
>>>> Richard.
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> OmniOS-discuss mailing list
>>>> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com>
>>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss <http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>>>>       
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com>
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss <http://lists.omniti.com/mailman/listinfo/omnios-discuss>
>>>     
>> 
>>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/d42ac1a3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3468 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/d42ac1a3/attachment-0001.bin>

From gordon at hafnia.dk  Tue Jun  7 20:15:15 2016
From: gordon at hafnia.dk (Gordon Selisek)
Date: Tue, 07 Jun 2016 22:15:15 +0200
Subject: [OmniOS-discuss] Python and Kerberos libraries
Message-ID: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>

Gents,



I'm trying to setup kerberos for use with pywinrm



https://github.com/diyan/pywinrm/



Unfortunately the instructions are geared towards linux, and I can't seem to get past this point



$ sudo yum install gcc krb5-devel krb5-workstation



Obviously I don't have yum, and where do I get the appropriate source? I'm on OmniOS 151016



Any suggestions please? And sorry for the ignorance, but this is my first attempt with Python.


And running the pip command throws the following errors:


root at omnitest:/root# pip install pywinrm[kerberos] 

DEPRECATION: Python 2.6 is no longer supported by the Python core team, please upgrade your Python. A future version of pip will drop support for Python 2.6 

Requirement already satisfied (use --upgrade to upgrade): pywinrm[kerberos] in /usr/lib/python2.6/site-packages 

Requirement already satisfied (use --upgrade to upgrade): xmltodict in /usr/lib/python2.6/site-packages (from pywinrm[kerberos]) 

Requirement already satisfied (use --upgrade to upgrade): requests&gt;=2.9.1 in /usr/lib/python2.6/site-packages (from pywinrm[kerberos]) 

Requirement already satisfied (use --upgrade to upgrade): six in /usr/lib/python2.6/site-packages (from pywinrm[kerberos]) 

Requirement already satisfied (use --upgrade to upgrade): requests-ntlm&gt;=0.3.0 in /usr/lib/python2.6/site-packages (from pywinrm[kerberos]) 

Collecting requests-kerberos&gt;=0.10.0; extra == "kerberos" (from pywinrm[kerberos]) 

/usr/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:318: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning. 

SNIMissingWarning 

/usr/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning. 

InsecurePlatformWarning 

Downloading requests_kerberos-0.10.0-py2.py3-none-any.whl 

Requirement already satisfied (use --upgrade to upgrade): python-ntlm3 in /usr/lib/python2.6/site-packages (from requests-ntlm&gt;=0.3.0-&gt;pywinrm[kerberos]) 

Collecting pykerberos&lt;2.0.0,&gt;=1.1.8; sys_platform != "win32" (from requests-kerberos&gt;=0.10.0; extra == "kerberos"-&gt;pywinrm[kerberos]) 

Downloading pykerberos-1.1.13.tar.gz 

Complete output from command python setup.py egg_info: 

Traceback (most recent call last): 

File "&lt;string&gt;", line 1, in &lt;module&gt; 

File "/tmp/pip-build-s071PJ/pykerberos/setup.py", line 52, in &lt;module&gt; 

extra_link_args = check_krb5_config("--libs", "gssapi") 

File "/tmp/pip-build-s071PJ/pykerberos/setup.py", line 36, in check_krb5_config 

raise subprocess.CalledProcessError(retcode, cmd, output=output) 

TypeError: __init__() got an unexpected keyword argument 'output' 



---------------------------------------- 

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-s071PJ/pykerberos/ 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/e023df92/attachment.html>

From danmcd at omniti.com  Tue Jun  7 20:26:37 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Tue, 7 Jun 2016 16:26:37 -0400
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
Message-ID: <7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>

I'd recommend installing a modern python.  The built-in one for OmniOS is specifically for pkg(5) and other OmniOS-only tools.

The ms.omniti.com IPS server has a python27, e.g.

bloody(~)[1]% pkg search python27
INDEX      ACTION VALUE                                PACKAGE
basename   dir    opt/python27                         pkg:/omniti/runtime/python-27 at 2.7.6-0.151008
basename   dir    opt/python27                         pkg:/omniti/runtime/python-27 at 2.7.6-0.151012
basename   dir    opt/python27                         pkg:/omniti/runtime/python-27 at 2.7.6-0.151014
basename   dir    opt/python27                         pkg:/omniti/library/python-2/docutils at 0.11-0.151014
basename   dir    opt/omni/lib/amd64/graphviz/python27 pkg:/omniti/image/graphviz at 2.28.0-0.151002
basename   dir    opt/python27                         pkg:/omniti/library/python-2/docutils at 0.11-0.151014
basename   dir    opt/python27                         pkg:/omniti/library/python-27/psycopg2 at 2.4.5-0.151006
basename   dir    opt/python27                         pkg:/omniti/runtime/python-27 at 2.7.6-0.151006
basename   dir    opt/python27                         pkg:/omniti/library/python-27/psycopg2 at 2.4.5-0.151014
bloody(~)[0]% pkg publisher
PUBLISHER                   TYPE     STATUS P LOCATION
omnios                      origin   online F file:///export/home/builder/builder.repo/
ms.omniti.com               origin   online F http://pkg.omniti.com/omniti-ms/
bloody(~)[0]% 


Dan


From henson at acm.org  Tue Jun  7 20:54:17 2016
From: henson at acm.org (Paul B. Henson)
Date: Tue, 7 Jun 2016 13:54:17 -0700
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
Message-ID: <20160607205416.GS21604@bender.unx.cpp.edu>

On Tue, Jun 07, 2016 at 04:26:37PM -0400, Dan McDonald wrote:
> I'd recommend installing a modern python.  The built-in one for OmniOS
> is specifically for pkg(5) and other OmniOS-only tools.

If it doesn't play well with the illumos bundled kerberos, you could
also try pkgsrc, either from the joyent prebuilt binaries or via
building it yourself...

From Josh.Barton at usurf.usu.edu  Tue Jun  7 21:39:02 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Tue, 7 Jun 2016 21:39:02 +0000
Subject: [OmniOS-discuss] Driver Install
Message-ID: <7542dcba13054715ba372be9e3bd6763@Ek.usurf.usu.edu>

How do I go about installing drivers from either the pkg repo or from a file I get from a vendor like Avago (LSI 9300) whilst booted into the shell of the omnios install do? I tried a chroot but I get errors about /dev/urandom being missing.

I ask because ordinarily the cd environment is read only and I'm not sure how I could mount my hard disk and do a pkg install there.

Thanks
Josh Barton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/43140e72/attachment.html>

From danmcd at omniti.com  Tue Jun  7 22:10:36 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Tue, 7 Jun 2016 18:10:36 -0400
Subject: [OmniOS-discuss] Driver Install
In-Reply-To: <7542dcba13054715ba372be9e3bd6763@Ek.usurf.usu.edu>
References: <7542dcba13054715ba372be9e3bd6763@Ek.usurf.usu.edu>
Message-ID: <FC6EFA32-2245-46FF-8A45-CB0005B8356D@omniti.com>

LSI 9300 is already in OmniOS - just a regular install should be enough.  Unless it's the 24-port version, you're fine without an extra driver.

Dan

Sent from my iPhone (typos, autocorrect, and all)

> On Jun 7, 2016, at 5:39 PM, Josh Barton <Josh.Barton at usurf.usu.edu> wrote:
> 
> How do I go about installing drivers from either the pkg repo or from a file I get from a vendor like Avago (LSI 9300) whilst booted into the shell of the omnios install do? I tried a chroot but I get errors about /dev/urandom being missing.
> 
> I ask because ordinarily the cd environment is read only and I'm not sure how I could mount my hard disk and do a pkg install there.
> 
> Thanks
> Josh Barton
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160607/0a40dbb4/attachment.html>

From henson at acm.org  Wed Jun  8 01:09:58 2016
From: henson at acm.org (Paul B. Henson)
Date: Tue, 7 Jun 2016 18:09:58 -0700
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
Message-ID: <038601d1c122$79e19210$6da4b630$@acm.org>

> From: Josh Barton
> Sent: Tuesday, June 07, 2016 10:53 AM
> 
> the word grub with a flashing cursor and I am unable to interact at all. I
did
> notice a warning about i/o requests not being aligned with the 4096 byte
disk

I believe you said you only saw that warning when manually running
grubinstall from the cli after dropping to the shell from the install cd?

> should be. I have checked to ensure that I am running via AHCI in the
BIOS.

As I understand you are trying to boot via the SAS controller, so the SATA
settings in the BIOS aren't relevant, unless you tried to connect one of the
disks directly to an onboard SATA connector as I suggested earlier.

I was working with Josh off list, I gave him a number of suggestions, I'm
not sure which ones he has tried; perhaps it would be helpful if he reviewed
what he has done? One of the suggestions was to try reinstalling grub, from
what I understand that is when he saw the sector alignment warnings and it
still did not boot successfully.

I also suggested disabling the controller bios on the two controllers that
he is not booting from, or connecting the boot disk directly to an onboard
SATA port to see what happens. Beyond that, I suggested he try installing a
Linux distribution to make sure it would boot just to rule out completely
faulty hardware.

Any other thoughts? Perhaps temporarily pulling out two of the controllers?
Installing to a different disk on a different controller?



From martijn at fennis.tk  Wed Jun  8 05:00:50 2016
From: martijn at fennis.tk (Martijn Fennis)
Date: Wed, 8 Jun 2016 07:00:50 +0200
Subject: [OmniOS-discuss] slices & zfs
Message-ID: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>

Hi,


Does someone have some info about setting up ZFS on top of slices ?

Having 10 drives which i would like to have the outer ring configured @ raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.


What i find on google is to use complete devs and difficult to interpret slicing info..



Thanks,
Martijn

Verzonden vanuit Mail voor Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/cbc8d6af/attachment.html>

From danmcd at omniti.com  Wed Jun  8 05:28:09 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 8 Jun 2016 01:28:09 -0400
Subject: [OmniOS-discuss] io-lx-public update
Message-ID: <45151D8D-2615-41B7-8AC0-233E9F080583@omniti.com>

I've pushed back a bunch of bits to the public repo:

	https://github.com/danmcd/io-lx-public/

Mostly build and global-zone stability.  I'm now back where I was with try#2.  (You'll see a branch labelled "io-lx-try3", but that was a placeholder...)  There are a couple of lint fixes I could probably push over to Joyent if they wanted them.  I think I'll wait until I tackle more and catchup again with Joyent.

It boots global-only, but ipkg & lipkg zones are still not running yet.  I'm sure I mismerged zoneadmd and friends.

FYI,
Dan


From daleg at omniti.com  Wed Jun  8 06:20:42 2016
From: daleg at omniti.com (Dale Ghent)
Date: Wed, 8 Jun 2016 02:20:42 -0400
Subject: [OmniOS-discuss] slices & zfs
In-Reply-To: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>
References: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>
Message-ID: <1F082D02-A536-4C69-A288-9A06568E9594@omniti.com>


> On Jun 8, 2016, at 1:00 AM, Martijn Fennis <martijn at fennis.tk> wrote:
> 
> Hi,
> 
> 
> Does someone have some info about setting up ZFS on top of slices ?
> 
> Having 10 drives which i would like to have the outer ring configured @ raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
> 
> 
> What i find on google is to use complete devs and difficult to interpret slicing info..

ZFS is designed to operate with full control of the drive - this means no slicing. Yes, one can use ZFS with slices, but you must first understand why that is not optimal, and what you give up when such a configuration is used.

When consuming a partition on a disk, ZFS can no-longer assume that it has complete control over the entire disk and cannot enable (and proactively manage) the disk's own write caching capabilities. This will incur a performance penalty, the magnitude of which depends on your specific IO patterns.

I am curious why you think you need to slice up your drives like that in such a scheme... the mixing of RAID levels across the same devices seem unwieldy given that ZFS was designed to avoid this kind of scenario, and ZFS will compete with itself because it now is operating 2 pools across the same physical devices, which is absolutely terrible for IO scheduling.

/dale
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/7cc25bf5/attachment.bin>

From jimklimov at cos.ru  Wed Jun  8 07:24:33 2016
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 08 Jun 2016 09:24:33 +0200
Subject: [OmniOS-discuss] slices & zfs
In-Reply-To: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>
References: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>
Message-ID: <3AEA6AA6-CEA9-4063-8303-368619F97E7D@cos.ru>

8 ???? 2016??. 7:00:50 CEST, Martijn Fennis <martijn at fennis.tk> ?????:
>Hi,
>
>
>Does someone have some info about setting up ZFS on top of slices ?
>
>Having 10 drives which i would like to have the outer ring configured @
>raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
>
>
>What i find on google is to use complete devs and difficult to
>interpret slicing info..
>
>
>
>Thanks,
>Martijn
>
>Verzonden vanuit Mail voor Windows 10
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>OmniOS-discuss mailing list
>OmniOS-discuss at lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

You just set up slices (with format utility on one disk, replicate setup with prtvtoc to others if they are identical). Then you use slice numbers as vdevs to zpool command. Note that slices s0 and s2 are reserved, so you have s1 and s3-s7 to play with. (X86 may expose s8 and s9 - also reserved).

Also note that dedup may require some RAM and maybe a separate fast SSD to cache reads and writes, to be efficient. Otherwise it can bog you down below single mb/s of i/o.

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

From jimklimov at cos.ru  Wed Jun  8 09:40:43 2016
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 08 Jun 2016 11:40:43 +0200
Subject: [OmniOS-discuss] slices & zfs
In-Reply-To: <1F082D02-A536-4C69-A288-9A06568E9594@omniti.com>
References: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>
	<1F082D02-A536-4C69-A288-9A06568E9594@omniti.com>
Message-ID: <BEE302B8-B9F0-47E8-A71F-C32881805847@cos.ru>

8 ???? 2016??. 8:20:42 CEST, Dale Ghent <daleg at omniti.com> ?????:
>
>> On Jun 8, 2016, at 1:00 AM, Martijn Fennis <martijn at fennis.tk> wrote:
>> 
>> Hi,
>> 
>> 
>> Does someone have some info about setting up ZFS on top of slices ?
>> 
>> Having 10 drives which i would like to have the outer ring configured
>@ raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
>> 
>> 
>> What i find on google is to use complete devs and difficult to
>interpret slicing info..
>
>ZFS is designed to operate with full control of the drive - this means
>no slicing. Yes, one can use ZFS with slices, but you must first
>understand why that is not optimal, and what you give up when such a
>configuration is used.
>
>When consuming a partition on a disk, ZFS can no-longer assume that it
>has complete control over the entire disk and cannot enable (and
>proactively manage) the disk's own write caching capabilities. This
>will incur a performance penalty, the magnitude of which depends on
>your specific IO patterns.
>
>I am curious why you think you need to slice up your drives like that
>in such a scheme... the mixing of RAID levels across the same devices
>seem unwieldy given that ZFS was designed to avoid this kind of
>scenario, and ZFS will compete with itself because it now is operating
>2 pools across the same physical devices, which is absolutely terrible
>for IO scheduling.
>
>/dale
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>OmniOS-discuss mailing list
>OmniOS-discuss at lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

This setup sort of makes sense on servers with limited amount of disks (ok, 10 is not that - rather the older/smaller 4-disk ones). There you have a low-traffic rpool mirror (4-way, or 2-way rpool and 2-way swap of same size) and a raidzN or raid10 in the bigger partitions/slices for zones and data. I did it in Sol10 from the get-go. Rpools suffices to be minimal, like 4gb there. With IPS and its package caches i'd recommend no less that 16gb for an rpool now, more if you want substantial GZ software and/or multiple versions to roll back to.

Caches you can enable/disable manually too, perhaps automated in an init-script (iirc i posted an example in wiki or git somewhere).

Queuing commands is in a way a headache for the disks, assuming scsi/sas or (e)sata. It may make sense to keep a fast-tracked scratch area for bursty fast io as a separate pool...

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

From martijn at fennis.tk  Wed Jun  8 14:37:50 2016
From: martijn at fennis.tk (Martijn Fennis)
Date: Wed, 8 Jun 2016 16:37:50 +0200
Subject: [OmniOS-discuss] slices & zfs
Message-ID: <DUB402-EAS17457F777885943CC058EE1B55E0@phx.gbl>

Hi Dale and Jim,

Thanks for your time.

The reason is to store VMs on the Quick-pool and downloads on the Slow-pool.

I would personally not assign the Slow-pool any of my memory, perhaps meta-data.

That?s why i would like to assign the inner part to the slow-pool.



Also i?ve read about a maximum of 2 TB per slice, anyone?


But maybe i should not do the slicing at all?


Thanks in advance


Van: Dale Ghent<mailto:daleg at omniti.com>
Verzonden: woensdag 8 juni 2016 08:21
Aan: Martijn Fennis<mailto:martijn at fennis.tk>
CC: omnios-discuss at lists.omniti.com<mailto:omnios-discuss at lists.omniti.com>
Onderwerp: Re: [OmniOS-discuss] slices & zfs


> On Jun 8, 2016, at 1:00 AM, Martijn Fennis <martijn at fennis.tk> wrote:
>
> Hi,
>
>
> Does someone have some info about setting up ZFS on top of slices ?
>
> Having 10 drives which i would like to have the outer ring configured @ raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
>
>
> What i find on google is to use complete devs and difficult to interpret slicing info..

ZFS is designed to operate with full control of the drive - this means no slicing. Yes, one can use ZFS with slices, but you must first understand why that is not optimal, and what you give up when such a configuration is used.

When consuming a partition on a disk, ZFS can no-longer assume that it has complete control over the entire disk and cannot enable (and proactively manage) the disk's own write caching capabilities. This will incur a performance penalty, the magnitude of which depends on your specific IO patterns.

I am curious why you think you need to slice up your drives like that in such a scheme... the mixing of RAID levels across the same devices seem unwieldy given that ZFS was designed to avoid this kind of scenario, and ZFS will compete with itself because it now is operating 2 pools across the same physical devices, which is absolutely terrible for IO scheduling.

/dale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/97134973/attachment-0001.html>

From gordon at hafnia.dk  Wed Jun  8 16:03:43 2016
From: gordon at hafnia.dk (Gordon Selisek)
Date: Wed, 08 Jun 2016 18:03:43 +0200
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
Message-ID: <15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>

Dan,



Tried with your recommendation, I'm really stuck here, now it fails like this:





root at omnitest:/root# pip install pywinrm[kerberos] 

Requirement already satisfied (use --upgrade to upgrade): pywinrm[kerberos] in /           opt/python27/lib/python2.7/site-packages 

Requirement already satisfied (use --upgrade to upgrade): xmltodict in /opt/pyth           on27/lib/python2.7/site-packages (from pywinrm[kerberos]) 

Requirement already satisfied (use --upgrade to upgrade): requests&gt;=2.9.1 in /op           t/python27/lib/python2.7/site-packages (from pywinrm[kerberos]) 

Requirement already satisfied (use --upgrade to upgrade): six in /opt/python27/l           ib/python2.7/site-packages (from pywinrm[kerberos]) 

Requirement already satisfied (use --upgrade to upgrade): requests-ntlm&gt;=0.3.0 i           n /opt/python27/lib/python2.7/site-packages (from pywinrm[kerberos]) 

Collecting requests-kerberos&gt;=0.10.0; extra == "kerberos" (from pywinrm[kerberos           ]) 

Using cached requests_kerberos-0.10.0-py2.py3-none-any.whl 

Requirement already satisfied (use --upgrade to upgrade): python-ntlm3 in /opt/p           ython27/lib/python2.7/site-packages (from requests-ntlm&gt;=0.3.0-&gt;pywinrm[kerberos           ]) 

Collecting pykerberos&lt;2.0.0,&gt;=1.1.8; sys_platform != "win32" (from requests-kerb           eros&gt;=0.10.0; extra == "kerberos"-&gt;pywinrm[kerberos]) 

Using cached pykerberos-1.1.13.tar.gz 

Complete output from command python setup.py egg_info: 

Traceback (most recent call last): 

File "&lt;string&gt;", line 1, in &lt;module&gt; 

File "/tmp/pip-build-3gE8gK/pykerberos/setup.py", line 52, in &lt;module&gt; 

extra_link_args = check_krb5_config("--libs", "gssapi") 

File "/tmp/pip-build-3gE8gK/pykerberos/setup.py", line 36, in check_krb5_c           onfig 

raise subprocess.CalledProcessError(retcode, cmd, output=output) 

subprocess.CalledProcessError: Command 'krb5-config' returned non-zero exit            status 1 



---------------------------------------- 

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-3g           E8gK/pykerberos/ 









---- On Tue, 07 Jun 2016 22:26:37 +0200 Dan McDonald &lt;danmcd at omniti.com&gt;wrote ---- 




I'd recommend installing a modern python. The built-in one for OmniOS is specifically for pkg(5) and other OmniOS-only tools. 

 

The ms.omniti.com IPS server has a python27, e.g. 

 

bloody(~)[1]% pkg search python27 

INDEX ACTION VALUE PACKAGE 

basename dir opt/python27 pkg:/omniti/runtime/python-27 at 2.7.6-0.151008 

basename dir opt/python27 pkg:/omniti/runtime/python-27 at 2.7.6-0.151012 

basename dir opt/python27 pkg:/omniti/runtime/python-27 at 2.7.6-0.151014 

basename dir opt/python27 pkg:/omniti/library/python-2/docutils at 0.11-0.151014 

basename dir opt/omni/lib/amd64/graphviz/python27 pkg:/omniti/image/graphviz at 2.28.0-0.151002 

basename dir opt/python27 pkg:/omniti/library/python-2/docutils at 0.11-0.151014 

basename dir opt/python27 pkg:/omniti/library/python-27/psycopg2 at 2.4.5-0.151006 

basename dir opt/python27 pkg:/omniti/runtime/python-27 at 2.7.6-0.151006 

basename dir opt/python27 pkg:/omniti/library/python-27/psycopg2 at 2.4.5-0.151014 

bloody(~)[0]% pkg publisher 

PUBLISHER TYPE STATUS P LOCATION 

omnios origin online F file:///export/home/builder/builder.repo/ 

ms.omniti.com origin online F http://pkg.omniti.com/omniti-ms/ 

bloody(~)[0]% 

 

 

Dan 

 






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/65c42bcd/attachment.html>

From danmcd at omniti.com  Wed Jun  8 16:44:35 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 8 Jun 2016 12:44:35 -0400
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
	<15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>
Message-ID: <A858B461-EC49-43F0-9BDA-73AB95EF30B8@omniti.com>

From what I can see, this is a problem with pywinrm:

> Traceback (most recent call last): 
> File "<string>", line 1, in <module> 
> File "/tmp/pip-build-3gE8gK/pykerberos/setup.py", line 52, in <module> 
> extra_link_args = check_krb5_config("--libs", "gssapi") 
> File "/tmp/pip-build-3gE8gK/pykerberos/setup.py", line 36, in check_krb5_c           onfig 
> raise subprocess.CalledProcessError(retcode, cmd, output=output) 
> subprocess.CalledProcessError: Command 'krb5-config' returned non-zero exit            status 1 
> 

I wonder if it's assuming Linux commands for some things?

At this point, you'll have to ask someone with more Python knowledge than me.

Sorry,
Dan


From jimklimov at cos.ru  Wed Jun  8 16:45:42 2016
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 08 Jun 2016 18:45:42 +0200
Subject: [OmniOS-discuss] slices & zfs
In-Reply-To: <DUB402-EAS17457F777885943CC058EE1B55E0@phx.gbl>
References: <DUB402-EAS17457F777885943CC058EE1B55E0@phx.gbl>
Message-ID: <A2323AA3-B04A-4FB7-82BA-D2C77C30DD25@cos.ru>

8 ???? 2016??. 16:37:50 CEST, Martijn Fennis <martijn at fennis.tk> ?????:
>Hi Dale and Jim,
>
>Thanks for your time.
>
>The reason is to store VMs on the Quick-pool and downloads on the
>Slow-pool.
>
>I would personally not assign the Slow-pool any of my memory, perhaps
>meta-data.
>
>That?s why i would like to assign the inner part to the slow-pool.
>
>
>
>Also i?ve read about a maximum of 2 TB per slice, anyone?
>
>
>But maybe i should not do the slicing at all?
>
>
>Thanks in advance
>
>
>Van: Dale Ghent<mailto:daleg at omniti.com>
>Verzonden: woensdag 8 juni 2016 08:21
>Aan: Martijn Fennis<mailto:martijn at fennis.tk>
>CC:
>omnios-discuss at lists.omniti.com<mailto:omnios-discuss at lists.omniti.com>
>Onderwerp: Re: [OmniOS-discuss] slices & zfs
>
>
>> On Jun 8, 2016, at 1:00 AM, Martijn Fennis <martijn at fennis.tk> wrote:
>>
>> Hi,
>>
>>
>> Does someone have some info about setting up ZFS on top of slices ?
>>
>> Having 10 drives which i would like to have the outer ring configured
>@ raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
>>
>>
>> What i find on google is to use complete devs and difficult to
>interpret slicing info..
>
>ZFS is designed to operate with full control of the drive - this means
>no slicing. Yes, one can use ZFS with slices, but you must first
>understand why that is not optimal, and what you give up when such a
>configuration is used.
>
>When consuming a partition on a disk, ZFS can no-longer assume that it
>has complete control over the entire disk and cannot enable (and
>proactively manage) the disk's own write caching capabilities. This
>will incur a performance penalty, the magnitude of which depends on
>your specific IO patterns.
>
>I am curious why you think you need to slice up your drives like that
>in such a scheme... the mixing of RAID levels across the same devices
>seem unwieldy given that ZFS was designed to avoid this kind of
>scenario, and ZFS will compete with itself because it now is operating
>2 pools across the same physical devices, which is absolutely terrible
>for IO scheduling.
>
>/dale
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>OmniOS-discuss mailing list
>OmniOS-discuss at lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

2tb limit - not true. This pool worked back in SXCE:

[root at thumper ~]# format c1t2d0s0
selecting c1t2d0s0
[disk formatted]
/dev/dsk/c1t2d0s0 is part of active ZFS pool temp. Please see zpool(1M).
/dev/dsk/c1t2d0s1 is part of active ZFS pool pond. Please see zpool(1M).

partition> p
Current partition table (original):
Total disk sectors available: 5860516717 + 16384 (reserved sectors)

Part      Tag    Flag     First Sector          Size          Last Sector
  0        usr    wm               256         2.50TB           5372126207
  1        usr    wm        5372126400       232.87GB           5860500351
  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        usr    wm        5860500367         8.00MB           5860516750

partition>

There is an issue about 2TB for boot disks though - grub doesn't see more, so you must ensure rpool is below 2tb and maybe add compatibility MBR partitioning along with real EFI layout with same partition offsets and sizes.

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

From daleg at omniti.com  Wed Jun  8 16:55:34 2016
From: daleg at omniti.com (Dale Ghent)
Date: Wed, 8 Jun 2016 12:55:34 -0400
Subject: [OmniOS-discuss] Looking for people with X550 SFP+
Message-ID: <D5E07067-E7EA-4E13-A1A4-DBEBFAA1D463@omniti.com>


Hello,

I'm interested in knowing if any users of OmniOS have hardware that is equipped with a Intel X550 10Gb ethernet chip *with* SFP as the PHY (not base-T). I know SuperMicro at least has some servers on offer with this specific combination, and I'm hoping some enterprising OmniOS users out there might have one already.

If you do have one of these, are able to wire the SFP ports up to a proper switch or directly to another SFP-based 10Gb NIC, and are interested in doing some basic functionality testing of a new ixgbe driver... please contact me off-list.

/dale
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/789095af/attachment.bin>

From richard.elling at richardelling.com  Wed Jun  8 17:24:46 2016
From: richard.elling at richardelling.com (Richard Elling)
Date: Wed, 8 Jun 2016 10:24:46 -0700
Subject: [OmniOS-discuss] slices & zfs
In-Reply-To: <DUB402-EAS17457F777885943CC058EE1B55E0@phx.gbl>
References: <DUB402-EAS17457F777885943CC058EE1B55E0@phx.gbl>
Message-ID: <45D8B7A8-EEE9-43D6-B2AB-D2E3ADF89EFD@RichardElling.com>


> On Jun 8, 2016, at 7:37 AM, Martijn Fennis <martijn at fennis.tk> wrote:
> 
> Hi Dale and Jim,
>  
> Thanks for your time.
>  
> The reason is to store VMs on the Quick-pool and downloads on the Slow-pool.
>  
> I would personally not assign the Slow-pool any of my memory, perhaps meta-data.
>  
> That?s why i would like to assign the inner part to the slow-pool.
>  
>  
>  
> Also i?ve read about a maximum of 2 TB per slice, anyone?

For SMI labels, use EFI labels for modern disks.
 
>  
>  
> But maybe i should not do the slicing at all?

You cannot not slice. The only question is whether ZFS creates an EFI label and slice 0 for you,
or you do that yourself using ?format -e?  This is purely a convenience feature, there is no other
science or strategy behind it.
 ? richard

>  
>  
> Thanks in advance
>  
>  
> Van: Dale Ghent <mailto:daleg at omniti.com>
> Verzonden: woensdag 8 juni 2016 08:21
> Aan: Martijn Fennis <mailto:martijn at fennis.tk>
> CC: omnios-discuss at lists.omniti.com <mailto:omnios-discuss at lists.omniti.com>
> Onderwerp: Re: [OmniOS-discuss] slices & zfs
>  
> 
> > On Jun 8, 2016, at 1:00 AM, Martijn Fennis <martijn at fennis.tk <mailto:martijn at fennis.tk>> wrote:
> > 
> > Hi,
> > 
> > 
> > Does someone have some info about setting up ZFS on top of slices ?
> > 
> > Having 10 drives which i would like to have the outer ring configured @ raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
> > 
> > 
> > What i find on google is to use complete devs and difficult to interpret slicing info..
> 
> ZFS is designed to operate with full control of the drive - this means no slicing. Yes, one can use ZFS with slices, but you must first understand why that is not optimal, and what you give up when such a configuration is used.
> 
> When consuming a partition on a disk, ZFS can no-longer assume that it has complete control over the entire disk and cannot enable (and proactively manage) the disk's own write caching capabilities. This will incur a performance penalty, the magnitude of which depends on your specific IO patterns.
> 
> I am curious why you think you need to slice up your drives like that in such a scheme... the mixing of RAID levels across the same devices seem unwieldy given that ZFS was designed to avoid this kind of scenario, and ZFS will compete with itself because it now is operating 2 pools across the same physical devices, which is absolutely terrible for IO scheduling.
> 
> /dale
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com <mailto:OmniOS-discuss at lists.omniti.com>
> http://lists.omniti.com/mailman/listinfo/omnios-discuss <http://lists.omniti.com/mailman/listinfo/omnios-discuss>
--

Richard.Elling at RichardElling.com
+1-760-896-4422



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/afc6d678/attachment-0001.html>

From richard.elling at richardelling.com  Wed Jun  8 17:28:26 2016
From: richard.elling at richardelling.com (Richard Elling)
Date: Wed, 8 Jun 2016 10:28:26 -0700
Subject: [OmniOS-discuss] slices & zfs
In-Reply-To: <3AEA6AA6-CEA9-4063-8303-368619F97E7D@cos.ru>
References: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>
	<3AEA6AA6-CEA9-4063-8303-368619F97E7D@cos.ru>
Message-ID: <4EA37525-85AB-4689-A11D-E7124F9DE0E2@RichardElling.com>


> On Jun 8, 2016, at 12:24 AM, Jim Klimov <jimklimov at cos.ru> wrote:
> 
> 8 ???? 2016 ?. 7:00:50 CEST, Martijn Fennis <martijn at fennis.tk> ?????:
>> Hi,
>> 
>> 
>> Does someone have some info about setting up ZFS on top of slices ?
>> 
>> Having 10 drives which i would like to have the outer ring configured @
>> raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
>> 
>> 
>> What i find on google is to use complete devs and difficult to
>> interpret slicing info..
>> 
>> 
>> 
>> Thanks,
>> Martijn
>> 
>> Verzonden vanuit Mail voor Windows 10
>> 
>> 
>> 
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> You just set up slices (with format utility on one disk, replicate setup with prtvtoc to others if they are identical). Then you use slice numbers as vdevs to zpool command. Note that slices s0 and s2 are reserved, so you have s1 and s3-s7 to play with. (X86 may expose s8 and s9 - also reserved).

This is not correct. For SMI labels, s2, by convention, defaults to the whole disk ? aka the ?backup? partition (slice).
Since around 1980, I know of no backup software that expects s2 to be the whole disk. This was also an overlapping
slice. For modern disks and EFI labels, overlapping slices are not permitted ? thus preventing many common mistakes
that led to corrupted data on the old SMI-labeled drives.
 ? richard


> 
> Also note that dedup may require some RAM and maybe a separate fast SSD to cache reads and writes, to be efficient. Otherwise it can bog you down below single mb/s of i/o.
> 
> Jim
> --
> Typos courtesy of K-9 Mail on my Samsung Android
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

--

Richard.Elling at RichardElling.com
+1-760-896-4422



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/3cde076a/attachment.html>

From Josh.Barton at usurf.usu.edu  Wed Jun  8 17:50:05 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Wed, 8 Jun 2016 17:50:05 +0000
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <038601d1c122$79e19210$6da4b630$@acm.org>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
	<038601d1c122$79e19210$6da4b630$@acm.org>
Message-ID: <4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>

I replaced the OS drive with a 1TB HGST drive we had on hand and re-installed and Omni booted no problem. It seems as though there is an issue with the Seagate ST2000NX0243 (2TB) drives, can anyone corroborate this or recommend a good method for running disk diagnostics / verifying OmniOS compatibility?

Thanks

Josh Barton  

-----Original Message-----
From: Paul B. Henson [mailto:henson at acm.org] 
Sent: Tuesday, June 7, 2016 7:10 PM
To: Josh Barton <Josh.Barton at usurf.usu.edu>; omnios-discuss at lists.omniti.com
Subject: RE: [OmniOS-discuss] Only grub after boot

> From: Josh Barton
> Sent: Tuesday, June 07, 2016 10:53 AM
> 
> the word grub with a flashing cursor and I am unable to interact at 
> all. I
did
> notice a warning about i/o requests not being aligned with the 4096 
> byte
disk

I believe you said you only saw that warning when manually running grubinstall from the cli after dropping to the shell from the install cd?

> should be. I have checked to ensure that I am running via AHCI in the
BIOS.

As I understand you are trying to boot via the SAS controller, so the SATA settings in the BIOS aren't relevant, unless you tried to connect one of the disks directly to an onboard SATA connector as I suggested earlier.

I was working with Josh off list, I gave him a number of suggestions, I'm not sure which ones he has tried; perhaps it would be helpful if he reviewed what he has done? One of the suggestions was to try reinstalling grub, from what I understand that is when he saw the sector alignment warnings and it still did not boot successfully.

I also suggested disabling the controller bios on the two controllers that he is not booting from, or connecting the boot disk directly to an onboard SATA port to see what happens. Beyond that, I suggested he try installing a Linux distribution to make sure it would boot just to rule out completely faulty hardware.

Any other thoughts? Perhaps temporarily pulling out two of the controllers?
Installing to a different disk on a different controller?



From danmcd at omniti.com  Wed Jun  8 18:07:53 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 8 Jun 2016 14:07:53 -0400
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
	<038601d1c122$79e19210$6da4b630$@acm.org>
	<4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>
Message-ID: <98C4A43C-97AF-4E6A-A4D8-280BEF9F9737@omniti.com>


> On Jun 8, 2016, at 1:50 PM, Josh Barton <Josh.Barton at usurf.usu.edu> wrote:
> 
> I replaced the OS drive with a 1TB HGST drive we had on hand and re-installed and Omni booted no problem. It seems as though there is an issue with the Seagate ST2000NX0243 (2TB) drives, can anyone corroborate this or recommend a good method for running disk diagnostics / verifying OmniOS compatibility?

Did you boot that 1TB drive off the HBA?  Or off one of the UHCI SATA ports?  I'm assuming off the HBA (so as all other things were kept equal).

If that's the case, I'm curious as to the "ashift" values of your drives:

	zdb -C <poolname>

will give you configuration information about various pools.

I've not heard of people having problems booting with ashift=12 (4k sector), but maybe I'm wrong?

Dan


From doug at will.to  Wed Jun  8 18:13:00 2016
From: doug at will.to (Doug Hughes)
Date: Wed, 8 Jun 2016 14:13:00 -0400
Subject: [OmniOS-discuss] Looking for people with X550 SFP+
In-Reply-To: <D5E07067-E7EA-4E13-A1A4-DBEBFAA1D463@omniti.com>
References: <D5E07067-E7EA-4E13-A1A4-DBEBFAA1D463@omniti.com>
Message-ID: <cd380173-321a-a1f5-02fd-a3fdedb38794@will.to>

I've used the Intel 520DA2, but not the 550 specifically. Works well. 
Not sure if that is useful information or not.

On 6/8/2016 12:55 PM, Dale Ghent wrote:
> Hello,
>
> I'm interested in knowing if any users of OmniOS have hardware that is equipped with a Intel X550 10Gb ethernet chip *with* SFP as the PHY (not base-T). I know SuperMicro at least has some servers on offer with this specific combination, and I'm hoping some enterprising OmniOS users out there might have one already.
>
> If you do have one of these, are able to wire the SFP ports up to a proper switch or directly to another SFP-based 10Gb NIC, and are interested in doing some basic functionality testing of a new ixgbe driver... please contact me off-list.
>
> /dale
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160608/d4b07b93/attachment.html>

From danmcd at omniti.com  Wed Jun  8 18:16:42 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 8 Jun 2016 14:16:42 -0400
Subject: [OmniOS-discuss] io-lx-public update
In-Reply-To: <45151D8D-2615-41B7-8AC0-233E9F080583@omniti.com>
References: <45151D8D-2615-41B7-8AC0-233E9F080583@omniti.com>
Message-ID: <462B2307-EECD-4F1D-A77C-A6F211652CFA@omniti.com>


> On Jun 8, 2016, at 1:28 AM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> I've pushed back a bunch of bits to the public repo:
> 
> 	https://github.com/danmcd/io-lx-public/

And every time I push back to the above repo, I will update this webrev:

	http://kebe.com/~danmcd/webrevs/io-lx-public/

Dan


From danmcd at omniti.com  Wed Jun  8 18:23:22 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Wed, 8 Jun 2016 14:23:22 -0400
Subject: [OmniOS-discuss] Looking for people with X550 SFP+
In-Reply-To: <cd380173-321a-a1f5-02fd-a3fdedb38794@will.to>
References: <D5E07067-E7EA-4E13-A1A4-DBEBFAA1D463@omniti.com>
	<cd380173-321a-a1f5-02fd-a3fdedb38794@will.to>
Message-ID: <717D3B3A-0973-4455-AA0E-1F041F706BD4@omniti.com>


> On Jun 8, 2016, at 2:13 PM, Doug Hughes <doug at will.to> wrote:
> 
> I've used the Intel 520DA2, but not the 550 specifically. Works well. Not sure if that is useful information or not.

Unfortunately, that's not.  The 520 uses the existing 82599 chipset.  The X550 is a new chipset, and Dale's been trying to get that up and running.

Dan


From henson at acm.org  Wed Jun  8 18:34:33 2016
From: henson at acm.org (Paul B. Henson)
Date: Wed, 8 Jun 2016 11:34:33 -0700
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <98C4A43C-97AF-4E6A-A4D8-280BEF9F9737@omniti.com>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
	<038601d1c122$79e19210$6da4b630$@acm.org>
	<4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>
	<98C4A43C-97AF-4E6A-A4D8-280BEF9F9737@omniti.com>
Message-ID: <50F10AEA-2044-4E08-834A-85B44D31A9E3@acm.org>

Josh, did you ever try booting the 2tb drive off the sata controller?

When the box posts, does the hba bios properly report the size of the 2tb drives? When I first installed my lsi hba with 3tb sata drives, it showed them as invalid during post. They worked fine with the os, but the hba bios didn't recognize them. After I updated the hba bios, it properly reported them as 3tb drives. Given grub relies on the hba bios to access the drive, if it doesn't recognize the drive it won't work. 

Btw, his pool does have ashift=12, they are 4K drives. But that shouldn't matter to grub, particularly stage1 loading stage2, which just uses bios calls to read raw sectors? That's where it's failing. 

> On Jun 8, 2016, at 11:07 AM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> 
>> On Jun 8, 2016, at 1:50 PM, Josh Barton <Josh.Barton at usurf.usu.edu> wrote:
>> 
>> I replaced the OS drive with a 1TB HGST drive we had on hand and re-installed and Omni booted no problem. It seems as though there is an issue with the Seagate ST2000NX0243 (2TB) drives, can anyone corroborate this or recommend a good method for running disk diagnostics / verifying OmniOS compatibility?
> 
> Did you boot that 1TB drive off the HBA?  Or off one of the UHCI SATA ports?  I'm assuming off the HBA (so as all other things were kept equal).
> 
> If that's the case, I'm curious as to the "ashift" values of your drives:
> 
>    zdb -C <poolname>
> 
> will give you configuration information about various pools.
> 
> I've not heard of people having problems booting with ashift=12 (4k sector), but maybe I'm wrong?
> 
> Dan
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From Josh.Barton at usurf.usu.edu  Wed Jun  8 22:17:00 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Wed, 8 Jun 2016 22:17:00 +0000
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <50F10AEA-2044-4E08-834A-85B44D31A9E3@acm.org>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
	<038601d1c122$79e19210$6da4b630$@acm.org>
	<4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>
	<98C4A43C-97AF-4E6A-A4D8-280BEF9F9737@omniti.com>
	<50F10AEA-2044-4E08-834A-85B44D31A9E3@acm.org>
Message-ID: <c3cfd68235bf44569b954215f97a629b@Ek.usurf.usu.edu>

The hba is reporting the correct sizes for all drives, I didn't ever try directly plugging in to the motherboard sata controller because I couldn't find a molex to sata power adapter. 

To answer Dan, the ashift is 12 on all the disks.  At this point I just need to figure out an easier way of referencing drives rather than using the c1t5<WWN---------> method  which is very long. I appreciate everyone's help on this.

-----Original Message-----
From: Paul B. Henson [mailto:henson at acm.org] 
Sent: Wednesday, June 8, 2016 12:35 PM
To: Dan McDonald <danmcd at omniti.com>
Cc: Josh Barton <Josh.Barton at usurf.usu.edu>; omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] Only grub after boot

Josh, did you ever try booting the 2tb drive off the sata controller?

When the box posts, does the hba bios properly report the size of the 2tb drives? When I first installed my lsi hba with 3tb sata drives, it showed them as invalid during post. They worked fine with the os, but the hba bios didn't recognize them. After I updated the hba bios, it properly reported them as 3tb drives. Given grub relies on the hba bios to access the drive, if it doesn't recognize the drive it won't work. 

Btw, his pool does have ashift=12, they are 4K drives. But that shouldn't matter to grub, particularly stage1 loading stage2, which just uses bios calls to read raw sectors? That's where it's failing. 

> On Jun 8, 2016, at 11:07 AM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> 
>> On Jun 8, 2016, at 1:50 PM, Josh Barton <Josh.Barton at usurf.usu.edu> wrote:
>> 
>> I replaced the OS drive with a 1TB HGST drive we had on hand and re-installed and Omni booted no problem. It seems as though there is an issue with the Seagate ST2000NX0243 (2TB) drives, can anyone corroborate this or recommend a good method for running disk diagnostics / verifying OmniOS compatibility?
> 
> Did you boot that 1TB drive off the HBA?  Or off one of the UHCI SATA ports?  I'm assuming off the HBA (so as all other things were kept equal).
> 
> If that's the case, I'm curious as to the "ashift" values of your drives:
> 
>    zdb -C <poolname>
> 
> will give you configuration information about various pools.
> 
> I've not heard of people having problems booting with ashift=12 (4k sector), but maybe I'm wrong?
> 
> Dan
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From henson at acm.org  Thu Jun  9 02:38:25 2016
From: henson at acm.org (Paul B. Henson)
Date: Wed, 8 Jun 2016 19:38:25 -0700
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <c3cfd68235bf44569b954215f97a629b@Ek.usurf.usu.edu>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
	<038601d1c122$79e19210$6da4b630$@acm.org>
	<4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>
	<98C4A43C-97AF-4E6A-A4D8-280BEF9F9737@omniti.com>
	<50F10AEA-2044-4E08-834A-85B44D31A9E3@acm.org>
	<c3cfd68235bf44569b954215f97a629b@Ek.usurf.usu.edu>
Message-ID: <007401d1c1f7$ff96c990$fec45cb0$@acm.org>

> From: Josh Barton
> Sent: Wednesday, June 08, 2016 3:17 PM
> 
> The hba is reporting the correct sizes for all drives, I didn't ever try
directly
> plugging in to the motherboard sata controller because I couldn't find a
> molex to sata power adapter.

You could also see if anybody has a sff8087 breakout cable laying around so
you could hook up the SATA port to the hotswap backplane :).

Did you try installing a linux distribution to see if you could get its grub
to boot off of the 2TB drive via the SAS HBA? If that works, it would rule
out the hard drive itself as being faulty.



From henson at acm.org  Thu Jun  9 02:45:57 2016
From: henson at acm.org (Paul B. Henson)
Date: Wed, 8 Jun 2016 19:45:57 -0700
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <A858B461-EC49-43F0-9BDA-73AB95EF30B8@omniti.com>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>	<15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>
	<A858B461-EC49-43F0-9BDA-73AB95EF30B8@omniti.com>
Message-ID: <007f01d1c1f9$0d734290$2859c7b0$@acm.org>

> From: Dan McDonald
> Sent: Wednesday, June 08, 2016 9:45 AM
> 
> > extra_link_args = check_krb5_config("--libs", "gssapi")
>
> I wonder if it's assuming Linux commands for some things?

No, it's trying to use krb5-config options available under MIT kerberos that
don't exist under illumos kerberos. You will note the illumos variant, shown
second, is a bit sparse 8-/. I will say for the third time and then give up,
he should probably just install from pkgsrc :).

$ krb5-config --help
Usage: /usr/bin/krb5-config [OPTIONS] [LIBRARIES]
Options:
        [--help]          Help
        [--all]           Display version, vendor, and various values
        [--version]       Version information
        [--vendor]        Vendor information
        [--prefix]        Kerberos installed prefix
        [--exec-prefix]   Kerberos installed exec_prefix
        [--defccname]     Show built-in default ccache name
        [--defktname]     Show built-in default keytab name
        [--defcktname]    Show built-in default client keytab name
        [--cflags]        Compile time CFLAGS
        [--libs]          List libraries required to link [LIBRARIES]
Libraries:
        krb5              Kerberos 5 application
        gssapi            GSSAPI application with Kerberos 5 bindings
        gssrpc            GSSAPI RPC application
        kadm-client       Kadmin client
        kadm-server       Kadmin server
        kdb               Application that accesses the kerberos database


$ krb5-config --help
Usage: /usr/bin/krb5-config [OPTIONS] [LIBRARIES]
Options:
        [--help]          Help
        [--all]           Display version, vendor, and various values
        [--version]       Version information
        [--vendor]        Vendor information
        [--prefix]        Kerberos installed prefix
        [--exec-prefix]   Kerberos installed exec_prefix
        [--cflags]        Compile time CFLAGS
        [--libs]          List libraries required to link [LIBRARIES]
Libraries:
        krb5              Kerberos 5 application


From timo.raatikainen at sourapple.fi  Thu Jun  9 08:02:48 2016
From: timo.raatikainen at sourapple.fi (Timo Raatikainen)
Date: Thu, 9 Jun 2016 11:02:48 +0300
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <007401d1c1f7$ff96c990$fec45cb0$@acm.org>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
	<038601d1c122$79e19210$6da4b630$@acm.org>
	<4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>
	<98C4A43C-97AF-4E6A-A4D8-280BEF9F9737@omniti.com>
	<50F10AEA-2044-4E08-834A-85B44D31A9E3@acm.org>
	<c3cfd68235bf44569b954215f97a629b@Ek.usurf.usu.edu>
	<007401d1c1f7$ff96c990$fec45cb0$@acm.org>
Message-ID: <FAD201B0-7660-4D2A-9A1F-51C5C70FF273@sourapple.fi>

Notice that the drive in question (ST2000NX0243) is a 4k native drive. I?ve never tried booting from such drive, could someone confirm if grub can handle it? I suspect that it might not.

--
Timo Raatikainen



> On 9.6.2016, at 5.38, Paul B. Henson <henson at acm.org> wrote:
> 
>> From: Josh Barton
>> Sent: Wednesday, June 08, 2016 3:17 PM
>> 
>> The hba is reporting the correct sizes for all drives, I didn't ever try
> directly
>> plugging in to the motherboard sata controller because I couldn't find a
>> molex to sata power adapter.
> 
> You could also see if anybody has a sff8087 breakout cable laying around so
> you could hook up the SATA port to the hotswap backplane :).
> 
> Did you try installing a linux distribution to see if you could get its grub
> to boot off of the 2TB drive via the SAS HBA? If that works, it would rule
> out the hard drive itself as being faulty.
> 
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From gordon.w.ross at gmail.com  Thu Jun  9 14:32:50 2016
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 9 Jun 2016 10:32:50 -0400
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <007f01d1c1f9$0d734290$2859c7b0$@acm.org>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
	<15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>
	<A858B461-EC49-43F0-9BDA-73AB95EF30B8@omniti.com>
	<007f01d1c1f9$0d734290$2859c7b0$@acm.org>
Message-ID: <CAD0Ztp3pVAaWG1=ZPPvv0G8ZnwyvOC_sJSG1mYaL0GkLnW+0_w@mail.gmail.com>

You could also tweak the krb5-config to support what this package wants.
It's just a script...

On Wed, Jun 8, 2016 at 10:45 PM, Paul B. Henson <henson at acm.org> wrote:
>> From: Dan McDonald
>> Sent: Wednesday, June 08, 2016 9:45 AM
>>
>> > extra_link_args = check_krb5_config("--libs", "gssapi")
>>
>> I wonder if it's assuming Linux commands for some things?
>
> No, it's trying to use krb5-config options available under MIT kerberos that
> don't exist under illumos kerberos. You will note the illumos variant, shown
> second, is a bit sparse 8-/. I will say for the third time and then give up,
> he should probably just install from pkgsrc :).
>
> $ krb5-config --help
> Usage: /usr/bin/krb5-config [OPTIONS] [LIBRARIES]
> Options:
>         [--help]          Help
>         [--all]           Display version, vendor, and various values
>         [--version]       Version information
>         [--vendor]        Vendor information
>         [--prefix]        Kerberos installed prefix
>         [--exec-prefix]   Kerberos installed exec_prefix
>         [--defccname]     Show built-in default ccache name
>         [--defktname]     Show built-in default keytab name
>         [--defcktname]    Show built-in default client keytab name
>         [--cflags]        Compile time CFLAGS
>         [--libs]          List libraries required to link [LIBRARIES]
> Libraries:
>         krb5              Kerberos 5 application
>         gssapi            GSSAPI application with Kerberos 5 bindings
>         gssrpc            GSSAPI RPC application
>         kadm-client       Kadmin client
>         kadm-server       Kadmin server
>         kdb               Application that accesses the kerberos database
>
>
> $ krb5-config --help
> Usage: /usr/bin/krb5-config [OPTIONS] [LIBRARIES]
> Options:
>         [--help]          Help
>         [--all]           Display version, vendor, and various values
>         [--version]       Version information
>         [--vendor]        Vendor information
>         [--prefix]        Kerberos installed prefix
>         [--exec-prefix]   Kerberos installed exec_prefix
>         [--cflags]        Compile time CFLAGS
>         [--libs]          List libraries required to link [LIBRARIES]
> Libraries:
>         krb5              Kerberos 5 application
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From gordon.w.ross at gmail.com  Thu Jun  9 14:39:13 2016
From: gordon.w.ross at gmail.com (Gordon Ross)
Date: Thu, 9 Jun 2016 10:39:13 -0400
Subject: [OmniOS-discuss] slices & zfs
In-Reply-To: <4EA37525-85AB-4689-A11D-E7124F9DE0E2@RichardElling.com>
References: <DUB402-EAS2508B3BD7D426CE4527B38BB55E0@phx.gbl>
	<3AEA6AA6-CEA9-4063-8303-368619F97E7D@cos.ru>
	<4EA37525-85AB-4689-A11D-E7124F9DE0E2@RichardElling.com>
Message-ID: <CAD0Ztp0aPSCB3s2j4jQ49yMUUknHRMaAGu28-bv5DkJ09RjT5w@mail.gmail.com>

One thing to watch out for when using slices is that you can easily
end up with a slices that are not 4KB aligned.  That doesn't matter
when the underlying device truly uses 512 byte sectors, but these days
a _lot_ of devices "lie" about that, and advertise 512 byte sectors
when in reality you pay a (possibly severe) performance penalty for
doing I/O that's not 4K aligned (or larger).
Unfortunately, the format tools and the default "fake" geometry
(cylinders, heads, sectors) typically gives you un-aligned slices.

A while back I took a stab at making format do "megabyte aligned
partitions" (which is what most OS's with slices or partitions do now)
but that work never quite made it to completion.
(It did get far enough so I could setup my dual boot SSD with aligned
partitions:)

Gordon


On Wed, Jun 8, 2016 at 1:28 PM, Richard Elling
<richard.elling at richardelling.com> wrote:
>
> On Jun 8, 2016, at 12:24 AM, Jim Klimov <jimklimov at cos.ru> wrote:
>
> 8 ???? 2016 ?. 7:00:50 CEST, Martijn Fennis <martijn at fennis.tk> ?????:
>
> Hi,
>
>
> Does someone have some info about setting up ZFS on top of slices ?
>
> Having 10 drives which i would like to have the outer ring configured @
> raid 10 for about 1 TB with dedup, the rest of the drives in Raid 50.
>
>
> What i find on google is to use complete devs and difficult to
> interpret slicing info..
>
>
>
> Thanks,
> Martijn
>
> Verzonden vanuit Mail voor Windows 10
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
> You just set up slices (with format utility on one disk, replicate setup
> with prtvtoc to others if they are identical). Then you use slice numbers as
> vdevs to zpool command. Note that slices s0 and s2 are reserved, so you have
> s1 and s3-s7 to play with. (X86 may expose s8 and s9 - also reserved).
>
>
> This is not correct. For SMI labels, s2, by convention, defaults to the
> whole disk ? aka the ?backup? partition (slice).
> Since around 1980, I know of no backup software that expects s2 to be the
> whole disk. This was also an overlapping
> slice. For modern disks and EFI labels, overlapping slices are not permitted
> ? thus preventing many common mistakes
> that led to corrupted data on the old SMI-labeled drives.
>  ? richard
>
>
>
> Also note that dedup may require some RAM and maybe a separate fast SSD to
> cache reads and writes, to be efficient. Otherwise it can bog you down below
> single mb/s of i/o.
>
> Jim
> --
> Typos courtesy of K-9 Mail on my Samsung Android
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
> --
>
> Richard.Elling at RichardElling.com
> +1-760-896-4422
>
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From Josh.Barton at usurf.usu.edu  Thu Jun  9 18:58:06 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Thu, 9 Jun 2016 18:58:06 +0000
Subject: [OmniOS-discuss] Only grub after boot
In-Reply-To: <FAD201B0-7660-4D2A-9A1F-51C5C70FF273@sourapple.fi>
References: <a0d0946c7ec64716a9f3f4637ea17c8e@Ek.usurf.usu.edu>
	<038601d1c122$79e19210$6da4b630$@acm.org>
	<4e1353b5765c44d2b48d3ce3da00102f@Ek.usurf.usu.edu>
	<98C4A43C-97AF-4E6A-A4D8-280BEF9F9737@omniti.com>
	<50F10AEA-2044-4E08-834A-85B44D31A9E3@acm.org>
	<c3cfd68235bf44569b954215f97a629b@Ek.usurf.usu.edu>
	<007401d1c1f7$ff96c990$fec45cb0$@acm.org>
	<FAD201B0-7660-4D2A-9A1F-51C5C70FF273@sourapple.fi>
Message-ID: <d8540149190e4500b172003ef36cfd4c@Ek.usurf.usu.edu>

Interesting thought, I'll bet that?s what it was but I would love to hear if anyone has a definitive answer. Thank you everyone for your help!

Josh

-----Original Message-----
From: Timo Raatikainen [mailto:timo.raatikainen at sourapple.fi] 
Sent: Thursday, June 9, 2016 2:03 AM
To: Paul B. Henson <henson at acm.org>
Cc: Josh Barton <Josh.Barton at usurf.usu.edu>; Dan McDonald <danmcd at omniti.com>; omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] Only grub after boot

Notice that the drive in question (ST2000NX0243) is a 4k native drive. I?ve never tried booting from such drive, could someone confirm if grub can handle it? I suspect that it might not.

--
Timo Raatikainen



> On 9.6.2016, at 5.38, Paul B. Henson <henson at acm.org> wrote:
> 
>> From: Josh Barton
>> Sent: Wednesday, June 08, 2016 3:17 PM
>> 
>> The hba is reporting the correct sizes for all drives, I didn't ever 
>> try
> directly
>> plugging in to the motherboard sata controller because I couldn't 
>> find a molex to sata power adapter.
> 
> You could also see if anybody has a sff8087 breakout cable laying 
> around so you could hook up the SATA port to the hotswap backplane :).
> 
> Did you try installing a linux distribution to see if you could get 
> its grub to boot off of the 2TB drive via the SAS HBA? If that works, 
> it would rule out the hard drive itself as being faulty.
> 
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From henson at acm.org  Fri Jun 10 01:44:58 2016
From: henson at acm.org (Paul B. Henson)
Date: Thu, 9 Jun 2016 18:44:58 -0700
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <CAD0Ztp3pVAaWG1=ZPPvv0G8ZnwyvOC_sJSG1mYaL0GkLnW+0_w@mail.gmail.com>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
	<15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>
	<A858B461-EC49-43F0-9BDA-73AB95EF30B8@omniti.com>
	<007f01d1c1f9$0d734290$2859c7b0$@acm.org>
	<CAD0Ztp3pVAaWG1=ZPPvv0G8ZnwyvOC_sJSG1mYaL0GkLnW+0_w@mail.gmail.com>
Message-ID: <00f401d1c2b9$b268b580$173a2080$@acm.org>

> From: Gordon Ross
> Sent: Thursday, June 09, 2016 7:33 AM
> 
> You could also tweak the krb5-config to support what this package wants.
> It's just a script...

True; but with no offense intended to the OP, if you weren't in a position to figure out that's what you needed to do when it failed, is that really going to be your easiest path forward, particularly if there are potentially other illumos vs sun kerberos quirks waiting for you down the road :)? I didn't say the only thing to do was install from pkgsrc, I'm saying the easiest thing for him to do would be install from pkgsrc...

Although somebody probably should at some point update the illumos krb5-config to match the MIT options. Is there an issue open for that yet ;)? Or should I add it to the good half-dozen that are biting at my heels like little puppies waiting to get some attention <sigh>. I still need to do that trivial smb server machine account creation delegation privilege removal one. The day job is switching to 4/10 for the summer starting next week, hopefully I can get in some extracurricular activities on Fridays.




From paladinemishakal at gmail.com  Fri Jun 10 09:45:02 2016
From: paladinemishakal at gmail.com (Lawrence Giam)
Date: Fri, 10 Jun 2016 17:45:02 +0800
Subject: [OmniOS-discuss] Znapzend installation
Message-ID: <CAGueQCfDYCUaF0-BDUzpt9EL8-mXMFtEa9R30yYeh1VJuFJmsg@mail.gmail.com>

Hi All,

I am trying to test Znapzend on OmniOS R151014 but getting errors on the
installation. This is the errors:

root at sgtestnas02:/opt/znapzend# ./configure --prefix=/opt/znapzend
--enable-svcinstall=/var/svc/manifest/site
checking in to see how you are doing... keep fighting man!
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... conftools/install-sh -c -d
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... (cached) yes
checking for perl... /usr/bin/perl
checking for curl... /usr/bin/curl
checking for wget... /usr/bin/wget
checking for pod2man... no
checking for perl version greater than or equal to 5.10.1... ok
checking is perl reasonably complete... yes. ExtUtils::MakeMaker is
available
checking if require a c compiler to get perl modules compiled... yes
checking for gcc... /usr/bin/gcc
checking is perls favorite c compiler (gcc) available... yes
checking for grep that handles long lines and -e... /usr/bin/ggrep
checking for gnumake... no
checking for gmake... /usr/bin/gmake
checking for gnu make availablility... /usr/bin/gmake is GNU make
checking the price for bergulian eckels... way to expensive!
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating thirdparty/Makefile
config.status: creating lib/Makefile
config.status: creating init/znapzend.xml
config.status: WARNING:  'init/znapzend.xml.in' seems to ignore the
--datarootdir setting

** CONFIGURE DONE **********************************************

Settings:

  PERL5LIB = not set
  PERL = /usr/bin/perl
  SVCINSTALLDIR = /var/svc/manifest/site

The Makefiles use GNU make functionality.
Continue installation with

  /usr/bin/gmake install

root at sgtestnas02:/opt/znapzend# /usr/bin/gmake install
Making install in thirdparty
gmake[1]: Entering directory `/opt/znapzend-0.15.7/thirdparty'
  GEN      touch
Successfully installed IO-Socket-IP-0.37
Successfully installed Mojolicious-6.46
Successfully installed Scalar-List-Utils-1.45 (upgraded from 1.25)
Successfully installed Exporter-5.72 (upgraded from 5.66)
Successfully installed IO-Pipely-0.005
Successfully installed Mojo-IOLoop-ForkCall-0.17
Successfully installed Test-Harness-3.36 (upgraded from 3.23)
7 distributions installed
  GEN      touch
gmake[2]: Entering directory `/opt/znapzend-0.15.7/thirdparty'
gmake[2]: Nothing to be done for `install-exec-am'.
gmake[2]: Nothing to be done for `install-data-am'.
gmake[2]: Leaving directory `/opt/znapzend-0.15.7/thirdparty'
gmake[1]: Leaving directory `/opt/znapzend-0.15.7/thirdparty'
Making install in lib
gmake[1]: Entering directory `/opt/znapzend-0.15.7/lib'
gmake[2]: Entering directory `/opt/znapzend-0.15.7/lib'
gmake[2]: Nothing to be done for `install-exec-am'.
 ../conftools/install-sh -c -d '/opt/znapzend/lib'
 /usr/bin/install -c -m 644  ./ZnapZend.pm '/opt/znapzend/lib/.'
/usr/bin/install: './ZnapZend.pm' and '/opt/znapzend/lib/./ZnapZend.pm' are
the same file
gmake[2]: *** [install-nobase_dataDATA] Error 1
gmake[2]: Leaving directory `/opt/znapzend-0.15.7/lib'
gmake[1]: *** [install-am] Error 2
gmake[1]: Leaving directory `/opt/znapzend-0.15.7/lib'
gmake: *** [install-recursive] Error 1
root at sgtestnas02:/opt/znapzend#

Don't know what is missing, any help here?

Thanks & Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160610/d947bdfd/attachment.html>

From gordon at hafnia.dk  Fri Jun 10 11:06:56 2016
From: gordon at hafnia.dk (Gordon Selisek)
Date: Fri, 10 Jun 2016 13:06:56 +0200
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <00f401d1c2b9$b268b580$173a2080$@acm.org>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>
	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>
	<15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>
	<A858B461-EC49-43F0-9BDA-73AB95EF30B8@omniti.com>
	<007f01d1c1f9$0d734290$2859c7b0$@acm.org>
	<CAD0Ztp3pVAaWG1=ZPPvv0G8ZnwyvOC_sJSG1mYaL0GkLnW+0_w@mail.gmail.com>
	<00f401d1c2b9$b268b580$173a2080$@acm.org>
Message-ID: <15539fe52e0.da36a3b2230616.8840377854667818972@hafnia.dk>

Paul,



I'd have to say you are right, I might be able to tweak the script without too much effort, but what is laying ahead? 



I really have an affinity for illumos, I would be sad to drop it for this particular project, and go with centos, which would take me to the finish line quicker.


Anyway, thank you all for your qualified inputs.



Cordial regards

Gordon




---- On Fri, 10 Jun 2016 03:44:58 +0200 Paul B. Henson &lt;henson at acm.org&gt;wrote ---- 




&gt; From: Gordon Ross 

&gt; Sent: Thursday, June 09, 2016 7:33 AM 

&gt; 

&gt; You could also tweak the krb5-config to support what this package wants. 

&gt; It's just a script... 

 

True; but with no offense intended to the OP, if you weren't in a position to figure out that's what you needed to do when it failed, is that really going to be your easiest path forward, particularly if there are potentially other illumos vs sun kerberos quirks waiting for you down the road :)? I didn't say the only thing to do was install from pkgsrc, I'm saying the easiest thing for him to do would be install from pkgsrc... 

 

Although somebody probably should at some point update the illumos krb5-config to match the MIT options. Is there an issue open for that yet ;)? Or should I add it to the good half-dozen that are biting at my heels like little puppies waiting to get some attention &lt;sigh&gt;. I still need to do that trivial smb server machine account creation delegation privilege removal one. The day job is switching to 4/10 for the summer starting next week, hopefully I can get in some extracurricular activities on Fridays. 

 

 

 

_______________________________________________ 

OmniOS-discuss mailing list 

OmniOS-discuss at lists.omniti.com 

http://lists.omniti.com/mailman/listinfo/omnios-discuss 






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160610/7d24cd5e/attachment.html>

From tobi at oetiker.ch  Fri Jun 10 11:37:00 2016
From: tobi at oetiker.ch (Tobias Oetiker)
Date: Fri, 10 Jun 2016 13:37:00 +0200 (CEST)
Subject: [OmniOS-discuss] Znapzend installation
In-Reply-To: <CAGueQCfDYCUaF0-BDUzpt9EL8-mXMFtEa9R30yYeh1VJuFJmsg@mail.gmail.com>
References: <CAGueQCfDYCUaF0-BDUzpt9EL8-mXMFtEa9R30yYeh1VJuFJmsg@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1606101335530.15761@engelberg.oetiker.ch>

Hi Lawrence,

if you install something from source, NEVER unpack the source in
the installation directory ...

unpack in /scratch or /tmp ... install to /opt/package-version

cheers
tobi

Today Lawrence Giam wrote:

> Hi All,
>
> I am trying to test Znapzend on OmniOS R151014 but getting errors on the
> installation. This is the errors:
>
> root at sgtestnas02:/opt/znapzend# ./configure --prefix=/opt/znapzend
> --enable-svcinstall=/var/svc/manifest/site
> checking in to see how you are doing... keep fighting man!
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... conftools/install-sh -c -d
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking whether make supports nested variables... (cached) yes
> checking for perl... /usr/bin/perl
> checking for curl... /usr/bin/curl
> checking for wget... /usr/bin/wget
> checking for pod2man... no
> checking for perl version greater than or equal to 5.10.1... ok
> checking is perl reasonably complete... yes. ExtUtils::MakeMaker is
> available
> checking if require a c compiler to get perl modules compiled... yes
> checking for gcc... /usr/bin/gcc
> checking is perls favorite c compiler (gcc) available... yes
> checking for grep that handles long lines and -e... /usr/bin/ggrep
> checking for gnumake... no
> checking for gmake... /usr/bin/gmake
> checking for gnu make availablility... /usr/bin/gmake is GNU make
> checking the price for bergulian eckels... way to expensive!
> checking that generated files are newer than configure... done
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating thirdparty/Makefile
> config.status: creating lib/Makefile
> config.status: creating init/znapzend.xml
> config.status: WARNING:  'init/znapzend.xml.in' seems to ignore the
> --datarootdir setting
>
> ** CONFIGURE DONE **********************************************
>
> Settings:
>
>   PERL5LIB = not set
>   PERL = /usr/bin/perl
>   SVCINSTALLDIR = /var/svc/manifest/site
>
> The Makefiles use GNU make functionality.
> Continue installation with
>
>   /usr/bin/gmake install
>
> root at sgtestnas02:/opt/znapzend# /usr/bin/gmake install
> Making install in thirdparty
> gmake[1]: Entering directory `/opt/znapzend-0.15.7/thirdparty'
>   GEN      touch
> Successfully installed IO-Socket-IP-0.37
> Successfully installed Mojolicious-6.46
> Successfully installed Scalar-List-Utils-1.45 (upgraded from 1.25)
> Successfully installed Exporter-5.72 (upgraded from 5.66)
> Successfully installed IO-Pipely-0.005
> Successfully installed Mojo-IOLoop-ForkCall-0.17
> Successfully installed Test-Harness-3.36 (upgraded from 3.23)
> 7 distributions installed
>   GEN      touch
> gmake[2]: Entering directory `/opt/znapzend-0.15.7/thirdparty'
> gmake[2]: Nothing to be done for `install-exec-am'.
> gmake[2]: Nothing to be done for `install-data-am'.
> gmake[2]: Leaving directory `/opt/znapzend-0.15.7/thirdparty'
> gmake[1]: Leaving directory `/opt/znapzend-0.15.7/thirdparty'
> Making install in lib
> gmake[1]: Entering directory `/opt/znapzend-0.15.7/lib'
> gmake[2]: Entering directory `/opt/znapzend-0.15.7/lib'
> gmake[2]: Nothing to be done for `install-exec-am'.
>  ../conftools/install-sh -c -d '/opt/znapzend/lib'
>  /usr/bin/install -c -m 644  ./ZnapZend.pm '/opt/znapzend/lib/.'
> /usr/bin/install: './ZnapZend.pm' and '/opt/znapzend/lib/./ZnapZend.pm' are
> the same file
> gmake[2]: *** [install-nobase_dataDATA] Error 1
> gmake[2]: Leaving directory `/opt/znapzend-0.15.7/lib'
> gmake[1]: *** [install-am] Error 2
> gmake[1]: Leaving directory `/opt/znapzend-0.15.7/lib'
> gmake: *** [install-recursive] Error 1
> root at sgtestnas02:/opt/znapzend#
>
> Don't know what is missing, any help here?
>
> Thanks & Regards.
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch tobi at oetiker.ch +41 62 775 9902


From henson at acm.org  Fri Jun 10 20:03:34 2016
From: henson at acm.org (Paul B. Henson)
Date: Fri, 10 Jun 2016 13:03:34 -0700
Subject: [OmniOS-discuss] Python and Kerberos libraries
In-Reply-To: <15539fe52e0.da36a3b2230616.8840377854667818972@hafnia.dk>
References: <1552c813e8f.c52e436c47473.4783516383124801807@hafnia.dk>	<7D083281-ABF2-4B46-885D-D4AC5A36EACF@omniti.com>	<15530c14fa3.d4aa7bc7108413.719671338269014121@hafnia.dk>	<A858B461-EC49-43F0-9BDA-73AB95EF30B8@omniti.com>	<007f01d1c1f9$0d734290$2859c7b0$@acm.org>	<CAD0Ztp3pVAaWG1=ZPPvv0G8ZnwyvOC_sJSG1mYaL0GkLnW+0_w@mail.gmail.com>	<00f401d1c2b9$b268b580$173a2080$@acm.org>
	<15539fe52e0.da36a3b2230616.8840377854667818972@hafnia.dk>
Message-ID: <006c01d1c353$2b57c7d0$82075770$@acm.org>

> From: Gordon Selisek
> Sent: Friday, June 10, 2016 4:07 AM
> 
> I'd have to say you are right, I might be able to tweak the script without too
> much effort, but what is laying ahead?
>
> I really have an affinity for illumos, I would be sad to drop it for this particular
> project, and go with centos, which would take me to the finish line quicker.

I'm certainly not suggesting you should abandon omnios :(. Feel free to tweak the script, and if you run into another problem, bring it back to the list. Or just install standard MIT Kerberos from pkgsrc. If you put that krb5-config first in your path, Python will find and use it and should work fine.


From ergi.thanasko at avsquad.com  Fri Jun 10 20:26:50 2016
From: ergi.thanasko at avsquad.com (Ergi Thanasko)
Date: Fri, 10 Jun 2016 20:26:50 +0000
Subject: [OmniOS-discuss] CLSET_NODELAYONERR
Message-ID: <2D6C5E2C-8972-4F49-BE46-DF37191E0244@avsquad.com>


Hi Dan,
We had a crash yesterday in our server, no hardware issue just the O/S become i responsive, not even ping. 
We restarted the unit and everything came back online, check the logs below. We have a lot of CLSET_NODELAYERR. When i googled the error Dan?s name came  up and though i would ping you.
This unit has been running for a year, no config changes or software upgrades  were made lately. Please let me know if you have any additional information  

8 15:23:09 SV02 last message repeated 3 times
Jun  8 15:37:24 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  8 15:37:24 SV02 last message repeated 1 time
Jun  8 16:25:12 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  8 16:25:12 SV02 last message repeated 1 time
Jun  8 17:46:24 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  8 17:46:24 SV02 last message repeated 1 time
Jun  8 18:08:00 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  8 18:11:15 SV02 last message repeated 2 times
Jun  9 11:44:21 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 11:44:21 SV02 last message repeated 1 time
Jun  9 11:57:35 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 11:59:25 SV02 last message repeated 3 times
Jun  9 12:25:13 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 12:25:13 SV02 last message repeated 1 time
Jun  9 12:35:21 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 12:35:21 SV02 last message repeated 1 time
Jun  9 13:54:55 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 13:54:55 SV02 last message repeated 1 time
Jun  9 14:10:50 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 14:10:50 SV02 last message repeated 1 time
Jun  9 14:29:45 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 14:29:45 SV02 last message repeated 1 time
Jun  9 14:32:45 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 14:43:43 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 14:56:57 SV02 last message repeated 3 times
Jun  9 14:57:09 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 14:59:28 SV02 last message repeated 1 time
Jun  9 15:26:34 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 15:26:34 SV02 last message repeated 1 time
Jun  9 15:36:04 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 15:51:50 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 15:51:50 SV02 last message repeated 1 time
Jun  9 16:15:21 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 16:15:21 SV02 last message repeated 1 time
Jun  9 17:17:53 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 17:17:53 SV02 last message repeated 1 time
Jun  9 17:44:52 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 18:28:14 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
Jun  9 19:51:43 SV02 genunix: [ID 598308 kern.notice] ^MOpen Drives Build  opus-oi_151_a9_2457044 64-bit (illumos)
Jun  9 19:51:43 SV02 genunix: [ID 107366 kern.notice] SunOS Release 5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
Jun  9 19:51:43 SV02 genunix: [ID 864463 kern.notice] All rights reserved. Use is subject to license terms.
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: lgpg
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: tsc
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: msr
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: mtrr
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: pge
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: de
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: cmov
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: mmx
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: mca
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: pae
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: cv8
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: pat
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: sep
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: sse
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: sse2
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: htt
Jun  9 19:51:43 SV02 genunix: [ID 223955 kern.info] x86_feature: asysc

last log 18:28:14NOTICE: Unable to set CLSET_NODELAYONERR


From danmcd at omniti.com  Fri Jun 10 20:32:00 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Fri, 10 Jun 2016 16:32:00 -0400
Subject: [OmniOS-discuss] CLSET_NODELAYONERR
In-Reply-To: <2D6C5E2C-8972-4F49-BE46-DF37191E0244@avsquad.com>
References: <2D6C5E2C-8972-4F49-BE46-DF37191E0244@avsquad.com>
Message-ID: <E69F686B-8B4F-4E31-9D7D-887CD7C1FB30@omniti.com>


> Jun  9 18:28:14 SV02 genunix: [ID 497209 kern.notice] NOTICE: Unable to set CLSET_NODELAYONERR
> Jun  9 19:51:43 SV02 genunix: [ID 598308 kern.notice] ^MOpen Drives Build  opus-oi_151_a9_2457044 64-bit (illumos)
> Jun  9 19:51:43 SV02 genunix: [ID 107366 kern.notice] SunOS Release 5.11 - Copyright 1983-2010 Oracle and/or its affiliates.
> Jun  9 19:51:43 SV02 genunix: [ID 864463 kern.notice] All rights reserved. Use is subject to license terms.

1.) CLSET_NODELAYONERR is a nfs lock manager diagnostic.  It's either too chatty (I see this all the time w/o a hang or crash) or there's something that still needs fixing in the NLM.

2.) No other suspicious messages.

3.) You're running OpenIndiana, not OmniOS.

4.) "crash" means kernel panic.  "hang" means unresponsive.  For future reference.

Sorry I can't be of more help,
Dan


From grzempek at gmail.com  Sun Jun 12 09:35:39 2016
From: grzempek at gmail.com (Krzysztof Grzempa)
Date: Sun, 12 Jun 2016 11:35:39 +0200
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
Message-ID: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>

Cheers guys,

I'm planning to build my own server at home for multiple purposes (my
projects, home NAS etc). I'm planning to use zones to separate WAN access
server (www hosting, git and svn repos, email maybe..) and SAN
functionalities for LAN only access.
Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11, and i
really enjoy it. I wish to use ZFS as the best storage solution, but what
concern me most is availability of technologies that i'm going to use. For
WAN purposes I need apache2, php5, mariadb, python (at least 2.7),git, svn,
and maybe fish shell ;) . For my NAS, I need samba, nfs, ftp, DLNA
[mediatomb, serviio] (sharing video to TV directly).
AFAIK and read on the net, probably every of those technologies are doable
on OmniOS, but the problem is time spent on installing, solving problems
etc.
Of course, there is always the linux solution, but i would like not go
there as Illumos has may better storage (ZFS on linux sucks IHMO)
Has anyone got expierience in setting up such stack on OmniOS? (or any
other Illumos distro?) Problems? Advices?

thanks,
Kris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160612/32899328/attachment.html>

From doug at will.to  Sun Jun 12 13:36:46 2016
From: doug at will.to (Doug Hughes)
Date: Sun, 12 Jun 2016 09:36:46 -0400
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <CAOpmc6wDFBL4560TMf2BcwaZbz6iQcdtVWQNaFeGgvrpBmanqA@mail.gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<CAOpmc6ymDPmbop8oGpQMQin5Ux_L3HpLYeBSg2=wGX-hanfMDw@mail.gmail.com>
	<CAOpmc6xcGEXeLQqakKeVEFRV8Q0nOtbbMuQktBTV+tiM+c+WdQ@mail.gmail.com>
	<CAOpmc6zjjfcnEvBceBScebaq2ahXozqfPPWOm1N059ifUcSBzQ@mail.gmail.com>
	<CAOpmc6wDFBL4560TMf2BcwaZbz6iQcdtVWQNaFeGgvrpBmanqA@mail.gmail.com>
Message-ID: <CAOpmc6xP_GZaE2x50B22A1gLv=fp73YxeZQhE23Cv_3A=QL5sA@mail.gmail.com>

I have not tried dlna or fish shell, but the rest are either integrated or
just a package install away. I have a web server with Marian, NFS, and
samba where I store axis camera videos. The one that took the most fiddling
was samba because the integrated samba is a bit different than standard
samba offerings and documentation is spotty, but it works. (Had to use a
little bit of snoop)
On Jun 12, 2016 5:50 AM, "Krzysztof Grzempa" <grzempek at gmail.com> wrote:

Cheers guys,

I'm planning to build my own server at home for multiple purposes (my
projects, home NAS etc). I'm planning to use zones to separate WAN access
server (www hosting, git and svn repos, email maybe..) and SAN
functionalities for LAN only access.
Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11, and i
really enjoy it. I wish to use ZFS as the best storage solution, but what
concern me most is availability of technologies that i'm going to use. For
WAN purposes I need apache2, php5, mariadb, python (at least 2.7),git, svn,
and maybe fish shell ;) . For my NAS, I need samba, nfs, ftp, DLNA
[mediatomb, serviio] (sharing video to TV directly).
AFAIK and read on the net, probably every of those technologies are doable
on OmniOS, but the problem is time spent on installing, solving problems
etc.
Of course, there is always the linux solution, but i would like not go
there as Illumos has may better storage (ZFS on linux sucks IHMO)
Has anyone got expierience in setting up such stack on OmniOS? (or any
other Illumos distro?) Problems? Advices?

thanks,
Kris

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160612/25f73eba/attachment.html>

From danmcd at omniti.com  Sun Jun 12 16:41:10 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Sun, 12 Jun 2016 12:41:10 -0400
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
Message-ID: <1585B8E6-52C5-437B-8F2E-0E9C391956D6@omniti.com>

See here for starters:

http://kebesays.blogspot.com/2014/06/home-data-center-20-dogfooding-again.html?m=1

I use NFS for my home filing because I'm a Mac household.  I use the built-in SMB for a destination drop for my network scanner/printer.

The biggest weakness I feel my setup has is ipfilter, because it's old, has some NAT bugs that nobody's had cycles to debug and fix.

Your app set is a bit more than mine. You can run Linux as a KVM on OmniOS, but HOPEFULLY in the next year LX zones will become an alternative.

I've recently added a Python-based caldav server that, modulo Python flaws that I can work around using a cron job, pstack(1), and SMF, works well.

Hope this helps, (and pardon the top post)
Dan

Sent from my iPhone (typos, autocorrect, and all)

> On Jun 12, 2016, at 5:35 AM, Krzysztof Grzempa <grzempek at gmail.com> wrote:
> 
> Cheers guys,
> 
> I'm planning to build my own server at home for multiple purposes (my projects, home NAS etc). I'm planning to use zones to separate WAN access server (www hosting, git and svn repos, email maybe..) and SAN functionalities for LAN only access.
> Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11, and i really enjoy it. I wish to use ZFS as the best storage solution, but what concern me most is availability of technologies that i'm going to use. For WAN purposes I need apache2, php5, mariadb, python (at least 2.7),git, svn, and maybe fish shell ;) . For my NAS, I need samba, nfs, ftp, DLNA [mediatomb, serviio] (sharing video to TV directly).
> AFAIK and read on the net, probably every of those technologies are doable on OmniOS, but the problem is time spent on installing, solving problems etc.
> Of course, there is always the linux solution, but i would like not go there as Illumos has may better storage (ZFS on linux sucks IHMO)
> Has anyone got expierience in setting up such stack on OmniOS? (or any other Illumos distro?) Problems? Advices?
> 
> thanks,
> Kris
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

From natxo.asenjo at gmail.com  Sun Jun 12 18:16:18 2016
From: natxo.asenjo at gmail.com (Natxo Asenjo)
Date: Sun, 12 Jun 2016 20:16:18 +0200
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
Message-ID: <CAHBEJzWNvmTshzhoAXL+-+XXbtJSoir5hgAzv9mnXWYVU-uKUw@mail.gmail.com>

hi Krzysztof,

On Sun, Jun 12, 2016 at 11:35 AM, Krzysztof Grzempa <grzempek at gmail.com>
wrote:

> Cheers guys,
>
> I'm planning to build my own server at home for multiple purposes (my
> projects, home NAS etc). I'm planning to use zones to separate WAN access
> server (www hosting, git and svn repos, email maybe..) and SAN
> functionalities for LAN only access.
> Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11, and i
> really enjoy it. I wish to use ZFS as the best storage solution, but what
> concern me most is availability of technologies that i'm going to use. For
> WAN purposes I need apache2, php5, mariadb, python (at least 2.7),git, svn,
> and maybe fish shell ;) . For my NAS, I need samba, nfs, ftp, DLNA
> [mediatomb, serviio] (sharing video to TV directly).
> AFAIK and read on the net, probably every of those technologies are doable
> on OmniOS, but the problem is time spent on installing, solving problems
> etc.
> Of course, there is always the linux solution, but i would like not go
> there as Illumos has may better storage (ZFS on linux sucks IHMO)
> Has anyone got expierience in setting up such stack on OmniOS? (or any
> other Illumos distro?) Problems? Advices?
>
>

 I run a microserver at home that does NFS/cifs, dlna (serviio in the past,
pldna now), I use crashplan for backups to the cloud. I use it for testing
stuff in zones a lot as well with the stacks you mention and others. I
don't use samba, the cifs server is very reliable and easy to use, and now
we have smb2 in it. I don't use ftp either, so I cannot comment on that,
although I vaguely remember talk about removing it because it was removed
from illumos.

The only thing I cannot do is kvm because that is not available for amd
cpus, but that is not really a big deal. I got a nuc from work to use it as
hypervisor (esx/kvm) and use the omnios box as storage datastore for the
vms. Works great too.

Not much to say, it works very well, updates/upgrades are easy and work. An
omnios box is a great home server. But if you are not willing to spend some
time learning how things work in solaris/illumos then maybe the linux
solution is better suited for you. It is a different system after all, lots
of things are similar but others differ.

HTH,

--
Groeten,
natxo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160612/6f11fbec/attachment.html>

From bfriesen at simple.dallas.tx.us  Sun Jun 12 20:07:22 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Sun, 12 Jun 2016 15:07:22 -0500 (CDT)
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <CAHBEJzWNvmTshzhoAXL+-+XXbtJSoir5hgAzv9mnXWYVU-uKUw@mail.gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<CAHBEJzWNvmTshzhoAXL+-+XXbtJSoir5hgAzv9mnXWYVU-uKUw@mail.gmail.com>
Message-ID: <alpine.GSO.2.20.1606121458590.29536@freddy.simplesystems.org>

On Sun, 12 Jun 2016, Natxo Asenjo wrote:
> we have smb2 in it. I don't use ftp either, so I cannot comment on that,
> although I vaguely remember talk about removing it because it was removed
> from illumos.

I am using proftpd compiled from sources and it works good for 
anonymous ftp.

I am also using dovecot plus sieve extension for a local IMAP4 server. 
The key to compiling a working dovecot was to use the configure option 
--with-ioloop=poll or else an incomplete Linux emulation API is 
selected which does not work with chroot().

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

From whorfin at gmail.com  Sun Jun 12 23:01:04 2016
From: whorfin at gmail.com (Rick Sayre)
Date: Sun, 12 Jun 2016 16:01:04 -0700
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on r151014
	or r151018
Message-ID: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>

Greetings

Since r151018 is more recent let's consider this a report for that 
version, though I encountered it first on r151014

Upon issuing the recommended command to switch:
https://omnios.omniti.com/wiki.php/ReleaseNotes/r151018
     /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh 
--reject pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh 
--reject pkg:/service/network/ssh-common pkg:/network/openssh 
pkg:/network/openssh-server

I got the error:
     The Boot Environment OmniOS-r151018 failed to be updated. A 
snapshot was taken before the failed attempt and is mounted here 
/tmp/tmpSE7Agh. Use 'beadm unmount OmniOS-r151018-2' and then 'beadm 
activate OmniOS-r151018-2' if you wish to boot to this BE.

     pkg: Requested operation failed for package 
pkg://omnios/network/openssh-server at 7.2.2,5.11-0.151018:20160412T154009Z:
     User cannot be installed without user database files present.

...and then beadm is left in the slightly weird state

Google wasn't much help here.
Ultimately, after some sleuthing, I determined the problem to be
somewhere deep within a call to the "user" module of pkg, from
the package requirement:
     user ftpuser=false gcos-field="OpenSSH privsep user" group=sshd 
home-dir=/var/empty login-shell=/bin/false password=NP uid=92 username=sshd

This in turn was attempting to add an entry to
/etc/ftpd/ftpusers

Because of the move away from ftpd [i've switched to proftpd] w/
OmniOS, I was left with no /etc/ftpd directory.  Apparently this is
met with great hostility by user.py...

Manually creating an empty ftpusers in /etc/ftpd allowed the install
to succeed.

"leaving this here" so that others may find and benefit, and perhaps
the pkg rule will be cleaned up for OmniOS, now that ftpd isn't
there...

Cheers
         --Rick

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160612/931339ff/attachment.html>

From guorong.koh at gmail.com  Mon Jun 13 03:04:17 2016
From: guorong.koh at gmail.com (Guo-Rong Koh)
Date: Mon, 13 Jun 2016 12:34:17 +0930
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
Message-ID: <1465787057.17797.11.camel@gmail.com>

On Sun, 2016-06-12 at 11:35 +0200, Krzysztof Grzempa wrote:
> Cheers guys,
> 
> I'm planning to build my own server at home for multiple purposes (my
> projects, home NAS etc). I'm planning to use zones to separate WAN
> access server (www hosting, git and svn repos, email maybe..) and SAN
> functionalities for LAN only access.
> Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11,
> and i really enjoy it. I wish to use ZFS as the best storage
> solution, but what concern me most is availability of technologies
> that i'm going to use. For WAN purposes I need apache2, php5,
> mariadb, python (at least 2.7),git, svn, and maybe fish shell ;) .
> For my NAS, I need samba, nfs, ftp, DLNA [mediatomb, serviio]
> (sharing video to TV directly).
> AFAIK and read on the net, probably every of those technologies are
> doable on OmniOS, but the problem is time spent on installing,
> solving problems etc.
> Of course, there is always the linux solution, but i would like not
> go there as Illumos has may better storage (ZFS on linux sucks IHMO)
> Has anyone got expierience in setting up such stack on OmniOS? (or
> any other Illumos distro?) Problems? Advices?
> 
I run most of my WAN stack (apache, php, etc) from the Joyent pkgsrc
repository, which is very straightforward to get running and keep
updated on OmniOS.
For DLNA I used to run mediatomb from a self-compiled instance, but
have since swapped over to NFS shares, relying on a more capable media
player (OpenElec).
I also run a Linux KVM instance for the stuff that is "just too
difficult" (eg. crashplan, grafana3, etc).
regards,
Guo-Rong
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160613/582e8ba9/attachment.html>

From danmcd at omniti.com  Mon Jun 13 14:29:41 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 13 Jun 2016 10:29:41 -0400
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
	r151014 or r151018
In-Reply-To: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
Message-ID: <F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>


> On Jun 12, 2016, at 7:01 PM, Rick Sayre <whorfin at gmail.com> wrote:
> 
> "leaving this here" so that others may find and benefit, and perhaps 
> the pkg rule will be cleaned up for OmniOS, now that ftpd isn't 
> there... 

It's currently a documented interface in pkg(5).  And I quote from the man page:

   User Actions
       The user action defines a UNIX user as defined in /etc/passwd,
       /etc/shadow, /etc/group, and /etc/ftpd/ftpusers files. Entries are
       added to the appropriate files for users defined with this user action.

       The user action is intended to define a user for a daemon or other
       software to use. Do not use the user action to define administrative or
       interactive accounts.

And weirder still, in spite of removing any default FTP server, the /etc/ftpd directory is part of the basic packages:

	bloody(~)[0]% pkg search /etc/ftpd
	INDEX      ACTION VALUE    PACKAGE
	path       dir    etc/ftpd pkg:/SUNWcs at 0.5.11-0.151019
	bloody(~)[0]% 

I'm not sure what action uninstalled /etc/ftpd on your system, but that action is broken.  If it's a package in the "omnios" publisher, it's a bug for me to fix.  I doubt that's the case, however:

bloody(~)[0]% find ws/omnios-build/build -type f | xargs grep -l ftpd | grep -v build.log
bloody(~)[1]% 

I'm sorry about your pain.  The /etc/ftpd directory is a system-specified one, and it shouldn't be erased.

Dan


From vab at bb-c.de  Mon Jun 13 15:46:37 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Mon, 13 Jun 2016 17:46:37 +0200
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH
	on	r151014 or r151018
In-Reply-To: <F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
Message-ID: <22366.54621.935438.11693@shelob.bb-c.de>

> > "leaving this here" so that others may find and benefit, and perhaps
> > the pkg rule will be cleaned up for OmniOS, now that ftpd isn't
> > there...
>
> It's currently a documented interface in pkg(5).  And I quote from the man page:
>
>    User Actions
>        The user action defines a UNIX user as defined in /etc/passwd,
>        /etc/shadow, /etc/group, and /etc/ftpd/ftpusers files. Entries are
>        added to the appropriate files for users defined with this user action.
>
>        The user action is intended to define a user for a daemon or other
>        software to use. Do not use the user action to define administrative or
>        interactive accounts.
>
> And weirder still, in spite of removing any default FTP server, the
> /etc/ftpd directory is part of the basic packages:

I think the OPs problem was that the file ftpusers had vanished.
In Solaris 11.x, both the file /etc/ftpd/ftpusers and the symlink
pointing to it (/etc/ftpusers) are packaged in system/core-os.

The underlying issue is that in the IPS source file

  /usr/lib/python2.6/vendor-packages/pkg/actions/user/.py

th?ngs like

        def install(self, pkgplan, orig, retry=False):
                """client-side method that adds the user...
                   update any attrs that changed from orig
                   unless the on-disk stuff was changed"""
[...]
                        pw.writefile()
                        gr.writefile()
                        ftp.writefile()
                except EnvironmentError, e:
                        if e.errno != errno.ENOENT:
                                raise
                        # If we're in the postinstall phase and the files
                        # *still* aren't there, bail gracefully.
                        if retry:
                                txt = _("User cannot be installed without user "
                                    "database files present.")
                                raise apx.ActionExecutionError(self, error=e,
                                    details=txt, fmri=pkgplan.destination_fmri)

are hardcoded.  To avoid the problem here, the attempt to write to
/etc/ftpd/ftpusers should only be made if the file actually exists.


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 eric.sproul at circonus.com  Mon Jun 13 17:00:11 2016
From: eric.sproul at circonus.com (Eric Sproul)
Date: Mon, 13 Jun 2016 13:00:11 -0400
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
 r151014 or r151018
In-Reply-To: <22366.54621.935438.11693@shelob.bb-c.de>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
Message-ID: <CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>

On Mon, Jun 13, 2016 at 11:46 AM, Volker A. Brandt <vab at bb-c.de> wrote:
> are hardcoded.  To avoid the problem here, the attempt to write to
> /etc/ftpd/ftpusers should only be made if the file actually exists.

But /etc/ftpd/ftpusers is provided by pkg:/SUNWcs, so if it doesn't
exist, the system is broken.  There is no expected case where this
file is missing.

Eric

From Josh.Barton at usurf.usu.edu  Mon Jun 13 17:20:15 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Mon, 13 Jun 2016 17:20:15 +0000
Subject: [OmniOS-discuss] CD Mounting
Message-ID: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>

How do I find the right device to mount a cd, I have found that working with hardware like CD/USB drives  isn't well documented in the case of OmniOS. Or perhaps I simply don't know the right place to go.
I appreciate any suggestions. Thanks!

Josh Barton
USU Research Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160613/63b5432a/attachment.html>

From vab at bb-c.de  Mon Jun 13 17:23:03 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Mon, 13 Jun 2016 19:23:03 +0200
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
 r151014 or r151018
In-Reply-To: <CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
	<CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
Message-ID: <22366.60407.567814.988317@shelob.bb-c.de>

> But /etc/ftpd/ftpusers is provided by pkg:/SUNWcs, so if it doesn't
> exist, the system is broken.  There is no expected case where this
> file is missing.

So the OPs system is indeed broken.  The question is: What broke it?
Was it a pkg invocation?

BTW my 151016 system has the file, and SUNWcs is properly installed,
but "pkg search /etc/ftpd" or "pkg search /etc/ftpd/ftpusers" do not
show any output, even after a "pkg rebuild-index".  Strange.


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 bfriesen at simple.dallas.tx.us  Mon Jun 13 17:32:36 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Mon, 13 Jun 2016 12:32:36 -0500 (CDT)
Subject: [OmniOS-discuss] CD Mounting
In-Reply-To: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
References: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
Message-ID: <alpine.GSO.2.20.1606131231470.735@freddy.simplesystems.org>

On Mon, 13 Jun 2016, Josh Barton wrote:

> How do I find the right device to mount a cd, I have found that working with hardware like CD/USB drives  isn't well documented in the case of OmniOS. Or perhaps I simply don't know the right place to go.
> I appreciate any suggestions. Thanks!

I would have said 'rmformat -l' but I am not seeing that rmformat is 
installed on my OmniOS system.

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

From eric.sproul at circonus.com  Mon Jun 13 17:35:40 2016
From: eric.sproul at circonus.com (Eric Sproul)
Date: Mon, 13 Jun 2016 13:35:40 -0400
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
 r151014 or r151018
In-Reply-To: <22366.60407.567814.988317@shelob.bb-c.de>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
	<CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
	<22366.60407.567814.988317@shelob.bb-c.de>
Message-ID: <CAO8hXRDHNfEux_=WWT2gqBb_QrAEFGmd5mrF9i2bD55zNtv66A@mail.gmail.com>

On Mon, Jun 13, 2016 at 1:23 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> BTW my 151016 system has the file, and SUNWcs is properly installed,
> but "pkg search /etc/ftpd" or "pkg search /etc/ftpd/ftpusers" do not
> show any output, even after a "pkg rebuild-index".  Strange.

Paths are relative because packages are relocatable, so I usually
search for a basename if it's relatively unambiguous.  `pkg search
ftpusers` should work, and return both a file and a softlink.  Note
that "basename" is a virtual attribute that doesn't actually appear in
the pkg manifest, but is synthesized by the client, based on the last
element of the path value.

This is on my 014 install:

$ pkg search ftpusers
INDEX      ACTION VALUE             PACKAGE
basename   file   etc/ftpd/ftpusers pkg:/SUNWcs at 0.5.11-0.151014
basename   link   etc/ftpusers      pkg:/SUNWcs at 0.5.11-0.151014

Using the full set of search fields also works, though I've never
understood why I need the '*' at the beginning of the path value:

$ pkg search 'file:path:*etc/ftpd/ftpusers'
INDEX      ACTION VALUE             PACKAGE
path       file   etc/ftpd/ftpusers pkg:/SUNWcs at 0.5.11-0.151014

Eric

From alexander.r.eremin at gmail.com  Mon Jun 13 17:54:26 2016
From: alexander.r.eremin at gmail.com (Alexander)
Date: Mon, 13 Jun 2016 20:54:26 +0300
Subject: [OmniOS-discuss] CD Mounting
In-Reply-To: <alpine.GSO.2.20.1606131231470.735@freddy.simplesystems.org>
References: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
	<alpine.GSO.2.20.1606131231470.735@freddy.simplesystems.org>
Message-ID: <etPan.575ef357.43583572.188e@gmail.com>

Hello Josh,

on the installed OmniOS you can get CD device name using iostat -En output (look for CD,CDRW, etc) and
then mount it using that name + s0:

mount -F hsfs /dev/dsk/c2t1d0s0 /media

While installing, OmniOS use mount_media utility ?from the system/install/media/internal package.


Yst?v?llisin terveisin
Alexander

On 13 June 2016 at 20:34:26, Bob Friesenhahn (bfriesen at simple.dallas.tx.us) wrote:

On Mon, 13 Jun 2016, Josh Barton wrote:  

> How do I find the right device to mount a cd, I have found that working with hardware like CD/USB drives isn't well documented in the case of OmniOS. Or perhaps I simply don't know the right place to go.  
> I appreciate any suggestions. Thanks!  

I would have said 'rmformat -l' but I am not seeing that rmformat is  
installed on my OmniOS system.  

Bob  
--  
Bob Friesenhahn  
bfriesen at simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/  
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/  
_______________________________________________  
OmniOS-discuss mailing list  
OmniOS-discuss at lists.omniti.com  
http://lists.omniti.com/mailman/listinfo/omnios-discuss  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160613/6296e922/attachment-0001.html>

From lkateley at kateley.com  Mon Jun 13 18:10:13 2016
From: lkateley at kateley.com (Linda Kateley)
Date: Mon, 13 Jun 2016 13:10:13 -0500
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <1465787057.17797.11.camel@gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<1465787057.17797.11.camel@gmail.com>
Message-ID: <01a13afe-51e4-9684-f008-58ecf1326fa5@kateley.com>

I actually have recently fell in love with nap-it. It bundles all the 
stuff you need..


lk


On 6/12/16 10:04 PM, Gui-Ron Koh wrote:
> On Sun, 2016-06-12 at 11:35 +0200, Krzysztof Grzempa wrote:
>> Cheers guys,
>>
>> I'm planning to build my own server at home for multiple purposes (my 
>> projects, home NAS etc). I'm planning to use zones to separate WAN 
>> access server (www hosting, git and svn repos, email maybe..) and SAN 
>> functionalities for LAN only access.
>> Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11, 
>> and i really enjoy it. I wish to use ZFS as the best storage 
>> solution, but what concern me most is availability of technologies 
>> that i'm going to use. For WAN purposes I need apache2, php5, 
>> mariadb, python (at least 2.7),git, svn, and maybe fish shell ;) . 
>> For my NAS, I need samba, nfs, ftp, DLNA [mediatomb, serviio] 
>> (sharing video to TV directly).
>> AFAIK and read on the net, probably every of those technologies are 
>> doable on OmniOS, but the problem is time spent on installing, 
>> solving problems etc.
>> Of course, there is always the linux solution, but i would like not 
>> go there as Illumos has may better storage (ZFS on linux sucks IHMO)
>> Has anyone got expierience in setting up such stack on OmniOS? (or 
>> any other Illumos distro?) Problems? Advices?
>
> I run most of my WAN stack (apache, php, etc) from the Joyent pkgsrc 
> repository, which is very straightforward to get running and keep 
> updated on OmniOS.
> For DLNA I used to run mediatomb from a self-compiled instance, but 
> have since swapped over to NFS shares, relying on a more capable media 
> player (OpenElec).
>
> I also run a Linux KVM instance for the stuff that is "just too 
> difficult" (eg. crashplan, grafana3, etc).
>
> regards,
> Guo-Rong
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160613/62661947/attachment.html>

From vab at bb-c.de  Mon Jun 13 18:34:24 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Mon, 13 Jun 2016 20:34:24 +0200
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
 r151014 or r151018
In-Reply-To: <CAO8hXRDHNfEux_=WWT2gqBb_QrAEFGmd5mrF9i2bD55zNtv66A@mail.gmail.com>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
	<CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
	<22366.60407.567814.988317@shelob.bb-c.de>
	<CAO8hXRDHNfEux_=WWT2gqBb_QrAEFGmd5mrF9i2bD55zNtv66A@mail.gmail.com>
Message-ID: <22366.64688.928256.200787@shelob.bb-c.de>

> On Mon, Jun 13, 2016 at 1:23 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> > BTW my 151016 system has the file, and SUNWcs is properly installed,
> > but "pkg search /etc/ftpd" or "pkg search /etc/ftpd/ftpusers" do not
> > show any output, even after a "pkg rebuild-index".  Strange.
>
> Paths are relative because packages are relocatable, so I usually
> search for a basename if it's relatively unambiguous.  `pkg search
> ftpusers` should work, and return both a file and a softlink.  Note
> that "basename" is a virtual attribute that doesn't actually appear in
> the pkg manifest, but is synthesized by the client, based on the last
> element of the path value.
>
> This is on my 014 install:
>
> $ pkg search ftpusers
> INDEX      ACTION VALUE             PACKAGE
> basename   file   etc/ftpd/ftpusers pkg:/SUNWcs at 0.5.11-0.151014
> basename   link   etc/ftpusers      pkg:/SUNWcs at 0.5.11-0.151014
>
> Using the full set of search fields also works, though I've never
> understood why I need the '*' at the beginning of the path value:
>
> $ pkg search 'file:path:*etc/ftpd/ftpusers'
> INDEX      ACTION VALUE             PACKAGE
> path       file   etc/ftpd/ftpusers pkg:/SUNWcs at 0.5.11-0.151014

$ uname -a
SunOS nfs 5.11 omnios-33c53a8 i86pc i386 i86pc

$ pkg version
1456488756

$ pkg search etc/ftpd/ftpusers
Exit 1

$ pkg search /etc/ftpd/ftpusers
Exit 1

$ pkg search 'file:path:*etc/ftpd/ftpusers'
Exit 1

$  pkg list -v SUNWcs
FMRI                                                                         IFO
pkg://omnios/SUNWcs at 0.5.11-0.151016:20160204T173743Z                         i--

$ pkg contents SUNWcs|grep ftpd
etc/ftpd
etc/ftpd/ftpusers

$ pkg search /etc/default/ftp
INDEX      ACTION VALUE           PACKAGE
path       file   etc/default/ftp pkg:/network/ftp at 0.5.11-0.151016


Beats me.  I'll try this again after I have updated to 151018 in a 
few days.


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 danmcd at omniti.com  Mon Jun 13 18:49:06 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 13 Jun 2016 14:49:06 -0400
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
	r151014 or r151018
In-Reply-To: <22366.64688.928256.200787@shelob.bb-c.de>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
	<CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
	<22366.60407.567814.988317@shelob.bb-c.de>
	<CAO8hXRDHNfEux_=WWT2gqBb_QrAEFGmd5mrF9i2bD55zNtv66A@mail.gmail.com>
	<22366.64688.928256.200787@shelob.bb-c.de>
Message-ID: <CD7E4C82-E2F2-41AD-BF3B-EEA84E374BE5@omniti.com>

I think our IPS repos need a batch of "pkgrepo refresh" runs.  I'm without power at the moment, but I will make sure it gets done  once I access OmniTI again.

Dan

Sent from my iPhone (typos, autocorrect, and all)

On Jun 13, 2016, at 2:34 PM, Volker A. Brandt <vab at bb-c.de> wrote:

>>> On Mon, Jun 13, 2016 at 1:23 PM, Volker A. Brandt <vab at bb-c.de> wrote:
>>> BTW my 151016 system has the file, and SUNWcs is properly installed,
>>> but "pkg search /etc/ftpd" or "pkg search /etc/ftpd/ftpusers" do not
>>> show any output, even after a "pkg rebuild-index".  Strange.
>> 
>> Paths are relative because packages are relocatable, so I usually
>> search for a basename if it's relatively unambiguous.  `pkg search
>> ftpusers` should work, and return both a file and a softlink.  Note
>> that "basename" is a virtual attribute that doesn't actually appear in
>> the pkg manifest, but is synthesized by the client, based on the last
>> element of the path value.
>> 
>> This is on my 014 install:
>> 
>> $ pkg search ftpusers
>> INDEX      ACTION VALUE             PACKAGE
>> basename   file   etc/ftpd/ftpusers pkg:/SUNWcs at 0.5.11-0.151014
>> basename   link   etc/ftpusers      pkg:/SUNWcs at 0.5.11-0.151014
>> 
>> Using the full set of search fields also works, though I've never
>> understood why I need the '*' at the beginning of the path value:
>> 
>> $ pkg search 'file:path:*etc/ftpd/ftpusers'
>> INDEX      ACTION VALUE             PACKAGE
>> path       file   etc/ftpd/ftpusers pkg:/SUNWcs at 0.5.11-0.151014
> 
> $ uname -a
> SunOS nfs 5.11 omnios-33c53a8 i86pc i386 i86pc
> 
> $ pkg version
> 1456488756
> 
> $ pkg search etc/ftpd/ftpusers
> Exit 1
> 
> $ pkg search /etc/ftpd/ftpusers
> Exit 1
> 
> $ pkg search 'file:path:*etc/ftpd/ftpusers'
> Exit 1
> 
> $  pkg list -v SUNWcs
> FMRI                                                                         IFO
> pkg://omnios/SUNWcs at 0.5.11-0.151016:20160204T173743Z                         i--
> 
> $ pkg contents SUNWcs|grep ftpd
> etc/ftpd
> etc/ftpd/ftpusers
> 
> $ pkg search /etc/default/ftp
> INDEX      ACTION VALUE           PACKAGE
> path       file   etc/default/ftp pkg:/network/ftp at 0.5.11-0.151016
> 
> 
> Beats me.  I'll try this again after I have updated to 151018 in a 
> few days.
> 
> 
> 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 danmcd at omniti.com  Mon Jun 13 19:17:56 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 13 Jun 2016 15:17:56 -0400
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
	r151014 or r151018
In-Reply-To: <CD7E4C82-E2F2-41AD-BF3B-EEA84E374BE5@omniti.com>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
	<CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
	<22366.60407.567814.988317@shelob.bb-c.de>
	<CAO8hXRDHNfEux_=WWT2gqBb_QrAEFGmd5mrF9i2bD55zNtv66A@mail.gmail.com>
	<22366.64688.928256.200787@shelob.bb-c.de>
	<CD7E4C82-E2F2-41AD-BF3B-EEA84E374BE5@omniti.com>
Message-ID: <936FFDB3-A161-4B99-B09A-195483BB3266@omniti.com>


> On Jun 13, 2016, at 2:49 PM, Dan McDonald <danmcd at omniti.com> wrote:
> 
> I think our IPS repos need a batch of "pkgrepo refresh" runs.  I'm without power at the moment, but I will make sure it gets done  once I access OmniTI again.

I've got power:

r151018(~)[0]% pkg search /etc/ftpd
INDEX      ACTION VALUE    PACKAGE
path       dir    etc/ftpd pkg:/SUNWcs at 0.5.11-0.151018
r151018(~)[0]% pkg search /etc/ftpd/
r151018(~)[1]% pkg search /etc/ftpd/ftpusers 
INDEX      ACTION VALUE             PACKAGE
path       file   etc/ftpd/ftpusers pkg:/SUNWcs at 0.5.11-0.151018
r151018(~)[0]% 


Note that searching for a directory ending with / won't hit.

Dan


From grzempek at gmail.com  Mon Jun 13 19:23:26 2016
From: grzempek at gmail.com (Krzysztof Grzempa)
Date: Mon, 13 Jun 2016 21:23:26 +0200
Subject: [OmniOS-discuss] Fwd:  OmniOS as home serwer (NAT, private projects)
In-Reply-To: <CAED-Y_DwekoCTxV8h82vuzV+z=1ZaqWTHg4O4yptfM8g+4DkGg@mail.gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<1465787057.17797.11.camel@gmail.com>
	<01a13afe-51e4-9684-f008-58ecf1326fa5@kateley.com>
	<CAED-Y_DwekoCTxV8h82vuzV+z=1ZaqWTHg4O4yptfM8g+4DkGg@mail.gmail.com>
Message-ID: <CAED-Y_BZHhsh=mya-UjKuF3xaqUG2qn6SvrichWpNQmCK14FUw@mail.gmail.com>

Guys,

Thanks for all your shares. So, it seems that it is possible, without
spending days and days setting it up. Thats great.

@Guo-Rong Koh
>I run most of my WAN stack (apache, php, etc) from the Joyent pkgsrc
repository, which is very straightforward to get running and >keep updated
on OmniOS

No native OmniOS apache2,php packages available? Does it work well, and
there is no conflicts on system updates? What about apache2 modules
availability and php libraries. My project that im planning to run uses
PEAR repo, is it possibile to install?
The same questions goes for Python, django. is there pip3 available ?

@Thomas
>As OmniOS is one of the OSdistro that has support in SFE, then it could
>work to get mediatomb for OmniOS as well. It would take some effort to
>see if the base functionality can be made work on OmniOS.

I know SFE, i used to use it on OpenIndiana some time ago..That was great
alternative to native's repositories. I had a access to the compile farm
even ;) I will try it for everything that i won't be able to find in native
repos..

@Linda Kateley
> I actually have recently fell in love with nap-it. It bundles all the
stuff you need..

Yep, i'm aware of it. But I would like to keep my Solaris/Illumos skills on
track since nowadays I am DevOps working with code and Linux mostly, so
having Illumos home box would be great. On the other hand napp-it probably
would safe a lot of my time, but the price for it is that i will install
it, configure it by clicking GUI and thats it. I prefer to get my hands
dirty, but with reasonable amount of time..

Cheers

2016-06-13 20:10 GMT+02:00 Linda Kateley <lkateley at kateley.com>:

> I actually have recently fell in love with nap-it. It bundles all the
> stuff you need..
>
>
> lk
>
> On 6/12/16 10:04 PM, Gui-Ron Koh wrote:
>
> On Sun, 2016-06-12 at 11:35 +0200, Krzysztof Grzempa wrote:
>
> Cheers guys,
>
> I'm planning to build my own server at home for multiple purposes (my
> projects, home NAS etc). I'm planning to use zones to separate WAN access
> server (www hosting, git and svn repos, email maybe..) and SAN
> functionalities for LAN only access.
> Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11, and i
> really enjoy it. I wish to use ZFS as the best storage solution, but what
> concern me most is availability of technologies that i'm going to use. For
> WAN purposes I need apache2, php5, mariadb, python (at least 2.7),git, svn,
> and maybe fish shell ;) . For my NAS, I need samba, nfs, ftp, DLNA
> [mediatomb, serviio] (sharing video to TV directly).
> AFAIK and read on the net, probably every of those technologies are doable
> on OmniOS, but the problem is time spent on installing, solving problems
> etc.
> Of course, there is always the linux solution, but i would like not go
> there as Illumos has may better storage (ZFS on linux sucks IHMO)
> Has anyone got expierience in setting up such stack on OmniOS? (or any
> other Illumos distro?) Problems? Advices?
>
>
> I run most of my WAN stack (apache, php, etc) from the Joyent pkgsrc
> repository, which is very straightforward to get running and keep updated
> on OmniOS.
> For DLNA I used to run mediatomb from a self-compiled instance, but have
> since swapped over to NFS shares, relying on a more capable media player
> (OpenElec).
>
> I also run a Linux KVM instance for the stuff that is "just too difficult"
> (eg. crashplan, grafana3, etc).
>
> regards,
> Guo-Rong
>
>
> _______________________________________________
> OmniOS-discuss mailing listOmniOS-discuss at lists.omniti.comhttp://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160613/fa487448/attachment-0001.html>

From vab at bb-c.de  Mon Jun 13 19:37:03 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Mon, 13 Jun 2016 21:37:03 +0200
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
	r151014 or r151018
In-Reply-To: <CD7E4C82-E2F2-41AD-BF3B-EEA84E374BE5@omniti.com>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
	<CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
	<22366.60407.567814.988317@shelob.bb-c.de>
	<CAO8hXRDHNfEux_=WWT2gqBb_QrAEFGmd5mrF9i2bD55zNtv66A@mail.gmail.com>
	<22366.64688.928256.200787@shelob.bb-c.de>
	<CD7E4C82-E2F2-41AD-BF3B-EEA84E374BE5@omniti.com>
Message-ID: <22367.2911.393709.793067@shelob.bb-c.de>

Dan McDonald writes:
> I think our IPS repos need a batch of "pkgrepo refresh" runs.

Aaaah, good clue!  I have a local copy of the 151016 repo. After a
"pkgrepo refresh" on the repo server and a "pkg refresh --full" on
the 151016 client, everything is well again, and "pkg search" works
just fine.  Thanks Dan!


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 danmcd at omniti.com  Mon Jun 13 19:43:57 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 13 Jun 2016 15:43:57 -0400
Subject: [OmniOS-discuss] Error attempting to switch to OpenSSH on
	r151014 or r151018
In-Reply-To: <22367.2911.393709.793067@shelob.bb-c.de>
References: <a0c0ef70-4eb8-2611-4782-9ecddeb62e3b@gmail.com>
	<F17761A3-8C8C-4A51-9703-EBB576A98DA7@omniti.com>
	<22366.54621.935438.11693@shelob.bb-c.de>
	<CAO8hXRCHLmR_TxNo3xPeH1zWdp+Gg0pfpxBfWjNMe3R2ZFdFDA@mail.gmail.com>
	<22366.60407.567814.988317@shelob.bb-c.de>
	<CAO8hXRDHNfEux_=WWT2gqBb_QrAEFGmd5mrF9i2bD55zNtv66A@mail.gmail.com>
	<22366.64688.928256.200787@shelob.bb-c.de>
	<CD7E4C82-E2F2-41AD-BF3B-EEA84E374BE5@omniti.com>
	<22367.2911.393709.793067@shelob.bb-c.de>
Message-ID: <31CAC0C3-7A46-466B-8F70-EC636B29D6B3@omniti.com>


> On Jun 13, 2016, at 3:37 PM, Volker A. Brandt <vab at bb-c.de> wrote:
> 
> Aaaah, good clue!  I have a local copy of the 151016 repo. After a
> "pkgrepo refresh" on the repo server and a "pkg refresh --full" on
> the 151016 client, everything is well again, and "pkg search" works
> just fine.  Thanks Dan!

The trick (and I forget this more than I should) is to pkgrepo refresh after any pushes of new packages.  We just had a big push last week.

Glad this helps.  Now I'm going back to see how I broke zoneadmd in io-lx.  :-/

Dan


From lists at marzocchi.net  Mon Jun 13 20:30:37 2016
From: lists at marzocchi.net (Olaf Marzocchi)
Date: Mon, 13 Jun 2016 22:30:37 +0200
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <01a13afe-51e4-9684-f008-58ecf1326fa5@kateley.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<1465787057.17797.11.camel@gmail.com>
	<01a13afe-51e4-9684-f008-58ecf1326fa5@kateley.com>
Message-ID: <c0f30084-d7a9-76d7-053f-978cad7138eb@marzocchi.net>

It's clearly an easy way to manage the server and to get info about its 
status, just remember to take a snapshot before installing it, it 
doesn't use packages and it does not install its stuff in /opt, so 
removing it it's not trivial.

Olaf


On 13/06/2016 20:10, Linda Kateley wrote:
> I actually have recently fell in love with nap-it. It bundles all the
> stuff you need..
>
>
> lk
>
>
> On 6/12/16 10:04 PM, Gui-Ron Koh wrote:
>> On Sun, 2016-06-12 at 11:35 +0200, Krzysztof Grzempa wrote:
>>> Cheers guys,
>>>
>>> I'm planning to build my own server at home for multiple purposes (my
>>> projects, home NAS etc). I'm planning to use zones to separate WAN
>>> access server (www hosting, git and svn repos, email maybe..) and SAN
>>> functionalities for LAN only access.
>>> Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11,
>>> and i really enjoy it. I wish to use ZFS as the best storage
>>> solution, but what concern me most is availability of technologies
>>> that i'm going to use. For WAN purposes I need apache2, php5,
>>> mariadb, python (at least 2.7),git, svn, and maybe fish shell ;) .
>>> For my NAS, I need samba, nfs, ftp, DLNA [mediatomb, serviio]
>>> (sharing video to TV directly).
>>> AFAIK and read on the net, probably every of those technologies are
>>> doable on OmniOS, but the problem is time spent on installing,
>>> solving problems etc.
>>> Of course, there is always the linux solution, but i would like not
>>> go there as Illumos has may better storage (ZFS on linux sucks IHMO)
>>> Has anyone got expierience in setting up such stack on OmniOS? (or
>>> any other Illumos distro?) Problems? Advices?
>>
>> I run most of my WAN stack (apache, php, etc) from the Joyent pkgsrc
>> repository, which is very straightforward to get running and keep
>> updated on OmniOS.
>> For DLNA I used to run mediatomb from a self-compiled instance, but
>> have since swapped over to NFS shares, relying on a more capable media
>> player (OpenElec).
>>
>> I also run a Linux KVM instance for the stuff that is "just too
>> difficult" (eg. crashplan, grafana3, etc).
>>
>> regards,
>> Guo-Rong
>>
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>

From danmcd at omniti.com  Mon Jun 13 22:03:41 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Mon, 13 Jun 2016 18:03:41 -0400
Subject: [OmniOS-discuss] I booted an lipkg zone under io-lx
Message-ID: <A5303ECA-39BB-4F45-9254-CD827BE9EB2A@omniti.com>

With this commit:

	https://github.com/danmcd/io-lx-public/commit/239c2482b13bdd8576623c1092f822cfd2d7e3a8

I got my test VM to boot a previously-configured lipkg zone.  I've LOTS more to do, of course, but this is a good step in the right direction.

Is anyone playing with io-lx yet?  Or are you all waiting for me to get to the part about instantiating an LX zone?  BTW, it will be different than SmartOS when it comes to configuration and installation.  If you have ideas about this (that don't involve porting all of SmartOS or at least vmadm(1M)), please let me know.

Dan


From jimklimov at cos.ru  Mon Jun 13 22:24:22 2016
From: jimklimov at cos.ru (Jim Klimov)
Date: Tue, 14 Jun 2016 00:24:22 +0200
Subject: [OmniOS-discuss] CD Mounting
In-Reply-To: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
References: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
Message-ID: <04A1A050-A59C-4E9D-8BDD-1F325572A8A3@cos.ru>

13 ???? 2016??. 19:20:15 CEST, Josh Barton <Josh.Barton at usurf.usu.edu> ?????:
>How do I find the right device to mount a cd, I have found that working
>with hardware like CD/USB drives  isn't well documented in the case of
>OmniOS. Or perhaps I simply don't know the right place to go.
>I appreciate any suggestions. Thanks!
>
>Josh Barton
>USU Research Foundation
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>OmniOS-discuss mailing list
>OmniOS-discuss at lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

Try 'format -e' ? Also 'dmesg' (or /var/adm/messages) may be of help.

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

From guorong.koh at gmail.com  Mon Jun 13 22:29:07 2016
From: guorong.koh at gmail.com (Guo-Rong Koh)
Date: Tue, 14 Jun 2016 07:59:07 +0930
Subject: [OmniOS-discuss] Fwd:  OmniOS as home serwer (NAT,
 private projects)
In-Reply-To: <CAED-Y_BZHhsh=mya-UjKuF3xaqUG2qn6SvrichWpNQmCK14FUw@mail.gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<1465787057.17797.11.camel@gmail.com>
	<01a13afe-51e4-9684-f008-58ecf1326fa5@kateley.com>
	<CAED-Y_DwekoCTxV8h82vuzV+z=1ZaqWTHg4O4yptfM8g+4DkGg@mail.gmail.com>
	<CAED-Y_BZHhsh=mya-UjKuF3xaqUG2qn6SvrichWpNQmCK14FUw@mail.gmail.com>
Message-ID: <1465856947.31473.13.camel@gmail.com>

Krzysztof,
On Mon, 2016-06-13 at 21:23 +0200, Krzysztof Grzempa wrote:
> Guys,
> 
> Thanks for all your shares. So, it seems that it is possible, without
> spending days and days setting it up. Thats great.
> 
> @Guo-Rong Koh
> >I run most of my WAN stack (apache, php, etc) from the Joyent pkgsrc
> repository, which is very straightforward to get running and >keep
> updated on OmniOS
> 
> No native OmniOS apache2,php packages available? Does it work well,
> and there is no conflicts on system updates? What about apache2
> modules availability and php libraries. My project that im planning
> to run uses PEAR repo, is it possibile to install?
> The same questions goes for Python, django. is there pip3 available ?
> 
> 
> 
OmniOS is an excellent minimal install, but the core holds very few
additional applications/libraries.
That stuff is supplemented by other repositories.
OmniTI host a pkg repository that has apache2 and php here:
https://pkg.omniti.com/omniti-ms/en/catalog.shtml
(I have used this in the past).
But I don't see django there, I do however see it here:
http://scott.mathematik.uni-ulm.de/release/en/catalog.shtml
(I have not used this repo before).
These repos are mentioned on the wiki here:
https://omnios.omniti.com/wiki.php/Packaging
For my install, you can browse the full list of Joyent's pkgsrc latest
packages here:
https://pkgsrc.joyent.com/packages/SmartOS/2016Q1/x86_64/
I haven't installed PHP PEAR, but packages are there.
And yes, django and pip3 are available, I use both in my zones.
pkgsrc installs to /opt/local and has not yet caused any issues with
my base OmniOS install.
regards,
Guo-Rong
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160614/6241bde0/attachment.html>

From robert at omniti.com  Tue Jun 14 00:07:45 2016
From: robert at omniti.com (Robert Treat)
Date: Mon, 13 Jun 2016 20:07:45 -0400
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <1465856947.31473.13.camel@gmail.com>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<1465787057.17797.11.camel@gmail.com>
	<01a13afe-51e4-9684-f008-58ecf1326fa5@kateley.com>
	<CAED-Y_DwekoCTxV8h82vuzV+z=1ZaqWTHg4O4yptfM8g+4DkGg@mail.gmail.com>
	<CAED-Y_BZHhsh=mya-UjKuF3xaqUG2qn6SvrichWpNQmCK14FUw@mail.gmail.com>
	<1465856947.31473.13.camel@gmail.com>
Message-ID: <CA+FJ0zsyNoVfUX=+r6F+w2_GgfY86m2kg+o5dU2bEBApMGiNDA@mail.gmail.com>

On Monday, June 13, 2016, Guo-Rong Koh <guorong.koh at gmail.com> wrote:

> OmniTI host a pkg repository that has apache2 and php here:
> https://pkg.omniti.com/omniti-ms/en/catalog.shtml
> (I have used this in the past).
>
> But I don't see django there, I do however see it here:
> http://scott.mathematik.uni-ulm.de/release/en/catalog.shtml
> (I have not used this repo before).
>

I was surprised to see you saying django was not in our repo; I can attest
it works as we run it in prod for our web consulting business.  I suspect
we must deploy it via some more pythonic method I guess. At some point I
hope that a real community based packaging process will make all this
easier, but alas I don't see it yet.

Robert Treat
https://omniti.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160613/eb14c867/attachment-0001.html>

From alka at hfg-gmuend.de  Tue Jun 14 10:43:26 2016
From: alka at hfg-gmuend.de (Guenther Alka)
Date: Tue, 14 Jun 2016 12:43:26 +0200
Subject: [OmniOS-discuss] OmniOS as home serwer (NAT, private projects)
In-Reply-To: <c0f30084-d7a9-76d7-053f-978cad7138eb@marzocchi.net>
References: <CAED-Y_B=S_JoWu9AiU7+UHXnxBaA-eee=Qx7PFcz+qtA=qbqyQ@mail.gmail.com>
	<1465787057.17797.11.camel@gmail.com>
	<01a13afe-51e4-9684-f008-58ecf1326fa5@kateley.com>
	<c0f30084-d7a9-76d7-053f-978cad7138eb@marzocchi.net>
Message-ID: <43e9005c-1ead-46a6-1085-e658bade393a@hfg-gmuend.de>

about removing or stopping napp-it

The napp-it installer creates a bootenvironment with the state prior the 
installation automatically so you can go back easily.

As napp-it is a pure copy and run installation, it copies everything to 
/var/web-gui. If you delete this folder, the init file 
/etc/init.d/napp-it, the user nappit and an entry in /etc/sudoers you 
have wiped it beside tools that are installed during setup like 
smartmontools, midnight commander, iperf or netcat.

If you install add-ons like the AMP stack, Mediatomb or Owncloud, they 
are mostly using pkgsrc from Joyent with files in /opt

see
http://www.napp-it.org/doc/downloads/napp-it.pdf chapter 5.3


Gea

Am 13.06.2016 um 22:30 schrieb Olaf Marzocchi:
> It's clearly an easy way to manage the server and to get info about 
> its status, just remember to take a snapshot before installing it, it 
> doesn't use packages and it does not install its stuff in /opt, so 
> removing it it's not trivial.
>
> Olaf
>
>
> On 13/06/2016 20:10, Linda Kateley wrote:
>> I actually have recently fell in love with nap-it. It bundles all the
>> stuff you need..
>>
>>
>> lk
>>
>>
>> On 6/12/16 10:04 PM, Gui-Ron Koh wrote:
>>> On Sun, 2016-06-12 at 11:35 +0200, Krzysztof Grzempa wrote:
>>>> Cheers guys,
>>>>
>>>> I'm planning to build my own server at home for multiple purposes (my
>>>> projects, home NAS etc). I'm planning to use zones to separate WAN
>>>> access server (www hosting, git and svn repos, email maybe..) and SAN
>>>> functionalities for LAN only access.
>>>> Now, i'm huge fan of Illumos. I used to work with Solaris 8 to 11,
>>>> and i really enjoy it. I wish to use ZFS as the best storage
>>>> solution, but what concern me most is availability of technologies
>>>> that i'm going to use. For WAN purposes I need apache2, php5,
>>>> mariadb, python (at least 2.7),git, svn, and maybe fish shell ;) .
>>>> For my NAS, I need samba, nfs, ftp, DLNA [mediatomb, serviio]
>>>> (sharing video to TV directly).
>>>> AFAIK and read on the net, probably every of those technologies are
>>>> doable on OmniOS, but the problem is time spent on installing,
>>>> solving problems etc.
>>>> Of course, there is always the linux solution, but i would like not
>>>> go there as Illumos has may better storage (ZFS on linux sucks IHMO)
>>>> Has anyone got expierience in setting up such stack on OmniOS? (or
>>>> any other Illumos distro?) Problems? Advices?
>>>
>>> I run most of my WAN stack (apache, php, etc) from the Joyent pkgsrc
>>> repository, which is very straightforward to get running and keep
>>> updated on OmniOS.
>>> For DLNA I used to run mediatomb from a self-compiled instance, but
>>> have since swapped over to NFS shares, relying on a more capable media
>>> player (OpenElec).
>>>
>>> I also run a Linux KVM instance for the stuff that is "just too
>>> difficult" (eg. crashplan, grafana3, etc).
>>>
>>> regards,
>>> Guo-Rong
>>>
>>>
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>>
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-- 
H          f   G
Hochschule f?r Gestaltung
university of design

Schw?bisch Gm?nd
Rektor-Klaus Str. 100
73525 Schw?bisch Gm?nd

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 627
Fax 07171 69259
guenther.alka at hfg-gmuend.de
http://rz.hfg-gmuend.de


From bfriesen at simple.dallas.tx.us  Tue Jun 14 13:28:37 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Tue, 14 Jun 2016 08:28:37 -0500 (CDT)
Subject: [OmniOS-discuss] CD Mounting
In-Reply-To: <alpine.GSO.2.20.1606131231470.735@freddy.simplesystems.org>
References: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
	<alpine.GSO.2.20.1606131231470.735@freddy.simplesystems.org>
Message-ID: <alpine.GSO.2.20.1606140827100.29536@freddy.simplesystems.org>

On Mon, 13 Jun 2016, Bob Friesenhahn wrote:

> On Mon, 13 Jun 2016, Josh Barton wrote:
>
>> How do I find the right device to mount a cd, I have found that working 
>> with hardware like CD/USB drives  isn't well documented in the case of 
>> OmniOS. Or perhaps I simply don't know the right place to go.
>> I appreciate any suggestions. Thanks!
>
> I would have said 'rmformat -l' but I am not seeing that rmformat is 
> installed on my OmniOS system.

I see that 'rmformat' is delivered on OmniOS by this package:

% pkg search rmformat
INDEX      ACTION VALUE            PACKAGE
basename   file   usr/bin/rmformat pkg:/service/storage/media-volume-manager at 0.5.11-0.151016

Presumably this also deliveres 'vold' which makes dealing with DVDs 
and USB-sticks more PC-like.

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

From henrikj at henkis.net  Tue Jun 14 18:05:08 2016
From: henrikj at henkis.net (henrikj at henkis.net)
Date: Tue, 14 Jun 2016 20:05:08 +0200
Subject: [OmniOS-discuss] Riak on OmniOS
Message-ID: <DDBB0C79-657A-4BC7-AA55-E07E6E427D76@henkis.net>

Hi,

Not related directly to OmniOS but to software supported.

Anyone running Riak on OmniOS? Seems lika a good match since basho have recommended ZFS and there are Dtrace probes available. But when talking to basho they say the no longer support OmniOS/illumos/Solaris. Anyone else heard this, should I be worried and be forced to run on Linux with ZoL or god forbid LVM?

Regards
Henrik

From Josh.Barton at usurf.usu.edu  Tue Jun 14 18:44:47 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Tue, 14 Jun 2016 18:44:47 +0000
Subject: [OmniOS-discuss] CD Mounting
In-Reply-To: <04A1A050-A59C-4E9D-8BDD-1F325572A8A3@cos.ru>
References: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
	<04A1A050-A59C-4E9D-8BDD-1F325572A8A3@cos.ru>
Message-ID: <cacd01b6d6e04ca4a7acf815ed9223d2@Ek.usurf.usu.edu>

That only showed me the hard disks and not the cd drive.

Josh Barton

-----Original Message-----
From: Jim Klimov [mailto:jimklimov at cos.ru] 
Sent: Monday, June 13, 2016 4:24 PM
To: Josh Barton <Josh.Barton at usurf.usu.edu>; omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] CD Mounting

13 ???? 2016??. 19:20:15 CEST, Josh Barton <Josh.Barton at usurf.usu.edu> ?????:
>How do I find the right device to mount a cd, I have found that working 
>with hardware like CD/USB drives  isn't well documented in the case of 
>OmniOS. Or perhaps I simply don't know the right place to go.
>I appreciate any suggestions. Thanks!
>
>Josh Barton
>USU Research Foundation
>
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>OmniOS-discuss mailing list
>OmniOS-discuss at lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

Try 'format -e' ? Also 'dmesg' (or /var/adm/messages) may be of help.

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

From Josh.Barton at usurf.usu.edu  Tue Jun 14 19:08:46 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Tue, 14 Jun 2016 19:08:46 +0000
Subject: [OmniOS-discuss] CD Mounting
In-Reply-To: <alpine.GSO.2.20.1606140827100.29536@freddy.simplesystems.org>
References: <1d219a50f04342dc876a838d5aa943ed@Ek.usurf.usu.edu>
	<alpine.GSO.2.20.1606131231470.735@freddy.simplesystems.org>
	<alpine.GSO.2.20.1606140827100.29536@freddy.simplesystems.org>
Message-ID: <5859f62975d647a68d8cda0ae9f461c7@Ek.usurf.usu.edu>

Thank you that did it.
Josh

-----Original Message-----
From: Bob Friesenhahn [mailto:bfriesen at simple.dallas.tx.us] 
Sent: Tuesday, June 14, 2016 7:29 AM
To: Josh Barton <Josh.Barton at usurf.usu.edu>
Cc: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] CD Mounting

On Mon, 13 Jun 2016, Bob Friesenhahn wrote:

> On Mon, 13 Jun 2016, Josh Barton wrote:
>
>> How do I find the right device to mount a cd, I have found that 
>> working with hardware like CD/USB drives  isn't well documented in 
>> the case of OmniOS. Or perhaps I simply don't know the right place to go.
>> I appreciate any suggestions. Thanks!
>
> I would have said 'rmformat -l' but I am not seeing that rmformat is 
> installed on my OmniOS system.

I see that 'rmformat' is delivered on OmniOS by this package:

% pkg search rmformat
INDEX      ACTION VALUE            PACKAGE
basename   file   usr/bin/rmformat pkg:/service/storage/media-volume-manager at 0.5.11-0.151016

Presumably this also deliveres 'vold' which makes dealing with DVDs and USB-sticks more PC-like.

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

From danmcd at omniti.com  Tue Jun 14 21:58:33 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Tue, 14 Jun 2016 17:58:33 -0400
Subject: [OmniOS-discuss] ipkg & lipkg zones under io-lx (LX for OmniOS
	project)
In-Reply-To: <A5303ECA-39BB-4F45-9254-CD827BE9EB2A@omniti.com>
References: <A5303ECA-39BB-4F45-9254-CD827BE9EB2A@omniti.com>
Message-ID: <C9EACC29-0C2B-4C3D-AE14-AE801ED42F04@omniti.com>

I discovered a regression which blocked zone halts.  I'm now, at least upon initial smoke tests, no longer regressing any ipkg/lipkg functionality.  I still have lots of testing, of course, but I'll ask again:

> Is anyone playing with io-lx yet?  Or are you all waiting for me to get to the part about instantiating an LX zone?  BTW, it will be different than SmartOS when it comes to configuration and installation.  If you have ideas about this (that don't involve porting all of SmartOS or at least vmadm(1M)), please let me know.

	Github:  https://github.com/danmcd/io-lx-public/

I'm planning on putting up a distinct IPS server for io-lx.  It will essentially be "bloody, but with io-lx, until such time as we need to tweak omnios-build too".  Would people be interested in that as well?

Thanks,
Dan


From jimklimov at cos.ru  Wed Jun 15 04:33:16 2016
From: jimklimov at cos.ru (Jim Klimov)
Date: Wed, 15 Jun 2016 06:33:16 +0200
Subject: [OmniOS-discuss] ipkg & lipkg zones under io-lx (LX for
	OmniOS	project)
In-Reply-To: <C9EACC29-0C2B-4C3D-AE14-AE801ED42F04@omniti.com>
References: <A5303ECA-39BB-4F45-9254-CD827BE9EB2A@omniti.com>
	<C9EACC29-0C2B-4C3D-AE14-AE801ED42F04@omniti.com>
Message-ID: <7AAB5124-4C44-46DF-AEA8-ABA9F885ADE0@cos.ru>

14 ???? 2016??. 23:58:33 CEST, Dan McDonald <danmcd at omniti.com> ?????:
>I discovered a regression which blocked zone halts.  I'm now, at least
>upon initial smoke tests, no longer regressing any ipkg/lipkg
>functionality.  I still have lots of testing, of course, but I'll ask
>again:
>
>> Is anyone playing with io-lx yet?  Or are you all waiting for me to
>get to the part about instantiating an LX zone?  BTW, it will be
>different than SmartOS when it comes to configuration and installation.
>If you have ideas about this (that don't involve porting all of SmartOS
>or at least vmadm(1M)), please let me know.
>
>	Github:  https://github.com/danmcd/io-lx-public/
>
>I'm planning on putting up a distinct IPS server for io-lx.  It will
>essentially be "bloody, but with io-lx, until such time as we need to
>tweak omnios-build too".  Would people be interested in that as well?
>
>Thanks,
>Dan
>
>_______________________________________________
>OmniOS-discuss mailing list
>OmniOS-discuss at lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

I guess it would help enthusiastic testing and, who onows, maybe co-developers (at least to tweak brand scripts when time cokes ripe for that).

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

From ryan at zinascii.com  Wed Jun 15 14:03:33 2016
From: ryan at zinascii.com (Ryan Zezeski)
Date: Wed, 15 Jun 2016 10:03:33 -0400
Subject: [OmniOS-discuss] Riak on OmniOS
In-Reply-To: <DDBB0C79-657A-4BC7-AA55-E07E6E427D76@henkis.net>
References: <DDBB0C79-657A-4BC7-AA55-E07E6E427D76@henkis.net>
Message-ID: <m2oa72im6i.fsf@zinascii.com>


henrikj at henkis.net writes:

> Hi,
>
> Not related directly to OmniOS but to software supported.
>
> Anyone running Riak on OmniOS? Seems lika a good match since basho have recommended ZFS and there are Dtrace probes available. But when talking to basho they say the no longer support OmniOS/illumos/Solaris. Anyone else heard this, should I be worried and be forced to run on Linux with ZoL or god forbid LVM?
>

Former Basho employee and Riak contributor here.

Riak and OmniOS should get along fine; it's just not a first class
platform for Basho anymore. Anyone who had an interest in illumos-based
operating systems left the company. They don't have the people to
properly field support calls for it.

If you run into issues I'm happy to provide consulting services. OmniTI
should also have the knowledge to do the same.

-Z

From paulb at lctcb.org  Wed Jun 15 17:44:30 2016
From: paulb at lctcb.org (Paul Bucher)
Date: Wed, 15 Jun 2016 17:44:30 +0000
Subject: [OmniOS-discuss] OmniOS & Softlayer
Message-ID: <2648A460-F68D-4ABD-9003-3B9CBD792BE1@lctcb.org>


I?m working on bringing up some new mission critical servers at hosting provider Softlayer and wondering if anyone out there also hosts at Softlayer using OmniOS and what they?ve used for disk HBA?s at Softlayer with OmniOS(just to make it more complicated I use napp-it all in one virtual machine setups). My understanding is the current Xeon v3 servers Softlayer is using LSI megaRAID 9361 cards in them and I?ve been unable to find much about running ZFS on the newer megaraid cards and I really don?t want to do some RAID 0 type of setup that I?ve used in the past. Softlayer is using Supermicro X10DRU-i+ MBs that have a bunch of SATA ports on them hung off the C612 chipset, I?m temped to tell them to use those ports, but I?d like to hear someone else?s experience with these since I now OmniOS doesn?t always play well with more modern kit. 

So far I?ve had great success with all in one setups in the past on Softlayers older generation of servers, but I?ve had to ship to Softlayer and convenience them to install the standard LSI HBA SAS controllers for me which has the downside that if a box goes down they can?t just spin me up a newer server in an hour or so since it requires me to buy and ship them a new disk controller.

-Paul




From info.fmo at gmx.de  Thu Jun 16 01:08:11 2016
From: info.fmo at gmx.de (Frank M.)
Date: Thu, 16 Jun 2016 03:08:11 +0200
Subject: [OmniOS-discuss] nvme-device hangs after power-on - after
	soft-reboot all is okay
Message-ID: <1093963642.20160616030811@gmx.de>

Hi,

I have a problem with a NVMe-Device Samsung SM951 in a virtualized Illumos-environment.
My default setup is a HP G8 Server (I have tried others) as ESXi6.02-Host and a newest OmniOS-bloody-VM.

I?ve learned to setup the nvme from here: https://www.mail-archive.com/smartos-discuss at lists.smartos.org/msg02873.html.
Also I have read this: https://www.illumos.org/issues/6908 and other informations on web.

The progress of my installation you can read here (if you speak german) - please follow all posts of effemmess:  
http://www.hardwareluxx.de/community/f101/zfs-stammtisch-570052-272.html#post24644356
The problem in http://www.hardwareluxx.de/community/f101/zfs-stammtisch-570052-272.html#post24660135 is solved -it was a old updated vm, now I use an fresh installed vm...
But previosly I thought, there is something with the powerstates of the nvme. Because of that I made these additions to /etc/vmware/passthru.map (info is from here: http://www.vmware.com/pdf/vsp_4_vmdirectpath_host.pdf:
# Samsung NVMe
144d  a801  d3d0     false
144d  a802  d3d0     false
These additions are active till now...

The actual problem is, that after every cold-boot of the vm the nvme hangs. I test this by running the command "format". I cant see in any logs something interesting.
Now I reset the vm via second ssh and the command "reboot -p". Now works the nvme very well for hours. As long as I only reboot the vm all is okay, but if I cold-boot the vm, the nvme hangs again.
The whole process is reproducible. Gea says in hardwareluxx-forum, he has also problems with "format" with intel-NVMe.

Btw, in all Windows-VMs the NVMe runs promptly after every cold-vm-start.
Now I testet it in a freshly installed Openindiana-vm - full updated.
Here I have a critical fault after every cold-boot and soft-boot. Also a "fmadm repaired dev:////pci at 0,0/pci15ad,7a0 at 15/pci144d,a801 at 0" doesn't help.

In summary, the NVMe runs always very well on bar-metal and on Windows-vm's and after soft-boot also very well in OmniOS.

Can anybody help?

Best regards,
 Frank 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160616/5a1baf17/attachment.html>

From alka at hfg-gmuend.de  Thu Jun 16 06:34:56 2016
From: alka at hfg-gmuend.de (Guenther Alka)
Date: Thu, 16 Jun 2016 08:34:56 +0200
Subject: [OmniOS-discuss] OmniOS & Softlayer
In-Reply-To: <2648A460-F68D-4ABD-9003-3B9CBD792BE1@lctcb.org>
References: <2648A460-F68D-4ABD-9003-3B9CBD792BE1@lctcb.org>
Message-ID: <93c624e0-af67-adc3-5865-0cd1e6891d13@hfg-gmuend.de>

The LSI megaRAID 9361 is a hardware raid controller - the wrong type for 
ZFS.
You want a HBA controller best with a raidless IT firmware with an LSI 
2008 or 3008 chipset
like the LSI 9207 or 9003 or Sata in AHCI mode.

Your options:
- replace the 9361 with an HBA

or
- use it as a bootdevice for ESXi and the local datastore
- pass-through Sata in AHCI mode (enable hotplug for Sata)

or
- add an HBA

Gea


Am 15.06.2016 um 19:44 schrieb Paul Bucher:
> I?m working on bringing up some new mission critical servers at hosting provider Softlayer and wondering if anyone out there also hosts at Softlayer using OmniOS and what they?ve used for disk HBA?s at Softlayer with OmniOS(just to make it more complicated I use napp-it all in one virtual machine setups). My understanding is the current Xeon v3 servers Softlayer is using LSI megaRAID 9361 cards in them and I?ve been unable to find much about running ZFS on the newer megaraid cards and I really don?t want to do some RAID 0 type of setup that I?ve used in the past. Softlayer is using Supermicro X10DRU-i+ MBs that have a bunch of SATA ports on them hung off the C612 chipset, I?m temped to tell them to use those ports, but I?d like to hear someone else?s experience with these since I now OmniOS doesn?t always play well with more modern kit.
>
> So far I?ve had great success with all in one setups in the past on Softlayers older generation of servers, but I?ve had to ship to Softlayer and convenience them to install the standard LSI HBA SAS controllers for me which has the downside that if a box goes down they can?t just spin me up a newer server in an hour or so since it requires me to buy and ship them a new disk controller.
>
> -Paul
>
>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From stephan.budach at JVM.DE  Thu Jun 16 09:20:54 2016
From: stephan.budach at JVM.DE (Stephan Budach)
Date: Thu, 16 Jun 2016 11:20:54 +0200
Subject: [OmniOS-discuss] Can't get omnios installer to boot under Xen4.4
Message-ID: <c294d893-5c67-7b58-ad89-271f6ea2254e@jvm.de>

Hi all,

I am trying to get OmniOS <insert release here ;) > to run as a guest 
under Xen4.4. The issue I have, is that the installer kernel seems to 
boot, but then it just sits there doing actually nothing. I  have tried 
a couple of releases r016 to bloody, but none will advance more than 
that stage.

I have also tried HVM and HVMPV, but that didn't make a change as well. 
Anyone there, who has successfully done that? Is there some magic I can 
add to the vm.cfg file to get the installer running? I can successfully 
run Solaris11 as a guest, but not OmniOS? and I do want OmniOS, that's 
for sure. ;)

Any hints, suggestions are much appreciated.

Thanks,
Stephan

From danmcd at omniti.com  Thu Jun 16 14:41:40 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Thu, 16 Jun 2016 10:41:40 -0400
Subject: [OmniOS-discuss] Can't get omnios installer to boot under Xen4.4
In-Reply-To: <c294d893-5c67-7b58-ad89-271f6ea2254e@jvm.de>
References: <c294d893-5c67-7b58-ad89-271f6ea2254e@jvm.de>
Message-ID: <333E72EB-35E6-4C29-9081-45D6D940611A@omniti.com>

Our AWS images have something called PVgrub, and you may need that.  I don't construct our AWS images, so I don't have immediate answers for you.

Our EC2 AMI wiki may be instructive:

	https://omnios.omniti.com/wiki.php/Ec2Ami

Dan


From stephan.budach at JVM.DE  Thu Jun 16 15:20:01 2016
From: stephan.budach at JVM.DE (Stephan Budach)
Date: Thu, 16 Jun 2016 17:20:01 +0200
Subject: [OmniOS-discuss] Can't get omnios installer to boot under Xen4.4
In-Reply-To: <333E72EB-35E6-4C29-9081-45D6D940611A@omniti.com>
References: <c294d893-5c67-7b58-ad89-271f6ea2254e@jvm.de>
	<333E72EB-35E6-4C29-9081-45D6D940611A@omniti.com>
Message-ID: <8a925245-9b07-6553-c1ba-e51ca2754b9e@jvm.de>

Am 16.06.16 um 16:41 schrieb Dan McDonald:
> Our AWS images have something called PVgrub, and you may need that.  I don't construct our AWS images, so I don't have immediate answers for you.
>
> Our EC2 AMI wiki may be instructive:
>
> 	https://omnios.omniti.com/wiki.php/Ec2Ami
>
> Dan
>
Ahh? that looks interesting? thanks for pointing me to that. I'm sure 
that this will help.

Thanks,
Stephan


From steve at linuxsuite.org  Thu Jun 16 19:01:38 2016
From: steve at linuxsuite.org (steve at linuxsuite.org)
Date: Thu, 16 Jun 2016 15:01:38 -0400
Subject: [OmniOS-discuss] Scrub leaves pool in wiered state with all devices
	in "repairing" ?
Message-ID: <6e7cba92a473ecfcba1cf316f739c243.squirrel@emailmg.netfirms.com>


Howdy!

         I started a scrub on a zfs pool and it appears to be stuck in some
wierd state. Details below...  Ideas on the problem or how to proceed???

       Thanx - steve

   Server is a DELL R710

   OmniOS v11 r151014

  SAS controller is a LSI 9201. Here is output from lsiutils

Main menu, select an option:  [1-99 or e/p/w or 0 to quit] 69

Seg/Bus/Dev/Fun    Board Name       Board Assembly   Board Tracer
 0   5   0   0     SAS9201-16e      H3-25379-01D     SV04414910



**********   Here is a zpool status **************



 pool: dfs1_data31
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://illumos.org/msg/ZFS-8000-9P
  scan: scrub in progress since Thu Jun 16 10:25:17 2016
    81.3G scanned out of 16.9T at 5.65M/s, (scan is slow, no estimated time)
    3.33G repaired, 0.47% done
config:

        NAME                         STATE     READ WRITE CKSUM
        dfs1_data31                  ONLINE       0     0     0
          raidz1-0                   ONLINE       0     0     0
            c0t5000C5008D634F3Bd0s0  ONLINE       9     0     0  (repairing)
            c0t5000C5008D632173d0s0  ONLINE      18     0     0  (repairing)
            c0t5000C5008D64A043d0s0  ONLINE       8     0     0  (repairing)
            c0t5000C5008D6450FFd0s0  ONLINE      10     0     0  (repairing)
            c0t5000C5008D62EEFBd0s0  ONLINE      18     0     0  (repairing)
        spares
          c7t5000CCA03B699D71d0s0    AVAIL

errors: No known data errors



*****           Here are log entries...  *******



kern.warning<4>: Jun 16 14:40:30 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:30 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:40:30 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:30 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:40:30 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:30 dfs102 #011Log info 0x3112010c received for
target 154 w5000c5008d62eef9.
kern.info<6>: Jun 16 14:40:30 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:40:31 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:31 dfs102 #011Log info 0x3112010c received for
target 156 w5000c5008d64a041.
kern.info<6>: Jun 16 14:40:31 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:40:31 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:31 dfs102 #011Log info 0x3112010c received for
target 153 w5000c5008d634f39.
kern.info<6>: Jun 16 14:40:31 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:40:37 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:37 dfs102 #011Log info 0x3112010c received for
target 154 w5000c5008d62eef9.
kern.info<6>: Jun 16 14:40:37 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:40:37 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:37 dfs102 #011Log info 0x3112010c received for
target 153 w5000c5008d634f39.
kern.info<6>: Jun 16 14:40:37 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:45 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:45 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:40:45 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:45 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:40:45 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:45 dfs102 #011Log info 0x3112010c received for
target 154 w5000c5008d62eef9.
kern.info<6>: Jun 16 14:40:45 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:48 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:48 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:40:48 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:48 dfs102 #011Log info 0x3112010c received for
target 154 w5000c5008d62eef9.
kern.info<6>: Jun 16 14:40:48 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:48 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:48 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:40:57 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:57 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInf2
kern.warning<4>: Jun 16 14:40:57 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:57 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x31120302
kern.info<6>: Jun 16 14:40:57 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:57 dfs102 #011Log info 0x31120302 received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:40:57 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:40:59 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:59 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:40:59 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:40:59 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:40:59 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:40:59 dfs102 #011Log info 0x3112010c received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:40:59 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:41:00 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:00 dfs102 #011Log info 0x3112010c received for
target 153 w5000c5008d634f39.
kern.info<6>: Jun 16 14:41:00 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:41:00 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:00 dfs102 #011Log info 0x3112010c received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:41:00 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:05 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:05 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:05 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:05 dfs102 #011Log info 0x3112010c received for
target 156 w5000c5008d64a041.
kern.info<6>: Jun 16 14:41:05 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:05 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:05 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:07 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:07 dfs102 #011Log info 0x3112010c received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:41:07 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:07 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:07 dfs102 #011Log info 0x3112010c received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:41:07 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:41:15 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:15 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:15 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:15 dfs102 #011Log info 0x3112010c received for
target 156 w5000c5008d64a041.
kern.info<6>: Jun 16 14:41:15 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:15 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:15 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:41:24 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:24 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:41:24 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:24 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:41:24 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:24 dfs102 #011Log info 0x3112010c received for
target 156 w5000c5008d64a041.
kern.info<6>: Jun 16 14:41:24 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:28 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:28 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:28 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:28 dfs102 #011Log info 0x3112010c received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:41:28 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:28 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:28 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:41:32 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:32 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:32 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:32 dfs102 #011Log info 0x3112010c received for
target 156 w5000c5008d64a041.
kern.info<6>: Jun 16 14:41:32 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:32 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:32 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:41:49 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:49 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInf2
kern.warning<4>: Jun 16 14:41:49 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:49 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x31120302
kern.info<6>: Jun 16 14:41:49 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:49 dfs102 #011Log info 0x31120302 received for
target 154 w5000c5008d62eef9.
kern.info<6>: Jun 16 14:41:49 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:53 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:53 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:53 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:53 dfs102 #011Log info 0x3112010c received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:41:53 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:53 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:53 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:41:55 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:55 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:41:55 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:41:55 dfs102 #011Log info 0x3112010c received for
target 157 w5000c5008d6450fd.
kern.info<6>: Jun 16 14:41:55 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:41:55 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:41:55 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:42:11 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:11 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:42:11 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:42:11 dfs102 #011Log info 0x3112010c received for
target 157 w5000c5008d6450fd.
kern.info<6>: Jun 16 14:42:11 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:42:11 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:11 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:42:18 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:18 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.info<6>: Jun 16 14:42:18 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:42:18 dfs102 #011Log info 0x3112010c received for
target 156 w5000c5008d64a041.
kern.info<6>: Jun 16 14:42:18 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:42:18 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:18 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:42:25 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:42:25 dfs102 #011Log info 0x3112010c received for
target 155 w5000c5008d632171.
kern.info<6>: Jun 16 14:42:25 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc
kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event_sync:
event 0xf, IOCStatus=0x8000, IOCLogInfc
kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001 kern.warning]
WARNING: /pci at 0,0/pci8086,3410 at 9/p:
kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event:
IOCStatus=0x8000, IOCLogInfo=0x3112010c
kern.info<6>: Jun 16 14:42:25 dfs102 genunix: [ID 365881 kern.info]
/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
kern.info<6>: Jun 16 14:42:25 dfs102 #011Log info 0x3112010c received for
target 156 w5000c5008d64a041.
kern.info<6>: Jun 16 14:42:25 dfs102 #011scsi_status=0x0,
ioc_status=0x804b, scsi_state=0xc




From daleg at omniti.com  Thu Jun 16 21:18:43 2016
From: daleg at omniti.com (Dale Ghent)
Date: Thu, 16 Jun 2016 17:18:43 -0400
Subject: [OmniOS-discuss] Intel X550 testers wanted
References: <A49E8A9A-5C15-4C04-A915-E804D6EDF485@elemental.org>
Message-ID: <1D7F38F6-E7B4-4DB7-A3DF-153CE7CCB4F4@omniti.com>

All; below is a mail I sent today to the developers at illumos list, submitting my ixgbe patch for review. It adds Intel X550 support. While the coding parts may not be of interest, please skip down to the "What's needed to help" section and, if you can afford some resources and time, follow the instructions on installing a new ixgbe driver to test with.

I'm interested in those with ANY model of card supported by ixgbe, especially if you have one of those old 82598 cards, as it was the one part I could not get ahold of to test with (it's the original ixgbe card and fairly dated now)

I'll welcome feedback either in this thread or directly to myself.

/dale
==================

The following webrev serves to introduce Intel X550 (including X552 and X557) support to ixgbe(7D)

http://elemental.org/webrevs/x550-final/

One may find it in git patch format here:
http://elemental.org/webrevs/0001-6064-ixgbe-needs-X550-support.patch

New adapters supported (and tested) with this patch:
* X550-T2 - PCIe add-on card supporting speeds of 10Gb, 1Gb, 100Mb baseT, as well as 2.5Gb and 5.0Gb NBASE-T (Intel?s pre-802.3bz feature)
* X550EM - Xeon-D SoC embedded X550 MAC, utilizing one of two models of external PHYs: X552 (for SFP+) and X557 (10Gb, 1Gb baseT)

Existing adapters tested with this patch:
* X540-T1
* 82599 SFP (aka X520)

Patch Description
==============

At a high level, there were two intertwined goals with this patch:

1) To introduce support for the Intel X550 family of adapters.
2) To bring the illumos version of the Intel Common Code (ICC) up to date after ~4 years of deltas accumulating between it and FreeBSD (our source for the ICC)

As worked progressed, it became clear that simply adding case statements for the new hardware and a few changes to accommodate adjustments in ICC APIs were not going to be sufficient, and several specific areas required heavy re-working to not only support X550, but also maintain expected behavior with existing adapters. Among these areas of heavy focus are:

* Rewrite of autonegotiation management and its interfacing with GLD
* RSS (Receive-Side Scaling) overhaul to account for differences between new and legacy adapters
* Basic adapter initialization

This patch also piggy-backs on Robert?s recent commit which relocated the ixgbe ICC files to their own directory, allowing us to cleanly exempt them from the prying eyes of lint(1). The updated ICC source files are very lint-noisy now, to such an extent that it would be beyond reasonable effort to add and maintain local corrections.

I would like the thank and acknowledge Robert Mustacchi and Dan McDonald for their patient guidance and encouragement throughout this project.

What?s needed to help test
====================

Since this patch is fairly wide-reaching, touching all previously supported adapters as well as the new ones, my hope is that enough interested parties here can assist in vetting it. These adapters include:

82598 - Important, as this is the one part I do not have
82599 (X520)
X540
X550 (and X550EM on Xeon-D SoC systems)

To encourage testing, I am providing updated ixgbe packages for OmniOS r151014, r15108, and Bloody. Robert Mustacchi has kindly assembled SmartOS images containing this new ixgbe driver code as well.

OmniOS users:
--------------------
OmniOS Bloody users need only to utter 'pkg update' to upgrade their Bloody systems to the latest bits, which include this new ixgbe driver code. For users of OmniOS r151014 or r151018, package archive download and installation instructions may be found here:

http://omnios.omniti.com/media/x550/INSTALL.txt

SmartOS users:
---------------------
SmartOS users can download the following images:

SmartOS ISO:
https://us-east.manta.joyent.com/rmustacc/public/preview/x550/platform-20160616T055400Z.iso

SmartOS USB:
https://us-east.manta.joyent.com/rmustacc/public/preview/x550/platform-20160616T055400Z.usb.bz2

SmartOS Raw Platform:
https://us-east.manta.joyent.com/rmustacc/public/preview/x550/platform-20160616T055400Z.tgz

But wait! There?s more (work)!
=======================

During the course of this work, it became apparent that a few additional areas deserve some attention, but are areas which are more suitable as follow-ups to this initial support patch. Among these areas are:

* Interrupt handler task queue overhaul to convert them to taskq_dispatch_ent
* SFP setup and interrupt handling, with further refinements to autonegotiation logic to accommodate multispeed fiber correctly
* Additional interrupt handlers for currently unclaimed types - 82599 (and newer) thermal sensor alarms and uncorrectable ECC events

I will be filing bugs for these follow-ups once they can be fully (and properly) characterized.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160616/b18eae69/attachment.bin>

From paulb at lctcb.org  Thu Jun 16 21:29:13 2016
From: paulb at lctcb.org (Paul Bucher)
Date: Thu, 16 Jun 2016 21:29:13 +0000
Subject: [OmniOS-discuss] OmniOS & Softlayer
Message-ID: <D84804E7-6454-489E-82C1-AC266CFC16F3@lctcb.org>

Gea,

Thanks for the FYI, I know all too well I should have LSI SAS HBAs but I?m trying to stay within the limits of what Softlayer has on the self. My current boxes at Softlayer I bought and shipped them the correct controllers.

Anyways I?m going to try out the JBOD mode of the 9361 to start with. I?ve noticed Oracle uses 9361 with some of their storage units so there might be hope. Currently I?m waiting on Softlayer?s build team to get approval to rip out the SAS expander based backplane and put in a standard SAS one so I can have a dual controller setup. If the 9361 fails I?ll see about the motherboard SATA ports in AHCI mode, hopefully that?s not too strange of a cabling request for them.

Any comments if I end with the SATA ports how well Intel S3700?s work on them? The drives they use are the good news in the setup.

-Paul

On Thu, 16 Jun 2016 08:34:56 +0200 Guenther Alka <alka at hfg-gmuend.de> wrote:
>The LSI megaRAID 9361 is a hardware raid controller - the wrong type for 
>ZFS.
>You want a HBA controller best with a raidless IT firmware with an LSI 
>2008 or 3008 chipset
>like the LSI 9207 or 9003 or Sata in AHCI mode.
>
>Your options:
>- replace the 9361 with an HBA
>
>or
>- use it as a bootdevice for ESXi and the local datastore
>- pass-through Sata in AHCI mode (enable hotplug for Sata)
>
>or
>- add an HBA
>
>Gea
>
>
>Am 15.06.2016 um 19:44 schrieb Paul Bucher:
>> I?m working on bringing up some new mission critical servers at hosting provider Softlayer and wondering if anyone out there also hosts at Softlayer using OmniOS and what they?ve used for disk HBA?s at Softlayer with OmniOS(just to make it more complicated I use napp-it all in one virtual machine setups). My understanding is the current Xeon v3 servers Softlayer is using LSI megaRAID 9361 cards in them and I?ve been unable to find much about running ZFS on the newer megaraid cards and I really don?t want to do some RAID 0 type of setup that I?ve used in the past. Softlayer is using Supermicro X10DRU-i+ MBs that have a bunch of SATA ports on them hung off the C612 chipset, I?m temped to tell them to use those ports, but I?d like to hear someone else?s experience with these since I now OmniOS doesn?t always play well with more modern kit.
>>
>> So far I?ve had great success with all in one setups in the past on Softlayers older generation of servers, but I?ve had to ship to Softlayer and convenience them to install the standard LSI HBA SAS controllers for me which has the downside that if a box goes down they can?t just spin me up a newer server in an hour or so since it requires me to buy and ship them a new disk controller.
>>
>> -Paul
>>



From danmcd at omniti.com  Thu Jun 16 21:53:53 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Thu, 16 Jun 2016 17:53:53 -0400
Subject: [OmniOS-discuss] New bloody update
Message-ID: <4FB3DCC1-61B7-4289-B44A-44B906AC6C51@omniti.com>

Hello folks!

As Dale hinted, there's a new update on the bloody pkg server:

	http://pkg.omniti.com/omnios/bloody/

with new bloody bits.  "uname -v" will say "omnios-master-7397b49".  Highlights with this update:

	- Intel i40e support, from Joyent.

	- Intel X550 support from OmniTI's own Dale Ghent.

	- pvscsi support from Nexenta.

	- Several small & medium size ZFS fixes from upstream/OpenZFS

No release media have been cut for this update yet.  But I wanted to get these new bits out, so I'm announcing now.

Thanks,
Dan


From bfriesen at simple.dallas.tx.us  Thu Jun 16 22:08:06 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Thu, 16 Jun 2016 17:08:06 -0500 (CDT)
Subject: [OmniOS-discuss] Intel X550 testers wanted
In-Reply-To: <1D7F38F6-E7B4-4DB7-A3DF-153CE7CCB4F4@omniti.com>
References: <A49E8A9A-5C15-4C04-A915-E804D6EDF485@elemental.org>
	<1D7F38F6-E7B4-4DB7-A3DF-153CE7CCB4F4@omniti.com>
Message-ID: <alpine.GSO.2.20.1606161706000.12914@freddy.simplesystems.org>

It is expected that after sufficient successful testing that OmniOS 
will put the updated drivers in its various existing supported 
branches, or will we have to wait until 'bloody' finally becomes the 
next stable?

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

From daleg at omniti.com  Thu Jun 16 22:25:46 2016
From: daleg at omniti.com (Dale Ghent)
Date: Thu, 16 Jun 2016 18:25:46 -0400
Subject: [OmniOS-discuss] Intel X550 testers wanted
In-Reply-To: <alpine.GSO.2.20.1606161706000.12914@freddy.simplesystems.org>
References: <A49E8A9A-5C15-4C04-A915-E804D6EDF485@elemental.org>
	<1D7F38F6-E7B4-4DB7-A3DF-153CE7CCB4F4@omniti.com>
	<alpine.GSO.2.20.1606161706000.12914@freddy.simplesystems.org>
Message-ID: <1672ADFC-9367-45EC-8465-8CC4DF0F50E2@omniti.com>


> On Jun 16, 2016, at 6:08 PM, Bob Friesenhahn <bfriesen at simple.dallas.tx.us> wrote:
> 
> It is expected that after sufficient successful testing that OmniOS will put the updated drivers in its various existing supported branches, or will we have to wait until 'bloody' finally becomes the next stable?

Once ixgbe passes review and testing, it will be made available on 014 (LTS) and 018 (Stable)

This goes for the new i40e driver (for X/XL710 40Gb cards) as well.

/dale
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160616/066da220/attachment.bin>

From alka at hfg-gmuend.de  Fri Jun 17 08:17:16 2016
From: alka at hfg-gmuend.de (Guenther Alka)
Date: Fri, 17 Jun 2016 10:17:16 +0200
Subject: [OmniOS-discuss] OmniOS & Softlayer
In-Reply-To: <D84804E7-6454-489E-82C1-AC266CFC16F3@lctcb.org>
References: <D84804E7-6454-489E-82C1-AC266CFC16F3@lctcb.org>
Message-ID: <8c89f59d-d733-fb76-fbce-e5884e68ab7d@hfg-gmuend.de>

Sata/AHCI 6G is fast and stable so the S3700 should work perfectly

A much faster solution in an AiO setup are NVMes like a P750, P3600 or 
P3700
but the current NVMe driver gives problems in pass-through mode under ESXi

see the discussion with Frank next to your initial mail and the ongoing 
discussion in Illumos-discuss

Gea


Am 16.06.2016 um 23:29 schrieb Paul Bucher:
> Gea,
>
> Thanks for the FYI, I know all too well I should have LSI SAS HBAs but I?m trying to stay within the limits of what Softlayer has on the self. My current boxes at Softlayer I bought and shipped them the correct controllers.
>
> Anyways I?m going to try out the JBOD mode of the 9361 to start with. I?ve noticed Oracle uses 9361 with some of their storage units so there might be hope. Currently I?m waiting on Softlayer?s build team to get approval to rip out the SAS expander based backplane and put in a standard SAS one so I can have a dual controller setup. If the 9361 fails I?ll see about the motherboard SATA ports in AHCI mode, hopefully that?s not too strange of a cabling request for them.
>
> Any comments if I end with the SATA ports how well Intel S3700?s work on them? The drives they use are the good news in the setup.
>
> -Paul
>
> On Thu, 16 Jun 2016 08:34:56 +0200 Guenther Alka <alka at hfg-gmuend.de> wrote:
>> The LSI megaRAID 9361 is a hardware raid controller - the wrong type for
>> ZFS.
>> You want a HBA controller best with a raidless IT firmware with an LSI
>> 2008 or 3008 chipset
>> like the LSI 9207 or 9003 or Sata in AHCI mode.
>>
>> Your options:
>> - replace the 9361 with an HBA
>>
>> or
>> - use it as a bootdevice for ESXi and the local datastore
>> - pass-through Sata in AHCI mode (enable hotplug for Sata)
>>
>> or
>> - add an HBA
>>
>> Gea
>>
>>
>> Am 15.06.2016 um 19:44 schrieb Paul Bucher:
>>> I?m working on bringing up some new mission critical servers at hosting provider Softlayer and wondering if anyone out there also hosts at Softlayer using OmniOS and what they?ve used for disk HBA?s at Softlayer with OmniOS(just to make it more complicated I use napp-it all in one virtual machine setups). My understanding is the current Xeon v3 servers Softlayer is using LSI megaRAID 9361 cards in them and I?ve been unable to find much about running ZFS on the newer megaraid cards and I really don?t want to do some RAID 0 type of setup that I?ve used in the past. Softlayer is using Supermicro X10DRU-i+ MBs that have a bunch of SATA ports on them hung off the C612 chipset, I?m temped to tell them to use those ports, but I?d like to hear someone else?s experience with these since I now OmniOS doesn?t always play well with more modern kit.
>>>
>>> So far I?ve had great success with all in one setups in the past on Softlayers older generation of servers, but I?ve had to ship to Softlayer and convenience them to install the standard LSI HBA SAS controllers for me which has the downside that if a box goes down they can?t just spin me up a newer server in an hour or so since it requires me to buy and ship them a new disk controller.
>>>
>>> -Paul
>>>
>
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-- 
H          f   G
Hochschule f?r Gestaltung
university of design

Schw?bisch Gm?nd
Rektor-Klaus Str. 100
73525 Schw?bisch Gm?nd

Guenther Alka, Dipl.-Ing. (FH)
Leiter des Rechenzentrums
head of computer center

Tel 07171 602 627
Fax 07171 69259
guenther.alka at hfg-gmuend.de
http://rz.hfg-gmuend.de


From cal-s at blue-bolt.com  Fri Jun 17 10:18:11 2016
From: cal-s at blue-bolt.com (Cal Sawyer)
Date: Fri, 17 Jun 2016 11:18:11 +0100
Subject: [OmniOS-discuss] OmniOS & Softlayer
In-Reply-To: <mailman.2929.1466151347.1748.omnios-discuss@lists.omniti.com>
References: <mailman.2929.1466151347.1748.omnios-discuss@lists.omniti.com>
Message-ID: <5763CE63.4050700@blue-bolt.com>

It should be possible to reflash a 9361 into IT mode, making it a 9300, 
non?  Shame to waste $300, though :)

In a past life, when i had a Supermicro VAR building servers for me, i 
got them to reflash the onboard LSI controller on the bench so the 
servers arrived ready to rock.

Side note: If you're working with a VAR that will do that much for you, 
also get them to populate the FRU (inventory) on the BMC with your 
system asset details.  They'll have SM's tool which makes it easy - 
doing it after the fact remotely is a pita.

regards,

Cal Sawyer | Systems Engineer | BlueBolt Ltd
15-16 Margaret Street | London W1W 8RW
+44 (0)20 7637 5575 | www.blue-bolt.com

On 17/06/16 09:15, omnios-discuss-request at lists.omniti.com wrote:
> Message: 2
> Date: Thu, 16 Jun 2016 21:29:13 +0000
> From: Paul Bucher<paulb at lctcb.org>
> To:"omnios-discuss at lists.omniti.com"
> 	<omnios-discuss at lists.omniti.com>
> Subject: Re: [OmniOS-discuss] OmniOS & Softlayer
> Message-ID:<D84804E7-6454-489E-82C1-AC266CFC16F3 at lctcb.org>
> Content-Type: text/plain; charset="utf-8"
>
> Gea,
>
> Thanks for the FYI, I know all too well I should have LSI SAS HBAs but I?m trying to stay within the limits of what Softlayer has on the self. My current boxes at Softlayer I bought and shipped them the correct controllers.
>
> Anyways I?m going to try out the JBOD mode of the 9361 to start with. I?ve noticed Oracle uses 9361 with some of their storage units so there might be hope. Currently I?m waiting on Softlayer?s build team to get approval to rip out the SAS expander based backplane and put in a standard SAS one so I can have a dual controller setup. If the 9361 fails I?ll see about the motherboard SATA ports in AHCI mode, hopefully that?s not too strange of a cabling request for them.
>
> Any comments if I end with the SATA ports how well Intel S3700?s work on them? The drives they use are the good news in the setup.
>
> -Paul
>
> On Thu, 16 Jun 2016 08:34:56 +0200 Guenther Alka<alka at hfg-gmuend.de>  wrote:
>> >The LSI megaRAID 9361 is a hardware raid controller - the wrong type for
>> >ZFS.
>> >You want a HBA controller best with a raidless IT firmware with an LSI
>> >2008 or 3008 chipset
>> >like the LSI 9207 or 9003 or Sata in AHCI mode.
>> >
>> >Your options:
>> >- replace the 9361 with an HBA
>> >
>> >or
>> >- use it as a bootdevice for ESXi and the local datastore
>> >- pass-through Sata in AHCI mode (enable hotplug for Sata)
>> >
>> >or
>> >- add an HBA
>> >
>> >Gea
>> >
>> >
>> >Am 15.06.2016 um 19:44 schrieb Paul Bucher:
>>> >>I?m working on bringing up some new mission critical servers at hosting provider Softlayer and wondering if anyone out there also hosts at Softlayer using OmniOS and what they?ve used for disk HBA?s at Softlayer with OmniOS(just to make it more complicated I use napp-it all in one virtual machine setups). My understanding is the current Xeon v3 servers Softlayer is using LSI megaRAID 9361 cards in them and I?ve been unable to find much about running ZFS on the newer megaraid cards and I really don?t want to do some RAID 0 type of setup that I?ve used in the past. Softlayer is using Supermicro X10DRU-i+ MBs that have a bunch of SATA ports on them hung off the C612 chipset, I?m temped to tell them to use those ports, but I?d like to hear someone else?s experience with these since I now OmniOS doesn?t always play well with more modern kit.
>>> >>
>>> >>So far I?ve had great success with all in one setups in the past on Softlayers older generation of servers, but I?ve had to ship to Softlayer and convenience them to install the standard LSI HBA SAS controllers for me which has the downside that if a box goes down they can?t just spin me up a newer server in an hour or so since it requires me to buy and ship them a new disk controller.
>>> >>
>>> >>-Paul
>>> >>


From mir at miras.org  Fri Jun 17 10:27:37 2016
From: mir at miras.org (mir at miras.org)
Date: Fri, 17 Jun 2016 12:27:37 +0200
Subject: [OmniOS-discuss] Joyent takeover by Samsung
Message-ID: <67ec5e3663646c77e9a0db19e680b697@miras.org>

Hi all,

Anybody knows if Samsung's acquisition of Joyent will have any 
implication for Illumos?
http://www.serverwatch.com/server-news/joyent-acquired-by-samsung.html

----

This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.


From ci4 at outlook.com  Fri Jun 17 11:04:15 2016
From: ci4 at outlook.com (Chavdar Ivanov)
Date: Fri, 17 Jun 2016 12:04:15 +0100
Subject: [OmniOS-discuss] Joyent takeover by Samsung
In-Reply-To: <67ec5e3663646c77e9a0db19e680b697@miras.org>
References: <67ec5e3663646c77e9a0db19e680b697@miras.org>
Message-ID: <DUB403-EAS121C185EB519149B010109CE2570@phx.gbl>


-----Original Message-----
From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On
Behalf Of mir at miras.org
Sent: 17 June 2016 11:28
To: omnios-discuss <omnios-discuss at lists.omniti.com>
Subject: [OmniOS-discuss] Joyent takeover by Samsung

Hi all,

Hi, 
Have a look at the few blog posts available and make up your mind.

--Anybody knows if Samsung's acquisition of Joyent will have any implication
for Illumos?
--http://www.serverwatch.com/server-news/joyent-acquired-by-samsung.html

CEO's:
https://www.joyent.com/blog/samsung-acquires-joyent

Perhaps more interesting in this context, CTO's:
https://www.joyent.com/blog/samsung-acquires-joyent-a-ctos-perspective 

Cheers, 

Chavdar Ivanov

----

This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.

_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

From steve at linuxsuite.org  Fri Jun 17 18:21:53 2016
From: steve at linuxsuite.org (steve at linuxsuite.org)
Date: Fri, 17 Jun 2016 14:21:53 -0400
Subject: [OmniOS-discuss] Scrub leaves pool in wiered state with all
 devices	in "repairing" ?
In-Reply-To: <33C32C9D-1526-4B1D-B494-8EF2DEEF744F@marzocchi.net>
References: <6e7cba92a473ecfcba1cf316f739c243.squirrel@emailmg.netfirms.com>
	<33C32C9D-1526-4B1D-B494-8EF2DEEF744F@marzocchi.net>
Message-ID: <c8dbbdd0f5c450a0073b4d99d1dde08a.squirrel@emailmg.netfirms.com>

> Start praying...
> I think.

        Not sure that changes out comes....

        For some context, this is a zfs pool that is in a 16 slot JBOD
chassis with
each 5 disk raidz1 having a shared hotspare..

        Tried a zfs send but it was having the issue as the scrub. scrub or
zfs send would take "forever" to complete... Also tried srub on another
pool in
the same chassis, same thing.

      I successfully  exported the problematic zfs and installed it into
another JBOD chassis
and imported. scrub and zfs send now run fine. So it isn't the
disks, must be cable or chassis or HBA or ....

           thanx - steve



>
> So many read errors mean the disks are all dying. If you get to the end of
> the scrub you should copy everything to a new pool. Don't bother replacing
> one by one because every replacement consists of a full scrub and that
> means too many scrubs, they would not survive that much stress. And in any
> case, since they are all to be replaced, making a new pool is easier.
>
> Wait for other opinions but when read errors are abundant and everywhere
> and when you have raidz1...
>
> Using that spare as additional redundancy (raidz2) from the beginning
> gives more fault tolerance than keeping it running without using it.
> Hot spares are no more such good idea.
>
> Olaf
>
>
>
> Il 16 giugno 2016 21:01:38 CEST, steve at linuxsuite.org ha scritto:
>>
>>Howdy!
>>
>>     I started a scrub on a zfs pool and it appears to be stuck in some
>>wierd state. Details below...  Ideas on the problem or how to
>>proceed???
>>
>>       Thanx - steve
>>
>>   Server is a DELL R710
>>
>>   OmniOS v11 r151014
>>
>>  SAS controller is a LSI 9201. Here is output from lsiutils
>>
>>Main menu, select an option:  [1-99 or e/p/w or 0 to quit] 69
>>
>>Seg/Bus/Dev/Fun    Board Name       Board Assembly   Board Tracer
>> 0   5   0   0     SAS9201-16e      H3-25379-01D     SV04414910
>>
>>
>>
>>**********   Here is a zpool status **************
>>
>>
>>
>> pool: dfs1_data31
>> state: ONLINE
>>status: One or more devices has experienced an unrecoverable error.  An
>>   attempt was made to correct the error.  Applications are unaffected.
>>action: Determine if the device needs to be replaced, and clear the
>>errors
>>        using 'zpool clear' or replace the device with 'zpool replace'.
>>   see: http://illumos.org/msg/ZFS-8000-9P
>>  scan: scrub in progress since Thu Jun 16 10:25:17 2016
>>81.3G scanned out of 16.9T at 5.65M/s, (scan is slow, no estimated
>>time)
>>    3.33G repaired, 0.47% done
>>config:
>>
>>        NAME                         STATE     READ WRITE CKSUM
>>        dfs1_data31                  ONLINE       0     0     0
>>          raidz1-0                   ONLINE       0     0     0
>>       c0t5000C5008D634F3Bd0s0  ONLINE       9     0     0  (repairing)
>>       c0t5000C5008D632173d0s0  ONLINE      18     0     0  (repairing)
>>       c0t5000C5008D64A043d0s0  ONLINE       8     0     0  (repairing)
>>       c0t5000C5008D6450FFd0s0  ONLINE      10     0     0  (repairing)
>>       c0t5000C5008D62EEFBd0s0  ONLINE      18     0     0  (repairing)
>>        spares
>>          c7t5000CCA03B699D71d0s0    AVAIL
>>
>>errors: No known data errors
>>
>>
>>
>>*****           Here are log entries...  *******
>>
>>
>>
>>kern.warning<4>: Jun 16 14:40:30 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:30 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:40:30 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:30 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:40:30 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:30 dfs102 #011Log info 0x3112010c received
>>for
>>target 154 w5000c5008d62eef9.
>>kern.info<6>: Jun 16 14:40:30 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:40:31 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:31 dfs102 #011Log info 0x3112010c received
>>for
>>target 156 w5000c5008d64a041.
>>kern.info<6>: Jun 16 14:40:31 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:40:31 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:31 dfs102 #011Log info 0x3112010c received
>>for
>>target 153 w5000c5008d634f39.
>>kern.info<6>: Jun 16 14:40:31 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:31 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:31 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:40:37 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:37 dfs102 #011Log info 0x3112010c received
>>for
>>target 154 w5000c5008d62eef9.
>>kern.info<6>: Jun 16 14:40:37 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:40:37 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:37 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:40:37 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:37 dfs102 #011Log info 0x3112010c received
>>for
>>target 153 w5000c5008d634f39.
>>kern.info<6>: Jun 16 14:40:37 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:45 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:45 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:40:45 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:45 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:40:45 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:45 dfs102 #011Log info 0x3112010c received
>>for
>>target 154 w5000c5008d62eef9.
>>kern.info<6>: Jun 16 14:40:45 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:48 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:48 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:40:48 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:48 dfs102 #011Log info 0x3112010c received
>>for
>>target 154 w5000c5008d62eef9.
>>kern.info<6>: Jun 16 14:40:48 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:48 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:48 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:40:57 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:57 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInf2
>>kern.warning<4>: Jun 16 14:40:57 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:57 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x31120302
>>kern.info<6>: Jun 16 14:40:57 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:57 dfs102 #011Log info 0x31120302 received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:40:57 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:40:59 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:59 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:40:59 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:40:59 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:40:59 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:40:59 dfs102 #011Log info 0x3112010c received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:40:59 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:41:00 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:00 dfs102 #011Log info 0x3112010c received
>>for
>>target 153 w5000c5008d634f39.
>>kern.info<6>: Jun 16 14:41:00 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:41:00 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:00 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:41:00 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:00 dfs102 #011Log info 0x3112010c received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:41:00 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:05 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:05 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:05 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:05 dfs102 #011Log info 0x3112010c received
>>for
>>target 156 w5000c5008d64a041.
>>kern.info<6>: Jun 16 14:41:05 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:05 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:05 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:07 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:07 dfs102 #011Log info 0x3112010c received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:41:07 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:07 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:07 dfs102 #011Log info 0x3112010c received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:41:07 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:07 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:07 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:41:15 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:15 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:15 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:15 dfs102 #011Log info 0x3112010c received
>>for
>>target 156 w5000c5008d64a041.
>>kern.info<6>: Jun 16 14:41:15 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:15 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:15 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:41:24 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:24 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:41:24 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:24 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:41:24 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:24 dfs102 #011Log info 0x3112010c received
>>for
>>target 156 w5000c5008d64a041.
>>kern.info<6>: Jun 16 14:41:24 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:28 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:28 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:28 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:28 dfs102 #011Log info 0x3112010c received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:41:28 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:28 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:28 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:41:32 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:32 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:32 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:32 dfs102 #011Log info 0x3112010c received
>>for
>>target 156 w5000c5008d64a041.
>>kern.info<6>: Jun 16 14:41:32 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:32 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:32 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:41:49 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:49 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInf2
>>kern.warning<4>: Jun 16 14:41:49 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:49 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x31120302
>>kern.info<6>: Jun 16 14:41:49 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:49 dfs102 #011Log info 0x31120302 received
>>for
>>target 154 w5000c5008d62eef9.
>>kern.info<6>: Jun 16 14:41:49 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:53 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:53 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:53 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:53 dfs102 #011Log info 0x3112010c received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:41:53 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:53 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:53 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:41:55 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:55 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:41:55 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:41:55 dfs102 #011Log info 0x3112010c received
>>for
>>target 157 w5000c5008d6450fd.
>>kern.info<6>: Jun 16 14:41:55 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:41:55 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:41:55 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:42:11 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:11 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:42:11 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:42:11 dfs102 #011Log info 0x3112010c received
>>for
>>target 157 w5000c5008d6450fd.
>>kern.info<6>: Jun 16 14:42:11 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:42:11 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:11 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:42:18 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:18 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.info<6>: Jun 16 14:42:18 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:42:18 dfs102 #011Log info 0x3112010c received
>>for
>>target 156 w5000c5008d64a041.
>>kern.info<6>: Jun 16 14:42:18 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:42:18 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:18 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:42:25 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:42:25 dfs102 #011Log info 0x3112010c received
>>for
>>target 155 w5000c5008d632171.
>>kern.info<6>: Jun 16 14:42:25 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event_sync:
>>event 0xf, IOCStatus=0x8000, IOCLogInfc
>>kern.warning<4>: Jun 16 14:42:25 dfs102 genunix: [ID 243001
>>kern.warning]
>>WARNING: /pci at 0,0/pci8086,3410 at 9/p:
>>kern.warning<4>: Jun 16 14:42:25 dfs102 #011mptsas_handle_event:
>>IOCStatus=0x8000, IOCLogInfo=0x3112010c
>>kern.info<6>: Jun 16 14:42:25 dfs102 genunix: [ID 365881 kern.info]
>>/pci at 0,0/pci8086,3410 at 9/pci1000,30d0 at 0 (:
>>kern.info<6>: Jun 16 14:42:25 dfs102 #011Log info 0x3112010c received
>>for
>>target 156 w5000c5008d64a041.
>>kern.info<6>: Jun 16 14:42:25 dfs102 #011scsi_status=0x0,
>>ioc_status=0x804b, scsi_state=0xc
>>
>>
>>
>>_______________________________________________
>>OmniOS-discuss mailing list
>>OmniOS-discuss at lists.omniti.com
>>http://lists.omniti.com/mailman/listinfo/omnios-discuss
>



From eric.sproul at circonus.com  Fri Jun 17 18:32:16 2016
From: eric.sproul at circonus.com (Eric Sproul)
Date: Fri, 17 Jun 2016 14:32:16 -0400
Subject: [OmniOS-discuss] Scrub leaves pool in wiered state with all
 devices in "repairing" ?
In-Reply-To: <c8dbbdd0f5c450a0073b4d99d1dde08a.squirrel@emailmg.netfirms.com>
References: <6e7cba92a473ecfcba1cf316f739c243.squirrel@emailmg.netfirms.com>
	<33C32C9D-1526-4B1D-B494-8EF2DEEF744F@marzocchi.net>
	<c8dbbdd0f5c450a0073b4d99d1dde08a.squirrel@emailmg.netfirms.com>
Message-ID: <CAO8hXRCBwK5NPUXQ-LaVHFQqUTARqGHsR6sWKqBEwzmF5hP1eg@mail.gmail.com>

On Fri, Jun 17, 2016 at 2:21 PM,  <steve at linuxsuite.org> wrote:
>       I successfully  exported the problematic zfs and installed it into
> another JBOD chassis
> and imported. scrub and zfs send now run fine. So it isn't the
> disks, must be cable or chassis or HBA or ....

FWIW there is a handy tool [1] that decodes LSI log info codes.
Looking at your logs, there are two unique IOCLogInfo codes:

IOCLogInfo=0x3112010c
IOCLogInfo=0x31120302

$ ./lsi_decode_loginfo.py 0x3112010c
Value     3112010Ch
Type:     30000000h SAS
Origin:   01000000h PL
Code:     00120000h PL_LOGINFO_CODE_ABORT See Sub-Codes below
(PL_LOGINFO_SUB_CODE)
Sub Code: 00000100h PL_LOGINFO_SUB_CODE_OPEN_FAILURE
SubSub Code: 0000000Ch PL_LOGINFO_SUB_CODE_OPEN_FAIL_OPEN_TIMEOUT_EXP

$ ./lsi_decode_loginfo.py 0x31120302
Value     31120302h
Type:     30000000h SAS
Origin:   01000000h PL
Code:     00120000h PL_LOGINFO_CODE_ABORT See Sub-Codes below
(PL_LOGINFO_SUB_CODE)
Sub Code: 00000300h PL_LOGINFO_SUB_CODE_WRONG_REL_OFF_OR_FRAME_LENGTH
Unparsed   00000002h

If I had to hazard a guess I'd say there's a low-level issue in the
SAS fabric, maybe a bad expander or cable that's disrupting
everything.  The HBA is aborting the commands it's waiting for answers
to, either because the target never responds, or in the latter case,
possibly corruption of the protocol traffic.  This would seem to align
with your finding that moving the disks to a new chassis made the
issue go away.

Eric

[1] https://github.com/baruch/lsi_decode_loginfo

From gary at genashor.com  Sat Jun 18 11:39:45 2016
From: gary at genashor.com (Gary Gendel)
Date: Sat, 18 Jun 2016 07:39:45 -0400
Subject: [OmniOS-discuss] SECURITY AND FEATURE UPDATES for OmniOS LTS,
 Stable, and old-Stable
In-Reply-To: <C42EF447-EDDC-4D3C-8A11-0A5C54A92E1E@omniti.com>
References: <FD4BAABC-DA92-408D-BDDA-AACD52079B27@omniti.com>
	<5756D52F.1010109@genashor.com>
	<C42EF447-EDDC-4D3C-8A11-0A5C54A92E1E@omniti.com>
Message-ID: <d407e58a-635e-ae7d-f6d6-1f9cf387eef9@genashor.com>

Finally got around to trying this again.  Unfortunately, it froze before 
anything was written to the logs.  The console displayed this before 
hanging:

SunOS Release 5.11 Version omnios-r151818-95eaa7e 64-bit
Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
WARNING: illegal PCI request: offset = f48, size = 2
WARNING: illegal PCI request: offset = 100, size = 4
WARNING: illegal PCI request: offset = f48, size = 2
WARNING: illegal PCI request: offset = 100, size = 4
WARNING: illegal PCI request: offset = f48, size = 2
WARNING: illegal PCI request: offset = 100, size = 4
WARNING: illegal PCI request: offset = f48, size = 2
WARNING: illegal PCI request: offset = 100, size = 4
WARNING: illegal PCI request: offset = 100, size = 4
WARNING: illegal PCI request: offset = 100, size = 4

That's all I've got.  I'd like to upgrade but I'm not sure where to go 
from here.

Gary

On 6/7/2016 10:50 AM, Dale Ghent wrote:
> Please do, we would of course be very interested in what the errors are.
>
> You can mount the updated BE and see if the errors made it into the logs before it hung.
>
> /dale
>
>> On Jun 7, 2016, at 10:07 AM, Gary Gendel <gary at genashor.com> wrote:
>>
>> Thanks for the update.  I'm on 151018 and after the update it wouldn't boot so I rolled back to the previous BE.  I got a whole lot of PCI overflow errors (I think since these were on the console) and then it hung.
>>
>> I suspect the bge network driver as this has caused me issues in the past which was the impetus for my move from OI to OmniOS.  I didn't see anything interesting in the kernel logs.  I'd like to try again but where can I find information on the proper way to capture the problem so I can report it properly.
>>
>> Gary
>>
>> On 06/06/2016 02:47 PM, Dan McDonald wrote:
>>> Please "pkg update" on your OmniOS r151014, r151016, or r151018 machines at your earliest convenience.
>>>
>>> The following security fixes are on ALL THREE:
>>>
>>> 	? libxml update to 2.9.4
>>> 	? DTrace stability fixes (illumos 7033-7035)
>>> 	? setid binaries disallow ld.so.1's $ORIGIN (illumos 6987)
>>> 	? ZFS no longer bleeds zvol entries into non-global zones (illumos 7019,7020)
>>> 	? NTP to 4.2.8p8
>>> 	? expat to 2.1.1 (with CVE 2016-0718 fix)
>>>
>>> The following other fixes are on r151014 and r151018:
>>>
>>> 	? missing MCFG table should lead to I/O PCIe config access (illumos 6859)
>>> 	? allow sendfile() on AF_UNIX sockets (illumos 6861)
>>> 	? ZFS-helper: kernel virtual memory fragmentation leads to hang (illumos 6914)
>>> 	? STMF kstat free is using an improper size for kmem_free(). (illumos 6938)
>>> 	? Driver support for Solarflare 10G and 40G ethernet
>>>
>>> The following are new to r151014, but are already on r151018:
>>>
>>> 	? Timezone, USB, and PCI data files updates. (Now matches r151018)
>>> 	? Driver support for vmxnet3s
>>> 	? MSI-X support fixed for virtio
>>> 	? The debug.illumos pkg(5) variant.
>>>
>>> Each release's release notes have been updated, and install media for r151014 and r151018 have been updated as well.
>>>
>>> Bloody will be getting an IPS-only update by the end of the day.  Watch for that in a separate mail.
>>>
>>> Thank you, and happy updating!
>>> Dan
>>>
>>> _______________________________________________
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss at lists.omniti.com
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss



From mir at miras.org  Sat Jun 18 21:25:59 2016
From: mir at miras.org (Michael Rasmussen)
Date: Sat, 18 Jun 2016 23:25:59 +0200
Subject: [OmniOS-discuss] bareos instead of bacula
Message-ID: <20160618232559.18503f2c@sleipner.datanom.net>

Hi all,

I am wondering why omniti-ms contains bacula and not bareos. bacula OSS
version seems more or less to be abandoned while bareos is actively
maintained.

So why not replace bacula with bareos?

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
/usr/games/fortune -es says:
An editor is one who separates the wheat from the chaff and prints the
chaff. -- Adlai Stevenson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160618/1d1ad171/attachment.bin>

From daleg at omniti.com  Sat Jun 18 22:01:26 2016
From: daleg at omniti.com (Dale Ghent)
Date: Sat, 18 Jun 2016 18:01:26 -0400
Subject: [OmniOS-discuss] bareos instead of bacula
In-Reply-To: <20160618232559.18503f2c@sleipner.datanom.net>
References: <20160618232559.18503f2c@sleipner.datanom.net>
Message-ID: <7829B98D-AF93-44CA-88C0-9E1F9BAE6939@omniti.com>


The omniti-ms (OmniTI Managed Services) repo is a repository that is provided as a convenience to non-OmniTI users; it contains software we currently use or formerly utilized ourselves for our various customers and internal projects.

As such, it carries with it no warranty regarding being up to date for any given software package, or contain the successor projects to ones currently there. This is explained on the Packaging wiki page:

https://omnios.omniti.com/wiki.php/Packaging


> On Jun 18, 2016, at 5:25 PM, Michael Rasmussen <mir at miras.org> wrote:
> 
> Hi all,
> 
> I am wondering why omniti-ms contains bacula and not bareos. bacula OSS
> version seems more or less to be abandoned while bareos is actively
> maintained.
> 
> So why not replace bacula with bareos?
> 
> --
> Hilsen/Regards
> Michael Rasmussen
> 
> Get my public GnuPG keys:
> michael <at> rasmussen <dot> cc
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
> mir <at> datanom <dot> net
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
> mir <at> miras <dot> org
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
> --------------------------------------------------------------
> /usr/games/fortune -es says:
> An editor is one who separates the wheat from the chaff and prints the
> chaff. -- Adlai Stevenson
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160618/5aebfbdc/attachment.bin>

From matej at zunaj.si  Sun Jun 19 08:43:24 2016
From: matej at zunaj.si (=?utf-8?Q?Matej_=C5=BDerovnik?=)
Date: Sun, 19 Jun 2016 10:43:24 +0200
Subject: [OmniOS-discuss] Scrub leaves pool in wiered state with all
	devices in "repairing" ?
In-Reply-To: <CAO8hXRCBwK5NPUXQ-LaVHFQqUTARqGHsR6sWKqBEwzmF5hP1eg@mail.gmail.com>
References: <6e7cba92a473ecfcba1cf316f739c243.squirrel@emailmg.netfirms.com>
	<33C32C9D-1526-4B1D-B494-8EF2DEEF744F@marzocchi.net>
	<c8dbbdd0f5c450a0073b4d99d1dde08a.squirrel@emailmg.netfirms.com>
	<CAO8hXRCBwK5NPUXQ-LaVHFQqUTARqGHsR6sWKqBEwzmF5hP1eg@mail.gmail.com>
Message-ID: <03787A28-0BEF-4D2D-B5A6-94F174397DFA@zunaj.si>

Hey there,

I was getting the same 0x31120302 error on a brand new Supermicro JBOD chasis. I changed the JBOD with a different one and I?m not seeing those problems anymore. I sent my old chasis to service since there is probably a problem with the backplane or something (all target numbers, that kernel logged, were on the same backplane in the JBOD and I was getting errors on drives that were active as well as on hot spare drives).

Just my 2 cents?

Matej

> On 17 Jun 2016, at 20:32, Eric Sproul <eric.sproul at circonus.com> wrote:
> 
> On Fri, Jun 17, 2016 at 2:21 PM,  <steve at linuxsuite.org> wrote:
>>      I successfully  exported the problematic zfs and installed it into
>> another JBOD chassis
>> and imported. scrub and zfs send now run fine. So it isn't the
>> disks, must be cable or chassis or HBA or ....
> 
> FWIW there is a handy tool [1] that decodes LSI log info codes.
> Looking at your logs, there are two unique IOCLogInfo codes:
> 
> IOCLogInfo=0x3112010c
> IOCLogInfo=0x31120302
> 
> $ ./lsi_decode_loginfo.py 0x3112010c
> Value     3112010Ch
> Type:     30000000h SAS
> Origin:   01000000h PL
> Code:     00120000h PL_LOGINFO_CODE_ABORT See Sub-Codes below
> (PL_LOGINFO_SUB_CODE)
> Sub Code: 00000100h PL_LOGINFO_SUB_CODE_OPEN_FAILURE
> SubSub Code: 0000000Ch PL_LOGINFO_SUB_CODE_OPEN_FAIL_OPEN_TIMEOUT_EXP
> 
> $ ./lsi_decode_loginfo.py 0x31120302
> Value     31120302h
> Type:     30000000h SAS
> Origin:   01000000h PL
> Code:     00120000h PL_LOGINFO_CODE_ABORT See Sub-Codes below
> (PL_LOGINFO_SUB_CODE)
> Sub Code: 00000300h PL_LOGINFO_SUB_CODE_WRONG_REL_OFF_OR_FRAME_LENGTH
> Unparsed   00000002h
> 
> If I had to hazard a guess I'd say there's a low-level issue in the
> SAS fabric, maybe a bad expander or cable that's disrupting
> everything.  The HBA is aborting the commands it's waiting for answers
> to, either because the target never responds, or in the latter case,
> possibly corruption of the protocol traffic.  This would seem to align
> with your finding that moving the disks to a new chassis made the
> issue go away.
> 
> Eric
> 
> [1] https://github.com/baruch/lsi_decode_loginfo
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3468 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160619/58fca76d/attachment-0001.bin>

From mir at miras.org  Sun Jun 19 22:43:16 2016
From: mir at miras.org (Michael Rasmussen)
Date: Mon, 20 Jun 2016 00:43:16 +0200
Subject: [OmniOS-discuss] bareos instead of bacula
In-Reply-To: <7829B98D-AF93-44CA-88C0-9E1F9BAE6939@omniti.com>
References: <20160618232559.18503f2c@sleipner.datanom.net>
	<7829B98D-AF93-44CA-88C0-9E1F9BAE6939@omniti.com>
Message-ID: <20160620004316.0b856213@sleipner.datanom.net>

On Sat, 18 Jun 2016 18:01:26 -0400
Dale Ghent <daleg at omniti.com> wrote:

> The omniti-ms (OmniTI Managed Services) repo is a repository that is provided as a convenience to non-OmniTI users; it contains software we currently use or formerly utilized ourselves for our various customers and internal projects.
> 
Understood.

So in light of the above I have packaged bareos myself and made it
publicly available here: http://pkg.datanom.net/

The version of bareos is the latest stable release which is 15.2.

Since this is my first package I would very much like to get feedback.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
/usr/games/fortune -es says:
He hated being thought of as one of those people that wore stupid
ornamental armour. It was gilt by association.
		-- Terry Pratchett, "Night Watch"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160620/1d321dc8/attachment.bin>

From danmcd at omniti.com  Tue Jun 21 04:59:57 2016
From: danmcd at omniti.com (Dan McDonald)
Date: Tue, 21 Jun 2016 00:59:57 -0400
Subject: [OmniOS-discuss] Experimental LX repo available for play
Message-ID: <319FC5E3-034B-4B27-9AC6-ED9D77661217@omniti.com>

It doesn't do LX yet, but its lipkg and ipkg pass smoke tests, and you can see the very larval "lx_install" program by configuring an LX zone with zonecfg(1M), and attempting an installation (which doesn't work yet) with zoneadm(1M).

Here's the repo:

	http://pkg.omniti.com/omnios/LX/

The idea is it will be close to the bloody repo, but instead of illumos-omnios:master and omnios-build:master, it will be the LX for OmniOS gates: io-lx-public and ob-lx-public, seen here:

	http://github.com/danmcd/

As I continue, I hope to put progress in LX up on that repo.

Thanks,
Dan


From henrikj at henkis.net  Wed Jun 22 19:22:52 2016
From: henrikj at henkis.net (henrikj at henkis.net)
Date: Wed, 22 Jun 2016 21:22:52 +0200
Subject: [OmniOS-discuss] I/O to pool seems to be hung
Message-ID: <DAB96640-CA0B-436F-8A33-DB40EC67304F@henkis.net>

Hi,

We have a few nodes with 36 internal disk each connected with LSI SAS9207-8i. Now multiple times different servers have crashed with hanging I/O, with one disk in the pool missing after reboot. A power-cycle have solved the problem so far. We have downgraded the firmware in the controllers (to 18)  since there are know problems with the latest firmware and illumos, but this one we have not seen before.

We are running OmniOS 151018.

Here is some output from the crash dump:

/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Timeout of 60 seconds expired with 12 commands on target 12 lun 0.
WARNING: /pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Disconnected command timeout for target 12 w5000c5007bc6d89d, enclosure 2
WARNING: /pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        mptsas_handle_event_sync: event 0xf, IOCStatus=0x8000, IOCLogInfo=0x31170000
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31130000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Log info 0x31140000 received for target 12 w5000c5007bc6d89d.
        scsi_status=0x0, ioc_status=0x8048, scsi_state=0xc
WARNING: /pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        mptsas_check_task_mgt: Task 0x3 failed. IOCStatus=0x4a IOCLogInfo=0x0 target=12

WARNING: /pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        mptsas_ioc_task_management failed try to reset ioc to recovery!
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        MPT Firmware version v18.0.0.0 (SAS2308)
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        mpt_sas0 MPI Version 0x200
/pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        mpt0: IOC Operational.
WARNING: /scsi_vhci (scsi_vhci0):
        /scsi_vhci/disk at g5000c5007bc6d89d (sd5): Command Timeout on path mpt_sas1/disk at w5000c5007bc6d8
9d,0
WARNING: /pci at 0,0/pci8086,2f04 at 2/pci1000,3020 at 0 (mpt_sas0):
        Target 12 reset for command timeout recovery failed!
NOTICE: SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major


panic[cpu0]/thread=fffff001e86cbc40:
I/O to pool ?server03zp01' appears to be hung.


fffff001e86cba20 zfs:vdev_deadman+10b ()
fffff001e86cba70 zfs:vdev_deadman+4a ()
fffff001e86cbac0 zfs:vdev_deadman+4a ()
fffff001e86cbaf0 zfs:spa_deadman+ad ()
fffff001e86cbb90 genunix:cyclic_softint+fd ()
fffff001e86cbba0 unix:cbe_low_level+14 ()
fffff001e86cbbf0 unix:av_dispatch_softvect+78 ()
fffff001e86cbc20 apix:apix_dispatch_softint+35 ()
fffff001e8605990 unix:switch_sp_and_call+13 ()
fffff001e86059e0 apix:apix_do_softint+6c ()
fffff001e8605a40 apix:apix_do_interrupt+34a ()
fffff001e8605a50 unix:_interrupt+ba ()
fffff001e8605bc0 unix:acpi_cpu_cstate+11b ()
fffff001e8605bf0 unix:cpu_acpi_idle+8d ()
fffff001e8605c00 unix:cpu_idle_adaptive+13 ()
fffff001e8605c20 unix:idle+a7 ()
fffff001e8605c30 unix:thread_start+8 ()

syncing file systems...
 done
dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel
NOTICE: ahci0: ahci_tran_reset_dport port 0 reset port

Anyone seen this?

Regards
Henrik

From Josh.Barton at usurf.usu.edu  Wed Jun 22 23:06:10 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Wed, 22 Jun 2016 23:06:10 +0000
Subject: [OmniOS-discuss] ZPOOL disk performance on Supermicro with LSI
	9300-8i
Message-ID: <47c83c52ca6c48b4a2a46e0c707de3ce@Ek.usurf.usu.edu>

We just built a Supermicro server with 3 LSI 9300-8i HBAs and 12 2 TB hard drives and are concerned about slowness after running a postgres benchmark. We also ran this benchmark on an HP Proliant 380 G9 with 14 disks and on a Sunfire server running OmniOS as well. The results showed the HP Proliant being many times faster (orders of magnitude) than the newer Supermicro server and the Sunfire.

Any ideas why the HP is so much faster? It just has one Smart Array Controller which I didn't think would be faster than JBOD

Results:
Sunfire
-bash-4.2# ./pgbench -c 50 -s 100 -t 100 -U postgres climate
Scale option ignored, using pgbench_branches table count = 1
starting vacuum...end.
transaction type: TPC-B (sort of)
scaling factor: 1
query mode: simple
number of clients: 50
number of threads: 1
number of transactions per client: 100
number of transactions actually processed: 5000/5000
latency average: 0.000 ms
tps = 76.249498 (including connections establishing)
tps = 76.940244 (excluding connections establishing)


Supermicro Server
-bash-4.3$ ./pgbench -c 50 -s 100 -t 100 -U postgres climate
Scale option ignored, using pgbench_branches table count = 1
starting vacuum...end.
transaction type: TPC-B (sort of)
scaling factor: 1
query mode: simple
number of clients: 50
number of threads: 1
number of transactions per client: 100
number of transactions actually processed: 5000/5000
latency average: 0.000 ms
tps = 119.929719 (including connections establishing)
tps = 120.786598 (excluding connections establishing)
tps is the metric we've been comparing (tx per second)

HP Server
root at cldb3:/usr/local/src/postgresql-9.4.4/contrib/pgbench#<mailto:root at cldb3:/usr/local/src/postgresql-9.4.4/contrib/pgbench#> ./pgbench -c 50 -s 100 -t 100 -U postgres climate
Scale option ignored, using pgbench_branches table count = 1
starting vacuum...end.
transaction type: TPC-B (sort of)
scaling factor: 1
query mode: simple
number of clients: 50
number of threads: 1
number of transactions per client: 100
number of transactions actually processed: 5000/5000
latency average: 0.000 ms
tps = 1068.027362 (including connections establishing)
tps = 1254.114121 (excluding connections establishing)


Thank you all,

Josh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160622/cecef42d/attachment.html>

From mailinglists at qutic.com  Thu Jun 23 12:10:56 2016
From: mailinglists at qutic.com (qutic development)
Date: Thu, 23 Jun 2016 14:10:56 +0200
Subject: [OmniOS-discuss] ZPOOL disk performance on Supermicro with LSI
	9300-8i
In-Reply-To: <47c83c52ca6c48b4a2a46e0c707de3ce@Ek.usurf.usu.edu>
References: <47c83c52ca6c48b4a2a46e0c707de3ce@Ek.usurf.usu.edu>
Message-ID: <10217EE6-B4D6-48F4-8F3B-9E015B165632@qutic.com>


> Am 23.06.2016 um 01:06 schrieb Josh Barton <Josh.Barton at usurf.usu.edu>:
> 
> Any ideas why the HP is so much faster? It just has one Smart Array Controller which I didn?t think would be faster than JBOD

Could you please provide a few more information about the servers? CPU speed, cores, RAM, etc?

OmniOS tuned or all raw installations? All the same OmniOS version?

- Stefan

From stephan.budach at JVM.DE  Thu Jun 23 12:50:55 2016
From: stephan.budach at JVM.DE (Stephan Budach)
Date: Thu, 23 Jun 2016 14:50:55 +0200
Subject: [OmniOS-discuss] ZPOOL disk performance on Supermicro with LSI
 9300-8i
In-Reply-To: <10217EE6-B4D6-48F4-8F3B-9E015B165632@qutic.com>
References: <47c83c52ca6c48b4a2a46e0c707de3ce@Ek.usurf.usu.edu>
	<10217EE6-B4D6-48F4-8F3B-9E015B165632@qutic.com>
Message-ID: <b1e28781-8fc4-1fb2-fc52-557cc3a36bfe@jvm.de>

Am 23.06.16 um 14:10 schrieb qutic development:
>> Am 23.06.2016 um 01:06 schrieb Josh Barton <Josh.Barton at usurf.usu.edu>:
>>
>> Any ideas why the HP is so much faster? It just has one Smart Array Controller which I didn?t think would be faster than JBOD
> Could you please provide a few more information about the servers? CPU speed, cores, RAM, etc?
>
> OmniOS tuned or all raw installations? All the same OmniOS version?
>
> - Stefan
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
Smells like caching on the HP?

You could only compare those results, if you'd stuff your LSIs into the 
HP as well. A magnitude is quite a lot in that regard. Then, what does 
this benchmark actually do? How much of it is CPU bound and how much is 
I/O bound? And I know, that the SmartArray often times has quite an 
amount of RAM cache on board, especially, if you buy one those bigger 
boxes, like a 380.

Cheers,
Stephan

From Josh.Barton at usurf.usu.edu  Thu Jun 23 18:10:54 2016
From: Josh.Barton at usurf.usu.edu (Josh Barton)
Date: Thu, 23 Jun 2016 18:10:54 +0000
Subject: [OmniOS-discuss] ZPOOL disk performance on Supermicro with LSI
 9300-8i
In-Reply-To: <10217EE6-B4D6-48F4-8F3B-9E015B165632@qutic.com>
References: <47c83c52ca6c48b4a2a46e0c707de3ce@Ek.usurf.usu.edu>
	<10217EE6-B4D6-48F4-8F3B-9E015B165632@qutic.com>
Message-ID: <20398423923b43f5aa10ae62100bd35c@Ek.usurf.usu.edu>

        HP is running: 151012
        Sunfire:            151010
        Supermicro:    151014

Supermicro specs:
_______________________________________________________________
Item Number                                       |       Item Type                    |     # of Units    |
CSE-216BAC-R920LPB                        |        Chassis	                                                    |
LSI 9300-8i                                           |    Disk Controller               |    3.00              |
 X10DRi-T4+                                         |   Motherboard                  |    1.00              |
Micron/Crucial CT16G4RFD4213     |  16 GB Ram                        |     12.00           |
Samsung M393A4K40BB0-CPB        |  32 GB Ram                        |     8.00              |
Seagate ST2000NX0243                    |  2TB Drive                           |    12.00             |
Intel Xeon E5-2637 v3 Quad-core   | 3.5 GHz CPU                       |     2.00              |
--------------------------------------------------------------------------------------------------------
The benchmarks shouldn't be CPU bound in the case of the Supermicro. It has twice the # of processors of the HP but the HP has 8 cores total in the one processor (Xeon E5-2640 @ 2ghz). Postgres prefers higher CPU frequency rather than  number of cores. The Sunfire has 48 drives and so writes should be spread fairly evenly, reducing writes per drive. Is there any other information I can provide? 

Josh  


-----Original Message-----
From: qutic development [mailto:mailinglists at qutic.com] 
Sent: Thursday, June 23, 2016 6:11 AM
To: Josh Barton <Josh.Barton at usurf.usu.edu>
Cc: omnios-discuss <omnios-discuss at lists.omniti.com>
Subject: Re: [OmniOS-discuss] ZPOOL disk performance on Supermicro with LSI 9300-8i


> Am 23.06.2016 um 01:06 schrieb Josh Barton <Josh.Barton at usurf.usu.edu>:
> 
> Any ideas why the HP is so much faster? It just has one Smart Array Controller which I didn?t think would be faster than JBOD

Could you please provide a few more information about the servers? CPU speed, cores, RAM, etc?

OmniOS tuned or all raw installations? All the same OmniOS version?

- Stefan

From bfriesen at simple.dallas.tx.us  Thu Jun 23 21:05:08 2016
From: bfriesen at simple.dallas.tx.us (Bob Friesenhahn)
Date: Thu, 23 Jun 2016 16:05:08 -0500 (CDT)
Subject: [OmniOS-discuss] ZPOOL disk performance on Supermicro with LSI
 9300-8i
In-Reply-To: <20398423923b43f5aa10ae62100bd35c@Ek.usurf.usu.edu>
References: <47c83c52ca6c48b4a2a46e0c707de3ce@Ek.usurf.usu.edu>
	<10217EE6-B4D6-48F4-8F3B-9E015B165632@qutic.com>
	<20398423923b43f5aa10ae62100bd35c@Ek.usurf.usu.edu>
Message-ID: <alpine.GSO.2.20.1606231603080.8389@freddy.simplesystems.org>

On Thu, 23 Jun 2016, Josh Barton wrote:

> per drive. Is there any other information I can provide?

What filesystem is being used and exactly how was it configured?  For 
example, if it is zfs, the pool organization and filesystem blocksize 
is very important.

Another important factor is if there is a non-volatile write cache 
(SSD or static RAM cache) involved which dramatically lessens the 
latency for writes.

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

From richard at netbsd.org  Fri Jun 24 05:24:33 2016
From: richard at netbsd.org (Richard PALO)
Date: Fri, 24 Jun 2016 07:24:33 +0200
Subject: [OmniOS-discuss] illumos-gate, perl & sunpro
Message-ID: <nkig57$4fo$1@ger.gmane.org>

since over a year I needed to use the following patch as already discusse here
and on developer@:
> richard at omnis:/home/richard/src/illumos-gate/usr/src/cmd/perl$ git diff illumos-omnios .
> diff --git a/usr/src/cmd/perl/Makefile.perl b/usr/src/cmd/perl/Makefile.perl
> index 0164546..b3944aa 100644
> --- a/usr/src/cmd/perl/Makefile.perl
> +++ b/usr/src/cmd/perl/Makefile.perl
> @@ -55,3 +55,6 @@ XSUBPP64 = $(PERLDIR)/bin/$(MACH64)/perl $(PERLDIR)/lib/ExtUtils/xsubpp \
>         -typemap $(PERLDIR)/lib/ExtUtils/typemap
>  
>  C99MODE = $(C99_ENABLE)
> +
> +CERRWARN += -_cc=-erroff=E_ATTRIBUTE_UNKNOWN
> +CERRWARN += -_cc=-erroff=E_ATTRIBUTE_PARAM_UNDEFINED
> 

This is needed in order to simply build illumos-gate with the studio shadow compiler.

In the meanwhile, alp@ came up with a patch that seems to work
for OpenIndiana/Hipster but I haven't seen it in omnios-build.
'oi-userland/components/perl/perl516/patches/sunpro.patch'

Any way to get consensus on one or the other?

(I'd try to apply it myself and do a pull request but it has
been ages since I've had a working omnios-build, unfortunately,
and perl is particularly broken on my machine also as already discussed
prior in this forum)

cheers

-- 
Richard PALO



From richard at netbsd.org  Sun Jun 26 06:25:53 2016
From: richard at netbsd.org (Richard PALO)
Date: Sun, 26 Jun 2016 08:25:53 +0200
Subject: [OmniOS-discuss] illumos-gate, perl & sunpro
In-Reply-To: <nkig57$4fo$1@ger.gmane.org>
References: <nkig57$4fo$1@ger.gmane.org>
Message-ID: <576F7571.4040802@netbsd.org>

Le 24/06/16 07:24, Richard PALO a ?crit :
> since over a year I needed to use the following patch as already discusse here
> and on developer@:
>> richard at omnis:/home/richard/src/illumos-gate/usr/src/cmd/perl$ git diff illumos-omnios .
>> diff --git a/usr/src/cmd/perl/Makefile.perl b/usr/src/cmd/perl/Makefile.perl
>> index 0164546..b3944aa 100644
>> --- a/usr/src/cmd/perl/Makefile.perl
>> +++ b/usr/src/cmd/perl/Makefile.perl
>> @@ -55,3 +55,6 @@ XSUBPP64 = $(PERLDIR)/bin/$(MACH64)/perl $(PERLDIR)/lib/ExtUtils/xsubpp \
>>         -typemap $(PERLDIR)/lib/ExtUtils/typemap
>>  
>>  C99MODE = $(C99_ENABLE)
>> +
>> +CERRWARN += -_cc=-erroff=E_ATTRIBUTE_UNKNOWN
>> +CERRWARN += -_cc=-erroff=E_ATTRIBUTE_PARAM_UNDEFINED
>>
> 
> This is needed in order to simply build illumos-gate with the studio shadow compiler.
> 
> In the meanwhile, alp@ came up with a patch that seems to work
> for OpenIndiana/Hipster but I haven't seen it in omnios-build.
> 'oi-userland/components/perl/perl516/patches/sunpro.patch'
> 
> Any way to get consensus on one or the other?
> 
> (I'd try to apply it myself and do a pull request but it has
> been ages since I've had a working omnios-build, unfortunately,
> and perl is particularly broken on my machine also as already discussed
> prior in this forum)
> 
> cheers
> 

??? fetching and merging recent illumos-gate and after a pkg update on bloody, I can
no longer build the gate!  what's up?

> /usr/perl5/5.16.1/bin/amd64/perl /usr/perl5/5.16.1/lib/ExtUtils/xsubpp  -typemap /usr/perl5/5.16.1/lib/ExtUtils/typemap  Intrs.xs >amd64/Intrs.c
> /home/richard/src/illumos-gate/usr/src/tools/proto/root_i386-nd/opt/onbld/bin/i386/cw -_gcc -O -m32 -xspace -Xa  -xildoff -errtags=yes -errwarn=%all -erroff=E_EMPTY_TRANSLATION_UNIT -erroff=E_STATEMENT_NOT_REACHED -_gcc=-Wno-missing-braces -_gcc=-Wno-sign-compare -_gcc=-Wno-unknown-pragmas -_gcc=-Wno-unused-parameter -_gcc=-Wno-missing-field-initializers -_gcc=-Wno-array-bounds -_gcc=-Wno-unused -_gcc=-Wno-empty-body -_cc=-erroff=E_ATTRIBUTE_UNKNOWN -_cc=-erroff=E_ATTRIBUTE_PARAM_UNDEFINED -_gcc=-Wno-unused-variable -xc99=%all    -W0,-xglobalstatic -_gcc=-fno-inline-small-functions  -_gcc=-fno-inline-functions-called-once  -_gcc=-fno-ipa-cp     -DTEXT_DOMAIN=\"SUNW_OST_OSLIB\" -D_TS_ERRNO  -I/home/richard/src/illumos-gate/proto/root_i386-nd/usr/include      -c -m64 -DPERL_EUPXS_ALWAYS_EXPORT -D_LARGEFILE64_SOURCE  -DPERL_USE_SAFE_PUTENV -D_TS_ERRNO -K pic -I/usr/perl5/5.16.1/lib/i86pc-solaris-thread-multi-64/CORE amd64/Intrs.c -o amd64/Intrs.o
> Incompatible -xarch= and/or -m32/-m64 options used.
> *** Error code 2

now there's both '-m32' and '-m64' specified on the same command line!
-- 
Richard PALO


From richard at netbsd.org  Sun Jun 26 07:17:30 2016
From: richard at netbsd.org (Richard PALO)
Date: Sun, 26 Jun 2016 09:17:30 +0200
Subject: [OmniOS-discuss] illumos-gate, perl & sunpro
In-Reply-To: <576F7571.4040802@netbsd.org>
References: <nkig57$4fo$1@ger.gmane.org> <576F7571.4040802@netbsd.org>
Message-ID: <576F818A.7080604@netbsd.org>

Le 26/06/16 08:25, Richard PALO a ?crit :
> Le 24/06/16 07:24, Richard PALO a ?crit :
>> since over a year I needed to use the following patch as already discusse here
>> and on developer@:
>>> richard at omnis:/home/richard/src/illumos-gate/usr/src/cmd/perl$ git diff illumos-omnios .
>>> diff --git a/usr/src/cmd/perl/Makefile.perl b/usr/src/cmd/perl/Makefile.perl
>>> index 0164546..b3944aa 100644
>>> --- a/usr/src/cmd/perl/Makefile.perl
>>> +++ b/usr/src/cmd/perl/Makefile.perl
>>> @@ -55,3 +55,6 @@ XSUBPP64 = $(PERLDIR)/bin/$(MACH64)/perl $(PERLDIR)/lib/ExtUtils/xsubpp \
>>>         -typemap $(PERLDIR)/lib/ExtUtils/typemap
>>>  
>>>  C99MODE = $(C99_ENABLE)
>>> +
>>> +CERRWARN += -_cc=-erroff=E_ATTRIBUTE_UNKNOWN
>>> +CERRWARN += -_cc=-erroff=E_ATTRIBUTE_PARAM_UNDEFINED
>>>
>>
>> This is needed in order to simply build illumos-gate with the studio shadow compiler.
>>
>> In the meanwhile, alp@ came up with a patch that seems to work
>> for OpenIndiana/Hipster but I haven't seen it in omnios-build.
>> 'oi-userland/components/perl/perl516/patches/sunpro.patch'
>>
>> Any way to get consensus on one or the other?
>>
>> (I'd try to apply it myself and do a pull request but it has
>> been ages since I've had a working omnios-build, unfortunately,
>> and perl is particularly broken on my machine also as already discussed
>> prior in this forum)
>>
>> cheers
>>
> 
> ??? fetching and merging recent illumos-gate and after a pkg update on bloody, I can
> no longer build the gate!  what's up?
> 
>> /usr/perl5/5.16.1/bin/amd64/perl /usr/perl5/5.16.1/lib/ExtUtils/xsubpp  -typemap /usr/perl5/5.16.1/lib/ExtUtils/typemap  Intrs.xs >amd64/Intrs.c
>> /home/richard/src/illumos-gate/usr/src/tools/proto/root_i386-nd/opt/onbld/bin/i386/cw -_gcc -O -m32 -xspace -Xa  -xildoff -errtags=yes -errwarn=%all -erroff=E_EMPTY_TRANSLATION_UNIT -erroff=E_STATEMENT_NOT_REACHED -_gcc=-Wno-missing-braces -_gcc=-Wno-sign-compare -_gcc=-Wno-unknown-pragmas -_gcc=-Wno-unused-parameter -_gcc=-Wno-missing-field-initializers -_gcc=-Wno-array-bounds -_gcc=-Wno-unused -_gcc=-Wno-empty-body -_cc=-erroff=E_ATTRIBUTE_UNKNOWN -_cc=-erroff=E_ATTRIBUTE_PARAM_UNDEFINED -_gcc=-Wno-unused-variable -xc99=%all    -W0,-xglobalstatic -_gcc=-fno-inline-small-functions  -_gcc=-fno-inline-functions-called-once  -_gcc=-fno-ipa-cp     -DTEXT_DOMAIN=\"SUNW_OST_OSLIB\" -D_TS_ERRNO  -I/home/richard/src/illumos-gate/proto/root_i386-nd/usr/include      -c -m64 -DPERL_EUPXS_ALWAYS_EXPORT -D_LARGEFILE64_SOURCE  -DPERL_USE_SAFE_PUTENV -D_TS_ERRNO -K pic -I/usr/perl5/5.16.1/lib/i86pc-solaris-thread-multi-64/CORE amd64/Intrs.c -o amd64/Intrs.o
>> Incompatible -xarch= and/or -m32/-m64 options used.
>> *** Error code 2
> 
> now there's both '-m32' and '-m64' specified on the same command line!
> 
I just found:
> commit a751bb41bf91ec99a88fa7928684970b739403aa
> Author: Dan McDonald <danmcd at omniti.com>
> Date:   Wed Jun 22 13:42:02 2016 -0400
> 
>     Fix our breakage 7069 exposed

I'll try updating ENABLE_PERL64 with this.

-- 
Richard PALO


From geoffn at gnaa.net  Tue Jun 28 18:51:15 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2016 11:51:15 -0700
Subject: [OmniOS-discuss] virtualbox memory fault.
Message-ID: <5772C723.80509@gnaa.net>

Hi.

I am running OmniOS v11 r151018.

I have quite a few OI/Omnios OS boxes running Virtualbox.  I haven't see 
this before.  On a new server I just installed I am getting a memory 
fault right away when starting a vm.

/usr/bin/VBoxHeadless -s test
Oracle VM VirtualBox Headless Interface 5.0.22
(C) 2008-2016 Oracle Corporation
All rights reserved.
Memory fault

I attached the vbox log of an Ubuntu 16.04 live CD boot.

any thoughts?

thanks,

Geoff







-------------- next part --------------
A non-text attachment was scrubbed...
Name: VBox.log
Type: text/x-log
Size: 42723 bytes
Desc: not available
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160628/9965f457/attachment-0001.bin>

From jdg117 at elvis.arl.psu.edu  Tue Jun 28 18:59:01 2016
From: jdg117 at elvis.arl.psu.edu (John D Groenveld)
Date: Tue, 28 Jun 2016 14:59:01 -0400
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: Your message of "Tue, 28 Jun 2016 11:51:15 PDT."
	<5772C723.80509@gnaa.net> 
References: <5772C723.80509@gnaa.net> 
Message-ID: <201606281859.u5SIx1vN013435@elvis.arl.psu.edu>

In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>I am running OmniOS v11 r151018.
>
>I have quite a few OI/Omnios OS boxes running Virtualbox.  I haven't see 
>this before.  On a new server I just installed I am getting a memory 
>fault right away when starting a vm.

Perhaps set disable_smap=1?
<URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>

BTW have you done any benchmarking between VBox and KVM?
John
groenveld at acm.org


From geoffn at gnaa.net  Tue Jun 28 19:11:34 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2016 12:11:34 -0700
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: <201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
Message-ID: <5772CBE6.4010608@gnaa.net>



On 2016-06-28 11:59 AM, John D Groenveld wrote:
> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>> I am running OmniOS v11 r151018.
>>
>> I have quite a few OI/Omnios OS boxes running Virtualbox.  I haven't see
>> this before.  On a new server I just installed I am getting a memory
>> fault right away when starting a vm.
> Perhaps set disable_smap=1?
> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>
>
> BTW have you done any benchmarking between VBox and KVM?
> John
> groenveld at acm.org
>

Hi John.

Yes, I set the disable_smap in the system and rebooted, but it doesn't 
seem to help.  That setting supposedly prevents the host from rebooting.

On a Windows Server 2012 R2 I am getting the following networking 
performance with iperf (default settings).

Client -> VM  903Mbps
VM -> Client  572Mbps

I am focused on small business systems and protecting their data, so 
these numbers are more than good enough.

thanks,

Geoff


From daleg at omniti.com  Tue Jun 28 19:23:31 2016
From: daleg at omniti.com (Dale Ghent)
Date: Tue, 28 Jun 2016 15:23:31 -0400
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: <5772CBE6.4010608@gnaa.net>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
	<5772CBE6.4010608@gnaa.net>
Message-ID: <9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>


Is the vbox version you?re using on your new server different from that which you are using on existing ones?

Are you compiling vbox on OmniOS, or using the pre-compiled Solaris binaries from Oracle?

/dale

> On Jun 28, 2016, at 3:11 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
> 
> 
> 
> On 2016-06-28 11:59 AM, John D Groenveld wrote:
>> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>>> I am running OmniOS v11 r151018.
>>> 
>>> I have quite a few OI/Omnios OS boxes running Virtualbox.  I haven't see
>>> this before.  On a new server I just installed I am getting a memory
>>> fault right away when starting a vm.
>> Perhaps set disable_smap=1?
>> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>
>> 
>> BTW have you done any benchmarking between VBox and KVM?
>> John
>> groenveld at acm.org
>> 
> 
> Hi John.
> 
> Yes, I set the disable_smap in the system and rebooted, but it doesn't seem to help.  That setting supposedly prevents the host from rebooting.
> 
> On a Windows Server 2012 R2 I am getting the following networking performance with iperf (default settings).
> 
> Client -> VM  903Mbps
> VM -> Client  572Mbps
> 
> I am focused on small business systems and protecting their data, so these numbers are more than good enough.
> 
> thanks,
> 
> Geoff
> 
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss at lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss


From geoffn at gnaa.net  Tue Jun 28 19:57:06 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2016 12:57:06 -0700
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: <9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
	<5772CBE6.4010608@gnaa.net>
	<9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>
Message-ID: <5772D692.6010108@gnaa.net>



On 2016-06-28 12:23 PM, Dale Ghent wrote:
> Is the vbox version you?re using on your new server different from that which you are using on existing ones?
>
> Are you compiling vbox on OmniOS, or using the pre-compiled Solaris binaries from Oracle?
>
> /dale
>
>> On Jun 28, 2016, at 3:11 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>
>>
>>
>> On 2016-06-28 11:59 AM, John D Groenveld wrote:
>>> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>>>> I am running OmniOS v11 r151018.
>>>>
>>>> I have quite a few OI/Omnios OS boxes running Virtualbox.  I haven't see
>>>> this before.  On a new server I just installed I am getting a memory
>>>> fault right away when starting a vm.
>>> Perhaps set disable_smap=1?
>>> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>
>>>
>>> BTW have you done any benchmarking between VBox and KVM?
>>> John
>>> groenveld at acm.org
>>>
>> Hi John.
>>
>> Yes, I set the disable_smap in the system and rebooted, but it doesn't seem to help.  That setting supposedly prevents the host from rebooting.
>>
>> On a Windows Server 2012 R2 I am getting the following networking performance with iperf (default settings).
>>
>> Client -> VM  903Mbps
>> VM -> Client  572Mbps
>>
>> I am focused on small business systems and protecting their data, so these numbers are more than good enough.
>>
>>

Hi Dale.

I am using the pre-compiled binaries from the vbox download site.

I have another server using the same OmniOS release.   The one that 
works is running 5.0.20, but i have tried both versions of vbox on the 
new server and both are producing the memory fault.

The only thing that seems to be different about these boxes are the 
CPUs.   The one that works has older Xeons, the new one that doesn't 
work is running E5-2630V3 (haswell).

thanks,

Geoff



From geoffn at gnaa.net  Wed Jun 29 00:25:25 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2016 17:25:25 -0700
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: <5772D692.6010108@gnaa.net>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
	<5772CBE6.4010608@gnaa.net>
	<9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>
	<5772D692.6010108@gnaa.net>
Message-ID: <57731575.7010502@gnaa.net>



On 2016-06-28 12:57 PM, Geoff Nordli wrote:
>
>
> On 2016-06-28 12:23 PM, Dale Ghent wrote:
>> Is the vbox version you?re using on your new server different from 
>> that which you are using on existing ones?
>>
>> Are you compiling vbox on OmniOS, or using the pre-compiled Solaris 
>> binaries from Oracle?
>>
>> /dale
>>
>>> On Jun 28, 2016, at 3:11 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>>
>>>
>>>
>>> On 2016-06-28 11:59 AM, John D Groenveld wrote:
>>>> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>>>>> I am running OmniOS v11 r151018.
>>>>>
>>>>> I have quite a few OI/Omnios OS boxes running Virtualbox. I 
>>>>> haven't see
>>>>> this before.  On a new server I just installed I am getting a memory
>>>>> fault right away when starting a vm.
>>>> Perhaps set disable_smap=1?
>>>> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html> 
>>>>
>>>>
>>>> BTW have you done any benchmarking between VBox and KVM?
>>>> John
>>>> groenveld at acm.org
>>>>
>>> Hi John.
>>>
>>> Yes, I set the disable_smap in the system and rebooted, but it 
>>> doesn't seem to help.  That setting supposedly prevents the host 
>>> from rebooting.
>>>
>>> On a Windows Server 2012 R2 I am getting the following networking 
>>> performance with iperf (default settings).
>>>
>>> Client -> VM  903Mbps
>>> VM -> Client  572Mbps
>>>
>>> I am focused on small business systems and protecting their data, so 
>>> these numbers are more than good enough.
>>>
>>>
>
> Hi Dale.
>
> I am using the pre-compiled binaries from the vbox download site.
>
> I have another server using the same OmniOS release.   The one that 
> works is running 5.0.20, but i have tried both versions of vbox on the 
> new server and both are producing the memory fault.
>
> The only thing that seems to be different about these boxes are the 
> CPUs.   The one that works has older Xeons, the new one that doesn't 
> work is running E5-2630V3 (haswell).
>
> thanks,
>
> Geoff
>
>
Just tried the newly released 5.0.24 and it still gives the same error.

From daleg at omniti.com  Wed Jun 29 01:18:37 2016
From: daleg at omniti.com (Dale Ghent)
Date: Tue, 28 Jun 2016 21:18:37 -0400
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: <57731575.7010502@gnaa.net>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
	<5772CBE6.4010608@gnaa.net>
	<9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>
	<5772D692.6010108@gnaa.net> <57731575.7010502@gnaa.net>
Message-ID: <C6340EF3-00C2-4C3E-B508-55847D83F431@omniti.com>


> On Jun 28, 2016, at 8:25 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
> 
> 
> 
> On 2016-06-28 12:57 PM, Geoff Nordli wrote:
>> 
>> 
>> On 2016-06-28 12:23 PM, Dale Ghent wrote:
>>> Is the vbox version you?re using on your new server different from that which you are using on existing ones?
>>> 
>>> Are you compiling vbox on OmniOS, or using the pre-compiled Solaris binaries from Oracle?
>>> 
>>> /dale
>>> 
>>>> On Jun 28, 2016, at 3:11 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>>> 
>>>> 
>>>> 
>>>> On 2016-06-28 11:59 AM, John D Groenveld wrote:
>>>>> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>>>>>> I am running OmniOS v11 r151018.
>>>>>> 
>>>>>> I have quite a few OI/Omnios OS boxes running Virtualbox. I haven't see
>>>>>> this before.  On a new server I just installed I am getting a memory
>>>>>> fault right away when starting a vm.
>>>>> Perhaps set disable_smap=1?
>>>>> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>
>>>>> 
>>>>> BTW have you done any benchmarking between VBox and KVM?
>>>>> John
>>>>> groenveld at acm.org
>>>>> 
>>>> Hi John.
>>>> 
>>>> Yes, I set the disable_smap in the system and rebooted, but it doesn't seem to help.  That setting supposedly prevents the host from rebooting.
>>>> 
>>>> On a Windows Server 2012 R2 I am getting the following networking performance with iperf (default settings).
>>>> 
>>>> Client -> VM  903Mbps
>>>> VM -> Client  572Mbps
>>>> 
>>>> I am focused on small business systems and protecting their data, so these numbers are more than good enough.
>>>> 
>>>> 
>> 
>> Hi Dale.
>> 
>> I am using the pre-compiled binaries from the vbox download site.
>> 
>> I have another server using the same OmniOS release.   The one that works is running 5.0.20, but i have tried both versions of vbox on the new server and both are producing the memory fault.
>> 
>> The only thing that seems to be different about these boxes are the CPUs.   The one that works has older Xeons, the new one that doesn't work is running E5-2630V3 (haswell).
>> 
>> thanks,
>> 
>> Geoff
>> 
>> 
> Just tried the newly released 5.0.24 and it still gives the same error.

Well, using Solaris on illumos is going to be a more and more iffy proposition as time marches on; it's hard to say what might have changed on Oracle Solaris, if anything; that the vbox packages were compiled on.

How about trying a earlier release of vbox, to perhaps isolate the issue further? Since there is no guarantee for Oracle Solaris binary compatibility, this is kind of an ambiguous zone here.

/dale

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160628/6daa0524/attachment.bin>

From geoffn at gnaa.net  Wed Jun 29 18:57:11 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Wed, 29 Jun 2016 11:57:11 -0700
Subject: [OmniOS-discuss] [vbox-dev] Fwd: memory fault -- OmniOS
In-Reply-To: <5773F829.2060403@gnaa.net>
References: <5772C124.5020008@gnaa.net> <5773E34F.3040304@gnaa.net>
	<1695700.VW55xMWu6u@noys2> <5773F829.2060403@gnaa.net>
Message-ID: <57741A07.7090808@gnaa.net>

BTW, the core dump stack looks like this:

 > $c
libkstat.so.1`kstat_read+0x31(289a7c0, 0, 0)
VBoxRT.so`_Z15rtMpSolarisOncePv+0x18c()
VBoxRT.so`RTOnceSlow+0x264()
VBoxRT.so`RTMpGetCoreCount+0x51()
VBoxVMM.so`CPUMR3LogCpuIds+0x8d()
VBoxVMM.so`VMMR3InitCompleted+0x89()
VBoxVMM.so`_Z19vmR3InitDoCompletedP2VM15VMINITCOMPLETED+0x1a()
VBoxVMM.so`_Z11vmR3CreateUP3UVMjPFiS0_P2VMPvES3_+0x7e1()
VBoxVMM.so`_Z18vmR3ReqProcessOneUP3UVMP5VMREQ+0x1ad()
VBoxVMM.so`VMR3ReqProcessU+0xa8()
VBoxVMM.so`_Z25vmR3EmulationThreadWithIdP11RTTHREADINTP6UVMCPUj+0xe8()
VBoxRT.so`rtThreadMain+0x2c()
VBoxRT.so`_Z18rtThreadNativeMainPv+0x51()
libc.so.1`_thrp_setup+0x8a(ffffbf7fff125240)
libc.so.1`_lwp_start()



On 2016-06-29 09:32 AM, Geoff Nordli wrote:
> Hi Frank.
>
> I have quite a few servers that either run OpenIndiana or Omnios 
> systems and they all work well with with the Solaris binaries.  I 
> haven't seen this type of error before on any OI/OmniOS/VBox 
> combination I have deployed.   The only difference I can think of is 
> this is a newer model of CPU.
>
> Sorry I should have provided a core dump.
>
> Here it is:
>
> https://www.dropbox.com/s/0wq73p4ekokq30h/core.VBoxHeadless.421?dl=1
>
> thanks,
>
> Geoff
>
>
>
> On 2016-06-29 08:26 AM, Frank Mehnert wrote:
>> Geoff,
>>
>> unfortunately we cannot do much with this information. We would require
>> to have at least a core dump. Also, OmniOS is not an officially 
>> supported
>> host so I wonder how compatible this OS is to Solaris 11.
>>
>> Also, you say that you haven't seen this before. So when did this start:
>> When you upgraded VirtualBox from 5.0.22 to 5.0.24 or when you upgraded
>> your OS or anything else?
>>
>> Kind regards,
>>
>> Fank
>>
>> On Wednesday 29 June 2016 08:03:43 Geoff Nordli wrote:
>>> Hello.
>>>
>>> Any thoughts on the memory fault error.  I tried the 5.0.24 version as
>>> well without success.
>>>
>>> thanks,
>>>
>>> Geoff
>>>
>>>
>>> -------- Forwarded Message --------
>>> Subject:     memory fault -- OmniOS
>>> Date:     Tue, 28 Jun 2016 11:25:40 -0700
>>> From:     Geoff Nordli <geoffn at gnaa.net>
>>> To:     vbox-users-community at lists.sourceforge.net
>>> <vbox-users-community at lists.sourceforge.net>
>>>
>>>
>>>
>>> Hi.
>>>
>>> I haven't seen this before, but when I try starting a VM I get a memory
>>> fault right away:
>>>
>>> /usr/bin/VBoxHeadless -s test
>>> Oracle VM VirtualBox Headless Interface 5.0.22
>>> (C) 2008-2016 Oracle Corporation
>>> All rights reserved.
>>> Memory fault
>>>
>>> Vbox is running on latest version of Omnios.
>>>
>>> I attached the vbox log of an Ubuntu 16.04 live CD boot.
>>>
>>> any thoughts?
>>>
>>> thanks,
>>>
>>> Geoff
>


From geoffn at gnaa.net  Wed Jun 29 18:58:08 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Wed, 29 Jun 2016 11:58:08 -0700
Subject: [OmniOS-discuss] [vbox-dev] Fwd: memory fault -- OmniOS
In-Reply-To: <57741A07.7090808@gnaa.net>
References: <5772C124.5020008@gnaa.net> <5773E34F.3040304@gnaa.net>
	<1695700.VW55xMWu6u@noys2> <5773F829.2060403@gnaa.net>
	<57741A07.7090808@gnaa.net>
Message-ID: <57741A40.6000708@gnaa.net>

Sorry for the noise, wrong list.

On 2016-06-29 11:57 AM, Geoff Nordli wrote:
> BTW, the core dump stack looks like this:
>
> > $c
> libkstat.so.1`kstat_read+0x31(289a7c0, 0, 0)
> VBoxRT.so`_Z15rtMpSolarisOncePv+0x18c()
> VBoxRT.so`RTOnceSlow+0x264()
> VBoxRT.so`RTMpGetCoreCount+0x51()
> VBoxVMM.so`CPUMR3LogCpuIds+0x8d()
> VBoxVMM.so`VMMR3InitCompleted+0x89()
> VBoxVMM.so`_Z19vmR3InitDoCompletedP2VM15VMINITCOMPLETED+0x1a()
> VBoxVMM.so`_Z11vmR3CreateUP3UVMjPFiS0_P2VMPvES3_+0x7e1()
> VBoxVMM.so`_Z18vmR3ReqProcessOneUP3UVMP5VMREQ+0x1ad()
> VBoxVMM.so`VMR3ReqProcessU+0xa8()
> VBoxVMM.so`_Z25vmR3EmulationThreadWithIdP11RTTHREADINTP6UVMCPUj+0xe8()
> VBoxRT.so`rtThreadMain+0x2c()
> VBoxRT.so`_Z18rtThreadNativeMainPv+0x51()
> libc.so.1`_thrp_setup+0x8a(ffffbf7fff125240)
> libc.so.1`_lwp_start()
>
>
>
> On 2016-06-29 09:32 AM, Geoff Nordli wrote:
>> Hi Frank.
>>
>> I have quite a few servers that either run OpenIndiana or Omnios 
>> systems and they all work well with with the Solaris binaries. I 
>> haven't seen this type of error before on any OI/OmniOS/VBox 
>> combination I have deployed.   The only difference I can think of is 
>> this is a newer model of CPU.
>>
>> Sorry I should have provided a core dump.
>>
>> Here it is:
>>
>> https://www.dropbox.com/s/0wq73p4ekokq30h/core.VBoxHeadless.421?dl=1
>>
>> thanks,
>>
>> Geoff
>>
>>
>>
>> On 2016-06-29 08:26 AM, Frank Mehnert wrote:
>>> Geoff,
>>>
>>> unfortunately we cannot do much with this information. We would require
>>> to have at least a core dump. Also, OmniOS is not an officially 
>>> supported
>>> host so I wonder how compatible this OS is to Solaris 11.
>>>
>>> Also, you say that you haven't seen this before. So when did this 
>>> start:
>>> When you upgraded VirtualBox from 5.0.22 to 5.0.24 or when you upgraded
>>> your OS or anything else?
>>>
>>> Kind regards,
>>>
>>> Fank
>>>
>>> On Wednesday 29 June 2016 08:03:43 Geoff Nordli wrote:
>>>> Hello.
>>>>
>>>> Any thoughts on the memory fault error.  I tried the 5.0.24 version as
>>>> well without success.
>>>>
>>>> thanks,
>>>>
>>>> Geoff
>>>>
>>>>
>>>> -------- Forwarded Message --------
>>>> Subject:     memory fault -- OmniOS
>>>> Date:     Tue, 28 Jun 2016 11:25:40 -0700
>>>> From:     Geoff Nordli <geoffn at gnaa.net>
>>>> To:     vbox-users-community at lists.sourceforge.net
>>>> <vbox-users-community at lists.sourceforge.net>
>>>>
>>>>
>>>>
>>>> Hi.
>>>>
>>>> I haven't seen this before, but when I try starting a VM I get a 
>>>> memory
>>>> fault right away:
>>>>
>>>> /usr/bin/VBoxHeadless -s test
>>>> Oracle VM VirtualBox Headless Interface 5.0.22
>>>> (C) 2008-2016 Oracle Corporation
>>>> All rights reserved.
>>>> Memory fault
>>>>
>>>> Vbox is running on latest version of Omnios.
>>>>
>>>> I attached the vbox log of an Ubuntu 16.04 live CD boot.
>>>>
>>>> any thoughts?
>>>>
>>>> thanks,
>>>>
>>>> Geoff
>>
>


From geoffn at gnaa.net  Wed Jun 29 19:00:38 2016
From: geoffn at gnaa.net (Geoff Nordli)
Date: Wed, 29 Jun 2016 12:00:38 -0700
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: <C6340EF3-00C2-4C3E-B508-55847D83F431@omniti.com>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
	<5772CBE6.4010608@gnaa.net>
	<9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>
	<5772D692.6010108@gnaa.net> <57731575.7010502@gnaa.net>
	<C6340EF3-00C2-4C3E-B508-55847D83F431@omniti.com>
Message-ID: <57741AD6.3080009@gnaa.net>



On 2016-06-28 06:18 PM, Dale Ghent wrote:
>> On Jun 28, 2016, at 8:25 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>
>>
>>
>> On 2016-06-28 12:57 PM, Geoff Nordli wrote:
>>>
>>> On 2016-06-28 12:23 PM, Dale Ghent wrote:
>>>> Is the vbox version you?re using on your new server different from that which you are using on existing ones?
>>>>
>>>> Are you compiling vbox on OmniOS, or using the pre-compiled Solaris binaries from Oracle?
>>>>
>>>> /dale
>>>>
>>>>> On Jun 28, 2016, at 3:11 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On 2016-06-28 11:59 AM, John D Groenveld wrote:
>>>>>> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>>>>>>> I am running OmniOS v11 r151018.
>>>>>>>
>>>>>>> I have quite a few OI/Omnios OS boxes running Virtualbox. I haven't see
>>>>>>> this before.  On a new server I just installed I am getting a memory
>>>>>>> fault right away when starting a vm.
>>>>>> Perhaps set disable_smap=1?
>>>>>> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>
>>>>>>
>>>>>> BTW have you done any benchmarking between VBox and KVM?
>>>>>> John
>>>>>> groenveld at acm.org
>>>>>>
>>>>> Hi John.
>>>>>
>>>>> Yes, I set the disable_smap in the system and rebooted, but it doesn't seem to help.  That setting supposedly prevents the host from rebooting.
>>>>>
>>>>> On a Windows Server 2012 R2 I am getting the following networking performance with iperf (default settings).
>>>>>
>>>>> Client -> VM  903Mbps
>>>>> VM -> Client  572Mbps
>>>>>
>>>>> I am focused on small business systems and protecting their data, so these numbers are more than good enough.
>>>>>
>>>>>
>>> Hi Dale.
>>>
>>> I am using the pre-compiled binaries from the vbox download site.
>>>
>>> I have another server using the same OmniOS release.   The one that works is running 5.0.20, but i have tried both versions of vbox on the new server and both are producing the memory fault.
>>>
>>> The only thing that seems to be different about these boxes are the CPUs.   The one that works has older Xeons, the new one that doesn't work is running E5-2630V3 (haswell).
>>>
>>> thanks,
>>>
>>> Geoff
>>>
>>>
>> Just tried the newly released 5.0.24 and it still gives the same error.
> Well, using Solaris on illumos is going to be a more and more iffy proposition as time marches on; it's hard to say what might have changed on Oracle Solaris, if anything; that the vbox packages were compiled on.
>
> How about trying a earlier release of vbox, to perhaps isolate the issue further? Since there is no guarantee for Oracle Solaris binary compatibility, this is kind of an ambiguous zone here.
>
> /dale
>

Dale, you are probably right, that is a tough pill to swallow though 
since I have a lot of scripts/tools to manage vbox and it works really 
well on OmniOS -- when it works :)

Getting some help on the vbox-dev mailing list.

Have a great day!!

Geoff

From daleg at omniti.com  Wed Jun 29 20:11:01 2016
From: daleg at omniti.com (Dale Ghent)
Date: Wed, 29 Jun 2016 16:11:01 -0400
Subject: [OmniOS-discuss] virtualbox memory fault.
In-Reply-To: <57741AD6.3080009@gnaa.net>
References: <5772C723.80509@gnaa.net>
	<201606281859.u5SIx1vN013435@elvis.arl.psu.edu>
	<5772CBE6.4010608@gnaa.net>
	<9B1B1587-CDC7-463C-B727-8FE4CB0CDBC3@omniti.com>
	<5772D692.6010108@gnaa.net> <57731575.7010502@gnaa.net>
	<C6340EF3-00C2-4C3E-B508-55847D83F431@omniti.com>
	<57741AD6.3080009@gnaa.net>
Message-ID: <C449089C-D789-4168-8265-D04C56D7B92B@omniti.com>


> On Jun 29, 2016, at 3:00 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
> 
> 
> 
> On 2016-06-28 06:18 PM, Dale Ghent wrote:
>>> On Jun 28, 2016, at 8:25 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>> 
>>> 
>>> 
>>> On 2016-06-28 12:57 PM, Geoff Nordli wrote:
>>>> 
>>>> On 2016-06-28 12:23 PM, Dale Ghent wrote:
>>>>> Is the vbox version you?re using on your new server different from that which you are using on existing ones?
>>>>> 
>>>>> Are you compiling vbox on OmniOS, or using the pre-compiled Solaris binaries from Oracle?
>>>>> 
>>>>> /dale
>>>>> 
>>>>>> On Jun 28, 2016, at 3:11 PM, Geoff Nordli <geoffn at gnaa.net> wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On 2016-06-28 11:59 AM, John D Groenveld wrote:
>>>>>>> In message <5772C723.80509 at gnaa.net>, Geoff Nordli writes:
>>>>>>>> I am running OmniOS v11 r151018.
>>>>>>>> 
>>>>>>>> I have quite a few OI/Omnios OS boxes running Virtualbox. I haven't see
>>>>>>>> this before.  On a new server I just installed I am getting a memory
>>>>>>>> fault right away when starting a vm.
>>>>>>> Perhaps set disable_smap=1?
>>>>>>> <URL:http://openindiana.org/pipermail/openindiana-discuss/2016-June/019049.html>
>>>>>>> 
>>>>>>> BTW have you done any benchmarking between VBox and KVM?
>>>>>>> John
>>>>>>> groenveld at acm.org
>>>>>>> 
>>>>>> Hi John.
>>>>>> 
>>>>>> Yes, I set the disable_smap in the system and rebooted, but it doesn't seem to help.  That setting supposedly prevents the host from rebooting.
>>>>>> 
>>>>>> On a Windows Server 2012 R2 I am getting the following networking performance with iperf (default settings).
>>>>>> 
>>>>>> Client -> VM  903Mbps
>>>>>> VM -> Client  572Mbps
>>>>>> 
>>>>>> I am focused on small business systems and protecting their data, so these numbers are more than good enough.
>>>>>> 
>>>>>> 
>>>> Hi Dale.
>>>> 
>>>> I am using the pre-compiled binaries from the vbox download site.
>>>> 
>>>> I have another server using the same OmniOS release.   The one that works is running 5.0.20, but i have tried both versions of vbox on the new server and both are producing the memory fault.
>>>> 
>>>> The only thing that seems to be different about these boxes are the CPUs.   The one that works has older Xeons, the new one that doesn't work is running E5-2630V3 (haswell).
>>>> 
>>>> thanks,
>>>> 
>>>> Geoff
>>>> 
>>>> 
>>> Just tried the newly released 5.0.24 and it still gives the same error.
>> Well, using Solaris on illumos is going to be a more and more iffy proposition as time marches on; it's hard to say what might have changed on Oracle Solaris, if anything; that the vbox packages were compiled on.
>> 
>> How about trying a earlier release of vbox, to perhaps isolate the issue further? Since there is no guarantee for Oracle Solaris binary compatibility, this is kind of an ambiguous zone here.
>> 
>> /dale
>> 
> 
> Dale, you are probably right, that is a tough pill to swallow though since I have a lot of scripts/tools to manage vbox and it works really well on OmniOS -- when it works :)

One of the underlying reasons for this is that illumos (and by extension, OmniOS) still identify as ?SunOS 5.11?, which the vbox build system equates to ?Oracle Solaris 11?

Since Oracle Solaris 11 and illumos are moving on in their own directions and the technical differences between them only grow over time, this is a pain point when it comes to trying to get binaries that were compiled on one to work on the other. A good example of this in the context of vbox is vboxfs, which now uses some symbols added in a Oracle Solaris 11 update, but do not exist on illumos.

/dale

From filip.marvan at aira.cz  Thu Jun 30 08:27:06 2016
From: filip.marvan at aira.cz (Filip Marvan)
Date: Thu, 30 Jun 2016 10:27:06 +0200
Subject: [OmniOS-discuss] OpenStack
Message-ID: <3BE0DEED8863E5429BAE4CAEDF62456503E24339B633@AIRA-SRV.aira.local>

Hi,

I would like to ask you, is there any way, how to connect OmniOS as storage to OpenStack?

Thank you,
Filip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.omniti.com/pipermail/omnios-discuss/attachments/20160630/a628bfb8/attachment.html>

From vab at bb-c.de  Thu Jun 30 10:18:15 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Thu, 30 Jun 2016 12:18:15 +0200
Subject: [OmniOS-discuss] OpenStack
In-Reply-To: <3BE0DEED8863E5429BAE4CAEDF62456503E24339B633@AIRA-SRV.aira.local>
References: <3BE0DEED8863E5429BAE4CAEDF62456503E24339B633@AIRA-SRV.aira.local>
Message-ID: <22388.61927.867418.152692@shelob.bb-c.de>

Hi Filip!


> I would like to ask you, is there any way, how to connect OmniOS as storage
> to OpenStack?

It is certainly possible to run Cinder or possibly Swift on top of
OmniOS.  But there is nothing ready for installation yet.

If someone funds the effort, I am sure there are consultants who could
do it for you. :-)


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 filip.marvan at aira.cz  Thu Jun 30 10:32:04 2016
From: filip.marvan at aira.cz (Filip Marvan)
Date: Thu, 30 Jun 2016 12:32:04 +0200
Subject: [OmniOS-discuss] OpenStack
In-Reply-To: <22388.61927.867418.152692@shelob.bb-c.de>
References: <3BE0DEED8863E5429BAE4CAEDF62456503E24339B633@AIRA-SRV.aira.local>
	<22388.61927.867418.152692@shelob.bb-c.de>
Message-ID: <3BE0DEED8863E5429BAE4CAEDF62456503E24339B65C@AIRA-SRV.aira.local>

Thank you for reply.
I tried install Cinder on OmniOS and i seems possible. But, if I'm understand that right, I'm missing Cinder ZFS driver on OmniOS to get that fully working.

Filip


-----Original Message-----
From: Volker A. Brandt [mailto:vab at bb-c.de] 
Sent: Thursday, June 30, 2016 12:18 PM
To: Filip Marvan <filip.marvan at aira.cz>
Cc: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] OpenStack

Hi Filip!


> I would like to ask you, is there any way, how to connect OmniOS as 
> storage to OpenStack?

It is certainly possible to run Cinder or possibly Swift on top of OmniOS.  But there is nothing ready for installation yet.

If someone funds the effort, I am sure there are consultants who could do it for you. :-)


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 vab at bb-c.de  Thu Jun 30 10:32:33 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Thu, 30 Jun 2016 12:32:33 +0200
Subject: [OmniOS-discuss] 151018 kayak problems: utmpd / console-login
Message-ID: <22388.62785.386157.387787@shelob.bb-c.de>

Hi Dan!


I am doing test installations of 151018 via Kayak.  This means that I
am using NO_REBOOT=1 to try out various features and verify the results.

With the stock 95eaa7e miniroot, two SMF services go into maintenance.
One is svc:/system/utmp:default complaining that the utmpd binary is
missing.  I think this has been seen before:

  https://github.com/omniti-labs/kayak/issues/10

The other one is svc:/system/console-login:default, where the start
method /lib/svc/method/console-login is missing.

So I have added these two files to the miniroot.  This makes utmp shut
up.  However, the system becomes unusable because console-login enters
an infinite loop:

  [2016/06/29-19:54:43] Install complete
  Jun 29 19:54:43 svc.startd[8]: instance svc:/system/console-login:default exited with status 127
  Jun 29 19:54:43 svc.startd[8]: instance svc:/system/console-login:default exited with status 127
    :
    :

Then I disabled both services in the SMF system repository on the
miniroot by setting the general/enabled property to false.  This works,
but now I get the standard "single user" prompt just before the
installation starts:

  Configuring devices.
  Requesting System Maintenance Mode
  (See /lib/svc/share/README for more information.)
  Console login service(s) cannot run

  Enter user name for system maintenance (control-d to bypass): [2016/06/29-20:36:41] Forcing all interfaces into DHCP...
  [2016/06/29-20:36:41] Waiting for dhcpinfo...
  [2016/06/29-20:36:42] Waiting for dhcpinfo...
  [2016/06/29-20:36:43] Waiting for dhcpinfo...
    :
    :
  [2016/06/29-20:38:14] Updating GRUB menu for serial console.
  [2016/06/29-20:38:16] Install complete


  Enter user name for system maintenance (control-d to bypass): root
  Enter root password (control-d to bypass): 
  single-user privilege assigned to root on /dev/console.
  Entering System Maintenance Mode

  Jun 29 20:39:00 su: 'su root' succeeded for root on /dev/console

The installation itself works fine.  All of this only pops up when using
NO_REBOOT=1.  Since I can log in as root at the single-user prompt, I 
can do my checks, so I have a workaround.

But it's not really the proper solution. :-)


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 vab at bb-c.de  Thu Jun 30 11:07:14 2016
From: vab at bb-c.de (Volker A. Brandt)
Date: Thu, 30 Jun 2016 13:07:14 +0200
Subject: [OmniOS-discuss] OpenStack
In-Reply-To: <3BE0DEED8863E5429BAE4CAEDF62456503E24339B65C@AIRA-SRV.aira.local>
References: <3BE0DEED8863E5429BAE4CAEDF62456503E24339B633@AIRA-SRV.aira.local>
	<22388.61927.867418.152692@shelob.bb-c.de>
	<3BE0DEED8863E5429BAE4CAEDF62456503E24339B65C@AIRA-SRV.aira.local>
Message-ID: <22388.64866.528074.890739@shelob.bb-c.de>

> I tried install Cinder on OmniOS and i seems possible. But, if I'm
> understand that right, I'm missing Cinder ZFS driver on OmniOS to get that
> fully working. 

Exactly.

Oracle has ported OpenStack to Solaris. They have released the source
of their modifications, drivers, etc. under the Apache License 2.0:

  # cat openstack/cinder/files/solaris/zfs.py
  # vim: tabstop=4 shiftwidth=4 softtabstop=4
  # Copyright (c) 2012 OpenStack LLC.
  # All Rights Reserved.
  #
  # Copyright (c) 2014, 2016, Oracle and/or its affiliates. All rights reserved.
  #
  #    Licensed under the Apache License, Version 2.0 (the "License"); you may
  #    not use this file except in compliance with the License. You may obtain
  #    a copy of the License at
  #
  #         http://www.apache.org/licenses/LICENSE-2.0
  #
  #    Unless required by applicable law or agreed to in writing, software
  #    distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
  #    WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
  #    License for the specific language governing permissions and limitations
  #    under the License.
  """
  Drivers for Solaris ZFS operations in local and iSCSI modes
  """
   :
   :

So you can have a look at that and see if you can get it to work.

You can find it here:

  https://java.net/projects/solaris-userland/sources/gate/show/components/openstack


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"

