Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 05 Feb 2020 04:13:41 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 243890] md may hang in mddestroy
Message-ID:  <bug-243890-227@https.bugs.freebsd.org/bugzilla/>

index | next in thread | raw e-mail

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

            Bug ID: 243890
           Summary: md may hang in mddestroy
           Product: Base System
           Version: 11.3-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: mi@FreeBSD.org

If an md you're trying to unconfigure is part of a ccd, the attempt will hang
in an uninterruptible syscall mddestroy until all of the ccds involving the md
are unconfigured:

load: 2.10  cmd: mdconfig 54293 [mddestroy] 6.10r 0.00u 0.00s 0% 2384k
load: 1.84  cmd: mdconfig 54293 [mddestroy] 43.38r 0.00u 0.00s 0% 2384k
load: 1.66  cmd: mdconfig 54293 [mddestroy] 184.61r 0.00u 0.00s 0% 2384k

Worse, while this is happening, any attempt to use mdconfig (even to just list
the configured mds) will crash (segmentation fault).

The good news is, once the ccds are all destroyed, the hanging mdconfig will
exit nicely.

But it, probably, should fail immediately with an EBUSY or equivalent...

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

help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243890-227>