Hello Jaromir,
actually I did a forced fsck on the respective FS while it was unmounted
upfront. To be sure I just ran the command again - it passes with no
errors the second time. When I run dump -X again, the panic still occurs.
Best regards,
Matthias
nuc# fsck -P /dev/mapper/vg0-photo
On Wed, Nov 15, 2017 at 08:29:51PM +0100, Jaromír Dole?ek wrote:
> Hi,
>
> can you try if doing full forced fsck (fsck -f) would resolve this?
>
> I've seen several such persistent panics when I was debugging WAPBL. Even
> after kernel fixes I had persistent panics around ffs_newvnode() due to
>
Hi,
can you try if doing full forced fsck (fsck -f) would resolve this?
I've seen several such persistent panics when I was debugging WAPBL. Even
after kernel fixes I had persistent panics around ffs_newvnode() due to
disk data corruption from previous runs. This is worth trying.
Some day I
