From owner-freebsd-fs@freebsd.org  Wed Nov 22 21:17:47 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 601D6DF5F7C
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 22 Nov 2017 21:17:47 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4E9C66A6BD
 for <freebsd-fs@FreeBSD.org>; Wed, 22 Nov 2017 21:17:47 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAMLHlkN055907
 for <freebsd-fs@FreeBSD.org>; Wed, 22 Nov 2017 21:17:47 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 223786] Remounting a UFS filesystem read-only takes very long
 time
Date: Wed, 22 Nov 2017 21:17:47 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.4-STABLE
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mckusick@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2017 21:17:47 -0000

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.=