From owner-freebsd-fs@freebsd.org  Wed Nov 22 18:01:52 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 34572DF158A
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 22 Nov 2017 18:01:52 +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 22B473E68
 for <freebsd-fs@FreeBSD.org>; Wed, 22 Nov 2017 18:01:52 +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 vAMI1pBZ074132
 for <freebsd-fs@FreeBSD.org>; Wed, 22 Nov 2017 18:01:52 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 18:01:51 +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: cc
Message-ID: <bug-223786-3630-MuqJPhXsRK@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 18:01:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223786

Kirk McKusick <mckusick@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mckusick@FreeBSD.org

--- Comment #1 from Kirk McKusick <mckusick@FreeBSD.org> ---
This report is perhaps the third or fourth about the slow sync problem.
Unfortunately we have not been able to reproduce the slowdown.

We believe it started with r230553.  Note that I carefully use the word
'started' and not 'caused', because I believe that the change in r230553 is
required to avoid loss of user data.  But it is not clear what makes the sy=
nc
run for such a long time.

No users who reported the slowdown have provided a useful insight into their
configuration. What we need is a description of your filesystem. Ideal woul=
d be
a dump image that when restored demonstrates the problem.

--=20
You are receiving this mail because:
You are the assignee for the bug.=