From: Michael Arndt <Michael.Arndt@berlin.de>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: xfs remove / unlink extremely slow ?
Date: Thu, 15 Nov 2018 18:07:46 +0100 [thread overview]
Message-ID: <6102464C-F8C6-4BB0-AB98-FD11310BDF5E@berlin.de> (raw)
In-Reply-To: <20181115153815.GA27512@bfoster>
Brian,
Info, supporting your remark about VFS layer:
I did a reboot of cluster headnode and after that the remove was „fast“ meanig the typical millsecond /single file to seconds / removal of whole trees.
What does your intuition say, what could be suspected in the VFS layer / lvm2 layer or below to trigger this problem
( just to collect ideas, where to search). ?
Caused by the fact, that the problem was seen also two times before, the issue will reappear after some time.
Off topic: is the mount option delaylog still functional or obsoleted, because already default behaviour ?
best
Micha
thx for extremely friendly help
next prev parent reply other threads:[~2018-11-16 3:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3927644F-734A-4A2A-BACB-DE44CBC812EB@berlin.de>
2018-11-14 11:42 ` Fwd: xfs remove / unlink extremely slow ? Michael Arndt
2018-11-14 14:45 ` Brian Foster
2018-11-15 15:38 ` Brian Foster
2018-11-15 17:07 ` Michael Arndt
2018-11-15 17:07 ` Michael Arndt [this message]
2018-11-15 17:35 ` Brian Foster
2018-11-15 22:28 ` Fwd: " Dave Chinner
[not found] <c3cbf69c52f0e89631c796016449bbe3@berlin.de>
2018-04-24 8:28 ` xfs fstrim and quota michael.arndt
2018-04-24 11:35 ` Brian Foster
2018-11-14 10:51 ` xfs remove / unlink extremely slow ? Michael Arndt
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=6102464C-F8C6-4BB0-AB98-FD11310BDF5E@berlin.de \
--to=michael.arndt@berlin.de \
--cc=bfoster@redhat.com \
--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).