https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082009-10-07T02:28:17ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1561: panic: assertion: vp->v_rdev != NULL in devfs_spec_strategyhttps://bugs.dragonflybsd.org/issues/1561?journal_id=75872009-10-07T02:28:17Zalexh
<ul></ul><p>vmcore.4.gz at least isn't readable (missing permissions).</p>
<p>Cheers,<br />Alex Hornung</p> DragonFlyBSD - Bug #1561: panic: assertion: vp->v_rdev != NULL in devfs_spec_strategyhttps://bugs.dragonflybsd.org/issues/1561?journal_id=75902009-10-08T02:24:23Zthomas.nikolajsen
<ul></ul><p>Permissions fixed.</p> DragonFlyBSD - Bug #1561: panic: assertion: vp->v_rdev != NULL in devfs_spec_strategyhttps://bugs.dragonflybsd.org/issues/1561?journal_id=87492010-08-07T00:55:39Ztuxillo
<ul></ul><p>Was this ever checked? If it was and there was any relevant information, please<br />udpate the ticket.</p>
<p>Cheers,<br />Antonio Huete</p> DragonFlyBSD - Bug #1561: panic: assertion: vp->v_rdev != NULL in devfs_spec_strategyhttps://bugs.dragonflybsd.org/issues/1561?journal_id=92912010-11-19T16:00:35Zalexh
<ul></ul><p>I finally had some time to look into this. It seems you were using 'vn' disks. <br />The actual issue arises when a device is ripped out from under devfs while it's <br />still in use (mounted or for that matter open in any other way).</p>
<p>vn has a large number of issues I'm currently working on, and hope to commit it <br />relatively soon.</p>
<p>Regards,<br />Alex Hornung</p> DragonFlyBSD - Bug #1561: panic: assertion: vp->v_rdev != NULL in devfs_spec_strategyhttps://bugs.dragonflybsd.org/issues/1561?journal_id=92932010-11-19T23:43:42Zalexh
<ul></ul><p>this should be fixed in 1398353708029eb9dda9861e12c2efb4e66e8122</p>