Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Sašo Kiselkov
On 02/20/2013 08:05 PM, Reginald Beardsley wrote: > On an N40L running oi_151a7 w/ four ST2000DM001 drives I'm seeing > a large drop in performance for RAIDZ2 vs RAIDZ1 which surprises me. > > The discussions google found were not entirely enlightening and not > OI based. How much CPU does a smal

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Jozsef Brogyanyi
Please look the "load" in the top.The CPU idle time is not enough.The difference is very huge.In your case may be the load over the "2".If am I right then your CPU is weak for this feature. Check again. Brogyi 2013/2/20 Reginald Beardsley > On an N40L running oi_151a7 w/ four ST2000DM001 drives

[OpenIndiana-discuss] Problem with SMB Server:

2013-02-21 Thread Armin Maier
Hello, i set up a openindiana 151a7 server with zfs and Active Directory authentication. I can share zfs filesystems to windows server and set permissions to Active Directory users, no problem. The only issue is i can only access the server over the short name "\\server\share", using the FQDN N

[OpenIndiana-discuss] rge0 flip-flop up and down

2013-02-21 Thread Maurizio Boriani
Hi all, on a fresh openindiana 151a7 installation, my realtek flapping up and down, but for nwam is always up. The host is a laptop hp probook 4540s. There are some known issues, acpi or similar? tia, bye ___ OpenIndiana-discuss mailing list OpenInd

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Roy Sigurd Karlsbakk
> RAID-Z2 is quite CPU intensive, since it switches from XOR parity (for > RAID-Z1) to a Reed-Solomon error-correcting code (in order to be able > to > survive multiple drive failures). The N40L's piddly CPU (2 cores @ > 1.4GHz) probably doesn't like that very much. 30-50% idle means 1 core > compl

Re: [OpenIndiana-discuss] rge0 flip-flop up and down

2013-02-21 Thread Maurizio Boriani
On Thu, 2013-02-21 at 17:15 +0100, Maurizio Boriani wrote: > Hi all, > on a fresh openindiana 151a7 installation, my realtek flapping up and > down, but for nwam is always up. The host is a laptop hp probook 4540s. > There are some known issues, acpi or similar? > > tia, found. By setting ip:d

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Sašo Kiselkov
On 02/21/2013 06:56 PM, Roy Sigurd Karlsbakk wrote: > Are you sure z2 uses reed-solomon? I thought it just used two-dimensional XOR > like Raid-6 Pretty sure, unless the documentation is lying: https://github.com/illumos/illumos-gate/blob/master/usr/src/uts/common/fs/zfs/vdev_raidz.c#L38-L45 Ch

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Timothy Coalson
I think last time this was asked, the consensus was that the implementation was based on linear feedback shift registers and xor, which happens to be a reed-solomon code (not as clear on this part, but what matters is what it is, not what it isn't). Regardless, from reading the source previously,

[OpenIndiana-discuss] about tuntap

2013-02-21 Thread Maurizio Boriani
Hi all, in openindiana 151a7, the tuntap driver is: http://www.whiteboard.ne.jp/~admin2/tuntap/ or it has its' own? thanks, baux ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openin

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Sašo Kiselkov
On 02/21/2013 07:27 PM, Timothy Coalson wrote: > I think last time this was asked, the consensus was that the implementation > was based on linear feedback shift registers and xor, which happens to be a > reed-solomon code (not as clear on this part, but what matters is what it > is, not what it is

Re: [OpenIndiana-discuss] about tuntap

2013-02-21 Thread Jim Klimov
On 2013-02-21 19:40, Maurizio Boriani wrote: Hi all, in openindiana 151a7, the tuntap driver is: http://www.whiteboard.ne.jp/~admin2/tuntap/ or it has its' own? Should be it, last summer's release (1.3.0 iirc) ___ OpenIndiana-discuss mailing lis

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Sašo Kiselkov
On 02/21/2013 08:06 PM, Sašo Kiselkov wrote: > On 02/21/2013 07:27 PM, Timothy Coalson wrote: >> I think last time this was asked, the consensus was that the implementation >> was based on linear feedback shift registers and xor, which happens to be a >> reed-solomon code (not as clear on this part

Re: [OpenIndiana-discuss] about tuntap

2013-02-21 Thread Gordon Ross
On Thu, Feb 21, 2013 at 1:40 PM, Maurizio Boriani wrote: > Hi all, > in openindiana 151a7, the tuntap driver is: > > http://www.whiteboard.ne.jp/~admin2/tuntap/ > > or it has its' own? > > thanks, > > baux I have a "userland" style build for tuntap and openvpn here: https://bitbucket.org/gwr/

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Sašo Kiselkov
On 02/21/2013 07:27 PM, Timothy Coalson wrote: > I think last time this was asked, the consensus was that the implementation > was based on linear feedback shift registers and xor, which happens to be a > reed-solomon code (not as clear on this part, but what matters is what it > is, not what it is

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Reginald Beardsley
Wow! I'm also deeply embarrassed for not having looked at the source myself before posting. I should have. FWIW A 10x performance hit for double parity instead of single parity is probably a code tuning or algorithm issue. Have Fun! Reg --- On Thu, 2/21/13, Sašo Kiselkov wrote: > From: Saš

Re: [OpenIndiana-discuss] Problem with SMB Server:

2013-02-21 Thread Christopher Chan
On Thursday, February 21, 2013 10:32 PM, Armin Maier wrote: Hello, i set up a openindiana 151a7 server with zfs and Active Directory authentication. I can share zfs filesystems to windows server and set permissions to Active Directory users, no problem. The only issue is i can only access the s

Re: [OpenIndiana-discuss] RAIDZ performance

2013-02-21 Thread Timothy Coalson
The first parity uses straight XOR on uint64_t, while the second parity performs the LFSR on all bytes in a uint64_t with some bitwise math (search for VDEV_RAIDZ_64MUL_2) that adds up to 8 operators by my count, followed by xor - using the LFSR lookup table on each byte might have a chance at bein