Date: Sat, 29 May 2021 10:37:04 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 238565] panic: vinvalbuf: dirty bufs during unmount if clustered writes return errors Message-ID: <bug-238565-3630-UTCBsuQTxO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238565-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-238565-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238565 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #5 from Konstantin Belousov <kib@FreeBSD.org> --- I do not understand the complain. We do panic if there are dirty buffers discovered on a vnode at vflush() ti= me. It does not matter how the dirty buffer (AKA delayed-write buffer) was crea= ted, by bdwrite() or by cluster_write(). Right now we panic on assumption that the presence of the dirty buffers that we unable to write, either compromises filesystem metadata integrity, or causes user data corruption. We might consider adding a knob to (not very silently) ignore and destroy such buffers on vflush(). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238565-3630-UTCBsuQTxO>