Re: [OmniOS-discuss] [developer] Introducing io-lx -- an attempt to port LX Zones to OmniOS

2016-03-07 Thread Joshua M. Clulow 
On 7 March 2016 at 22:37, Jim Klimov  wrote:
> Cool! Will this include modernized linux distro support?

At Joyent, we have pre-built zone images (which we ship as "zfs send"
streams) for at least Ubuntu 14.04 and 15.04, Centos 6 and 7, Debian 7
and 8, and Alpine 3.  You could arguably distribute the same files in
a tar archive which you would extract into a zone root.  From what I
remember of the old days, a seed archive was the way to bootstrap an
LX zone.

The LX brand software has been substantially enhanced since the Sun
EOL of the 2.4-era bits; e.g., support for modern system calls and
other Linux facilities, 64-bit support, etc.


Cheers.

-- 
Joshua M. Clulow
UNIX Admin/Developer
http://blog.sysmgr.org
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] CIFS ignores TCP Buffer Settings

2016-03-07 Thread Jim Klimov 
8 марта 2016 г. 6:42:13 CET, Mini Trader  пишет:
>Is it possible that CIFS will ignore TCP buffer settings after a while?
>
>I've confirmed my systems max transfer rate using iperf and have tuned
>my
>buffers accordingly. For whatever reason CIFS seems to forget these
>settings after a while as speed drops significantly. Issuing a restart
>of
>the service immediately appears to restore the setting as transfer
>speed
>becomes normal again.
>
>Any ideas why this would happen?
>
>
>
>
>___
>OmniOS-discuss mailing list
>OmniOS-discuss@lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

As a random guess from experience with other network stuff - does the 
speed-drop happen on a running connection or new ones too? Do you have 
concurrent transfers at this time?

Some other subsystems (no idea if this one too) use best speeds for new or 
recently awakened dormant connections, so short-lived bursts are fast - at 
expence of long-running active bulk transfers (deemed to be bulk because they 
run for a long time).

HTH, Jim
--
Typos courtesy of K-9 Mail on my Samsung Android
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] [developer] Introducing io-lx -- an attempt to port LX Zones to OmniOS

2016-03-07 Thread Jim Klimov 
8 марта 2016 г. 3:47:10 CET, Dan McDonald  пишет:
>Hello!
>
>700+ cherrypicked commits later, and at least I haven't obviously
>regressed lipkg/ipkg zones.  :)
>
>This github repo:
>
>   https://github.com/danmcd/io-lx-public/
>
>is the beginning of my attempt to port LX zones over to OmniOS.  I KNOW
>there's a lot more work to be done, but I wanted to make sure this repo
>is viewable by the public so:
>
>1.) People know about it.
>
>2.) People who are interested in helping can do so.
>
>3.) People can laugh at all of the mismerges and other flub-ups I'm
>sure I haven't caught yet.  :)
>
>4.) I will be context-switching to OmniOS r151018 ramp-up very soon,
>and want to checkpoint state.
>
>I've Bcc:ed the SmartOS (home of LX zones) and the illumos (where I
>hope this work can be upstreamed at some point) lists.  Discussion on
>io-lx (Illumos-OmniOS-LX) should take place either on github or on the
>OmniOS mailing list.
>
>So far:
>
>- I've sidepulled 700+ commits, ending with illumos-joyent's
>8443e038ef8eb3ca6a95818d6e90b2a1eb4e9cb6.  There are some more
>illumos-joyent commits I'll need to bring over, but my cherrypicking
>script and setups are primed & tested, so I *should* be able to make
>short work of it.
>
>- I've smoke-tested a global-only OmniOS boot, and a single-lipkg zone
>OmniOS boot.  After some mismerge-related consternation, I booted the
>lipkg zone as well.  A rudimentary ppriv(1) comparison between root
>shells in global and lipkg zones was part of the smoke test.
>
>- Any files I didn't know where they went I put into the "brand/lx"
>package.  The inotify feature, for example, is in there, and perhaps it
>shouldn't be.
>
>- If you ONU to io-lx, note that to install brand/lx, you will need to
>UNINSTALL the "illumos-gate" consolidation package first.  I don't have
>changes in omnios-build or any of the other repos (like pkg5) yet.  I
>hope to avoid outside-illumos changes until it's time to figure out the
>admin model.
>
>After I'm comfortable with no ipkg/lipkg regressions, I will need to
>spend some design time figuring out how LX zones will look on OmniOS. 
>I will not be porting vmadm(1M) over from SmartOS, so I need to think
>about how LX will fit in with traditional zone tools.  I may discover
>other problems, but until I start the '018 process, and immediately
>after '018 ships, I will need to ensure no ipkg/lipkg regressions first
>and foremost.
>
>It's not much, but it's a start.
>
>Thanks for your time & patience,
>Dan
>
>
>
>---
>illumos-developer
>Archives: https://www.listbox.com/member/archive/182179/=now
>RSS Feed:
>https://www.listbox.com/member/archive/rss/182179/22416750-c03c8c44
>Modify Your Subscription:
>https://www.listbox.com/member/?member_id=22416750_secret=22416750-eb7e3ed7
>Powered by Listbox: http://www.listbox.com

