From: Anders Blomdell <anders.blomdell@gmail.com>
To: linux-xfs@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: XFS mount timeout in linux-6.9.11
Date: Fri, 9 Aug 2024 19:08:41 +0200 [thread overview]
Message-ID: <71864473-f0f7-41c3-95f2-c78f6edcfab9@gmail.com> (raw)
With a filesystem that contains a very large amount of hardlinks
the time to mount the filesystem skyrockets to around 15 minutes
on 6.9.11-200.fc40.x86_64 as compared to around 1 second on
6.8.10-300.fc40.x86_64, this of course makes booting drop
into emergency mode if the filesystem is in /etc/fstab. A git bisect
nails the offending commit as 14dd46cf31f4aaffcf26b00de9af39d01ec8d547.
The filesystem is a collection of daily snapshots of a live filesystem
collected over a number of years, organized as a storage of unique files,
that are reflinked to inodes that contain the actual {owner,group,permission,
mtime}, and these inodes are hardlinked into the daily snapshot trees.
The numbers for the filesystem are:
Total file size: 3.6e+12 bytes
Unique files: 12.4e+06
Reflink inodes: 18.6e+06
Hardlinks: 15.7e+09
Timing between the systems are:
6.8.10-300.fc40.x86_64:
# time mount /dev/vg1/test /test
real 0m0.835s
user 0m0.002s
sys 0m0.014s
6.9.11-200.fc40.x86_64:
# time mount /dev/vg1/test /test
real 15m36.508s
user 0m0.000s
sys 0m27.628s
(iotop reports 1-4 MB/s)
next reply other threads:[~2024-08-09 17:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 17:08 Anders Blomdell [this message]
2024-08-09 22:55 ` Dave Chinner
2024-08-10 8:29 ` Anders Blomdell
2024-08-10 23:11 ` Dave Chinner
2024-08-11 8:17 ` Anders Blomdell
2024-08-12 0:04 ` Dave Chinner
[not found] ` <6a19bfdf-9503-4c3b-bc5b-192685ec1bdd@gmail.com>
2024-08-13 9:19 ` Dave Chinner
2024-08-13 12:01 ` Anders Blomdell
2024-08-13 14:59 ` Christoph Hellwig
2024-08-13 15:25 ` Darrick J. Wong
2024-08-22 10:25 ` Anders Blomdell
2024-08-22 15:46 ` Darrick J. Wong
2024-09-04 7:45 ` David Woodhouse
2024-09-08 14:18 ` Greg KH
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=71864473-f0f7-41c3-95f2-c78f6edcfab9@gmail.com \
--to=anders.blomdell@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®