On 2011-May-02 16:32:30 +0200, Olaf Seibert o.seib...@cs.ru.nl wrote:
However, it doesn't automatically reboot in 15 seconds, as promised.
It just sits there the whole weekend, until I log onto the IPMI console
and press the virtual reset button.
Your reference to IMPI indicates this is not a
On Mon, May 02, 2011 at 04:32:30PM +0200, Olaf Seibert wrote:
I have a FreeBSD/amd64 8.2 server that has a few ZFS file systems served
over NFS. It has 8 GB of memory. There are 6 disks of 1,5 TB each
forming a pool with raidz2.
From time to time it crashes with some stack backtrace
On Tue 03 May 2011 at 17:21:52 +1000, Peter Jeremy wrote:
On 2011-May-02 16:32:30 +0200, Olaf Seibert o.seib...@cs.ru.nl wrote:
However, it doesn't automatically reboot in 15 seconds, as promised.
It just sits there the whole weekend, until I log onto the IPMI console
and press the virtual
On Tue 03 May 2011 at 02:21:13 -0700, Jeremy Chadwick wrote:
There are two things you might try fiddling with. These are sysctls so
you can try them on the fly:
hw.acpi.disable_on_reboot
hw.acpi.handle_reboot
Thanks. For now I've set the second to 1 and we'll see if that affects
matters.
On Tue, May 03, 2011 at 12:08:54PM +0200, Olaf Seibert wrote:
On Tue 03 May 2011 at 02:21:13 -0700, Jeremy Chadwick wrote:
There are two things you might try fiddling with. These are sysctls so
you can try them on the fly:
hw.acpi.disable_on_reboot
hw.acpi.handle_reboot
Thanks. For
On Tue 03 May 2011 at 05:20:52 -0700, Jeremy Chadwick wrote:
To be on the safe side, pick something that's small at first, then work
your way up. You'll need probably 1+ weeks of heavy ZFS I/O between
tests (e.g. don't change the tunable, reboot, then 4 hours later declare
the new (larger)
On Tue, May 03, 2011 at 02:30:15PM +0200, Olaf Seibert wrote:
On Tue 03 May 2011 at 05:20:52 -0700, Jeremy Chadwick wrote:
To be on the safe side, pick something that's small at first, then work
your way up. You'll need probably 1+ weeks of heavy ZFS I/O between
tests (e.g. don't change
Hi,
I have a FreeBSD/amd64 8.2 server that has a few ZFS file systems served
over NFS. It has 8 GB of memory. There are 6 disks of 1,5 TB each
forming a pool with raidz2.
From time to time it crashes with some stack backtrace (included below).
This already happened before the upgrade to 8.2.