Cool! Will this include modernized linux distro support?

As for the admin model... I tinkered with original lx24 guest zones back in the 
day, and it looked similar to usual solaris zones in terms of experience, 
except the console bootup reported some services as missing or disabled. Do you 
expect to produce something very different nowadays?

Thanks for the effort,
Jim
--
Typos courtesy of K-9 Mail on my Samsung Android
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] [smartos-discuss] Introducing io-lx -- an attempt to port LX Zones to OmniOS

2016-03-07 Thread Garrett D'Amore 
Congratulations.  Hopefully I'll have some time to help you. I'm excited about 
this effort. 

Sent from my iPhone

> On Mar 7, 2016, at 6:47 PM, Dan McDonald  wrote:
> 
> Hello!
> 
> 700+ cherrypicked commits later, and at least I haven't obviously regressed 
> lipkg/ipkg zones.  :)
> 
> This github repo:
> 
>https://github.com/danmcd/io-lx-public/
> 
> is the beginning of my attempt to port LX zones over to OmniOS.  I KNOW 
> there's a lot more work to be done, but I wanted to make sure this repo is 
> viewable by the public so:
> 
> 1.) People know about it.
> 
> 2.) People who are interested in helping can do so.
> 
> 3.) People can laugh at all of the mismerges and other flub-ups I'm sure I 
> haven't caught yet.  :)
> 
> 4.) I will be context-switching to OmniOS r151018 ramp-up very soon, and want 
> to checkpoint state.
> 
> I've Bcc:ed the SmartOS (home of LX zones) and the illumos (where I hope this 
> work can be upstreamed at some point) lists.  Discussion on io-lx 
> (Illumos-OmniOS-LX) should take place either on github or on the OmniOS 
> mailing list.
> 
> So far:
> 
> - I've sidepulled 700+ commits, ending with illumos-joyent's 
> 8443e038ef8eb3ca6a95818d6e90b2a1eb4e9cb6.  There are some more illumos-joyent 
> commits I'll need to bring over, but my cherrypicking script and setups are 
> primed & tested, so I *should* be able to make short work of it.
> 
> - I've smoke-tested a global-only OmniOS boot, and a single-lipkg zone OmniOS 
> boot.  After some mismerge-related consternation, I booted the lipkg zone as 
> well.  A rudimentary ppriv(1) comparison between root shells in global and 
> lipkg zones was part of the smoke test.
> 
> - Any files I didn't know where they went I put into the "brand/lx" package.  
> The inotify feature, for example, is in there, and perhaps it shouldn't be.
> 
> - If you ONU to io-lx, note that to install brand/lx, you will need to 
> UNINSTALL the "illumos-gate" consolidation package first.  I don't have 
> changes in omnios-build or any of the other repos (like pkg5) yet.  I hope to 
> avoid outside-illumos changes until it's time to figure out the admin model.
> 
> After I'm comfortable with no ipkg/lipkg regressions, I will need to spend 
> some design time figuring out how LX zones will look on OmniOS.  I will not 
> be porting vmadm(1M) over from SmartOS, so I need to think about how LX will 
> fit in with traditional zone tools.  I may discover other problems, but until 
> I start the '018 process, and immediately after '018 ships, I will need to 
> ensure no ipkg/lipkg regressions first and foremost.
> 
> It's not much, but it's a start.
> 
> Thanks for your time & patience,
> Dan
> 
> 
> 
> ---
> smartos-discuss
> Archives: https://www.listbox.com/member/archive/184463/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/184463/22103350-51080293
> Modify Your Subscription: 
> https://www.listbox.com/member/?member_id=22103350_secret=22103350-a7c9ea51
> Powered by Listbox: http://www.listbox.com
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] CIFS ignores TCP Buffer Settings

2016-03-07 Thread Mini Trader 
Is it possible that CIFS will ignore TCP buffer settings after a while?

