[smartos-discuss] avx2

[Fred Liu]

Hi,

I know qemu version on smartos is out of date. So kvm vm won’t have avx2 
instruction set by now. Will bhyve vm have them?

Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: https://www.listbox.com

Re: [smartos-discuss] Smartos bhyve support on AMD Sun Fire X4140

[Fred Liu]

Even Ryzen-based ?

Thanks

Fred




On Wed, Jul 4, 2018 at 1:56 AM +0800, "Jorge Schrauwen" 
mailto:sjorge...@blackdot.be>> wrote:

Yeah, no support as of yet. Although there does seem to be some interest in 
adding it eventually. (Based on conversations on IRC)

July 3, 2018 6:38 PM, "J?n Poctavek" 
mailto:jan.pocta...@erigones.com?to=%22J%C3%A1n%20Poctavek%22%20>>
 wrote:

Hi,

Just to be sure - so no AMD support again?
Jan

On 3. 7. 2018 11:42, Jorge Schrauwen wrote:
For now bhyve support on SmartOS requires VMX and EPT to work.
So older intel CPU without EPT or AMD CPU that use SVM are not support.

Regards

Jorge

July 3, 2018 11:15 AM, "Paolo Marcheschi" 
mailto:paolo.marches...@ftgm.it?to=%22paolo%20marcheschi%22%20%3cpaolo.marches...@ftgm.it%3E>>
 wrote:

Hi

Today I tried to run a bhyve VM on the latest Smartos:

SunOS 5.11 joyent_20180629T143106Z i86pc i386 i86pc

The server is an AMD Opteron Sun Fire X4140 :

psrinfo -vp The physical processor has 6 virtual processors (0-5) x86 
(AuthenticAMD 100F80 family 16 model 8 step 0 clock 2200 MHz) Six-Core AMD 
Opteron(tm) Processor 2427 [ Socket: F(1207) ] The physical processor has 6 
virtual processors (6-11) x86 (AuthenticAMD 100F80 family 16 model 8 step 0 
clock 2200 MHz) Six-Core AMD Opteron(tm) Processor 2427 [ Socket: F(1207) ]

when I try to create a bhyve VM I get:
#vmadm create -f centos.json
Bhyve not supported
Why ?
Thank you
Paolo




smartos-discuss | Archives 
| Modify Your Subscription   
[https://www.listbox.com/images/listbox-logo-small.png96494be.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Migration KVM to Bhyve - Performance Issues

[Fred Liu]

> -Original Message-
> From: Brian Bennett [mailto:brian.benn...@joyent.com]
> Sent: 星期日, 五月 27, 2018 2:14
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Migration KVM to Bhyve - Performance Issues
> 
> On May 26, 2018, at 6:57 AM, Humberto Ramirez   > wrote:
> 
> 
> 
>   Assuming some of this steps can be scripted is there plans for a "KVM  
> to
> Bhyve" conversion utility?
> 
> 
> 
> Joyent is looking into kvm->bhyve conversion being part of the product. It's
> certainly something we'd like to do, but there's a number of other bhyve 
> things
> that are being worked on first, and there are a number of architectural
> decisions that were changed with bhyve that makes direct conversion not quite
> so straight forward. In particular, the dataset layout has changed and kvm
> includes a mini dhcp server for networking, 

Any more details or source code about this mini dhcp server? Is it configurable?


whereas bhyve will consume the
> network settings using instance metadata.
> 
> --
> Brian Bennett
> Systems Engineer, Cloud Operations
> Joyent, Inc. | www.joyent.com 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] add device to OS/LX zone

[Fred Liu]

But creating ufs failed. It is just to emulate application's access on real 
hardware. I don't believe it will work as a raw block device.

Thanks.

Fred




On Tue, Feb 27, 2018 at 9:09 PM +0800, "Jorge Schrauwen" 
<sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>> wrote:


In your example you called newfs, which creates a new UFS file system.



I think if you don't create a filesystem on it and use it as a raw block device 
it should just work.
This is what qemu does when running inside a KVM branded zone.

Regards

Jorge

On 2018-02-27 14:05, Fred Liu wrote:

Actually?we need access the real hardware not the file system. There is some 
database software which claims having performance optimization on real 
hardware. I notice that we can tune zfs rec block size in vm, maybe that is 
another idea. Anyone tuned?

Thanks!

Fred





On Tue, Feb 27, 2018 at 8:45 PM +0800, "Jorge Schrauwen" 
<sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>> wrote:


Hi,

You probably want to set fs_allowed so it includes the filesystem you
are trying to create on it.

(from man vmadm)
fs_allowed:

This option allows you to specify filesystem types this zone
is allowed
to mount.  For example on a zone for building SmartOS you
probably want
to set this to: "ufs,pcfs,tmpfs".  To unset this property,
set the
value to the empty string.

type: string (comma separated list of filesystem types)
vmtype: OS
listable: no
create: yes
update: yes (requires zone reboot to take effect)

Regards

Jorge


On 2018-02-27 13:41, Fred Liu wrote:
> Hi,
> 
> For I have no spare hardware(disk), I have tried adding zvol to OS/LX
> zone. But it looks likes not working as the document.
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set
> match=/dev/zvol/rdsk/zones/device
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit
> 
> [root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
> [Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
> Last login: Tue Feb 27 20:25:02 on pts/6
>__.   .
>  _|  |_  | .-. .  . .-. :--. |-
> |__| ;|   ||  |(.-' |  | |
>   |__|   `--'  `-' `;-| `-' '  ' `-'
>/  ; Instance (base-multiarch-lts 15.4.0)
>`-'  https://docs.joyent.com/images/smartos/base
> 
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la
> /dev/zvol/rdsk/zones/device
> crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs
> /dev/zvol/rdsk/zones/device
> newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)?
> y
> can't check mount point; can't stat
> 
> Will the real hardware be different?
> 
> I also tried adding zvol to zones on solaris11.2. It works well.
> device:
>   match not specified
>   storage.template:
> dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
>   storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
>   0
>   bootpri: 0
> device:
>   match not specified
>   storage: dev:/dev/zvol/dsk/tank/device
>   2
>   bootpri: 2
> capped-memory:
>   physical: 2G
> keysource:
>   raw redacted
> zonecfg:kz01>
> 
> root@kz01:~# format
> Searching for disks...done
> 
> AVAILABLE DISK SELECTIONS:
> . c1d0
>   /kz-devices@ff/disk@0
>   c1d2
>   /kz-devices@ff/disk@2
> Specify disk (enter its number): ^C
> root@kz01:~# zpool create test1 c1d2
> root@kz01:~# zpool list
> NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
> rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
> test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
> root@kz01:~#
> 
> Thinking little bit more, for we already can add zvol to kvm zone, it
> should not be very hard to realize in OS/LX zone.
> 
> Thanks.
> 
> Fred
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] add device to OS/LX zone

[Fred Liu]

Actually?we need access the real hardware not the file system. There is some 
database software which claims having performance optimization on real 
hardware. I notice that we can tune zfs rec block size in vm, maybe that is 
another idea. Anyone tuned?

Thanks!

Fred




On Tue, Feb 27, 2018 at 8:45 PM +0800, "Jorge Schrauwen" 
<sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>> wrote:


Hi,

You probably want to set fs_allowed so it includes the filesystem you
are trying to create on it.

(from man vmadm)
fs_allowed:

This option allows you to specify filesystem types this zone
is allowed
to mount.  For example on a zone for building SmartOS you
probably want
to set this to: "ufs,pcfs,tmpfs".  To unset this property,
set the
value to the empty string.

type: string (comma separated list of filesystem types)
vmtype: OS
listable: no
create: yes
update: yes (requires zone reboot to take effect)

Regards

Jorge


On 2018-02-27 13:41, Fred Liu wrote:
> Hi,
> 
> For I have no spare hardware(disk), I have tried adding zvol to OS/LX
> zone. But it looks likes not working as the document.
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set
> match=/dev/zvol/rdsk/zones/device
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
> zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit
> 
> [root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
> [Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
> Last login: Tue Feb 27 20:25:02 on pts/6
>__.   .
>  _|  |_  | .-. .  . .-. :--. |-
> |__| ;|   ||  |(.-' |  | |
>   |__|   `--'  `-' `;-| `-' '  ' `-'
>/  ; Instance (base-multiarch-lts 15.4.0)
>`-'  https://docs.joyent.com/images/smartos/base
> 
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la
> /dev/zvol/rdsk/zones/device
> crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
> [root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs
> /dev/zvol/rdsk/zones/device
> newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)?
> y
> can't check mount point; can't stat
> 
> Will the real hardware be different?
> 
> I also tried adding zvol to zones on solaris11.2. It works well.
> device:
>   match not specified
>   storage.template:
> dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
>   storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
>   0
>   bootpri: 0
> device:
>   match not specified
>   storage: dev:/dev/zvol/dsk/tank/device
>   2
>   bootpri: 2
> capped-memory:
>   physical: 2G
> keysource:
>   raw redacted
> zonecfg:kz01>
> 
> root@kz01:~# format
> Searching for disks...done
> 
> AVAILABLE DISK SELECTIONS:
> . c1d0
>   /kz-devices@ff/disk@0
>   c1d2
>   /kz-devices@ff/disk@2
> Specify disk (enter its number): ^C
> root@kz01:~# zpool create test1 c1d2
> root@kz01:~# zpool list
> NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
> rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
> test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
> root@kz01:~#
> 
> Thinking little bit more, for we already can add zvol to kvm zone, it
> should not be very hard to realize in OS/LX zone.
> 
> Thanks.
> 
> Fred
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] add device to OS/LX zone

[Fred Liu]

Hi,

For I have no spare hardware(disk), I have tried adding zvol to OS/LX zone. But 
it looks likes not working as the document.
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> set 
match=/dev/zvol/rdsk/zones/device
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8:device> end
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> verify
zonecfg:f58e8c87-eb04-ea48-bf23-9b7be32515b8> exit

[root@pluto /zones/build]# zlogin f58e8c87-eb04-ea48-bf23-9b7be32515b8
[Connected to zone 'f58e8c87-eb04-ea48-bf23-9b7be32515b8' pts/6]
Last login: Tue Feb 27 20:25:02 on pts/6
   __.   .
 _|  |_  | .-. .  . .-. :--. |-
|__| ;|   ||  |(.-' |  | |
  |__|   `--'  `-' `;-| `-' '  ' `-'
   /  ; Instance (base-multiarch-lts 15.4.0)
   `-'  https://docs.joyent.com/images/smartos/base

[root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# ls -la 
/dev/zvol/rdsk/zones/device
crw--- 1 root sys 90, 26 Feb 27 20:35 /dev/zvol/rdsk/zones/device
[root@f58e8c87-eb04-ea48-bf23-9b7be32515b8 ~]# newfs /dev/zvol/rdsk/zones/device
newfs: construct a new file system /dev/zvol/rdsk/zones/device: (y/n)? y
can't check mount point; can't stat 


Will the real hardware be different?

I also tried adding zvol to zones on solaris11.2. It works well.
device:
match not specified
storage.template: 
dev:/dev/zvol/dsk/%{global-rootzpool}/VARSHARE/zones/%{zonename}/disk%{id}
storage: dev:/dev/zvol/dsk/rpool/VARSHARE/zones/kz01/disk0
id: 0
bootpri: 0
device:
match not specified
storage: dev:/dev/zvol/dsk/tank/device
id: 2
bootpri: 2
capped-memory:
physical: 2G
keysource:
raw redacted
zonecfg:kz01> 

root@kz01:~# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
   0. c1d0 
  /kz-devices@ff/disk@0
   1. c1d2 
  /kz-devices@ff/disk@2
Specify disk (enter its number): ^C
root@kz01:~# zpool create test1 c1d2
root@kz01:~# zpool list
NAMESIZE  ALLOC   FREE  CAP  DEDUP  HEALTH  ALTROOT
rpool  15.9G  5.35G  10.5G  33%  1.00x  ONLINE  -
test1  9.94G   124K  9.94G   0%  1.00x  ONLINE  -
root@kz01:~#

Thinking little bit more, for we already can add zvol to kvm zone, it should 
not be very hard to realize in OS/LX zone.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] rotate-kvm-log

[Fred Liu]

> 
> Hi Fred,
> 
> That'll only be true if the KVM VM is never booted. Whenever it is booted, the
> file will be non-empty until it is rotated since there are always messages
> written to the log when a KVM VM boots.
> 

 All of my KVM VMs are definitely running now.  I think
It came from the 'copytruncate' by "logadm -c". Once rotate-kvm-logs.sh ends,
all the non-empty vm.log files are rotating into "/var/log/sdc/upload/qemu-xxx".
And if rotate-kvm-log.sh runs again, no new entry will be generated.

 
> 
> 
>   Plus, I also notice that there is logadm invocation during "vmadm 
> create"
> in lines from #625 to #641 of source
> (https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef
> 4aea42e5a6f3/src/vm/sbin/vmadmd.js#L625
>  f4aea42e5a6f3/src/vm/sbin/vmadmd.js#L625> ) --
> 
> 
> 
> 
> You're right. I had forgotten about this code in vmadmd. I had looked only at
> vmadm.
> 
> I don't see how this changes anything though. Because it's still the
> rotate-kvm-logs.sh that it's calling to do the rotation. The same thing would
> have happened at the first cron execution after this if vmadmd didn't do it.
> 
> Since it seems that fixing the bug in logadm that causes this problem might be
> a while still in coming, I will look into the prospect of adding a workaround 
> that
> runs:
> 
> logadm -r /zones//root/tmp/vm.log
> 
> when deleting a KVM VM, or in the rotate-kvm-logs.sh itself when it sees a VM
> no longer exists. I've filed https://smartos.org/bugview/OS-6053 to look into
> this.

From my side, the intuitive and direct way is removing the entry by "vmadm 
destroy".
We can also add the similar cose in vmadmd source.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] rotate-kvm-log

[Fred Liu]

>From: Josh Wilsdon [mailto:jwils...@joyent.com] 
>Sent: 星期三, 四月 12, 2017 0:25
>To: smartos-discuss@lists.smartos.org
>Subject: Re: [smartos-discuss] rotate-kvm-log


>Yes. But "/usr/vm/sbin/rotate-kvm-logs.sh script" won't add entries in 
>"/var/logadm/timestamps" like following:
 
>"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
>05:20:15 2017'"

>The weirdness is how this type of entry has been added per every kvm instance?

>Fred,

>That's exactly what the entries look like that come from running 
>rotate-kvm-logs.sh. What evidence do you have that it's not that script? When 
>I manually ran rotate-kvm-logs.sh without any cron involved, it just generated 
>an entry:

>/zones/3d93a436-3a86-4406-ae69-fbaaf67b45b7/root/tmp/vm.log -P 'Tue Apr 11 
>16:20:40 2017'

Josh,

I think I see exactly the same issue 
(https://github.com/joyent/smartos-live/issues/319).
The reason why I haven't got the concerning entry is lines from  #36 to #38 of 
the source 
(https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef4aea42e5a6f3/src/vm/sbin/rotate-kvm-logs.sh#L36)
 -- 

"
 if [[ ! -s ${logfile} ]]; then
# file doesn't exist or is empty
return;
fi
".

Because all my ${logfile} has size of 0,   rotate_log() returns.
And the script won't go to lines from #72 to 
#78(https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef4aea42e5a6f3/src/vm/sbin/rotate-kvm-logs.sh#L72)
 -- 

"
logadm \
-c \
-s 1b \
-p now \
-t '$dirname/vm.log.rotating' \
-R "cat \$file >> ${destfile} && rm -f \$file" \
${logfile}
"

Plus, I also notice that there is logadm invocation during "vmadm create" in 
lines from #625 to #641 of source 
(https://github.com/joyent/smartos-live/blob/64998c0b5a7c33287eb7dd118fef4aea42e5a6f3/src/vm/sbin/vmadmd.js#L625)
 --

"
unction rotateKVMLog(vm_uuid)
{
setTimeout(function () {
execFile('/usr/vm/sbin/rotate-kvm-logs.sh', [vm_uuid],
function (error, stdout, stderr) {
if (error) {
log.error({err: error, stdout: stdout, stderr: stderr},
'failed to rotate kvm log for just-booted ' + vm_uuid);
return;
}
log.debug({stdout: stdout, stderr: stderr}, 'rotated kvm log '
+ 'for just-booted ' + vm_uuid);
return;
}
);
}, 30 * 1000);
}

"

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] rotate-kvm-log

[Fred Liu]

>From: Josh Wilsdon [mailto:jwils...@joyent.com] 
>It doesn't go in logadm.conf. The rotation happens via the 
>/usr/vm/sbin/rotate-kvm-logs.sh script which is run by root's crontab in the 
>GZ.

Yes. But "/usr/vm/sbin/rotate-kvm-logs.sh script" won't add entries in 
"/var/logadm/timestamps" like following:

"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
05:20:15 2017'"

The weirdness is how this type of entry has been added per every kvm instance?


Thanks.

Fred





---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] rotate-kvm-log

[Fred Liu]

But there is  nothing about rotate-kvm-log in /etc/logadm.conf from stock. It 
is weird. How were these entries had been added in time stamp? It should be 
logadm command invoking. But where was it invoked? I haven't done it manually.


Fred

Get Outlook for iOS



On Tue, Apr 11, 2017 at 3:52 AM +0800, "Josh Wilsdon" 
> wrote:


I am running joyent_20161013T025521Z now. It seems in this version 
rotate-kvm-log is done by cron not logadm.
But I also noticed when a kvm instance was created there was a corresponding 
entry occurred in /var/logadm/timestamp like following:
"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
05:20:15 2017'". Is this from the "vmadm create" operation?

And it looks because of this bug(https://smartos.org/bugview/OS-3097), if the 
kvm instance is destroyed, the corresponding logadm action won't be removed.


Hi Fred,

Using "vmadm create" does not do anything with log rotation, neither does 
"vmadm delete", but what you're seeing there does look like what ends up 
happening due to this logadm bug.

Thanks,
Josh
smartos-discuss | Archives 
[https://www.listbox.com/images/feed-icon-10x10.jpg96494be.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
   | 
Modify Your Subscription   
[https://www.listbox.com/images/listbox-logo-small.png96494be.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] rotate-kvm-log

[Fred Liu]

Hi,

I am running joyent_20161013T025521Z now. It seems in this version 
rotate-kvm-log is done by cron not logadm.
But I also noticed when a kvm instance was created there was a corresponding 
entry occurred in /var/logadm/timestamp like following:
"/zones/c3f09892-f36e-4784-9853-b4ceb3e762da/root/tmp/vm.log -P 'Wed Jan  4 
05:20:15 2017'". Is this from the "vmadm create" operation?

And it looks because of this bug(https://smartos.org/bugview/OS-3097), if the 
kvm instance is destroyed, the corresponding logadm action won't be removed.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] vnic mac address updatable?

[Fred Liu]

> -Original Message-
> From: Johan Claesson [mailto:jo...@jobetech.se]
> Sent: 星期四, 一月 05, 2017 20:01
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] vnic mac address updatable?
> 
> 2017-01-05 04:32 skrev Fred Liu:
> > Hi,
> >
> >
> > Sorry, if there is already answer. From crossbow heritage, this
> > property should be configurable just like what I am doing in LDOM of
> > Solaris.
> > What is the reason why it is not applicable in smartos? The main
> > purpose here is to migrate legacy hardware.
> >
> 
> The MAC of a VNIC can only be set during creation.
> So, you first need to remove it and then re-add it with the "mac"
> property set to you desired value.
> If you don't set the "mac" property it will be auto-generated for you.
> 
> 

It works exactly as what you described.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] vnic mac address updatable?

[Fred Liu]

Hi,


Sorry, if there is already answer. From crossbow heritage, this property should 
be configurable just like what I am doing in LDOM of Solaris.
What is the reason why it is not applicable in smartos? The main purpose here 
is to migrate legacy hardware.



Thanks.



Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] vnc resolution configurable?

[Fred Liu]

Hi,

We noticed that GUI since SL7.2 did not work with the low resolution 1024x768 
which is the default-detected resolution from SmartOS vnc server.
Is there a way to configure the vnc to run in higher resolution like 1280x1024? 
And I don't need to hack Linux to forcedly run in higher resolution.

BTW, is spice stable enough on SmartOS?


Thanks.

Fred
> -Original Message-
> From: Nahum Shalman [mailto:nshalman-smar...@elys.com]
> Sent: 星期一, 三月 25, 2013 21:01
> To: smartos-discuss@lists.smartos.org
> Cc: Alain O'Dea
> Subject: Re: [smartos-discuss] Cannot get working VNC Viewer onto KVM Zone
> 
> On 03/23/2013 09:56 PM, Alain O'Dea wrote:
> > Is SPICE a feasible option here?  I notice the experimental
> > configuration options for it.  I'm really only looking at having a
> > console long enough to install the OS and bootstrap a Bomgar session
> > onto the desktop.
> 
> Feasible, possibly. Ideal, probably not.
> In order to use Spice, you need to use an alternate QEMU binary rather than
> the one that ships with the platform.
> (See http://wiki.smartos.org/display/DOC/Spice+on+SmartOS for details)
> 
> The benefit of using "my" QEMU is that you can use Spice. The biggest down
> side is that if you run into problems, you're not using the Joyent supported
> QEMU.
> 
> One option if you're trying to build a fresh image to use later as a template 
> that
> will have SSH already working, you could try using the Spice enabled QEMU for
> the stage of building your image, verify that a fresh boot of that image does
> bring up SSH as desired, then use that image with the platform QEMU.
> 
> So, order of preference from best to worst from my perspective:
>Try to get VNC working.
>Use Spice enabled QEMU for image building, platform QEMU for production
> workload.
>Use Spice enabled QEMU for building and running in production
> 
> I do run "my" QEMU in production, but I can't provide support.
> 
> -Nahum
> 
> P.S.  I might not-so-secretly be hoping that you'll choose #3 *and* that 
> you'll
> then ask Joyent to support it... A guy can dream.
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] RE: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

[Fred Liu]

This is encouraging!

Thanks.

Fred

> -Original Message-
> From: wo...@4amlunch.net [mailto:wo...@4amlunch.net]
> Sent: 星期三, 十一月 30, 2016 20:04
> To: Fred Liu
> Cc: omnios-disc...@lists.omniti.com; smartos-discuss@lists.smartos.org;
> Discussion list for OpenIndiana; develo...@lists.illumos.org
> Subject: Re: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?
> 
> I'm using ConnectX-2 cards in my OmniOS fileserver. Everything works 
> perfectly.
> Including SRP (SCSI RDMA). I use it with ESXi hosts.
> 
> -brian
> 
> > On Nov 30, 2016, at 06:47, Fred Liu <fred_...@issi.com> wrote:
> >
> > Hi,
> >
> > Please post if you know.
> >
> >
> > Thanks.
> >
> > Fred
> > ___
> > OmniOS-discuss mailing list
> > omnios-disc...@lists.omniti.com
> > http://lists.omniti.com/mailman/listinfo/omnios-discuss


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] any supoorted in Mellanox HBA in illumos?

[Fred Liu]

Hi,

Please post if you know.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] SmartOS release-20161013

[Fred Liu]

> -Original Message-
> From: Trent Mick [mailto:trent.m...@joyent.com]
> Sent: 星期五, 十月 14, 2016 5:35
> To: smartos-discuss@lists.smartos.org
> Subject: [smartos-discuss] SmartOS release-20161013
> 
> Hello All,
> 
> The latest bi-weekly "release" branch build of SmartOS is up:
> 
> curl -C - -O
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest
> .iso
> curl -C - -O
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest
> -USB.img.bz2
> curl -C - -O
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos-latest.
> vmwarevm.tar.bz2
> 
> A generated changelog is here:
> 
> 
> https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos.html#
> 20161013T025521Z
> 
> The full build bits directory, for those interested, is here in Manta:
> 
> /Joyent_Dev/public/SmartOS/20161013T025521Z
> 
> 
> # Highlights
> 
> - NVMe 1.1 support
> - GNU screen has been updated to 4.4.0-32, and now includes support for
> vertical
>   splits.
> 
> 
We are running this release for several days. Works like charm!
1): NVMe 1.1 is so sweet.
2): USB device is recognized again.
3): KVM improvement -- ext4 corruption warning disappears in SL6.7.

Tremendous thanks for your awesome work!!


Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] enable services in smartos

