From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@kernel.org
Subject: [Bug 200835] XFS hangs in xfs_reclaim_inode()
Date: Fri, 17 Aug 2018 05:32:13 +0000 [thread overview]
Message-ID: <bug-200835-201763-kGEJGFnAIg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200835-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200835
--- Comment #3 from Peter Klotz (peter.klotz99@gmail.com) ---
Hello Dave
Thanks for the reply. I will upload a complete journald leading to one of the
crashes.
It seems the problem now occurs on a daily basis. The trigger is the deletion
of old backups.
I have a directory structure of this kind:
Backups
Machine1
Day1
Day2
...
Machine2
Day1
Day2
...
The files in the daily directories are hardlinked, so a minimum amount of space
is wasted. However subdirectories still consume inodes, so lots of them are in
use.
[root@hpmicroserver ~]# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/halvar 390701504 12805954 377895550 4% /mnt/halvar
/dev/mapper/faxe 2929890048 24276605 2905613443 1% /mnt/faxe
The only unusual thing I had to configure is "libata.force=noncq" since the
SATA controller had otherwise problems when talking to the SSD.
Any help (maybe a workaround) is appreciated.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-08-17 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 16:03 [Bug 200835] New: XFS hangs in xfs_reclaim_inode() bugzilla-daemon
2018-08-16 16:04 ` [Bug 200835] " bugzilla-daemon
2018-08-17 2:36 ` bugzilla-daemon
2018-08-17 5:32 ` bugzilla-daemon [this message]
2018-08-17 5:34 ` bugzilla-daemon
2018-08-17 8:43 ` bugzilla-daemon
2018-08-17 11:55 ` bugzilla-daemon
2018-08-17 13:06 ` bugzilla-daemon
2018-08-17 13:25 ` bugzilla-daemon
2018-08-17 14:04 ` bugzilla-daemon
2018-08-17 14:06 ` 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-200835-201763-kGEJGFnAIg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.