On Sep 30, 2015 4:07 AM, "Nikola M" <[email protected]> wrote: > > On 09/30/15 10:37 AM, John McEntee wrote: >> >> Not quite sure who wants these, so I thought I would start here. >> >> >> >> I have a production Open Indiana box that mainly acts as a windows file server ( inbuilt kernel cifs server, joined to AD domain). We have an excel file that when opened, changed slightly, then saved would cause the openinidana server to kernel panic and reboot. I have about 16 dump files if anyone is interested. It looks to me like zfs is at fault. > > I use mega.nz for posting large files because I can count on both privacy of it as well as publicly sharing what I want. Also you can maybe thare same table filled with random data instead of actual one so more people could test. > > Latest OI /dev with some bugs resolved and updated illumos is: 151a9 (/dev). You can try update and running that and report a bug on that to Openindiana bug tracking > https://www.illumos.org/projects/openindiana/issues > > Latest OI with the rolling-release cycle and somewhat regular ISO release snapshots is Openindiana Hipster. (currently repo is at /hipster-2015) > > This is illumos cifs bug and should be reported to illumos. If one wants to report a bug for cifs server that comes with illumos, one should be able to reproduce bug with newest illumos and newest Hipster always comes with newest illumos. > > It is not suggested to run newest OI Hipster in production but there are also ISO snapshots one can use to install from and then update to test it with newest illumos. > > Since ZFS in illumos (OpenZFS) now (after 151a3) uses ZFS feature flags and moves away from latest Sun's ZFS version 28, (updates in /dev would work), to be able to dual-boot both older installation together with new one and any more recent OI Hipster lost ability to update form /dev, > I use a trick of installing OI Hipster from ISO inside VirtualBox (any machine with VBox would be fine) and then do zfs send/zfs receive of both Hipster dataset and installed user dir (make sure it's user that does not exist yet on physical machine) to physical machine's newly made Boot environment (whose zfs datastet has been emptied). > That way one can get both OI /dev and OI Hipster on same machine leaving unupdated ZFS version 28. > > So you can test how it behaves with newest illumos kernel with no need to recompile and install illumos yourself and you have minimal downtime, because ideally, it would need only one reboot to make new Boot environment with Hipster active and you can tinker with it's settings both before zfs send it to physical machine, inside VirtualBox or after, by changing directly configuration files before booting new BE. > I also suggest you can try test using samba 4 inside OI Hipster instead of cifs because of greater chance of it being maintained upstream. >
The CIFS server is actively developed and one of the fairly important components of illumos, as is ZFS. If the problem is reproducible on a recent build, a start would be to extract basic information from the crash dump following the instructions on the illumos wiki. That should narrow down what is causing the panic. -Albert ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