[Fred Liu]

> -Original Message-
> From: Jonathan Perkin [mailto:jper...@joyent.com]
> Sent: 星期二, 十月 18, 2016 17:33
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] enable services in smartos
> 
> * On 2016-10-18 at 10:19 BST, Fred Liu wrote:
> 
> > It looks nis/client has been added as a dependency in 20160901 but
> > not in 20160527 like following;
> 
> Correct, this was to fix https://smartos.org/bugview/OS-5568
> 
> > I totally understand minimalism, but some disabled services we
> > really need such ldap, dns and nis etc.
> >
> > What is the simplest way to enable these services?
> 
> I would use jclulow's rc.local gist:
> 
>   https://gist.github.com/jclulow/2606370
> 
> and then just add the svcadm commands to the postboot script.
> 

Good idea as a command hub!


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] enable services in smartos

[Fred Liu]

Hi

It looks nis/client has been added as a dependency in 20160901 but not in 
20160527 like following;

uname -a
SunOS pluto 5.11 joyent_20160901T054050Z i86pc i386 i86pc
svcs -l name-services
fmri svc:/milestone/name-services:default
name name services milestone
enabled  true
stateonline
next_state   none
state_time   October 18, 2016 01:40:50 PM CST
alt_logfile  /etc/svc/volatile/milestone-name-services:default.log
logfile  /var/svc/log/milestone-name-services:default.log
restartersvc:/system/svc/restarter:default
dependency   optional_all/refresh svc:/network/dns/client (disabled)
dependency   optional_all/refresh svc:/network/ldap/client (disabled)
dependency   optional_all/refresh svc:/network/nis/client (disabled)


uname -a
SunOS kepler-452b 5.11 joyent_20160527T033529Z i86pc i386 i86pc

svcs -l name-services
fmri svc:/milestone/name-services:default
name name services milestone
enabled  true
stateonline
next_state   none
state_time   October 18, 2016 05:05:38 PM CST
alt_logfile  /etc/svc/volatile/milestone-name-services:default.log
logfile  /var/svc/log/milestone-name-services:default.log
restartersvc:/system/svc/restarter:default
dependency   optional_all/refresh svc:/network/dns/client (disabled)
dependency   optional_all/refresh svc:/network/ldap/client (disabled)
dependency   optional_all/refresh svc:/network/nis/client (absent)

I totally understand minimalism, but some disabled services we really need such 
ldap, dns and nis etc.

What is the simplest way to enable these services?
I have tried add my own services under /opt but it can't be a dependency for 
other services because of hard-coded name space.
I also think about enabling them when build smartos. Is there anyone who knows 
how to do it when I am building smartos?
Building normally takes some time. And it should not be a best way.
Brainstorm.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Samsung 950 Pro on SmartOS?

[Fred Liu]

> -Original Message-
> From: Fred Liu
> Sent: 星期三, 三月 09, 2016 13:02
> To: smartos-discuss@lists.smartos.org
> Cc: illumos-developer
> Subject: RE: [smartos-discuss] Samsung 950 Pro on SmartOS?
> 
> 
> 
> From: Dirk Steinberg [mailto:d...@steinbergnet.net]
> Sent: 星期三, 三月 09, 2016 0:06
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Samsung 950 Pro on SmartOS?
> 
> 
> Am 07.03.2016 um 06:48 schrieb Fred Liu <fred.f...@gmail.com>:
> 
> 
> 2016-03-05 21:19 GMT+08:00 Dirk Steinberg <d...@steinbergnet.net>:
> > Apart from that: is NVMe support in SmartOS considered stable?
> 
> 
> There is driver support for it in the system. I have not heard many
> reports positively or negatively about it.
> 
> [Fred]: I am testing some Intel P3600 NVMe SSD. In normal workload, they just
> work . But in burning mode like continuous scrubbings, I have got lots of
> checksum errors. And I tested the same scrubbings under Linux, no checksum
> errors were found.
> Fred
> 
> Hi Fred,
> 
> do you attribute these errors to the SmartOS NVMe driver?
> Sounds like it since you are saying that the same SSD works under Linux.
> 
> So have you given up on NVMe on SmartOS?
> 
> [Fred]: I personally attribute those errors to the immaturity of the NVMe 
> driver
> in Illumos. But that  is not so severe based on the fact that there are no
> substantial data loss with those checksum errors.
> I used to get some some kernel panics under "too may check sum erros" and
> after disabling "sha512|skeun|edonr" checksum algorithm, the server has
> been running well for more than two weeks.
> It looks like "sha512|skeun|edonr" checksum algorithm still has some glitches.
> 
> Thanks.
>

