linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 216329] New: kernel crash and hung up while umounting
Date: Fri, 05 Aug 2022 06:34:24 +0000	[thread overview]
Message-ID: <bug-216329-201763@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216329

            Bug ID: 216329
           Summary: kernel crash and hung up while umounting
           Product: File System
           Version: 2.5
    Kernel Version: 5.3.0-45-generic
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: hyz0906@qq.com
        Regression: No

OS: Ubuntu 18.04.1
Using XFS with Ceph rdb and mount by OverlayFS, sometimes system hung up with
kernel crash below:

2022-07-27 16:17
Jul 27 15:21:43 k8s-node-b01-17-05 kernel: [25666453.856553] VFS: Busy inodes
after unmount of overlay. Self-destruct in 5 seconds.  Have a nice day...
Jul 27 15:22:01 k8s-node-b01-17-05 kernel: [25666471.122435] XFS (rbd59):
Unmounting Filesystem
Jul 27 15:22:25 k8s-node-b01-17-05 kernel: [25666495.392431] BUG: Dentry
00000000d683c981{i=38c31f07,n=README_zh.md}  still in use (1) [unmount of xfs
rbd23]"

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-08-05  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  6:34 bugzilla-daemon [this message]
2022-08-05 12:36 ` [Bug 216329] kernel crash and hung up while umounting bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-216329-201763@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).