From: "Theodore Ts'o" <tytso@mit.edu>
To: lihaoxiang9@huawei.com
Cc: "Theodore Ts'o" <tytso@mit.edu>,
louhongxiang@huawei.com, linfeilong@huawei.com,
linux-ext4@vger.kernel.org, liuzhiqiang26@huawei.com
Subject: Re: [PATCH] debugfs:add logdump with option -n that display n records
Date: Sat, 13 Aug 2022 10:58:10 -0400 [thread overview]
Message-ID: <166040264335.3360334.9256977073226062013.b4-ty@mit.edu> (raw)
In-Reply-To: <608df030-593f-8c69-cb65-632a34729d23@huawei.com>
On Thu, 14 Jul 2022 09:32:48 +0800, lihaoxiang (F) wrote:
> The current version's debugfs possessed the function logdump. Executing
> with option -O could output the log history. But when it occurred the block
> which had no magic number in it's header, the program would exit.
>
> Sometimes we were locating problems, needed for more transactions that
> had replayed instead of the latest batch of transactions and we weren't
> hope to display all the history in the meanwhile. So we introduced
> the option -n used for controlling the print of history transactions.
> Specially, this parameter was depending on the option -O otherwise it
> couldn't work.
>
> [...]
Applied, thanks!
[1/1] debugfs:add logdump with option -n that display n records
commit: 6e4cc3d5eeb2dfaa055e652b5390beaa6c3d05da
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
next prev parent reply other threads:[~2022-08-13 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 1:32 [PATCH] debugfs:add logdump with option -n that display n records lihaoxiang (F)
2022-08-11 12:33 ` lihaoxiang (F)
2022-08-13 14:58 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-06 10:06 lihaoxiang (F)
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=166040264335.3360334.9256977073226062013.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=lihaoxiang9@huawei.com \
--cc=linfeilong@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=louhongxiang@huawei.com \
/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.