[Fred]: With the patch 7321 (https://www.illumos.org/issues/7312), I can 
confirm these checksum errors are all gone.


Thanks.

Fred 
> 
> Sorry, I am not quite sure what you are trying to tell me.
> 
> I am running the sha512 hash on a regular disk pool without problems. I have
> also
> run a number of scrubs. I assume the the sha512 hash is working correctly.
> If I had a ton of checksum errors from ZFS I would be VERY concerned.
> Just turning off the checksum may not be the solution…
> I do not think that a bug in sha512 is generating these.
> 
> Also, what do you mean by „no substantial data loss“? Either there is
> data loss or there is no data loss. My policy here is that even a single
> bit of data loss is not acceptable. This is why ZFS goes to all the
> effort of using strong checksums and redundancy and scrubbing and so on…
> 
> If you are willing to accept „some nonsubstantial data loss“ and turn
> of checksums so as not to be bothered by all these checksum errors
> there is not much point in using ZFS in the first place!
> 
> Am I understanding something incorrectly?
> 
> [Fred]: "NVMe support" and "[sha512|skein|edonr] hash algorithm" are the
> major spot-lights
>  of Illumos in 2015. I am running 20160218T022556Z now. Disabling
> "sha512|skein|edonr"
>  doesn't mean setting "checksum=off". In default("checksum=on"),
> zfs automatically
>  selects an appropriate algorithm if these
> features("[sha512|skein|edonr]") are enabled.
>  I met random server reboots(triggered by zfs deadman) and panics.
> But I could not get
>  the nitty-gritty reason from core dump. And we do have very stable
> running of release of
>  2014. To reason by exclusive method, I recreated the zpool and set
> "checksum=sha256". And
>  till now the server has been running well at least for two weeks.
> This operation does
>  not intend to remove the *annoying* checksum errors.
>  As for "no substantial data loss", that means "zpool status" always
> show "errors: No known data errors" even with "too many checksum errors".
> 
> Thanks.
> 
> Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Any possibilities in python OSError?

[Fred Liu]

Hi,

We are running some python scripts in LX brand ((CentOS 6.7 20151005).
And we get following errors:

File "/tool/iqs/bin/execd.py", line 416, in polljob
runfiles = [int(f) for f in os.listdir(RUNDIR) if f.isdigit()]
exceptions.OSError: [Errno 4] Interrupted system call: '/tool/iqs/run'



They have been running well under normal Linux OS.

Any possibilities?


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] test

[Fred Liu]

---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Re: Any possibilities in python OSError?

[Fred Liu]

> -Original Message-
> From: Richard Elling [mailto:richard.ell...@richardelling.com]
> Sent: 星期一, 五月 16, 2016 21:45
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Re: Any possibilities in python OSError?
> 
> 
> > On May 16, 2016, at 3:40 AM, Fred Liu <fred.f...@gmail.com> wrote:
> >
> > It could be the slow read from the nfs path -- "/tool/iqs/run".
> > We see nfs v4 client not working in LX brand(I have already opened OS-5265).
> > And nfs v3 client is working but it has obvious lag( about 5-10
> > seconds) at the very first try to mount nfs path.
> > As long as the mount is done, there is no obvious lag in coming
> > nfs-related operations.
> > And further, we find if SmartOS where LX brands are living in serve
> > nfs service, the lag won't appear.
> > It could be something happened in network path.
> 
> this is consistent with name lookup timeout. double check dns, ldap, and all
> other name sources.
> 

I checked /etc/nsswitch.conf and I get following:
hosts:  files nis dns

The nfs server has already put in /etc/hosts file.

The lag on the very first try to mount is still there.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 16:30 GMT+08:00 Fred Liu <fred.f...@gmail.com>:
> 2016-05-17 15:41 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>>
>>> On 17 May 2016, at 08:25, Fred Liu <fred.f...@gmail.com> wrote:
>>>
>>> 2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>>>>
>>>>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote:
>>>>>
>>>>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
>>>>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>>>>>>> I have no success to boot the system V init scripts.
>>>>>>> Any success here?
>>>>>>
>>>>>> Can you give us a bit more detail about what you're doing?  Is this a
>>>>>> custom script you have added to your machine?  Is it in the global
>>>>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
>>>>>> what path did you install the file?
>>>>>>
>>>>>>
>>>>>> Cheers.
>>>>>>
>>>>>
>>>>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
>>>>> I installed it on /etc/init.d/iqs. It is just a simple sh script:
>>>>
>>>> Add “set -x” near the start of the script and find out where it is failing.
>>>>
>>>
>>> It can be started manually  with no problems.
>>> The issue it can't be automatically started when we reboot LX Brand.
>>> Because the boot process is totally different in LX Brand.
>>> So the question converts to how to debug the boot process in LX Brand.
>>
>> OK, that’s some useful extra detail. Does something even *try* to run your 
>> script? Have you used chkconfig to enable it for the right Linux run levels? 
>> Maybe the LX zone isn’t in the run level you think it is.
>>
>> I would have thought that set -x could still be helpful if the output is 
>> captured in a system log which you can look at later. (I don’t recall what 
>> Linux does.) Or echo something into a tmp file, and see if that gets written 
>> during the boot.
>>
>
> Added "-x" and rebooted.
> /var/log/message:
>
> May 17 16:26:56 sha01 init: tty (console) main process (3698) killed
> by TERM signal
> May 17 16:26:57 sha01 xinetd[3549]: Exiting...
> May 17 16:27:19 sha01 rpcbind: rpcbind terminating on signal. Restart
> with "rpcbind -w"
> May 17 16:27:20 sha01 kernel: Kernel logging (proc) stopped.
> May 17 16:27:20 sha01 rsyslogd: [origin software="rsyslogd"
> swVersion="5.8.10" x-pid="3374" x-info="http://www.rsyslog.com;]
> exiting on signal 15.
> May 17 16:27:26 sha01 kernel: imklog 5.8.10, log source = /proc/kmsg started.
> May 17 16:27:26 sha01 rsyslogd: [origin software="rsyslogd"
> swVersion="5.8.10" x-pid="4476" x-info="http://www.rsyslog.com;] start
> May 17 16:27:26 sha01 rpc.statd[4520]: Version 1.2.3 starting
> May 17 16:27:26 sha01 sm-notify[4521]: Version 1.2.3 starting
> May 17 16:27:26 sha01 ypbind[4566]: Connection to D-BUS system message
> bus failed: Failed to connect to socket
> /var/run/dbus/system_bus_socket: No such file or directory.
> May 17 16:27:28 sha01 ypbind: NIS domain: issish, NIS server: cn07
> May 17 16:27:30 sha01 xinetd[4675]: xinetd Version 2.3.14 started with
> libwrap loadavg labeled-networking options compiled in.
> May 17 16:27:30 sha01 xinetd[4675]: Started working: 1 available service
>
> Seems nothing special.
>
> Thanks.
>

After 2-3 minutes, it finally works!
I am sure it is related to the issue that there is a lag on the very
first try to mount nfs v3 path in Linux Brand.

Anyway, many thanks for your nice help!!

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 15:41 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>
>> On 17 May 2016, at 08:25, Fred Liu <fred.f...@gmail.com> wrote:
>>
>> 2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>>>
>>>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote:
>>>>
>>>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
>>>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>>>>>> I have no success to boot the system V init scripts.
>>>>>> Any success here?
>>>>>
>>>>> Can you give us a bit more detail about what you're doing?  Is this a
>>>>> custom script you have added to your machine?  Is it in the global
>>>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
>>>>> what path did you install the file?
>>>>>
>>>>>
>>>>> Cheers.
>>>>>
>>>>
>>>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
>>>> I installed it on /etc/init.d/iqs. It is just a simple sh script:
>>>
>>> Add “set -x” near the start of the script and find out where it is failing.
>>>
>>
>> It can be started manually  with no problems.
>> The issue it can't be automatically started when we reboot LX Brand.
>> Because the boot process is totally different in LX Brand.
>> So the question converts to how to debug the boot process in LX Brand.
>
> OK, that’s some useful extra detail. Does something even *try* to run your 
> script? Have you used chkconfig to enable it for the right Linux run levels? 
> Maybe the LX zone isn’t in the run level you think it is.
>
> I would have thought that set -x could still be helpful if the output is 
> captured in a system log which you can look at later. (I don’t recall what 
> Linux does.) Or echo something into a tmp file, and see if that gets written 
> during the boot.
>

Added "-x" and rebooted.
/var/log/message:

May 17 16:26:56 sha01 init: tty (console) main process (3698) killed
by TERM signal
May 17 16:26:57 sha01 xinetd[3549]: Exiting...
May 17 16:27:19 sha01 rpcbind: rpcbind terminating on signal. Restart
with "rpcbind -w"
May 17 16:27:20 sha01 kernel: Kernel logging (proc) stopped.
May 17 16:27:20 sha01 rsyslogd: [origin software="rsyslogd"
swVersion="5.8.10" x-pid="3374" x-info="http://www.rsyslog.com;]
exiting on signal 15.
May 17 16:27:26 sha01 kernel: imklog 5.8.10, log source = /proc/kmsg started.
May 17 16:27:26 sha01 rsyslogd: [origin software="rsyslogd"
swVersion="5.8.10" x-pid="4476" x-info="http://www.rsyslog.com;] start
May 17 16:27:26 sha01 rpc.statd[4520]: Version 1.2.3 starting
May 17 16:27:26 sha01 sm-notify[4521]: Version 1.2.3 starting
May 17 16:27:26 sha01 ypbind[4566]: Connection to D-BUS system message
bus failed: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory.
May 17 16:27:28 sha01 ypbind: NIS domain: issish, NIS server: cn07
May 17 16:27:30 sha01 xinetd[4675]: xinetd Version 2.3.14 started with
libwrap loadavg labeled-networking options compiled in.
May 17 16:27:30 sha01 xinetd[4675]: Started working: 1 available service

Seems nothing special.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 15:10 GMT+08:00 Chris Ridd <chrisr...@mac.com>:
>
>> On 17 May 2016, at 07:40, Fred Liu <fred.f...@gmail.com> wrote:
>>
>> 2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
>>> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>>>> I have no success to boot the system V init scripts.
>>>> Any success here?
>>>
>>> Can you give us a bit more detail about what you're doing?  Is this a
>>> custom script you have added to your machine?  Is it in the global
>>> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
>>> what path did you install the file?
>>>
>>>
>>> Cheers.
>>>
>>
>> We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
>> I installed it on /etc/init.d/iqs. It is just a simple sh script:
>
> Add “set -x” near the start of the script and find out where it is failing.
>

It can be started manually  with no problems.
The issue it can't be automatically started when we reboot LX Brand.
Because the boot process is totally different in LX Brand.
So the question converts to how to debug the boot process in LX Brand.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

2016-05-17 14:32 GMT+08:00 Joshua M. Clulow <j...@sysmgr.org>:
> On 16 May 2016 at 23:29, Fred Liu <fred.f...@gmail.com> wrote:
>> I have no success to boot the system V init scripts.
>> Any success here?
>
> Can you give us a bit more detail about what you're doing?  Is this a
> custom script you have added to your machine?  Is it in the global
> zone of your SmartOS host, or in a SmartOS or LX-branded zone?  At
> what path did you install the file?
>
>
> Cheers.
>

We are running (CentOS 6.7 20151005) LX Brand. It is a custom script.
I installed it on /etc/init.d/iqs. It is just a simple sh script:

#!/bin/sh

# start and stop iqs exec daemon   #


# Basic support for RedHat style chkconfig
#
# chkconfig: - 99 01
# description: Starts and stops the iqs exec daemon.
#
### BEGIN INIT INFO
# Provides:  iqs
# Required-Start: $remote_fs $all
# Should-Start:
# Required-Stop:
# Default-Start:  2 3 5
# Default-Stop:   0 6
# Description:Starts and stops iqs exec daemon.
### END INIT INFO

start()
{
  echo "Trying to start iqs exec daemon:"
  su  admin -c "/tool/iqs/bin/execd.py start"
}

stop()
{
  echo "Trying to stop iqs exec daemon:"
  su admin -c "/tool/iqs/bin/execd.py stop"
}case "$1" in
'start')
  start
  if [ -d /var/lock/subsys ]; then
touch /var/lock/subsys/iqs
  elif [ -d /var/lock ]; then
touch /var/lock/iqs
  fi
  ;;

'stop')
stop
if [ -d /var/lock/subsys ]; then
  rm -f /var/lock/subsys/iqs
elif [ -d /var/lock ]; then
  rm -f /var/lock/iqs
fi
  ;;

'restart')
restart
  ;;
*)
  echo "Usage: $0 {start|stop|restart}"
  exit 1
  ;;
esac

BTW, it works in normal Linux OS.

Thanks.

Fred



Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Do system V init scripts work in LX Brand?

[Fred Liu]

Hi,

I have no success to boot the system V init scripts.
Any success here?

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Re: Any possibilities in python OSError?

[Fred Liu]

2016-05-16 21:44 GMT+08:00 Richard Elling <richard.ell...@richardelling.com>:
>
>> On May 16, 2016, at 3:40 AM, Fred Liu <fred.f...@gmail.com> wrote:
>>
>> It could be the slow read from the nfs path -- "/tool/iqs/run".
>> We see nfs v4 client not working in LX brand(I have already opened OS-5265).
>> And nfs v3 client is working but it has obvious lag( about 5-10
>> seconds) at the very first try to mount nfs path.
>> As long as the mount is done, there is no obvious lag in coming
>> nfs-related operations.
>> And further, we find if SmartOS where LX brands are living in serve
>> nfs service, the lag won't appear.
>> It could be something happened in network path.
>
> this is consistent with name lookup timeout. double check dns, ldap, and all 
> other name sources.
>

I check  /etc/nsswitch.conf and I get following:
hosts:  files nis dns

The nfs server has already been put in /etc/hosts file.

The lag on the very first try to mount is still there.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Any possibilities in python OSError?

[Fred Liu]

Hi,

We are running some python scripts in LX brand (CentOS 6.7 20151005).
And we get following errors:

File "/tool/iqs/bin/execd.py", line 416, in polljob
runfiles = [int(f) for f in os.listdir(RUNDIR) if f.isdigit()]
exceptions.OSError: [Errno 4] Interrupted system call: '/tool/iqs/run'



They have been running well under normal Linux OS.

Any possibilities?


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] RE: [developer] HBA recommended except LSI and ARECA

[Fred Liu]

> -Original Message-
> From: Fred Liu
> Sent: 星期二, 五月 06, 2014 12:22
> To: Zhiwen Zheng; Keith Wesolowski
> Cc: omnios-disc...@lists.omniti.com; Discussion list for OpenIndiana; Fred 
> Liu;
> develo...@lists.illumos.org; smartos-discuss@lists.smartos.org
> Subject: RE: [developer] HBA recommended except LSI and ARECA
> 
> 
> >From: Zhiwen Zheng [mailto:zhiwen...@gmail.com]
> >Sent: 星期二, 五月 06, 2014 10:09
> >To: Keith Wesolowski
> >Cc: omnios-disc...@lists.omniti.com; Fred Liu; Discussion list for
> OpenIndiana; Fred Liu; develo...@lists.illumos.org;
> smartos-discuss@lists.smartos.org
> >Subject: Re: [developer] HBA recommended except LSI and ARECA
> 
> >Hi,
> >I get an Adaptec card several days ago, the pci id changed, after add the new
> pci id, pmcs still can not attach.
> >I checked the linux pm8001 driver,
> >it seems to access some registers, pci bar 4 address need to be shifted.
> >I am out of door now,  I think I can try to fix this several days later.
> 
> "prtconf -D" has no info about pm8001. "prtconf -vvv" will get only following
> info:
> 
> name='vendor-id' type=int items=1
> value=9005
> name='device-id' type=int items=1
> value=8081
> name='vendor-name' type=string items=1
> value='Adaptec'
> name='device-name' type=string items=1
> value='PMC-Sierra PM8001 SAS HBA [Series 6H]'
> name='subsystem-name' type=string items=1
> value='unknown subsystem'
> 
> And yes, pmcs doen't attach.

Any progress so far?

Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] RE: kernel zone

[Fred Liu]

From: Fred Liu 
Sent: 星期三, 三月 16, 2016 20:06
To: smartos-discuss@lists.smartos.org
Cc: illumos-developer
Subject: kernel zone

Hi,

Not sure if illumos is designed strictly by backward compatibility. That means 
applications built on older illumos  can still run
on newer illumos. 
For there has been short history of smartos, the older OS images can still run 
well in the current SmartOS release.
But in long-term, will  users be asked to upgrade their images?


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] kernel zone

[Fred Liu]

Hi,

Not sure if illumos is design strictly by backward compatibility. That means 
applications built on older illumos  can still run
on newer illumos.
For there has been short history of smartos, the older OS images can still run 
well in the current SmartOS release.
But in long-term, will the users be asked to upgrade their images?


Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Imaging LX brand zones

[Fred Liu]

I usually build form source if I want to try a custom image.  The instructions 
are pretty clear.



[Fred]:  The output dir is like following after a successful building:
bash-4.1$ pwd
/home/fliu/smartos-live/output
-bash-4.1$ ls -la
total 158393
drwxr-xr-x  3 fliu fliu 8 Feb 24 19:45 .
drwxr-xr-x 18 fliu fliu26 Feb 26 12:51 ..
-rw-r--r--  1 root root369348 Feb 24 19:43 boot-20160224T102420Z.tgz
-rw-r--r--  1 root root17 Feb 24 19:45 buildstamp
drwxr-xr-x  3 root root 4 Feb 24 19:36 platform-20160224T102420Z
-rw-r--r--  1 root root 161568675 Feb 24 19:45 platform-20160224T102420Z.tgz
lrwxrwxrwx  1 root root25 Feb 24 19:45 platform-latest -> 
platform-20160224T102420Z
lrwxrwxrwx  1 root root29 Feb 24 19:45 platform-latest.tgz -> 
platform-20160224T102420Z.tgz


And definitely, the “boot_archive” can’t be directly used as OS image from 
scratch. I guess we need some scripts and
manifest file to deliver image.

Can you please elaborate your process?

Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] How to mount different zfs volumn to the same lx branded zone

[Fred Liu]

From: Fred Liu [mailto:fred_...@issi.com]
Sent: 星期六, 三月 12, 2016 17:50
To: smartos-discuss@lists.smartos.org; smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] How to mount different zfs volumn to the same lx 
branded zone

It seems hardware pass-through is not applicable in SmartOS from what I know. 
But
there are some indirect methods(NFS/iSCSI) you can try for there is almost no 
network
overhead in LX.


[Fred]: I need to correct my aforementioned typing. Sorry for that! Zones do 
support to import raw and block
devices(including zvol) by using zonecfg. I did test adding  
the smartos usb stick to an OS vm. It works.
   I can make file system(ufs) on it and write some data on it. But 
the bizarre bits are  all the data written in OS
   Vm will vanish if this device is re-imported by global zone 
again. But anyway, passing raw disk to OS vm does occur
  in  heritage from Solaris.



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [zfs] [developer] Re: [smartos-discuss] an interesting survey -- the zpool with most disks you have ever built

[Fred Liu]

2016-03-08 4:55 GMT+08:00 Liam Slusser :

> I don't have a 2000 drive array (thats amazing!) but I do have two 280
> drive arrays which are in production.  Here are the generic stats:
>
> server setup:
> OpenIndiana oi_151
> 1 server rack
> Dell r720xd 64g ram with mirrored 250g boot disks
> 5 x LSI 9207-8e dualport SAS pci-e host bus adapters
> Intel 10g fibre ethernet (dual port)
> 2 x SSD for log cache
> 2 x SSD for cache
> 23 x Dell MD1200 with 3T,4T, or 6T NLSAS disks (a mix of Toshiba, Western
> Digital, and Seagate drives - basically whatever Dell sends)
>
> zpool setup:
> 23 x 12-disk raidz2 glued together.  276 total disks.  Basically each new
> 12 disk MD1200 is a new raidz2 added to the pool.
>
> Total size: ~797T
>
> We have an identical server which we replicate changes via zfs snapshots
> every few minutes.  The whole setup as been up and running for a few years
> now, no issues.  As we run low on space we purchase two additional MD1200
> shelfs (one for each system) and add the new raidz2 into pool on-the-fly.
>
> The only real issues we've had is sometimes a disk fails in such a way
> (think Monty Python and the holy grail i'm not dead yet) where the disk
> hasn't failed but is timing out and slows the whole array to a standstill
> until we can manual find and remove the disk.  Other problems are once a
> disk has been replaced sometimes the resilver process can take
> an eternity.  We have also found the snapshot replication process can
> interfere with the resilver process - resilver gets stuck at 99% and never
> ends - so we end up stopping or only doing one replication a day until the
> resilver process is done.
>
> The last helpful hint I have was lowering all the drive timeouts, see
> http://everycity.co.uk/alasdair/2011/05/adjusting-drive-timeouts-with-mdb-on-solaris-or-openindiana/
> for info.
>
> [Fred]: zpool wiith 280 drives in production is pretty big! I think 2000
> drives were just in test. It is true that huge pools have lots of operation
> challenges. I have met the similar sluggish issue caused by a
>
   will-die disk.  Just curious, what is the cluster software
implemented in
http://everycity.co.uk/alasdair/2011/05/adjusting-drive-timeouts-with-mdb-on-solaris-or-openindiana/
 ?

Thanks.

Fred

>
>
>
>>>
>>>
>>
> *illumos-zfs* | Archives
> 
>  |
> Modify
> 
> Your Subscription 
>



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Samsung 950 Pro on SmartOS?

[Fred Liu]

2016-03-05 21:19 GMT+08:00 Dirk Steinberg :

> > Apart from that: is NVMe support in SmartOS considered stable?
>
>
> There is driver support for it in the system. I have not heard many
> reports positively or negatively about it.
>
> [Fred]: I am testing some Intel P3600 NVMe SSD. In normal workload, they
> just work . But in burning mode like continuous scrubbings, I have got lots
> of checksum errors. And I tested the same scrubbings under Linux, no
> checksum errors were found.
> Fred
>
>
> Hi Fred,
>
> do you attribute these errors to the SmartOS NVMe driver?
> Sounds like it since you are saying that the same SSD works under Linux.
>
> So have you given up on NVMe on SmartOS?
>
> [Fred]: I personally attribute those errors to the immaturity of the NVMe
driver in Illumos. But that  is not so severe based on the fact that there
are no substantial data loss with those checksum errors.
I used to get some some kernel panics under "too may check sum erros" and
after disabling "sha512|skeun|edonr" checksum algorithm, the server has
been running well for more than two weeks.
It looks like "sha512|skeun|edonr" checksum algorithm still has some
glitches.

Thanks.

Fred

>
>
> *smartos-discuss* | Archives
> 
>  |
> Modify
> 
> Your Subscription 
>



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Re: [zfs] an interesting survey -- the zpool with most disks you have ever built

[Fred Liu]

2016-03-05 0:01 GMT+08:00 Freddie Cash <fjwc...@gmail.com>:

> On Mar 4, 2016 2:05 AM, "Fred Liu" <fred.f...@gmail.com> wrote:
> > 2016-03-04 13:47 GMT+08:00 Freddie Cash <fjwc...@gmail.com>:
> >>
> >> Currently, I just use a simple coordinate system. Columns are letters,
> rows are numbers.
> >> "smartos-discuss@lists.smartos.org" <smartos-discuss@lists.smartos.org
> >、
>
> developer <develo...@open-zfs.org>、
>
> illumos-developer <develo...@lists.illumos.org>、
>
> omnios-discuss <omnios-disc...@lists.omniti.com>、
>
> Discussion list for OpenIndiana <openindiana-disc...@openindiana.org>、
>
> illumos-zfs <z...@lists.illumos.org>、
>
> "zfs-disc...@list.zfsonlinux.org" <zfs-disc...@list.zfsonlinux.org>、
>
> "freebsd...@freebsd.org" <freebsd...@freebsd.org>、
>
> "zfs-de...@freebsd.org" <zfs-de...@freebsd.org>
>
> >> Each disk is partitioned using GPT with the first (only) partition
> starting at 1 MB and covering the whole disk, and labelled with the
> column/row where it is located (disk-a1, disk-g6, disk-p3, etc).
> >
> > [Fred]: So you manually pull off all the drives one by one to locate
> them?
>
> ​When putting the system together for the first time, I insert each disk
> one at a time, wait for it to be detected, partition it, then label it
> based on physical location.​  Then do the next one.  It's just part of the
> normal server build process, whether it has 2 drives, 20 drives, or 200
> drives.
>
> ​We build all our own servers from off-the-shelf parts; we don't buy
> anything pre-built from any of the large OEMs.​
>

[Fred]: Gotcha!


> >> The pool is created using the GPT labels, so the label shows in "zpool
> list" output.
> >
> > [Fred]:  What will the output look like?
>
> ​From our smaller backups server, with just 24 drive bays:
>
> $ zpool status storage
>
>   pool: storage
>
>  state: ONLINE
>
> status: Some supported features are not enabled on the pool. The pool can
>
> still be used, but some features are unavailable.
>
> action: Enable all features using 'zpool upgrade'. Once this is done,
>
> the pool may no longer be accessible by software that does not support
>
> the features. See zpool-features(7) for details.
>
>   scan: scrub canceled on Wed Feb 17 12:02:20 2016
>
> config:
>
>
> NAME STATE READ WRITE CKSUM
>
> storage  ONLINE   0 0 0
>
>  raidz2-0   ONLINE   0 0 0
>
>gpt/disk-a1  ONLINE   0 0 0
>
>gpt/disk-a2  ONLINE   0 0 0
>
>gpt/disk-a3  ONLINE   0 0 0
>
>gpt/disk-a4  ONLINE   0 0 0
>
>gpt/disk-a5  ONLINE   0 0 0
>
>gpt/disk-a6  ONLINE   0 0 0
>
>  raidz2-1   ONLINE   0 0 0
>
>gpt/disk-b1  ONLINE   0 0 0
>
>gpt/disk-b2  ONLINE   0 0 0
>
>gpt/disk-b3  ONLINE   0 0 0
>
>gpt/disk-b4  ONLINE   0 0 0
>
>gpt/disk-b5  ONLINE   0 0 0
>
>gpt/disk-b6  ONLINE   0 0 0
>
>  raidz2-2   ONLINE   0 0 0
>
>gpt/disk-c1  ONLINE   0 0 0
>
>gpt/disk-c2  ONLINE   0 0 0
>
>gpt/disk-c3  ONLINE   0 0 0
>
>gpt/disk-c4  ONLINE   0 0 0
>
>gpt/disk-c5  ONLINE   0 0 0
>
>gpt/disk-c6  ONLINE   0 0 0
>
>  raidz2-3   ONLINE   0 0 0
>
>gpt/disk-d1  ONLINE   0 0 0
>
>gpt/disk-d2  ONLINE   0 0 0
>
>gpt/disk-d3  ONLINE   0 0 0
>
>gpt/disk-d4  ONLINE   0 0 0
>
>gpt/disk-d5  ONLINE   0 0 0
>
>gpt/disk-d6  ONLINE   0 0 0
>
> cache
>
>  gpt/cache0 ONLINE   0 0 0
>
>  gpt/cache1 ONLINE   0 0 0
>
>
> errors: No known data errors
>
> The 90-bay systems look the same, just that the letters go all the way to
> p (so disk-p1 through disk-p6).  And there's one vdev that uses 3 drives
> from each chassis (7x 6-disk vdev only uses 42 drives of the 45-bay
> chassis, so there's lots of spares if using a single chassis; using two
> chassis, there's enough drives to add an extra 6-disk vdev).
>

[Fred]: It looks like the gpt label shown in "zpool status" only works in
FreeBSD/FreeNAS. Are you using FreeBSD/FreeNAS? I can't find the similar
possibilities in Illumos/Linux.

Thanks,

Fred

>
> *illumos-zfs* | Archives
> <https://www.listbox.com/member/archive/182191/=now>
> <https://www.listbox.com/member/archive/rss/182191/22147814-d504851f> |
> Modify
> <https://www.listbox.com/member/?;>
> Your Subscription <http://www.listbox.com>
>



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] an interesting survey -- the zpool with most disks you have ever built

[Fred Liu]

Hi,

Today when I was reading Jeff's new nuclear weapon -- DSSD D5's CUBIC RAID 
introduction,
the interesting survey -- the zpool with most disks you have ever built popped 
in my brain.

For zfs doesn't support nested vdev, the maximum fault tolerance should be 
three(from raidz3). It is stranded if you want to build a very huge pool.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] passing SSH keys to the LX brand zone

[Fred Liu]

Hi,

It looks like adding following “customer_metadat” section in json manifest 
won’t work.

"customer_metadata": {
"root_authorized_keys": "ssh-rsa 
B3NzaC1yc2EBIwAAAQEA8aQRt2JAgq6jpQOT5nukO8gI0Vst+EmBtwBz6gnRjQ4Jw8pERLlMAsa7jxmr5yzRA7Ji8M/kxGLbMHJnINdw/TBP1mCBJ49TjDpobzztGO9icro3337oyvXo5unyPTXIv5pal4hfvl6oZrMW9ghjG3MbIFphAUztzqx8BdwCG31BHUWNBdefRgP7TykD+KyhKrBEa427kAi8VpHU0+M9VBd212mhh8Dcqurq1kC/jLtf6VZDO8tu+XalWAIJcMxN3F3002nFmMLj5qi9EwgRzicndJ3U4PtZrD43GocxlT9M5XKcIXO/rYG4zfrnzXbLKEfabctxPMezGK7iwaOY7w==
 wooyay@houpla",
"user-script" : "/usr/sbin/mdata-get root_authorized_keys > 
~root/.ssh/authorized_keys ; /usr/sbin/mdata-get root_authorized_keys > 
~admin/.ssh/authorized_keys"
}

Even after zlogining  lx brand zone and manually updating 
“root_authorized_keys” and “user-script” via mdata-put command and rebooting 
the lx brand zone,
it still doesn’t work. And the only way is manually create 
“~root/.ssh/authorized_keys”.


Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] enable network/physical in noinstall/recovery?

[Fred Liu]

From: Nahum Shalman [mailto:nshalman-smar...@elys.com] 
Sent: 星期五, 二月 19, 2016 21:55
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] enable network/physical in noinstall/recovery?

If you know the mac address of the NIC you want to bring online, you can edit 
the kernel command line within grub and append the following stuff:

,admin_mac=11:22:33:44:55:66,admin_ip=dhcp
or
,admin_mac=11:22:33:44:55:66,admin_ip=192.168.x.y,admin_netmask=255.255.255.0,admin_gateway=192.168.x.1

[Fred]: I tried. It seems it did not work.

If you can't edit the kernel command line, the alternative to getting the 
system to finish coming up is to manually create the /usbkey directory, and 
create a minimal /usbkey/config file with the networking configuration you 
want. After that "sysinfo -f" then "svcadm clear network/physical" and the 
system should finish bringing services online.

You'll probably need to fix up /etc/resolv.conf if you want to make outbound 
connections.

[Fred]: It works well!

Be aware that you're bringing the machine online with a known root password 
that will work over SSH. You can replace the hash in the kernel command line 
with something else if you want to be extra cautious.

I hope that helps.

[Fred]: Are there comprehensive documents about all the parameters fed to 
kernel? Could the alternative way be
Adding ",smartos=false,noimport=true" to the normal boot kernel?

To answer your original question about why there isn't a rescue mode that 
includes networking, I think the main reasons are:
1. SmartOS is often used on machines with multiple NICs. There's no way to know 
which to use without more information from the operator.
2. SmartOS is often used on networks with no DHCP server. Without being told 
what IP address to use there would be no way for SmartOS to configure working 
networking.
3. The system would then come online with a known root password and SSH running 
and that could be dangerous.
4. In light of those other reasons, no one has written code for it.

[Fred]: Hm, what is your way to restore a bad zpool like zones?

Thanks.

Fred


On 02/19/2016 08:03 AM, Fred Liu wrote:
Yeah. That is doable. But because there is no zpool imported, network/physical 
can’t be started. And a lot of protocols can’t run neither.
 
Thanks.
 
Fred
From: Jorge Schrauwen [mailto:sjorge...@blackdot.be] 
Sent: 星 期五, 二月 19, 2016 19:21
To: smartos-discuss@lists.smartos.org
Cc: Fred Liu
Subject: Re: [smartos-discuss] enable network/physical in noinstall/recovery?
 
