On Mon, Oct 01, 2018 at 07:04:04AM +0000, Emmanuel Dreyfus wrote: > On Sun, Sep 30, 2018 at 11:13:11AM +0200, J. Hannken-Illjes wrote: > > This change is wrong, there is no upper time limit for a successfull > > file system suspension. > > Indeed, it can be infinite, as I experienced here: > http://mail-index.netbsd.org/tech-kern/2018/09/21/msg024099.html > > A umount, vndconfig or fssconfig failing with EAGAIN is indeed > bad,
It's actually quite bad if it happens at shutdown time. > but I doubt you will advocate that freezing the whole system > forever is better. at the very last, the timeout should be much longer (at last several seconds) before deciding if it would hang forever. > I have machines where the above described > scenario became 100% reproductible with the NetBSD 8.0 upgrade, > this is just a shame. Yes, it's a bug, probably related to vndconfig'ing a file on the same filesystem as /dev. I use vnconfig a lot myself and I've never seen it. -- Manuel Bouyer <bou...@antioche.eu.org> NetBSD: 26 ans d'experience feront toujours la difference --