Re: Various problems with 13.0 amd64 on vultr.com

From: Gautam Mani <list_at_execve.net>
Date: Fri, 28 May 2021 13:18:25 UTC
Hi,

On Thu, May 27, 2021 at 12:45 PM Mark Delany <x9k@charlie.emu.st> wrote:

> On 27May21, Nicolas Embriz allegedly wrote:
> >
> > Just in case you can reboot using:
> >
> >       shutdown -o -n -r now
> >
> > Not ideal but works for now as a workaround.
>
> Nicolas, what a great suggestion. This works perfectly on my vultr
> instance. Thanks.
>
>
I can confirm that I also see this issue on Vultr in a single-CPU ZFS based
system. On checking shutdown(8)


     -n      If the -o option is specified, prevent the file system cache
from
             being flushed by passing -n to halt(8) or reboot(8).  This
option
             should probably not be used.

So using -n could possibly result in filesystem corruption ?

I also found: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253175
and also possibly related to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254513 which relates to
virtio_random.

Thanks,
Gautam