You can use ifconfig to bring it up manually.
ifconfig e1000g0 inet auto-dhcp (from memory so it may be incorrect)
 
 
On 2016-02-19 11:30, Fred Liu wrote:
Hi,
 
“noinstall/recovery” is really helpful to fix/save zpools. But it is offline. 
Is it hard to enable networking in it? Just like “fail-safe-mode-with-network”.
Nobody wants to recover from remote backup but that is the ideal life.
 
 
Thanks.
 
Fred

smartos-discuss | Archives | Modify Your Subscription




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] the partition size is fixed 1.86G in USB stick. Can it be enlarged?

[Fred Liu]

zfs is much faster than pcfs. That is a big gain!
Thanks for your cool hacking.

Thanks.

Fred

From: Nahum Shalman [mailto:nshalman-smar...@elys.com]
Sent: 星期五, 二月 19, 2016 21:43
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?

After resizing you'd probably need to re-install grub...
An alternative is to format the USB stick with a ZFS pool and boot that way (as 
a bonus you can then take snapshots and I've heard that it boots a little 
faster than pcfs...):
http://blog.shalman.org/smartos-zfs-boot-media/

If you want to stick with pcfs, you could follow similar steps to format your 
USB stick at its full capacity and then install grub on it.

The reason that the image is fixed at such a small size is so that people can 
use it on pretty much any USB stick they have lying around (If we made the 
image 8GB and a person had lots of 4GB sticks lying around etc.)

-Nahum


On 02/18/2016 08:10 PM, Fred Liu wrote:
I have got no success with gparted.


Thanks.
Fred
Sent from Outlook Mobile<https://aka.ms/sdimjr>

_
From: Jorge Schrauwen <sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>>
Sent: 星期二, 二月 16, 2016 8:08 下午
Subject: RE: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?
To: 
<smartos-discuss@lists.smartos.org<mailto:smartos-discuss@lists.smartos.org>>
Cc: Fred Liu <fred_...@issi.com<mailto:fred_...@issi.com>>




You can also just resize the fat partition after writing to the UBS stick.


Jorge

On 2016-02-16 12:58, Fred Liu wrote:
It should be doable if we can hack in “gmake usb”.

From: Micky [mailto:mickylmar...@gmail.com]
Sent: 星期二, 二月 16, 2016 19:06
To: smartos-discuss@lists.smartos.org<mailto:smartos-discuss@lists.smartos.org>
Subject: Re: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?

Likely no, cause it's a disk image.

On Tue, Feb 16, 2016 at 1:20 PM, Fred Liu 
<fred_...@issi.com<mailto:fred_...@issi.com>> wrote:




You can also just resize the fat partition after writing to the UBS stick.


Jorge

On 2016-02-16 12:58, Fred Liu wrote:
It should be doable if we can hack in “gmake usb”.

From: Micky [mailto:mickylmar...@gmail.com]
Sent: 星期二, 二月 16, 2016 19:06
To: smartos-discuss@lists.smartos.org<mailto:smartos-discuss@lists.smartos.org>
Subject: Re: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?

Likely no, cause it's a disk image.

On Tue, Feb 16, 2016 at 1:20 PM, Fred Liu 
<fred_...@issi.com<mailto:fred_...@issi.com>> wrote:



smartos-discuss | Archives<https://www.listbox.com/member/archive/184463/=now> 
[https://www.listbox.com/images/feed-icon-10x10.jpg96494be.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
 <https://www.listbox.com/member/archive/rss/184463/21991222-c237e945> | 
Modify<https://www.listbox.com/member/?;> Your Subscription

[https://www.listbox.com/images/listbox-logo-small.png96494be.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]<http://www.listbox.com>





---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] enable network/physical in noinstall/recovery?

[Fred Liu]

Yeah. That is doable. But because there is no zpool imported, network/physical 
can’t be started. And a lot of protocols can’t run neither.

Thanks.

Fred
From: Jorge Schrauwen [mailto:sjorge...@blackdot.be]
Sent: 星期五, 二月 19, 2016 19:21
To: smartos-discuss@lists.smartos.org
Cc: Fred Liu
Subject: Re: [smartos-discuss] enable network/physical in noinstall/recovery?


You can use ifconfig to bring it up manually.

ifconfig e1000g0 inet auto-dhcp (from memory so it may be incorrect)




On 2016-02-19 11:30, Fred Liu wrote:
Hi,

“noinstall/recovery” is really helpful to fix/save zpools. But it is offline. 
Is it hard to enable networking in it? Just like “fail-safe-mode-with-network”.
Nobody wants to recover from remote backup but that is the ideal life.


Thanks.

Fred
smartos-discuss | Archives<https://www.listbox.com/member/archive/184463/=now> 
[program/resources/blocked.gif] 
<https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7> | 
Modify<https://www.listbox.com/member/?;> Your Subscription

[program/resources/blocked.gif]<http://www.listbox.com>





---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] enable network/physical in noinstall/recovery?

[Fred Liu]

Hi,

“noinstall/recovery” is really helpful to fix/save zpools. But it is offline. 
Is it hard to enable networking in it? Just like “fail-safe-mode-with-network”.
Nobody wants to recover from remote backup but that is the ideal life.


Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] the partition size is fixed 1.86G in USB stick. Can it be enlarged?

[Fred Liu]

I have got no success with gparted.


Thanks.
Fred

Sent from Outlook Mobile<https://aka.ms/sdimjr>

_
From: Jorge Schrauwen <sjorge...@blackdot.be<mailto:sjorge...@blackdot.be>>
Sent: 星期二, 二月 16, 2016 8:08 下午
Subject: RE: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?
To: 
<smartos-discuss@lists.smartos.org<mailto:smartos-discuss@lists.smartos.org>>
Cc: Fred Liu <fred_...@issi.com<mailto:fred_...@issi.com>>



You can also just resize the fat partition after writing to the UBS stick.



Jorge

On 2016-02-16 12:58, Fred Liu wrote:
It should be doable if we can hack in “gmake usb”.

From: Micky [mailto:mickylmar...@gmail.com]
Sent: 星期二, 二月 16, 2016 19:06
To: smartos-discuss@lists.smartos.org<mailto:smartos-discuss@lists.smartos.org>
Subject: Re: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?

Likely no, cause it's a disk image.

On Tue, Feb 16, 2016 at 1:20 PM, Fred Liu 
<fred_...@issi.com<mailto:fred_...@issi.com>> wrote:


smartos-discuss | Archives<https://www.listbox.com/member/archive/184463/=now> 
<https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7> | 
Modify<https://www.listbox.com/member/?;> Your Subscription 
<http://www.listbox.com>



You can also just resize the fat partition after writing to the UBS stick.



Jorge

On 2016-02-16 12:58, Fred Liu wrote:
It should be doable if we can hack in “gmake usb”.

From: Micky [mailto:mickylmar...@gmail.com]
Sent: 星期二, 二月 16, 2016 19:06
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?

Likely no, cause it's a disk image.

On Tue, Feb 16, 2016 at 1:20 PM, Fred Liu 
<fred_...@issi.com<mailto:fred_...@issi.com>> wrote:


smartos-discuss | Archives<https://www.listbox.com/member/archive/184463/=now> 
[program/resources/blocked.gif] 
<https://www.listbox.com/member/archive/rss/184463/26452851-88b650c7>  | 
Modify<https://www.listbox.com/member/?;> Your Subscription
[program/resources/blocked.gif] <http://www.listbox.com>



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] the partition size is fixed 1.86G in USB stick. Can it be enlarged?

[Fred Liu]

It should be doable if we can hack in “gmake usb”.

From: Micky [mailto:mickylmar...@gmail.com]
Sent: 星期二, 二月 16, 2016 19:06
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] the partition size is fixed 1.86G in USB stick. 
Can it be enlarged?

Likely no, cause it's a disk image.

On Tue, Feb 16, 2016 at 1:20 PM, Fred Liu 
<fred_...@issi.com<mailto:fred_...@issi.com>> wrote:


smartos-discuss | Archives<https://www.listbox.com/member/archive/184463/=now> 
[https://www.listbox.com/images/feed-icon-10x10.jpg96494be.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
 <https://www.listbox.com/member/archive/rss/184463/21991222-c237e945> | 
Modify<https://www.listbox.com/member/?;> Your Subscription

[https://www.listbox.com/images/listbox-logo-small.png96494be.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]<http://www.listbox.com>





---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] the partition size is fixed 1.86G in USB stick. Can it be enlarged?

[Fred Liu]

---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] RE: rpc.idmapd not working in lx brand

[Fred Liu]

[root@sha01 init.d]# /usr/sbin/rpc.idmapd -f -vvv
rpc.idmapd: libnfsidmap: using domain: issish.com
rpc.idmapd: libnfsidmap: Realms list: 'ISSISH.COM'
rpc.idmapd: libnfsidmap: processing 'Method' list
rpc.idmapd: libnfsidmap: loaded plugin /usr/lib64/libnfsidmap/nsswitch.so for 
method nsswitch

rpc.idmapd: Expiration time is 600 seconds.
rpc.idmapd: nfsdopenone: Opening /proc/net/rpc/nfs4.nametoid/channel failed: 
errno 20 (Not a directory)
rpc.idmapd: main: open(/var/lib/nfs/rpc_pipefs//nfs): No such file or directory

From: Fred Liu
Sent: 星期一, 一月 25, 2016 18:43
To: smartos-discuss@lists.smartos.org
Cc: illumos-developer
Subject: rpc.idmapd not working in lx brand

Hi,

I am playing following lx brand zone:

82cf0a0a-6afc-11e5-8f79-273b6aea6443  centos-620151005  linux
lx-dataset2015-10-05


And it looks like rpc.idmapd not working which cause NFSv4 mount not working.

Thanks.


Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] How can I update or comment on SmartOS wiki?

[Fred Liu]

> -Original Message-
> From: Travis Paul [mailto:t...@vispaul.me]
> Sent: 星期六, 二月 06, 2016 7:09
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] How can I update or comment on SmartOS
> wiki?
> 
> I can't say for sure as I don't have the privileges to add users. But
> you might try joining #smartos on freenode and post what you'd like to
> update/change.
> 
> At least, that's what worked for me :)
> 
Good idea! I am gonna try!

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] How can I update or comment on SmartOS wiki?

[Fred Liu]

Hi,

Just want to ask if it is possible to update or comment on SmartOS wiki.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] benchmarking between LX and KVM

[Fred Liu]

> 
> Are you performing active benchmarking and on the latest platform? This
> is a case where a quick use of the USE method may be rather insightful.
> If you just did a fire and forget, it's very easy to end up comparing
> different things.

Yes. I am running joyent_20160121T174331Z. It is just a quick-and-dirty test.
That is reason why I asked here to see if there are comprehensive tests.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] benchmarking between LX and KVM

[Fred Liu]

Hi,

Anyone who has ever tried performance benchmarking between LX and KVM.
In my dirty-and-quick test(compling gcc), LX is 20% slower than KVM. It is sort 
of disspointed!


Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [developer] [smartos-discuss] Is zfs dead man timer tunable?

[Fred Liu]

>From: Youzhong Yang [mailto:youzh...@gmail.com] 
>Sent: 星期三, 一月 27, 2016 11:41
>To: Fred Liu
>Cc: Richard Elling; smartos-discuss@lists.smartos.org; illumos-developer
>Subject: Re: [developer] [smartos-discuss] Is zfs dead man timer tunable?

>       -d
>                      Disregard dump header valid flag. Force savecore to
>                      attempt to save a crash dump even if the header
>                      information stored on the dump device indicates the dump
>                      has already been saved.

It works well this time. Thank you, Youzhong!

[root@pluto ~]# savecore -vd /zones/debug
savecore: System dump time: Mon Jan 25 19:24:52 2016

savecore: Saving compressed system crash dump in /zones/debug/vmdump.0
savecore: Copying /dev/zvol/dsk/zones/dump to /zones/debug/vmdump.0

savecore: Decompress the crash dump with 
'savecore -vf /zones/debug/vmdump.0'
0:05 dump copy is done
[root@pluto ~]# cd /zones/debug
[root@pluto /zones/debug]# ls
bounds   METRICS.csv  vmdump.0
[root@pluto /zones/debug]# ls -la
total 4818248
drwxr-xr-x   2 root root   5 Jan 27 13:17 .
drwxr-xr-x  16 root root  19 Jan 25 19:21 ..
-rw-r--r--   1 root root   2 Jan 27 13:17 bounds
-rw-r--r--   1 root root1058 Jan 27 13:17 METRICS.csv
-rw-r--r--   1 root root 4305518592 Jan 27 13:17 vmdump.0
[root@pluto /zones/debug]# du -sh *
   9K   bounds
   9K   METRICS.csv
 2.3G   vmdump.0
 [root@pluto /zones/debug]# savecore -d -vf vmdump.0 .
savecore: System dump time: Mon Jan 25 19:24:52 2016

savecore: saving system crash dump in ./{unix,vmcore}.0
Constructing namelist ./unix.0
Constructing corefile ./vmcore.0
 1:11 100% done: 6186530 of 6186530 pages saved
86613 (1%) zero pages were not written
1:11 dump decompress is done
[root@pluto /zones/debug]# ls -la
total 15270811
drwxr-xr-x   2 root root   7 Jan 27 13:20 .
drwxr-xr-x  16 root root  19 Jan 25 19:21 ..
-rw-r--r--   1 root root   2 Jan 27 13:17 bounds
-rw-r--r--   1 root root1233 Jan 27 13:21 METRICS.csv
-rw-r--r--   1 root root 2086628 Jan 27 13:20 unix.0
-rw-r--r--   1 root root 25727160320 Jan 27 13:21 vmcore.0
-rw-r--r--   1 root root 4305518592 Jan 27 13:17 vmdump.0
[root@pluto /zones/debug]# du -sh *
   9K   bounds
   9K   METRICS.csv
 1.1M   unix.0
 5.0G   vmcore.0
 2.3G   vmdump.0
 [root@pluto /zones/debug]# mdb -k unix.0 vmcore.0
mdb: failed to read panicbuf and panic_reg -- current register set will be 
unavailable
Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc apix 
scsi_vhci ufs ip hook neti sockfs arp usba stmf_sbd stmf zfs mm sd lofs idm 
sata crypto random cpc logindmux ptm kvm sppp nsmb smbsrv nfs ipc ]
> ::zio_state
 ADDRESS TYPE  STAGEWAITER   TIME_ELAPSED
 f0857784d8e8NULL  OPEN --
 f0857791f1a8NULL  OPEN --
 
 Thanks.
 
 Fred
 
 Thanks.
 
 Fred
 


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [developer] [smartos-discuss] Is zfs dead man timer tunable?

[Fred Liu]

>savecore serves two functions:
>1. copy the dump from the dump device to a filesystem: vmdump.# (done at boot 
>by
>   the dumpadm SMF service)
>2. extract the vmcore.# and unix.# from a vmdump.#

>Unless you've dumped again, the old dump should still be on the dump device.

root@pluto ~]# savecore -v /zones/debug
savecore: dump already processed
[root@pluto ~]# ls /zones/debug
[root@pluto ~]#

Looks I can't get vmdump.#

Thanks.

Fred
 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Is zfs dead man timer tunable?

[Fred Liu]

From: Richard Elling [mailto:richard.ell...@richardelling.com] 
Sent: 星期六, 一月 23, 2016 2:55
To: smartos-discuss@lists.smartos.org
Cc: illumos-developer
Subject: Re: [smartos-discuss] Is zfs dead man timer tunable?