I've confirmed my systems max transfer rate using iperf and have tuned my
buffers accordingly. For whatever reason CIFS seems to forget these
settings after a while as speed drops significantly. Issuing a restart of
the service immediately appears to restore the setting as transfer speed
becomes normal again.

Any ideas why this would happen?
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] Introducing io-lx -- an attempt to port LX Zones to OmniOS

2016-03-07 Thread Dan McDonald 
Hello!

700+ cherrypicked commits later, and at least I haven't obviously regressed 
lipkg/ipkg zones.  :)

This github repo:

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

is the beginning of my attempt to port LX zones over to OmniOS.  I KNOW there's 
a lot more work to be done, but I wanted to make sure this repo is viewable by 
the public so:

1.) People know about it.

2.) People who are interested in helping can do so.

3.) People can laugh at all of the mismerges and other flub-ups I'm sure I 
haven't caught yet.  :)

4.) I will be context-switching to OmniOS r151018 ramp-up very soon, and want 
to checkpoint state.

I've Bcc:ed the SmartOS (home of LX zones) and the illumos (where I hope this 
work can be upstreamed at some point) lists.  Discussion on io-lx 
(Illumos-OmniOS-LX) should take place either on github or on the OmniOS mailing 
list.

So far:

- I've sidepulled 700+ commits, ending with illumos-joyent's 
8443e038ef8eb3ca6a95818d6e90b2a1eb4e9cb6.  There are some more illumos-joyent 
commits I'll need to bring over, but my cherrypicking script and setups are 
primed & tested, so I *should* be able to make short work of it.

- I've smoke-tested a global-only OmniOS boot, and a single-lipkg zone OmniOS 
boot.  After some mismerge-related consternation, I booted the lipkg zone as 
well.  A rudimentary ppriv(1) comparison between root shells in global and 
lipkg zones was part of the smoke test.

- Any files I didn't know where they went I put into the "brand/lx" package.  
The inotify feature, for example, is in there, and perhaps it shouldn't be.

- If you ONU to io-lx, note that to install brand/lx, you will need to 
UNINSTALL the "illumos-gate" consolidation package first.  I don't have changes 
in omnios-build or any of the other repos (like pkg5) yet.  I hope to avoid 
outside-illumos changes until it's time to figure out the admin model.

After I'm comfortable with no ipkg/lipkg regressions, I will need to spend some 
design time figuring out how LX zones will look on OmniOS.  I will not be 
porting vmadm(1M) over from SmartOS, so I need to think about how LX will fit 
in with traditional zone tools.  I may discover other problems, but until I 
start the '018 process, and immediately after '018 ships, I will need to ensure 
no ipkg/lipkg regressions first and foremost.

It's not much, but it's a start.

Thanks for your time & patience,
Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] RSF-1/ZFS panics node when offlining one iSCSI storage mirror

2016-03-07 Thread Stephan Budach 

Hi Dan,

Am 07.03.16 um 15:41 schrieb Dan McDonald:

On Mar 6, 2016, at 9:44 AM, Stephan Budach  wrote:

when I noted that one node would panic,

AS A RULE -- if you have an OmniOS box panic, you should save off the corefile 
(vmdump.N) and be able to share it with the list.  I understand this may be an 
RSF-1 panic, BUT if it's not, it'd be nice to know.

You can upload it to uploads.omniti.com if you wish, just request an upload 
token.

Dan

thanks - I will keep that in mind and I actually had a core dump 
available, but since I was testing around, I didn't mean to occupy 
anyone's time more than absolutely necessary and so I dumoed them.
Speaking of that incident, I have lowered the iSCSI connection timeout 
to 60s, which seems to be the lowest value supported by issueing a


iscsiadm modify initiator-node -T conn-login-max=60

and afterwards I used stmfadm offline target on the storage node to cut 
the target off. This time, the initiator timed out after 60s and that 
particular zpool changed it's status to degraded without anything 
happening. I still have to test that under load, but I will probably 
push that to next weekend.


Thanks,
Stephan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] RSF-1/ZFS panics node when offlining one iSCSI storage mirror

2016-03-07 Thread Dan McDonald 

> On Mar 6, 2016, at 9:44 AM, Stephan Budach  wrote:
> 
> when I noted that one node would panic,

AS A RULE -- if you have an OmniOS box panic, you should save off the corefile 
(vmdump.N) and be able to share it with the list.  I understand this may be an 
RSF-1 panic, BUT if it's not, it'd be nice to know.

You can upload it to uploads.omniti.com if you wish, just request an upload 
token.

Dan

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss