From: Chanchal Mathew <chanch13@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS journal log resetting
Date: Fri, 10 Dec 2021 16:09:41 -0800 [thread overview]
Message-ID: <24D44CB5-F383-4F2A-B9C3-87770DFD7CDB@gmail.com> (raw)
In-Reply-To: <20211210213649.GQ449541@dread.disaster.area>
Thank you for the explanation!
Wouldn’t we expect zero pending modification or no unwritten data when a device is cleanly unmounted? Or do you mean, a successful ‘umount’ run on the device doesn’t guarantee there are no pending changes?
The devices I’m testing on are image files with same amount of data. One with lower log number is quicker to mount.
$ sudo xfs_logprint -t /dev/mapper/loop0p1
…
log tail: 451 head: 451 state: <CLEAN>
Whereas, the one with higher log number, such as the one below, is about 4-5 times slower running xlog_find_tail().
$ sudo xfs_logprint -t /dev/mapper/loop0p1
…
log tail: 17658 head: 17658 state: <CLEAN>
The images are of same size, and have same amount of data as well (as verified by df and df -i once mounted)
The only way I can work around this delay for an instance started from an image file with higher log number is, to reset it to 0 with xfs_repair.
Chanchal
next prev parent reply other threads:[~2021-12-11 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 18:27 XFS journal log resetting Chanchal Mathew
2021-12-10 21:36 ` Dave Chinner
2021-12-11 0:09 ` Chanchal Mathew [this message]
2021-12-11 5:55 ` Eric Sandeen
[not found] ` <F6A3B616-EF69-4AFF-BB12-17D6E53AC8D3@gmail.com>
2021-12-12 23:08 ` Dave Chinner
[not found] ` <5171B0E5-B782-4787-BE20-A432D090A9A4@gmail.com>
2021-12-20 20:54 ` Dave Chinner
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=24D44CB5-F383-4F2A-B9C3-87770DFD7CDB@gmail.com \
--to=chanch13@gmail.com \
--cc=david@fromorbit.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