On Jan 21, 2016, at 10:18 PM, Fred Liu <fred_...@issi.com> wrote:

Comment below.

From: Richard Elling [mailto:richard.ell...@richardelling.com]
Sent: 星期五, 一月 22, 2016 13:51
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] Is zfs dead man timer tunable?

answer far below...

On Jan 21, 2016, at 8:44 PM, Fred Liu <fred_...@issi.com> wrote:




-Original Message-
From: Richard Elling [mailto:richard.ell...@richardelling.com]
Sent: 星期五, 一月 22, 2016 12:02
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] Is zfs deadm man timer tunable?



On Jan 21, 2016, at 4:25 AM, Fred Liu <fred_...@issi.com> wrote:

zfs deadman timer is tunable. But if you hit it, you've got problems
that tuning the deadman won't help.

The tunable is zfs_deadman_synctime_ms, which is milliseconds.

For example, on a test machine here:
   [root@elvis ~]# echo zfs_deadman_synctime_ms/D | mdb -k
   zfs_deadman_synctime_ms:
   zfs_deadman_synctime_ms:    100

FYI, you can check on the state of I/Os in the ZIO pipeline and how
long they've been there using the zio_state dcmd. Elvis is not
currently busy or broken, but here is an example:
   [root@elvis ~]# echo ::zio_state | mdb -k
   ADDRESS TYPE  STAGE    WAITER
TIME_ELAPSED
   ff01ada853e0    NULL  OPEN -    -
   ff01ada85b10    NULL  OPEN -    -

If you see a large TIME_ELAPSED, you can track down the zio in question
for more debugging.
-- richard

Richard,

Many thanks! You have been always helpful since I first touched ZFS many years 
ago.
I am trying intel P3600 NVMe ssd on ZFS. I got several random server reboot 
every day. And I just captured "
panic message: I/O to pool 'zones' appears to be hung" from console. I doubt it 
is related to NVMe driver or
ssd firmware.

This is disturbing, to me. sd should sit between ZFS and the NVMe driver. sd 
manages 
timeouts, retries, and resets. But it is still somewhat at the mercy of the 
NVMe driver
(or mptsas).

more below...

[Fred]: Now I switch to joyent_20160121T174331Z(latest for now). In my burning 
test(scrubbing + compiling SmartOS), I can see the checksum errors like 
following:
"f086b921f3b0NULL  CHECKSUM_VERIFY  f003d1fc5c40 - "
If I don't issue "zfs clean", all the vdevs will get checksum erros thru "zpool 
status". And then the whole pool
will hang for 1000s before reboot. That means zfs deadman really works as the 
goal of design! In the version
before joyent_20160121T174331Z, there is no 1000s hanging and just a immediate 
reboot. I checked the changlog,
it should be some bug fixes in zfs.


- SmartOS Live Image v0.147+ build: 20151001T070028Z
[root@pluto ~]# echo zfs_deadman_synctime_ms/D | mdb -k
zfs_deadman_synctime_ms:
zfs_deadman_synctime_ms:    100
[root@pluto ~]# echo ::zio_state | mdb -k
ADDRESS TYPE  STAGE    WAITER   TIME_ELAPSED
f08576c15028    NULL  OPEN -    -
f08576c153a8    NULL  OPEN -    -
f08576c15728    NULL  OPEN -    -
f08576c15aa8    NULL  OPEN -    -
f08576c15e28    NULL  OPEN -    -
f08576c161a8    NULL  OPEN -    -
f08576c16528    NULL  OPEN -    -
f08576c168a8    NULL  OPEN -    -
f08576c16c28    NULL  OPEN -    -
...
...

Is it possible to trigger a core dump? Coz, I can't get anything from 
/var/adm/message.

If you hit the zfs deadman timer, you should get a core dump. The ::zio_state 
is very helpful
for debugging kernel dumps, too :-)

[Fred]: the dump device is zones/dump which is a zvol. How to get the core-dump 
file?

You should be able to pull it out using "savecore -v /some/directory/with/space"
Then you can run mdb on the resulting dump files. From there you should be able
to see which zios are stuck and dive down towards the cause.

[Fred]: [root@pluto ~]# savecore -v /zones/debug
savecore: System dump time: Mon Jan 25 19:24:52 2016

savecore: Saving compressed system crash dump in /zones/debug/vmdump.0
savecore: Copying /dev/zvol/dsk/zones/dump to /zones/debug/vmdump.0

savecore: Decompress the crash dump with 
'savecore -vf /zones/debug/vmdump.0'
1:08 dump copy is done

[root@pluto /zones/debug]# ls -la
total 4818285
drwxr-xr-x   2 root root   5 Jan 26 14:16 .
drwxr-xr-x  16 root root  19 Jan 25 19:21 ..
-rw-r--r--   1 root root   2 Jan 26 14:15 bounds
-rw-r--r--  

RE: [developer] RE: [smartos-discuss] Is zfs dead man timer tunable?

[Fred Liu]

> -Original Message-
> From: Robert Mustacchi [mailto:r...@joyent.com]
> Sent: 星期二, 一月 26, 2016 15:21
> To: smartos-discuss@lists.smartos.org
> Cc: illumos-developer
> Subject: Re: [developer] RE: [smartos-discuss] Is zfs dead man timer
> tunable?
> 
> On 1/25/16 23:18 , Fred Liu wrote:
> >
> >
> >> -Original Message-
> >> From: Robert Mustacchi [mailto:r...@joyent.com]
> >> Sent: 星期二, 一月 26, 2016 14:57
> >> To: smartos-discuss@lists.smartos.org
> >> Cc: illumos-developer
> >> Subject: Re: [smartos-discuss] Is zfs dead man timer tunable?
> >>
> >> On 1/25/16 22:50 , Fred Liu wrote:
> >>> [root@pluto /zones/debug]# ls -la
> >>> total 4818285
> >>> drwxr-xr-x   2 root root   5 Jan 26 14:16 .
> >>> drwxr-xr-x  16 root root  19 Jan 25 19:21 ..
> >>> -rw-r--r--   1 root root   2 Jan 26 14:15 bounds
> >>> -rw-r--r--   1 root root1056 Jan 26 14:15 METRICS.csv
> >>> -rw-r--r--   1 root root 4305518592 Jan 26 14:15 vmdump.0
> >>> [root@pluto /zones/debug]# mdb -f vmdump.0
> >>>> echo ::zio_state
> >>>  mdb:  failed to dereference symbol: operation not supported by
> >> target
> >>>   > ::status
> >>>  debugging file 'vmdump.0' (object file)
> >>>
> >>>  [root@pluto /zones/debug]# echo "::zio_state" | mdb -f vmdump.0
> >>>   invalid command '::zio_state': unknown dcmd name
> >>>
> >>>  It looks like I can't find too much useful info here.
> >>
> >> You don't want to be using mdb -f on a system dump. Instead here, I
> >> would go into that directory, run `savecore -vf vmdump.0 .`.
> >>
> >> That will create a unix.0 and vmcore.0 which you can then access
> with
> >> mdb by running `mdb 0` in that directory. Note that by using mdb -f,
> >> you've asked mdb not to interpret the core dump, but rather treat it
> >> as a raw file which is why the dcmds are not being found.
> >>
> >
> > It looks like "`savecore -vf vmdump.0 .`" won't work:
> >
> > [root@pluto /zones/debug]# ls -la
> > total 39
> > drwxr-xr-x   2 root root   2 Jan 26 15:15 .
> > drwxr-xr-x  16 root root  19 Jan 25 19:21 ..
> >
> > [root@pluto /zones/debug]# savecore -vf vmdump.0 .
> > savecore: stat("vmdump.0"): No such file or directory
> > savecore: open("vmdump.0"): No such file or directory
> >
> > [root@pluto /zones/debug]# touch vmdump.0 [root@pluto /zones/debug]#
> > savecore -vf vmdump.0 .
> > savecore: pread: Invalid argument
> > savecore: pread: Invalid argument
> >
> > For I cleaned "/zones/debug", it looks I need push server panic again:
> > [root@pluto /zones/debug]# savecore -v /zones/debug
> > savecore: dump already processed
> 
> It's certainly not going to work if the file's not there. Which your
> first ls shows it's not. Did you delete it?

Yes. I cleaned the whole folder

Fred 

> 
> 


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] rpc.idmapd not working in lx brand

[Fred Liu]

Hi,

I am playing following lx brand zone:

82cf0a0a-6afc-11e5-8f79-273b6aea6443  centos-620151005  linux
lx-dataset2015-10-05


And it looks like rpc.idmapd not working which cause NFSv4 mount not working.

Thanks.


Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Is zfs deadm man timer tunable?

[Fred Liu]

Hi,

Subject says it all.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Is zfs dead man timer tunable?

[Fred Liu]

Comment below.

From: Richard Elling [mailto:richard.ell...@richardelling.com]
Sent: 星期五, 一月 22, 2016 13:51
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] Is zfs dead man timer tunable?

answer far below...

On Jan 21, 2016, at 8:44 PM, Fred Liu <fred_...@issi.com> wrote:




-Original Message-
From: Richard Elling [mailto:richard.ell...@richardelling.com]
Sent: 星期五, 一月 22, 2016 12:02
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] Is zfs deadm man timer tunable?



On Jan 21, 2016, at 4:25 AM, Fred Liu <fred_...@issi.com> wrote:

zfs deadman timer is tunable. But if you hit it, you've got problems
that tuning the deadman won't help.

The tunable is zfs_deadman_synctime_ms, which is milliseconds.

For example, on a test machine here:
[root@elvis ~]# echo zfs_deadman_synctime_ms/D | mdb -k
zfs_deadman_synctime_ms:
zfs_deadman_synctime_ms:100

FYI, you can check on the state of I/Os in the ZIO pipeline and how
long they've been there using the zio_state dcmd. Elvis is not
currently busy or broken, but here is an example:
[root@elvis ~]# echo ::zio_state | mdb -k
ADDRESS TYPE  STAGEWAITER
TIME_ELAPSED
ff01ada853e0NULL  OPEN --
ff01ada85b10NULL  OPEN --

If you see a large TIME_ELAPSED, you can track down the zio in question
for more debugging.
-- richard

Richard,

Many thanks! You have been always helpful since I first touched ZFS many years 
ago.
I am trying intel P3600 NVMe ssd on ZFS. I got several random server reboot 
every day. And I just captured "
panic message: I/O to pool 'zones' appears to be hung" from console. I doubt it 
is related to NVMe driver or
ssd firmware.

- SmartOS Live Image v0.147+ build: 20151001T070028Z
[root@pluto ~]# echo zfs_deadman_synctime_ms/D | mdb -k
zfs_deadman_synctime_ms:
zfs_deadman_synctime_ms:100
[root@pluto ~]# echo ::zio_state | mdb -k
ADDRESS TYPE  STAGEWAITER   TIME_ELAPSED
f08576c15028NULL  OPEN --
f08576c153a8NULL  OPEN --
f08576c15728NULL  OPEN --
f08576c15aa8NULL  OPEN --
f08576c15e28NULL  OPEN --
f08576c161a8NULL  OPEN --
f08576c16528NULL  OPEN --
f08576c168a8NULL  OPEN --
f08576c16c28NULL  OPEN --
f08576c25048NULL  OPEN --
f08576c253c8NULL  OPEN --
f08576c25748NULL  OPEN --
f08576c25ac8NULL  OPEN --
f08576c25e48NULL  OPEN --
f08576c261c8NULL  OPEN --
f08576c26548NULL  OPEN --
f08576c268c8NULL  OPEN --
f08576c26c48NULL  OPEN --
f08576e41028NULL  OPEN --
f08576e413a8NULL  OPEN --
f08576e41728NULL  OPEN --
f08576e428a8NULL  OPEN --
f08576e45050NULL  OPEN --
f08576e453d0NULL  OPEN --
f08576e45750NULL  OPEN --
f08576e45ad0NULL  OPEN --
f08576e45e50NULL  OPEN --
f08576e461d0NULL  OPEN --
f08576e46550NULL  OPEN --
f08576e468d0NULL  OPEN --
f08576e46c50NULL  OPEN --
f08576e47038NULL  OPEN --
f08576e473b8NULL  OPEN --
f08576e47738NULL  OPEN --
f08576e47ab8NULL  OPEN --
f08576e47e38NULL  OPEN --
f08576e481b8NULL  OPEN --
f08576e48538NULL  OPEN --
f08576e488b8NULL  OPEN --
f08576e48c38NULL  OPEN --
f08576c4f040NULL  OPEN --
f08576c4f3c0NULL  OPEN --
f08576c4f740NULL  OPEN --
f08576c4

RE: [smartos-discuss] Is zfs dead man timer tunable?

[Fred Liu]

Got more stuff here:

[root@pluto /var/log]# echo ::zio_state | mdb -k
ADDRESS TYPE  STAGEWAITER   TIME_ELAPSED
f0857715f020NULL  OPEN --
f0857715f3a8NULL  OPEN --
f0857715f730NULL  OPEN --
f0857715fab8NULL  OPEN --
f0857715fe40NULL  OPEN --
f085771601c8NULL  OPEN --
f08577160550NULL  OPEN --
f085771608d8NULL  OPEN --
f08577160c60NULL  OPEN --
f08577163008NULL  OPEN --
f08577163390NULL  OPEN --
f08577163718NULL  OPEN --
f08577163aa0NULL  OPEN --
f08577163e28NULL  OPEN --
f085771641b0NULL  OPEN --
f08577164538NULL  OPEN --
f085771648c0NULL  OPEN --
f08577164c48NULL  OPEN --
f086b921f3b0NULL  CHECKSUM_VERIFY  f003d1fc5c40 -

> -Original Message-
> From: Fred Liu [mailto:fred_...@issi.com]
> Sent: 星期五, 一月 22, 2016 14:18
> To: smartos-discuss@lists.smartos.org
> illumos-developer
> Subject: [developer] RE: [smartos-discuss] Is zfs dead man timer
> tunable?
> 
> Comment below.
> 
> From: Richard Elling [mailto:richard.ell...@richardelling.com]
> Sent: 星期五, 一月 22, 2016 13:51
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Is zfs dead man timer tunable?
> 
> answer far below...
> 
> On Jan 21, 2016, at 8:44 PM, Fred Liu <fred_...@issi.com> wrote:
> 
> -Original Message-
> From: Richard Elling [mailto:richard.ell...@richardelling.com]
> Sent: 星期五, 一月 22, 2016 12:02
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Is zfs deadm man timer tunable?
> 
> On Jan 21, 2016, at 4:25 AM, Fred Liu <fred_...@issi.com> wrote:
> 
> zfs deadman timer is tunable. But if you hit it, you've got problems
> that tuning the deadman won't help.
> 
> The tunable is zfs_deadman_synctime_ms, which is milliseconds.
> 
> For example, on a test machine here:
> [root@elvis ~]# echo zfs_deadman_synctime_ms/D | mdb -k
> zfs_deadman_synctime_ms:
> zfs_deadman_synctime_ms:100
> 
> FYI, you can check on the state of I/Os in the ZIO pipeline and how
> long they've been there using the zio_state dcmd. Elvis is not
> currently busy or broken, but here is an example:
> [root@elvis ~]# echo ::zio_state | mdb -k
> ADDRESS TYPE  STAGEWAITER
> TIME_ELAPSED
> ff01ada853e0NULL  OPEN -
> -
> ff01ada85b10NULL  OPEN -
> -
> 
> If you see a large TIME_ELAPSED, you can track down the zio in question
> for more debugging.
> -- richard
> 
> Richard,
> 
> Many thanks! You have been always helpful since I first touched ZFS
> many years ago.
> I am trying intel P3600 NVMe ssd on ZFS. I got several random server
> reboot every day. And I just captured "
> panic message: I/O to pool 'zones' appears to be hung" from console. I
> doubt it is related to NVMe driver or ssd firmware.
> 
> -  SmartOS Live Image v0.147+ build: 20151001T070028Z [root@pluto ~]#
> echo zfs_deadman_synctime_ms/D | mdb -k
> zfs_deadman_synctime_ms:
> zfs_deadman_synctime_ms:100
> [root@pluto ~]# echo ::zio_state | mdb -k
> ADDRESS TYPE  STAGEWAITER
> TIME_ELAPSED
> f08576c15028NULL  OPEN --
> f08576c153a8NULL  OPEN --
> f08576c15728NULL  OPEN --
> f08576c15aa8NULL  OPEN --
> f08576c15e28NULL  OPEN --
> f08576c161a8NULL  OPEN --
> f08576c16528NULL  OPEN --
> f08576c168a8NULL  OPEN --
> f08576c16c28NULL  OPEN --
> f08576c25048NULL  OPEN --
> f08576c253c8NULL  OPEN --
> f08576c25748NULL  OPEN --
> f08576c25ac8NULL  OPEN   

