All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael L. Semon" <mlsemon35@gmail.com>
To: xfs@oss.sgi.com
Subject: generic/258 questions (mount issue)...
Date: Tue, 21 May 2013 20:43:13 -0400	[thread overview]
Message-ID: <519C14A1.8000009@gmail.com> (raw)

Hi!  When using xfstests generic/258 with along with $TEST_RTDEV 
$TEST_LOGDEV, it tends to scream bloody murder about corrupted 
partitions and such.  In fact, the commands in the test seem to do the 
right thing when executed by hand.  So once again, I grasped for straws 
and came up with this:

--- xfstests/tests/generic/258.orig	2013-05-21 20:19:38.430754829 -0400
+++ xfstests/tests/generic/258	2013-05-21 20:10:11.509021368 -0400
@@ -62,7 +62,7 @@
  # unmount, remount, and check the timestamp
  echo "Remounting to flush cache"
  umount $TEST_DEV
-mount $TEST_DEV $TEST_DIR
+_test_mount

  # Should yield -315593940 (prior to epoch)
  echo "Testing for negative seconds since epoch"

My questions are these:

1) Was there a better way to do this?

2) Not knowing the policy on umounting $TEST_DEV, could this have been a 
test for $SCRATCH_DEV?

This was tested only on XFS with rtdev and logdev partitions enabled.

Thanks!

Michael

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-05-22  0:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  0:43 Michael L. Semon [this message]
2013-05-22  1:26 ` generic/258 questions (mount issue) Dave Chinner
2013-05-22  3:03   ` Michael L. Semon
2013-05-22 14:10     ` Eric Sandeen
2013-05-22 16:15       ` Michael L. Semon
2013-05-22 16:19         ` Eric Sandeen
2013-05-22 16:48           ` Michael L. Semon
2013-05-22 17:08             ` Eric Sandeen
2013-05-22 19:01     ` Rich Johnston
2013-05-22 22:58   ` Michael L. Semon
2013-05-23  2:27   ` [PATCH] xfstests: Change mount method for shared/243 Michael L. Semon

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=519C14A1.8000009@gmail.com \
    --to=mlsemon35@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.