From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: [PATCH] xfstests: use blkid raw mode
Date: Sun, 14 Feb 2010 17:07:53 -0500 [thread overview]
Message-ID: <20100214220753.GB14927@infradead.org> (raw)
blkid without options usually gets no probe results at all just after
creating a filesystem. This problem is due to the cache that blkid
uses in it's default mode, and is unlikely to get fixed. Use the -p
option to bypass the cache layer.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfstests-dev/common
===================================================================
--- xfstests-dev.orig/common 2010-02-11 16:08:58.000000000 +0000
+++ xfstests-dev/common 2010-02-11 16:09:03.000000000 +0000
@@ -47,7 +47,7 @@ rm -f $tmp.list $tmp.tmp $tmp.sed
# Autodetect fs type based on what's on $TEST_DEV
if [ "$HOSTOS" == "Linux" ]
then
- export FSTYP=`blkid -s TYPE -o value $TEST_DEV`
+ export FSTYP=`blkid -p -s TYPE -o value $TEST_DEV`
else
export FSTYP=xfs
fi
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-02-14 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 22:07 Christoph Hellwig [this message]
2010-02-14 23:14 ` [PATCH] xfstests: use blkid raw mode 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=20100214220753.GB14927@infradead.org \
--to=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox