Date: Mon, 17 Oct 2016 09:37:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Message-ID: <bug-213507-3630-RY5ptIVylB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-213507-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-213507-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=3D213507 --- Comment #8 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Vladislav Movchan from comment #7) I probably was not clear enough. The problem is that a previous operation left the pages on the vnode page q= ueue behind the directory denode end. The damage is not limited to the situatio= n of extending the directory, it might have other consequences with varying severity. E.g., if the issue also happens for regular files, then extending file might result in the garbage or some previously removed unrelated disk = file content to appear in the extended portion, readable by user. That said, your patch seems to only paper over the real problem. Right thi= ng to do is to track the location where the damage happens. E.g., UFS also had similar problems, where failed file extension (e.g., for lack of free space) was followed by an incomplete cleanup and dandling buffers and pages. --=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-213507-3630-RY5ptIVylB>