-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/24/2010 6:31 PM, James C. McPherson wrote: > > > hi Kyle, > the serveraid driver was only ever a community effort; the > fact that it was done by a Sun engineer is actually irrelevant :-) >
Hi James, > That engineer has since left Sun, and I've obtained the source > for it from him. I just don't have any time to work on it at > the moment. One of the reasons that I asked originally, was because of these messages I see during boot: WARNING: mutex_init: ffffff04e4724d06 is not 8 byte aligned; caller ips_attach+22b in module ips. This is unsupported and may cause a panic. Please report this to the kernel module supplier. WARNING: mutex_init: ffffff04e4724d0e is not 8 byte aligned; caller ips_attach+264 in module ips. This is unsupported and may cause a panic. Please report this to the kernel module supplier. WARNING: mutex_init: ffffff04e4724cec is not 8 byte aligned; caller ips_attach+27e in module ips. This is unsupported and may cause a panic. Please report this to the kernel module supplier. WARNING: mutex_init: ffffff04e4724e12 is not 8 byte aligned; caller ips_attach+29e in module ips. This is unsupported and may cause a panic. Please report this to the kernel module supplier. WARNING: mutex_init: ffffff04e4724cfc is not 8 byte aligned; caller ips_attach+2b8 in module ips. This is unsupported and may cause a panic. Please report this to the kernel module supplier. I'm sure it's likely that this isn't as striaght forward as I'm hoping, but I think fixing these messages might be something I can actually do to help out. :) At the same time, I've been playing with NexentaStor on another machine with the same hardware, and when I write to the ZFS filesystem over NFS the machine quickly becomes unresponsive and eventually needs to be rebooted. I was watching some of the DTrace graphs the Web interface can show and it seems that ther may be a memory leak. Originally when I asked about these problems on the ZFS list someone from Nextenta suggested that it very likely might be the 'ips' driver that's causing the problems. So Id like to investigate that too if I could, but it's nearly impossible if you can't release the code. > > Apart from lack of time, I don't have any hardware to test > it on, so I cannot work on getting it integrated into ON - all > drivers require testability within our test suite framework. > I understand it can't be integrated into ON, which was why I was hoping to get it in the 'contrib' repository (outside of ON). I'm also currently trying out the NextentaCore distribution, but what I'd like to do is use the Distribution Constructor to be able to pull 'ips' from the contrib repository and make my own install image. I'm pretty sure I can't (easily) get DC to put the SVR4 packages from the website into the image - so getting this into some PKG repository would also be a big help. > I will investigate the license on the code and see whether it > is possible to make it available. > I can relate to being busy, that's for sure. So I greatly appreciate any time you can find to put into this. Thanks so much! -Kyle > > James C. McPherson > -- > Senior Software Engineer, Solaris > Oracle > http://www.jmcp.homeunix.com/blog -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) iQEcBAEBAgAGBQJMNNGWAAoJEEADRM+bKN5wfcUIAJ3NyKDghnp90+GCTgrTkWfm sTOjiYw943fl2vjb5nT4u6y4p9yvJlM/R8xO0xatLAThIud2DQ1aTWCYx2uKldR/ EQK0ta+wFCD9Lz3sFzqDzCizdN2B/8Re+YK7PihXiJTkUJpzfKsoowPCZX0bdF+n Tn7nipmY0EFk9vWq9vuULmgACQ/eEZBF5ZsZXadMgQ5C0gyovaqynk2t0J99brgN 6BVqny1eTwwJMOWPK/l+eQr39JCyebvBnoLYiUfkDrjFdRkMPjAgGppkPYyeC/4e RvvfzJt7EabU6/hZCCSSnotJtjW/w06B/NW9DNSI36WlrE7+AmnVu+kGP8gqVGk= =yiNe -----END PGP SIGNATURE----- _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
