Date: Wed, 22 Nov 2017 21:17:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223786] Remounting a UFS filesystem read-only takes very long time Message-ID: <bug-223786-3630-bWHsTEz3Yz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223786-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-223786-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=3D223786 --- Comment #3 from Kirk McKusick <mckusick@FreeBSD.org> --- (In reply to Mikhail T. from comment #2) Being in the biowr state is expected as the filesystem needs to sync out all the changes. The question is why there are so many of them. Randomly guessi= ng, perhaps it decides that there are a large number of access times that need = to be written. When upgrading to read-write, include the -o noatime option so there is no attempt to update access times. It would also be useful to collect the number of I/O (particularly writes) = that the downgrade command is doing (time -l if your shell does not otherwise privide the I/O statistics). You can also get an idea of the I/Os being done using iostat. --=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-223786-3630-bWHsTEz3Yz>