[OmniOS-discuss] Badlock SMB bug -- do we know if Illumos kernel CIFS implementation is also affected?

See http://badlock.org/ for more information. I'd like to assume that the devs in question would have communicated with other SMB implementations like the Solaris/Illumos and Apple's implementation, but -- Dave Pooser Cat-Herder-in-Chief, Pooserville.com

[OmniOS-discuss] Good way to debug DTrace invalid address errors?

I have a relatively complicated chunk of dtrace code that reads kernel data structures and chases pointers through them. Some of the time it spits out 'invalid address' errors during execution, for example: dtrace: error on enabled probe ID 8 (ID 75313: fbt:nfssrv:nfs3_fhtovp:return):

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

> On Mar 23, 2016, at 7:49 AM, Richard Jahnel wrote: > > It should be noted that using a 512e disk as a 512n disk subjects you to a > significant risk of silent corruption in the event of power loss. Because > 512e disks does a read>modify>write operation to modify

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

It should be noted that using a 512e disk as a 512n disk subjects you to a significant risk of silent corruption in the event of power loss. Because 512e disks does a read>modify>write operation to modify 512byte chunk of a 4k sector, zfs won't know about the other 7 corrupted 512e sectors in

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

> > The sd.conf whitelist also requires a reboot to activate if you need > > to add a new entry, as far as I know. > > > > (Nor do I know what happens if you have some 512n disks and > > some 512e disks, both correctly recognized and in different > > pools, and now you need to

Re: [OmniOS-discuss] 4kn or 512e with ashift=12

> -Original Message- > From: Richard Elling [mailto:richard.ell...@richardelling.com] > Sent: 星期三, 三月 23, 2016 4:53 > To: Chris Siebenmann > Cc: Fred Liu; omnios-discuss@lists.omniti.com > Subject: Re: [OmniOS-discuss] 4kn or 512e with ashift=12 > > > On Mar 22, 2016, at 7:41 AM,