RE: [smartos-discuss] Is zfs dead man timer tunable?

[Fred Liu]

> -Original Message-
> From: Richard Elling [mailto:richard.ell...@richardelling.com]
> Sent: 星期五, 一月 22, 2016 12:02
> To: smartos-discuss@lists.smartos.org
> Subject: Re: [smartos-discuss] Is zfs deadm man timer tunable?
> 
> 
> > On Jan 21, 2016, at 4:25 AM, Fred Liu <fred_...@issi.com> wrote:
> 
> zfs deadman timer is tunable. But if you hit it, you've got problems
> that tuning the deadman won't help.
> 
> The tunable is zfs_deadman_synctime_ms, which is milliseconds.
> 
> For example, on a test machine here:
>   [root@elvis ~]# echo zfs_deadman_synctime_ms/D | mdb -k
>   zfs_deadman_synctime_ms:
>   zfs_deadman_synctime_ms:100
> 
> FYI, you can check on the state of I/Os in the ZIO pipeline and how
> long they've been there using the zio_state dcmd. Elvis is not
> currently busy or broken, but here is an example:
>   [root@elvis ~]# echo ::zio_state | mdb -k
>   ADDRESS TYPE  STAGEWAITER
> TIME_ELAPSED
>   ff01ada853e0NULL  OPEN --
>   ff01ada85b10NULL  OPEN --
> 
> If you see a large TIME_ELAPSED, you can track down the zio in question
> for more debugging.
>  -- richard
> 

Richard,

Many thanks! You have been always helpful since I first touched ZFS many years 
ago.
I am trying intel P3600 NVMe ssd on ZFS. I got several random server reboot 
every day. And I just captured "
panic message: I/O to pool 'zones' appears to be hung" from console. I doubt it 
is related to NVMe driver or
ssd firmware.

- SmartOS Live Image v0.147+ build: 20151001T070028Z
[root@pluto ~]# echo zfs_deadman_synctime_ms/D | mdb -k
zfs_deadman_synctime_ms:
zfs_deadman_synctime_ms:100 
[root@pluto ~]# echo ::zio_state | mdb -k
ADDRESS TYPE  STAGEWAITER   TIME_ELAPSED
f08576c15028NULL  OPEN --
f08576c153a8NULL  OPEN --
f08576c15728NULL  OPEN --
f08576c15aa8NULL  OPEN --
f08576c15e28NULL  OPEN --
f08576c161a8NULL  OPEN --
f08576c16528NULL  OPEN --
f08576c168a8NULL  OPEN --
f08576c16c28NULL  OPEN --
f08576c25048NULL  OPEN --
f08576c253c8NULL  OPEN --
f08576c25748NULL  OPEN --
f08576c25ac8NULL  OPEN --
f08576c25e48NULL  OPEN --
f08576c261c8NULL  OPEN --
f08576c26548NULL  OPEN --
f08576c268c8NULL  OPEN --
f08576c26c48NULL  OPEN --
f08576e41028NULL  OPEN --
f08576e413a8NULL  OPEN --
f08576e41728NULL  OPEN --
f08576e428a8NULL  OPEN --
f08576e45050NULL  OPEN --
f08576e453d0NULL  OPEN --
f08576e45750NULL  OPEN --
f08576e45ad0NULL  OPEN --
f08576e45e50NULL  OPEN --
f08576e461d0NULL  OPEN --
f08576e46550NULL  OPEN --
f08576e468d0NULL  OPEN --
f08576e46c50NULL  OPEN --
f08576e47038NULL  OPEN --
f08576e473b8NULL  OPEN --
f08576e47738NULL  OPEN --
f08576e47ab8NULL  OPEN --
f08576e47e38NULL  OPEN --
f08576e481b8NULL  OPEN --
f08576e48538NULL  OPEN --  

[smartos-discuss] enable some services when building smartos

[Fred Liu]

Hi,

Is " smartos-live/overlay/generic/usr/lib/brand/joyent/manifests" the right one 
to modify?

I got successful building, but it looks the services enabled by me  are still 
disabled.

Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] RE: [developer] ypbind statvfs failed with [Value too large for defined data type]

[Fred Liu]

> -Original Message-
> From: Igor Kozhukhov [mailto:ikozhuk...@gmail.com]
> Sent: 星期五, 一月 15, 2016 19:45
> To: Fred Liu; smartos-discuss@lists.smartos.org
> Cc: illumos-developer
> Subject: Re: [developer] ypbind statvfs failed with [Value too large
> for defined data type]
> 
> Smartos designed to use read only image with RW configuration on /zones
> zpool.
> 
> If you want try to play with this file - you can take a look smartos
> build env and learn how to prepare new image.
> Or, maybe try to play with another illumos based distributions: OI,
> OmniOS, DilOS - but you need to learn build env based on another
> distributions if you want debug/test/fix it.
> 

Thanks. I know those illumos-based variations. Even SmartOS is designed mainly 
for virtualization prupose,
the naming service(NIS/LDAP) is not contradictive to this goal at all. I 
totally understand minimalism and 
purism. This is why I prefer "all-on-one"(virtualization + file service + 
computing) for SMB.

Thanks.

Fred

> 
> 
> On 15/01/16 14:40, "Fred Liu" <fred_...@issi.com> wrote:
> 
> >
> >
> >From: Igor Kozhukhov [mailto:ikozhuk...@gmail.com]
> >Sent: 星期五, 一月 15, 2016 19:26
> >To: Fred Liu; smartos-discuss@lists.smartos.org
> >Cc: illumos-developer
> >Subject: Re: [developer] ypbind statvfs failed with [Value too large
> >for defined data type]
> >
> >ypbind is part of illumos:
> >https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/ypcmd
> >
> >Take a look Makefile - it contain ypbind
> >
> >[Fred]o Oh. I doubt it is related to read-only file system. Is there a
> >way to trace what files are accessed by ypbind?
> >
> >Thanks.
> >
> >Fred
> >
> >From: Fred Liu <fred_...@issi.com>
> >Date: Friday 15 January 2016 at 12:53
> >To: "smartos-discuss@lists.smartos.org"
> ><smartos-discuss@lists.smartos.org>
> >Cc: illumos-dev <develo...@lists.illumos.org>
> >Subject: [developer] ypbind statvfs failed with [Value too large for
> >defined data type]
> >
> >Hi,
> >
> >I am trying to play ypbind on joyent_20160108T173524Z but I get
> >following
> >errors:
> >
> >2016-01-15T17:47:26+09:00 pluto ypbind[4634]: [ID 472466 daemon.error]
> >statvfs failed with [Value too large for defined data type]
> >
> >
> >Is the ypbind from SmartOS compiled from source or just copy from old
> >release?
> >
> >Thanks.
> >
> >Fred
> >illumos-developer | Archives | Modify Your Subscription
> >
> >
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] RE: [developer] ypbind statvfs failed with [Value too large for defined data type]

[Fred Liu]

From: Igor Kozhukhov [mailto:ikozhuk...@gmail.com] 
Sent: 星期五, 一月 15, 2016 19:26
To: Fred Liu; smartos-discuss@lists.smartos.org
Cc: illumos-developer
Subject: Re: [developer] ypbind statvfs failed with [Value too large for 
defined data type]

ypbind is part of illumos:
https://github.com/illumos/illumos-gate/tree/master/usr/src/cmd/ypcmd

Take a look Makefile - it contain ypbind

[Fred]o Oh. I doubt it is related to read-only file system. Is there a way to 
trace what files are accessed by ypbind?

Thanks.

Fred

From: Fred Liu <fred_...@issi.com>
Date: Friday 15 January 2016 at 12:53
To: "smartos-discuss@lists.smartos.org" <smartos-discuss@lists.smartos.org>
Cc: illumos-dev <develo...@lists.illumos.org>
Subject: [developer] ypbind statvfs failed with [Value too large for defined 
data type]

Hi,
 
I am trying to play ypbind on joyent_20160108T173524Z but I get following 
errors:
 
2016-01-15T17:47:26+09:00 pluto ypbind[4634]: [ID 472466 daemon.error] statvfs 
failed with [Value too large for defined data type]
 
 
Is the ypbind from SmartOS compiled from source or just copy from old release?
 
Thanks.
 
Fred
illumos-developer | Archives | Modify Your Subscription




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] ypbind statvfs failed with [Value too large for defined data type]

[Fred Liu]

Hi,

I am trying to play ypbind on joyent_20160108T173524Z but I get following 
errors:

2016-01-15T17:47:26+09:00 pluto ypbind[4634]: [ID 472466 daemon.error] statvfs 
failed with [Value too large for defined data type]


Is the ypbind from SmartOS compiled from source or just copy from old release?

Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] feeding HPET (High Precision Event Timer) to smartOS's KVM to address windows vm clock drift issue

[Fred Liu via smartos-discuss]

As good finding, after patching win2008r2 to the latest, the clock drift is 
acceptable.

 -Original Message-
 From: Fred Liu
 Sent: 星期二, 十二月 24, 2013 20:11
 To: smartos-discuss@lists.smartos.org
 Subject: RE: [smartos-discuss] feeding HPET (High Precision Event Timer)
 to smartOS's KVM to address windows vm clock drift issue
 
  Hi Fred,
 
  Sorry for the delay in getting back to you. Can you run the following
  DTrace one liner to see whether or not the HPET is at least
  instantiated by the virtual machine?
 
  dtrace -n 'pid$target::hpet*:entry{ @[probefunc] = count(); }' -p
  qemupid
 
  If that returns multiple probes, you should run this:
 
  dtrace -n 'pid$target::hpet_enabled:return{ @[arg1] = count(); }' -p
  qemupid.
 
  If you see non-zero return values from the hpet_enabled call, then
  you'll know that we have at least created the hpet and IIRC Windows
  has enabled it.
 
  Thanks,
  Robert
 
 
 Robert,
 
 Thanks for your help and debugging.  Following is the output from Dtrce:
 
 [root@00-25-90-74-f5-04 ~]# dtrace -n
 'pid$target::hpet*:entry{ @[probefunc] = count(); }' -p 36155
 dtrace: description 'pid$target::hpet*:entry' matched 21 probes
 
 ^C
 
   hpet_ram_writel   8
   hpet_set_timer8
   hpet_in_legacy_mode  123529
   hpet_timer   123529
   hpet_calculate_diff  123532
   hpet_time_after  247621
   hpet_ram_readl   251764
   hpet_enabled 375293
   hpet_get_ticks   375293
 [root@00-25-90-74-f5-04 ~]# dtrace -n
 'pid$target::hpet_enabled:return{ @[arg1] = count(); }' -p 36155
 dtrace: description 'pid$target::hpet_enabled:return' matched 1 probe
 
 
 ^C
 
 112193
 [root@00-25-90-74-f5-04 ~]#
 
 It looks like HPET is working but with a weird lag of approximate one
 minute in win7 vm.
 
 
 Thanks.
 
 Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] ntp service cannot be started in 20140627T001506Z

[Fred Liu via smartos-discuss]

 Distributors of NTP-enabled operating systems are generally not
 permitted to use the bare pool.ntp.org DNS name in any default NTP
 configurations[1].  To this end, I have been arranging a SmartOS-
 specific DNS name with the NTP Pool Project that we _can_ use.
 Hopefully this will be the default in SmartOS soon -- I'll keep you
 posted!
 

That is really cool!
BTW who is the contributor behind this smartos-specific ntp pool?


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] ntp service cannot be started in 20140627T001506Z

[Fred Liu via smartos-discuss]

 
  Why did it enter maintenance? Check the log with svcs -L.
 
 [ Jun 30 22:10:43 Enabled. ]
 [ Jun 30 22:10:43 Executing start method (/lib/svc/method/ntp
 start). ]
 Error: Servers/peers specified but none is reachable.
 [ Jun 30 22:10:58 Method start exited with status 96. ]
 

[root@00-25-90-74-f5-04 /zones/stuff]# !cat
cat /etc/inet/ntp.conf
driftfile /var/ntp/ntp.drift
logfile /var/log/ntp.log

# Default, ignore all
restrict default ignore
restrict -6 default ignore

# Allow localhost
restrict 127.0.0.1

# Specify Time Servers with ACL to allow them
server 169.229.70.183 burst iburst minpoll 4
restrict 169.229.70.183
server 128.177.27.52 burst iburst minpoll 4
restrict 128.177.27.52
server 69.65.40.29 burst iburst minpoll 4
restrict 69.65.40.29
[root@00-25-90-74-f5-04 /zones/stuff]# ping 169.229.70.183
169.229.70.183 is alive
[root@00-25-90-74-f5-04 /zones/stuff]# ping -s 169.229.70.183
PING 169.229.70.183: 56 data bytes
64 bytes from 169.229.70.183: icmp_seq=0. time=243.229 ms
64 bytes from 169.229.70.183: icmp_seq=1. time=243.300 ms
^C
169.229.70.183 PING Statistics
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms)  min/avg/max/stddev = 243.229/243.264/243.300/0.050
[root@00-25-90-74-f5-04 /zones/stuff]# ping -s 128.177.27.52
PING 128.177.27.52: 56 data bytes
^C
128.177.27.52 PING Statistics
6 packets transmitted, 0 packets received, 100% packet loss
[root@00-25-90-74-f5-04 /zones/stuff]# ping -s 69.65.40.29
PING 69.65.40.29: 56 data bytes
64 bytes from 69.65.40.29: icmp_seq=0. time=202.807 ms
64 bytes from 69.65.40.29: icmp_seq=1. time=192.780 ms
^C
69.65.40.29 PING Statistics
2 packets transmitted, 2 packets received, 0% packet loss
round-trip (ms)  min/avg/max/stddev = 192.780/197.794/202.807/7.090


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] ntp service cannot be started in 20140627T001506Z

[Fred Liu via smartos-discuss]

It looks the NTP service is NOT OK  on these three static IPs.

