I can reproduce the problem. I can crash the system.

Here are the steps I did (some steps may not be needed but I haven't tested

- Clean install of OI 151.a.7 on Supermicro hardware described above (32GB
RAM though, not the 128GB)

- Create 1 zpool, 6 raidz vdevs with 5 drives each

- NFS export a dataset
  zfs set sharenfs="rw=@10.20.1/24" vol01/htmlspace

- Create zfs child dataset
  zfs create vol01/htmlspace/A

  $ zfs get -H sharenfs vol01/htmlspace/A
  vol01/htmlspace/A       sharenfs        rw=@10.20.1/24  inherited from

- Stop NFS shearing for the child dataset

  zfs set sharenfs=off vol01/htmlspace/A

The crash is instant after the sharenfs=off command.

I thought it was coincident so after reboot I tried it on another dataset.
Instant crash again. I get my prompt back but that's it. The system is gone
after that.

The NFS exported file systems are not accessed by any system on the
network. They are not in use. That's why I wanted to stop exporting them.
And, even if they were in use this should now crash the system, right?

I can't try the other box because it is heavy in production. At least not
until later tonight.

I thought I'll collect some advice to make each crash as useful as possible.

Any pointers are appreciated.


-- Peter

On Wed, Mar 20, 2013 at 8:34 AM, Peter Wood <peterwood...@gmail.com> wrote:

> I have two identical Supermicro boxes with 32GB ram. Hardware details at
> the end of the message.
> They were running OI 151.a.5 for months. The zpool configuration was one
> storage zpool with 3 vdevs of 8 disks in RAIDZ2.
> The OI installation is absolutely clean. Just next-next-next until done.
> All I do is configure the network after install. I don't install or enable
> any other services.
> Then I added more disks and rebuild the systems with OI 151.a.7 and this
> time configured the zpool with 6 vdevs of 5 disks in RAIDZ.
> The systems started crashing really bad. They just disappear from the
> network, black and unresponsive console, no error lights but no activity
> indication either. The only way out is to power cycle the system.
> There is no pattern in the crashes. It may crash in 2 days in may crash in
> 2 hours.
> I upgraded the memory on both systems to 128GB at no avail. This is the
> max memory they can take.
> In summary all I did is upgrade to OI 151.a.7 and reconfigured zpool.
> Any idea what could be the problem.
> Thank you
> -- Peter
> Supermicro X9DRH-iF
> Xeon E5-2620 @ 2.0 GHz 6-Core
> LSI SAS9211-8i HBA
> 32x 3TB Hitachi HUS723030ALS640, SAS, 7.2K
zfs-discuss mailing list

Reply via email to