On 20 Jun 2016, at 17:34, Allan Jude wrote:
> Looking at the backtrace, do you have one or more ZVOLs?
>
No, there are no zvols:
% zfs list -t volume
no datasets available
Regards,
Kristof
___
svn-src-head@freebsd.org mailing list
On 2016-06-20 11:31, Kristof Provost wrote:
> No, it’s an HP Microserver. 4 data disks and that’s it.
>
> Bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210409
>
> Regards,
> Kristof
>
> On 20 Jun 2016, at 17:27, Alan Somers wrote:
>
> You say it's a 4-disk RAIDZ1. Anything
No, it’s an HP Microserver. 4 data disks and that’s it.
Bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210409
Regards,
Kristof
On 20 Jun 2016, at 17:27, Alan Somers wrote:
You say it's a 4-disk RAIDZ1. Anything topologically weird, like a
log, cache or spare device? SAS or SATA?
You say it's a 4-disk RAIDZ1. Anything topologically weird, like a
log, cache or spare device? SAS or SATA? Any SAS expanders? Please
open a bug for this and assign to me so we can be sure to get this
fixed in time for 11.0.
-Alan
On Mon, Jun 20, 2016 at 8:59 AM, Kristof Provost
Hi,
It looks like this change breaks boot on my machine.
I’m running a root-on-ZFS system and reliably see this panic during
boot. It’s a 4 disk raidz-1.
It’s now running r302028 with r300881 backed out, and booting fine.
The panic:
panic: solaris assert: refcount(count(>spa_refcount) >=
Author: asomers
Date: Fri May 27 22:32:44 2016
New Revision: 300881
URL: https://svnweb.freebsd.org/changeset/base/300881
Log:
Avoid issuing spa config updates for physical path when not necessary
ZFS's configuration needs to be updated whenever the physical path for a
device changes,
