From: Jia He <hejianet@gmail.com>
To: fstests@vger.kernel.org
Cc: eguan@redhat.com, Jia He <hejianet@gmail.com>
Subject: [PATCH V2 0/2] fstests: help user to troubleshoot the re-mount issue quickly
Date: Sat, 9 Jan 2016 11:54:51 +0800 [thread overview]
Message-ID: <1452311693-27529-1-git-send-email-hejianet@gmail.com> (raw)
When I tried to fix a mount issue of tests/xfs/003 failure, I found the
root cause is my mistake that I added "/" to the end of TEST_DIR, eg.
export TEST_DIR=/root/xfstests/test/
This patch set is to let user find the correct cause quickly.
V2: Instead of adding comments, remove all trailing "/"s by readlink.
This is suggested by Eryu Guan.
Jia He (2):
fstests: add user friendly prompts for already mounted point name
fstests: canonicalize the mount points by removing the trailing "/"
common/config | 5 +++++
common/rc | 8 ++++++--
2 files changed, 11 insertions(+), 2 deletions(-)
--
2.1.4
next reply other threads:[~2016-01-09 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 3:54 Jia He [this message]
2016-01-09 3:54 ` [PATCH V2 1/2] fstests: add user friendly prompts for already mounted points name Jia He
2016-01-09 3:54 ` [PATCH V2 2/2] fstests: canonicalize the mount points by removing the trailing "/" Jia He
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=1452311693-27529-1-git-send-email-hejianet@gmail.com \
--to=hejianet@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@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