Re: ufs_dirbad: /mnt: bad dir ino 50626 at offset 0: mangled entry

2021-10-22 Thread Mark Johnston
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:

Re: ufs_dirbad: /mnt: bad dir ino 50626 at offset 0: mangled entry

2021-10-22 Thread mike tancsa
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

Re: ufs_dirbad: /mnt: bad dir ino 50626 at offset 0: mangled entry

2021-10-22 Thread Mark Johnston
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