it is the same with mine on DilOS with non-DEBUG build.
-Igor
> On Sep 11, 2017, at 4:37 PM, Prakash Surya wrote:
>
> here's some info from a crash on a non-debug delphix/illumos system (i.e.
> with ASSERTs turned off):
> {noformat}
>
> ::status
> debugging crash dump vmcore.0 (64-bit) from p
here's some info from a crash on a non-debug delphix/illumos system (i.e. with
ASSERTs turned off):
{noformat}
> ::status
debugging crash dump vmcore.0 (64-bit) from ps-trunk.dcenter
operating system: 5.11 dlpx-trunk_2017-09-09-02-00-41dacd64be (i86pc)
image uuid: 2fb6a759-0230-e9bc-b411-bd8fa8a3e
I'm sorry, i forgot to report here that "_panic: allocating allocated segment_"
is the same bug happening on non-debug builds. I only have a debug build of
Illumos, but the troubleshooting was originally done to fix
https://github.com/zfsonlinux/zfs/issues/6315 which is a non-debug ZFSonLinux
b
I have a report from a FreeBSD user that 7578 caused a problem for him and that
the change in this PR fixes it.
His panic was different from what was reported here.
He got "zfs: allocating allocated segment" in this stack:
```
(kgdb) backtrace
#0 doadump (textdump=1) at pcpu.h:222
#1 0x8
more info with panic dump:
root@con1:/var/crash/myhost# cat 112.txt
MESSAGE
sd16 is /scsi_vhci/disk@g600144f07adeb118599164520004
/scsi_vhci/disk@g600144f07adeb118599164550005 (sd17) online
/scsi_vhci/disk@g600144f07adeb118000
Reproduced with iSCSI connected drives.
DilOS (based on illumos) Version 1.3.7.202 2017-09-11
root@con1:~# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
rpool 372G 170G 202G - 1% 45% 1.00x ONLINE -
tstpool2 97.5T 6.17M 97.5T - 0% 0% 1.00x ONLINE
perfect, thank you!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/462#issuecomment-328284378
--
openzfs-developer
Archives:
https://openzfs.to
> is it as simple as running the new zvol_misc_zil test case?
Good question. It should be: unfortunately i had to modify the first iteration
of the test case to use `dd` instead of `fio` because not every Linux distro
ships the same `fio` version, so there's not cli args consistency.
The origin
@loli10K in the ZOL PR you mentioned that you triggered the panic for this on
illumos; can you describe how you did that? is it as simple as running the new
`zvol_misc_zil` test case?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
