In one of my VMs, I do a bunch of testing to a nano image on /dev/md0
and increasingly I am getting a panic on umounting the file system
The image is just
truncate -s 5G /tmp/junk.bin
mdconfig -f /tmp/junk.bin
and then I dd my nano image, mount it, make some configuration changes
and then umo
On Fri, Oct 22, 2021 at 10:36:01AM -0400, mike tancsa wrote:
> In one of my VMs, I do a bunch of testing to a nano image on /dev/md0
> and increasingly I am getting a panic on umounting the file system
>
> The image is just
>
> truncate -s 5G /tmp/junk.bin
> mdconfig -f /tmp/junk.bin
>
> and th
On 10/22/2021 11:21 AM, Mark Johnston wrote:
On Fri, Oct 22, 2021 at 10:36:01AM -0400, mike tancsa wrote:
After cycles of this, unmounts, mounts etc, I get
panic: ufs_dirbad: /mnt: bad dir ino 50626 at offset 0: mangled entry
cpuid = 1
time = 1634912598
KDB: stack backtrace:
#0 0x80c77
On Fri, Oct 22, 2021 at 11:33:22AM -0400, mike tancsa wrote:
> On 10/22/2021 11:21 AM, Mark Johnston wrote:
> > On Fri, Oct 22, 2021 at 10:36:01AM -0400, mike tancsa wrote:
> >> After cycles of this, unmounts, mounts etc, I get
> >>
> >>
> >> panic: ufs_dirbad: /mnt: bad dir ino 50626 at offset 0:
Friends,
thanks to the good vibrations, this is going easier than I thought.
The problem is already well known, and is actually intended behaviour
(while probably not "works as designed").
The BPF didn't work with these circumstances either, but that one was
fixed:
https://reviews.freebsd.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The first BETA build of the 12.3-RELEASE release cycle is now available.
Installation images are available for:
o 12.3-BETA1 amd64 GENERIC
o 12.3-BETA1 i386 GENERIC
o 12.3-BETA1 powerpc GENERIC
o 12.3-BETA1 powerpc64 GENERIC64
o 12.3-BETA1 powerpcs
