Date: Tue, 22 Jun 2021 06:37:41 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyNTY3MTJdIFVGUzoga2VybmVsIHBhbmljOiBmZnNfYmxr?= =?UTF-8?B?ZnJlZV9jZzogZnJlZWluZyBmcmVlIGZyYWcg4oCTIGluIHJlc3BvbnNlIHRv?= =?UTF-8?B?IHBrZy1kZWxldGUoOCkgc29vbiBhZnRlciBsb2dpbg==?= Message-ID: <bug-256712-3630-rN4sltxrGW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256712 --- Comment #22 from Graham Perrin <grahamperrin@gmail.com> --- Earlier this month, I had a quite different test case with these criteria: a) soft updates disabled b) sync _not_ set in /etc/fstab Following interruption whilst installing a package, or packages, the base system was broken in that things such as /bin/sh and /sbin/fsck were unusable in single user mode (and so, no automated check). Whilst subsequent repairs yielded a file system that was marked clean, the base system remained essentially unusable. Please: should I open a separate bug for this? Or is breakage a (rare but explicable) possibility with the combination of those two criteria? ---- man 8 mount > … > noasync > Metadata I/O should be done synchronously, while data I/O > should be done asynchronously. This is the default. > … <https://docs.freebsd.org/en/books/handbook/config/#_more_details_about_soft_updates>; mentions "… no guarantee for a consistent state of the file system If there is a failure during an operation that updated large amounts of meta-data, …" * in the context of async * but not in the context of noasync -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256712-3630-rN4sltxrGW>