bsd.upgrade fails and shows following messages with a single partition disk.
```
Force checking of clean non-root filesystems? [no] no
umount: /mnt: Device busy
Can't umount sd0a!
```
sd0 has following partitions.
```
#size offset fstype [fsize bsize cpg]
a:
Doesn't this suggest a disk driver failed to perform/complete a write?
Not right at that moment but perhaps in the recent past?
Yuichiro NAITO wrote:
> bsd.upgrade fails and shows following messages with a single partition disk.
>
> ```
> Force checking of clean non-root filesystems? [no] no
>
Thanks for the comment.
I will see it further more.
On 11/8/21 12:45, Theo de Raadt wrote:
Doesn't this suggest a disk driver failed to perform/complete a write?
Not right at that moment but perhaps in the recent past?
Yuichiro NAITO wrote:
bsd.upgrade fails and shows following messages with
I tried to call 'db_enter' instead of 'panic' in 'vflush_vnode' function
as follows.
```
--- a/sys/kern/vfs_subr.c
+++ b/sys/kern/vfs_subr.c
@@ -966,6 +966,7 @@ vflush_vnode(struct vnode *vp, void *arg)
vprint("vflush: busy vnode", vp);
#endif
va->busy++;
+ db_ente
Yuichiro NAITO wrote:
> I don't have better idea than executing dd in foreground.
> How should we fix this?
You have provided really good information. Something is pretty
fundamentally broken, and we'll need to look into it. The dd
should die because it's filesystem is being taken away.
Yuichiro NAITO wrote:
> bsd.upgrade fails and shows following messages with a single partition disk.
>
> ```
> Force checking of clean non-root filesystems? [no] no
> umount: /mnt: Device busy
> Can't umount sd0a!
OK, we figured out what is going on. During upgrade, the async random
seed feedi
This reads correct.
OK florian
On 2021-12-02 00:01 -07, "Theo de Raadt" wrote:
> Yuichiro NAITO wrote:
>
>> bsd.upgrade fails and shows following messages with a single partition disk.
>>
>> ```
>> Force checking of clean non-root filesystems? [no] no
>> umount: /mnt: Device busy
>> Can't umou
