Date: Sun, 26 Aug 2018 18:03:19 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 223786] Remounting a UFS filesystem read-only takes very long time Message-ID: <bug-223786-3630-cRDHVJFLAX@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 Mikhail Teterin <mi@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mi@FreeBSD.org --- Comment #6 from Mikhail Teterin <mi@FreeBSD.org> --- Seeing this manifested pretty bad today - on a freshly-rebuilt world (r338291M). The other thing that changed is the RAM upgrade -- from 10GB to 40GB. Could it be, the kernel is trying to flush ALL filesystems, rather than just the one being remounted? Because, unlike the / on UFS, other filesystems co= uld be quite busy... While waiting, I press Ctrl-T once in a while, and get: root@narawntapu:/etc/mail (1022) mount -oro -u / load: 0.93 cmd: mount 26321 [biowr] 230.01r 0.00u 9.01s 2% 2224k load: 0.47 cmd: mount 26321 [biowr] 283.84r 0.00u 10.99s 1% 2224k load: 0.57 cmd: mount 26321 [biowr] 318.95r 0.00u 12.25s 2% 2224k The actual change to the /-filesystem is trivial. --=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-cRDHVJFLAX>