From: Eric Sandeen <sandeen@sandeen.net>
To: Ajeet Yadav <ajeet.yadav.77@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Testcase and guide to XFS log corruption issues.
Date: Fri, 12 Nov 2010 13:09:51 -0600 [thread overview]
Message-ID: <4CDD90FF.5070304@sandeen.net> (raw)
In-Reply-To: <AANLkTinsus+r4p6122hZwHupoQ7sXimGTpnwiTYmKVKC@mail.gmail.com>
On 11/10/2010 11:35 PM, Ajeet Yadav wrote:
> If there is already a procedure or tool to check these issues then I
> will be glad if you can share you knowledge with us.
Running xfstests would be a fine place to start.
There are tests in there which test log replay.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-11-12 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 5:35 Testcase and guide to XFS log corruption issues Ajeet Yadav
2010-11-12 19:09 ` Eric Sandeen [this message]
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=4CDD90FF.5070304@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ajeet.yadav.77@gmail.com \
--cc=xfs@oss.sgi.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.