Why not use a FQDN like pool.ntp.org in the configuration?

 -Original Message-
 From: Fred Liu
 Sent: 星期一, 六月 30, 2014 22:50
 To: 'smartos-discuss@lists.smartos.org'; Fred Liu; Robert Mustacchi
 Subject: RE: [smartos-discuss] ntp service cannot be started in
 20140627T001506Z
 
 
 
   Why did it enter maintenance? Check the log with svcs -L.
 
  [ Jun 30 22:10:43 Enabled. ]
  [ Jun 30 22:10:43 Executing start method (/lib/svc/method/ntp
  start). ]
  Error: Servers/peers specified but none is reachable.
  [ Jun 30 22:10:58 Method start exited with status 96. ]
 
 
 [root@00-25-90-74-f5-04 /zones/stuff]# !cat cat /etc/inet/ntp.conf
 driftfile /var/ntp/ntp.drift logfile /var/log/ntp.log
 
 # Default, ignore all
 restrict default ignore
 restrict -6 default ignore
 
 # Allow localhost
 restrict 127.0.0.1
 
 # Specify Time Servers with ACL to allow them server 169.229.70.183
 burst iburst minpoll 4 restrict 169.229.70.183 server 128.177.27.52
 burst iburst minpoll 4 restrict 128.177.27.52 server 69.65.40.29 burst
 iburst minpoll 4 restrict 69.65.40.29
 [root@00-25-90-74-f5-04 /zones/stuff]# ping 169.229.70.183
 169.229.70.183 is alive
 [root@00-25-90-74-f5-04 /zones/stuff]# ping -s 169.229.70.183 PING
 169.229.70.183: 56 data bytes
 64 bytes from 169.229.70.183: icmp_seq=0. time=243.229 ms
 64 bytes from 169.229.70.183: icmp_seq=1. time=243.300 ms ^C
 169.229.70.183 PING Statistics
 2 packets transmitted, 2 packets received, 0% packet loss round-trip
 (ms)  min/avg/max/stddev = 243.229/243.264/243.300/0.050
 [root@00-25-90-74-f5-04 /zones/stuff]# ping -s 128.177.27.52 PING
 128.177.27.52: 56 data bytes ^C
 128.177.27.52 PING Statistics
 6 packets transmitted, 0 packets received, 100% packet loss
 [root@00-25-90-74-f5-04 /zones/stuff]# ping -s 69.65.40.29 PING
 69.65.40.29: 56 data bytes
 64 bytes from 69.65.40.29: icmp_seq=0. time=202.807 ms
 64 bytes from 69.65.40.29: icmp_seq=1. time=192.780 ms ^C
 69.65.40.29 PING Statistics
 2 packets transmitted, 2 packets received, 0% packet loss round-trip
 (ms)  min/avg/max/stddev = 192.780/197.794/202.807/7.090


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Working backplane/enclosure for SES in mass non-Solaris/fishwork-ZFS deployment

[Fred Liu via smartos-discuss]

 -Original Message-
 From: Richard Elling [mailto:richard.ell...@richardelling.com]
 Sent: 星期六, 五月 10, 2014 21:53
 To: smartos-discuss@lists.smartos.org; Robert Mustacchi
 Cc: Fred Liu
 Subject: Re: [smartos-discuss] Working backplane/enclosure for SES in
 mass non-Solaris/fishwork-ZFS deployment
 
 Speaking of lighting LEDs...
 
 On May 9, 2014, at 7:11 PM, Robert Mustacchi via smartos-discuss
 smartos-discuss@lists.smartos.org wrote:
 
  On 5/9/14 18:01 , Fred Liu via smartos-discuss wrote:
  I post here for I don't know where the largest non-Solaris/fishwork-
 ZFS deployment in the world is. But Joyent provide cloud service. The
 people from their datacenters must play bunch of disks everyday. As
 long as I know, only
 dataON+nexenta(http://www.dataonstorage.com/dataon-
 solutions/nexenta/dsm-30-for-nexentastor.html) released a solution for
 disk management in illumos-ZFS product. And don't know too much in
 Linux/FreeBSD side.
 
 DSM uses a wrapper around sg3_utils to check LED status and change.
 
 NexentaStor created its own LED lighting CLI code (I can't recall its
 name off the top of my head) that had the annoying habit of lighting
 LED 0 if you gave it the wrong input. Later they worked that into their
 GUI (circa 2011/2012).
 
 For most folks, the lack of documentation for fmtopo means they miss
 the fact that you can test or change all of the enumerated LEDs on the
 system, including PSUs, chassis locator, etc. Whether this actually
 lights LEDs is not a question that is easy to answer, given the
 plethora of firmware in the world of dubious quality. This is an area
 where companies like DataOn provide good value: they test their
 hardware/firmware in an illumos environment.
 
 Usage: /usr/lib/fm/fmd/fmtopo [-bCedpSVx] [-P
 group.property[=type:value]] [-R root] [-l file] [-m method] [-s scheme]
 [fmri]
 -b  walk in sibling-first order (default is child-first)
 -C  dump core after completing execution
 -d  set debug mode for libtopo modules
 -e  display FMRIs as paths using esc/eft notation
 -l  load specified topology map file
 -m  execute given method
 -P  get/set specified properties
 -p  display of FMRI protocol properties
 -R  set root directory for libtopo plug-ins and other files
 -s  display topology for the specified FMRI scheme
 -S  display FMRI status (present/usable)
 -V  set verbose mode
 -x  display a xml formatted topology
 
 -P is the option you're looking for to get/set properties (=uint32:1) -
 C is one of those options that makes you think someone was smoking
 something...
 or else they don't know how to use debuggers or dtrace :-P
 
 Warning: the command example you're about to see is butugly
 
 # /usr/lib/fm/fmd/fmtopo -P facility.mode=uint32:1 hc://:product-
 id=NEWISYS-NDS-4600-JD:server-id=:chassis-id=500093d00169b000/ses-
 enclosure=0/bay=60?indicator=ident
 TIME UUID
 May 10 13:49:32 40bcdaad-3474-41b1-9fba-fa6ea2de5971
 
 hc://:product-id=NEWISYS-NDS-4600-JD:server-id=:chassis-
 id=500093d00169b000/ses-enclosure=0/bay=60?indicator=ident
   group: facility   version: 1   stability:
 Private/Private
 mode  uint320x1 (ON)
 
 # /usr/lib/fm/fmd/fmtopo -V hc://:product-id=NEWISYS-NDS-4600-
 JD:server-id=:chassis-id=500093d00169b000/ses-
 enclosure=0/bay=60?indicator=ident
 TIME UUID
 May 10 13:50:50 63d689fa-af5c-664f-896e-d42d58c3a5d0
 
 hc://:product-id=NEWISYS-NDS-4600-JD:server-id=:chassis-
 id=500093d00169b000/ses-enclosure=0/bay=60?indicator=ident
   group: protocol   version: 1   stability:
 Private/Private
 resource  fmri  hc://:product-id=NEWISYS-NDS-4600-
 JD:server-id=:chassis-id=500093d00169b000/ses-
 enclosure=0/bay=60?indicator=ident
   group: authority  version: 1   stability:
 Private/Private
 product-idstringNEWISYS-NDS-4600-JD
 chassis-idstring500093d00169b000
 server-id string
   group: facility   version: 1   stability:
 Private/Private
 type  uint320x1 (LOCATE)
 mode  uint320x1 (ON)
   group: sesversion: 1   stability:
 Private/Private
 node-id   uint640x1003e
 
 # /usr/lib/fm/fmd/fmtopo -P facility.mode=uint32:1 hc://:product-
 id=NEWISYS-NDS-4600-JD:server-id=:chassis-id=500093d00169b000/ses-
 enclosure=0/bay=60?indicator=ident
 TIME UUID
 May 10 13:49:32 40bcdaad-3474-41b1-9fba-fa6ea2de5971
 
 hc://:product-id=NEWISYS-NDS-4600-JD:server-id=:chassis-
 id=500093d00169b000/ses-enclosure=0/bay=60?indicator=ident
   group: facility   version: 1   stability:
 Private/Private
 mode  uint320x1 (ON)
 
 # /usr/lib/fm/fmd/fmtopo -P facility.mode=uint32:0 hc://:product-
 id=NEWISYS-NDS-4600-JD:server-id=:chassis-id

[smartos-discuss] RE: [developer] HBA recommended except LSI and ARECA

[Fred Liu]

[fred]：ok. Let's see how it goes after I get the hba.

[fred]: I have got 6805H HBA. It can recognize the sata drives in bios but 
these drives cannot be detected in the latest illumos(smartos,oi) release.
  I haven’t got a sas  drive to test. But the price delta between 
sas and sata drive under the same capacity is not small like USD30 at all. ☹.

   Thanks.

 Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] failed to add cache device

[Fred Liu via smartos-discuss]

Hi,

I failed to add cache device like following:
[root@00-25-90-74-f5-04 ~]# zpool add zones cache c0t50015179596E5EB1d0p1
Assertion failed: rchildren == 2, file zpool_vdev.c, line 641
Abort (core dumped)
[root@00-25-90-74-f5-04 ~]# uname -a
SunOS 00-25-90-74-f5-04 5.11 joyent_20140418T031241Z i86pc i386 i86pc

c0t50015179596E5EB1d0p1 is fdisk partition.

But it worked in 20120713T005832Z before.


Thanks.

Fred


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] RE: [developer] HBA recommended except LSI and ARECA

[Fred Liu via smartos-discuss]

Is 6805H/6405H(http://www.adaptec.com//en-us/products/series/6h/) worthy of 
recommendation too?

Thanks.

Fred

 -Original Message-
 From: Keith Wesolowski [mailto:keith.wesolow...@joyent.com]
 Sent: 星期四, 五月 01, 2014 0:29
 To: Fred Liu
 Cc: develo...@lists.illumos.org
 Subject: Re: [developer] HBA recommended except LSI and ARECA
 
 On Wed, Apr 30, 2014 at 06:34:29AM -0700, Fred Liu via illumos-
 developer wrote:
 
  Sorry for the typo…
 
  From: Fred Liu
  Sent: 星期三, 四月 30, 2014 21:31
  To: 'develo...@lists.illumos.org'
  Subject: HBA recommended except LSI and ARECO
 
  Hi,
 
  Any ideas will be highly appreciated!
 
 Well, since you've excluded two of the three HBA vendors, I'm not sure
 why you're asking for ideas.  The remaining player is PMC-Sierra, who
 recently bought Adaptec and are now using that as a consumer-facing
 brand for cards based on the ASICs they've made for years.
 
 I have not yet evaluated them in my lab, but I suspect that e.g. the
 7085H/7805H likely work with our pmcs(7D) driver.  If so, I would
 recommend giving this a close look (if not, we need to get in touch
 with them and fix that); we used PMC-Sierra ASICs on a Sun-made board
 when I was at Fishworks and I was reasonably pleased with the product.
 At the time anyway, PMC was much better aligned with the ZFS-centric
 storage architecture than LSI: less work being done in firmware, better
 non-RAID options, superior error handling and telemetry, etc.  I have
 not seen LSI change their stance on this; they clearly remain committed
 to selling people expensive HW RAID controllers with bloated firmware
 stacks.  Assuming this generation of PMC products is similar to the old,
 you'll likely find them a better fit than the other vendors.
 
 See http://www.adaptec.com/en-us/products/series/7h/.
 
 I would not recommend any of the consumer-grade (pre-PMC) or HW RAID
 based stuff from Adaptec.  That stuff was trash, and I'm not sure any
 of it works with illumos at all.


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Re: [developer] HBA recommended except LSI and ARECA

[Fred Liu via smartos-discuss]

Keith Wesolowski via smartos-discuss smartos-discuss@lists.smartos.org
于2014年5月1日星期四写道：

 On Wed, Apr 30, 2014 at 10:13:49AM -0700, Fred Liu wrote:

  Is 6805H/6405H(http://www.adaptec.com//en-us/products/series/6h/)
 worthy of recommendation too?

 That uses the PM8001, which I believe is the same ASIC I have direct
 experience with.  So it would be good to look at too, yes.

 [fred]: gotcha! I will give it a try. Does it work well with commodity
 sata drives?



Thanks.

Fred

 ---
 smartos-discuss
 Archives: https://www.listbox.com/member/archive/184463/=now
 RSS Feed:
 https://www.listbox.com/member/archive/rss/184463/22027488-c60da3c5
 Modify Your Subscription:
 https://www.listbox.com/member/?;
 Powered by Listbox: http://www.listbox.com




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Re: [developer] HBA recommended except LSI and ARECA

[Fred Liu via smartos-discuss]

Keith Wesolowski keith.wesolow...@joyent.com于2014年5月1日星期四写道：

 On Thu, May 01, 2014 at 02:13:38AM +0800, Fred Liu wrote:

   That uses the PM8001, which I believe is the same ASIC I have direct
   experience with.  So it would be good to look at too, yes.
  
   [fred]: gotcha! I will give it a try. Does it work well with commodity
   sata drives?

 Unknown.  The interface to the ASIC is basically SAS-only; the model in
 the 8001 was that the SATL is provided by software, not firmware or
 hardware.  Presumably PMC/Adapted implemented a SATL in their bundled
 drivers for legacy OSs.  This is markedly different from LSI's model
 (and a big advantage of PMC's).  I do not know how far they got on
 making that work, because by the time we started using this device we
 had long since decided that we would never again ship a storage product
 with SATA devices in it.  So from my perspective this HBA is completely
 untested with SATA end devices (commodity or otherwise).  It may work,
 it may not.  Certainly it was intended that it be usable in that
 configuration by the people at Sun who wrote the drivers, and it is
 possible to make it work if it does not.  But I don't recommend using
 SATA, ever.  SAS disks cost $30 more.  Best $30 you'll ever spend.


  [fred]：ok. Let's see how it goes after I get the hba.


   Thanks.

 Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] hacking grub to enable smartos booting from multi-version.

[Fred Liu via smartos-discuss]

Hi,

It seems my grub only work with the fixed path name like /platform/ and 
it cannot work with different name like /platform-xxx/.

Is it possible to switch to different versions?


Thanks.

Fred



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] hacking grub to enable smartos booting from multi-version.

[Fred Liu via smartos-discuss]

Daniel，

Can you post the detailed configuration about your iPXE?

Thanks.

Fred



发件人: Daniel Malon [daniel.ma...@me.com]
发送时间: 2014年4月29日 4:34
收件人: smartos-discuss@lists.smartos.org; Fred Liu
主题: Re: [smartos-discuss] hacking grub to enable smartos booting from 
multi-version.

Hi,

a folder structure like: /version/platform/… works fine for me while booting 
via iPXE.

as far as I know you need to have the platform folder like it is for the boot 
manager to recognize the illumos kernel correctly (but that might be only for 
iPXE).


regards,
Daniel

Am 29.04.2014 um 12:59 schrieb Fred Liu via smartos-discuss 
smartos-discuss@lists.smartos.orgmailto:smartos-discuss@lists.smartos.org:

Hi,

It seems my grub only work with the fixed path name like “/platform/” and 
it cannot work with different name like “/platform-xxx/”.

Is it possible to switch to different versions?


Thanks.

Fred
smartos-discuss | Archiveshttps://www.listbox.com/member/archive/184463/=now 
[https://www.listbox.com/images/feed-icon-10x10.jpgc2c8124.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
 https://www.listbox.com/member/archive/rss/184463/21955186-c7d24c67  | 
Modifyhttps://www.listbox.com/member/?; Your Subscription   
[https://www.listbox.com/images/listbox-logo-small.pngc2c8124.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 http://www.listbox.com/

---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com