All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Andy Lutomirski <luto@amacapital.net>, Eric Sandeen <sandeen@redhat.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	xfs@oss.sgi.com, lsf@lists.linux-foundation.org,
	"Linux FS Devel" <linux-fsdevel@vger.kernel.org>,
	"Sedat Dilek" <sedat.dilek@gmail.com>,
	"Lukáš Czerner" <lczerner@redhat.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [Lsf] [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all
Date: Thu, 03 Apr 2014 15:46:24 -0600	[thread overview]
Message-ID: <533DD6B0.6010102@sandeen.net> (raw)
In-Reply-To: <CALCETrVq1DfpyhThajc9FYA7NLWYt9oX4vadCDcqn+d26aALGA@mail.gmail.com>

On 4/3/14, 1:21 PM, Andy Lutomirski wrote:
> On Thu, Apr 3, 2014 at 12:06 PM, Eric Sandeen <sandeen@redhat.com> wrote:

...

>>> The various test scripts do need to be able to find the device where
>>> the file system lives, and parsing /etc/fstab would be awkward.  So if
>>> your comment is that either the /etc/fstab entry shouldn't be
>>> required, or the xfstests runtime environment should be able to derive
>>> $SCRATCH_DEV automatically from $SCRATCH_MNT, or vice versa, instead
>>
>> I guess I don't know why you'd expect to derive one from the other...
> 
> Sigh.
> 
> If $SCRATCH_MNT is specified, then the line in /etc/fstab is
> unnecessary.  If $SCRATCH_MNT is not specified, then /etc/fstab will
> do the trick.
> 
> What does not work is specifying $SCRATCH_DIR [sic] but not adding an
> fstab entry.  Oops.

Oh, I see.

I'd never really thought about xfstests devices as "part of the system" -
since they're constantly scribbled on, re-made, etc, and managed wholly
by xfstests (at least the scratch device) - so the notion of using fstab
was just outside my realm of expected behaviors.  :)

-Eric

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

  reply	other threads:[~2014-04-03 21:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  9:03 [PATCH] xfstests-bld: Simplify determination of number of CPUs in build-all Sedat Dilek
2014-03-28 16:18 ` tytso
2014-03-29 10:04   ` Sedat Dilek
2014-03-29 14:04     ` Theodore Ts'o
2014-03-31  2:51   ` [Lsf] " Dave Chinner
2014-04-01  2:37     ` Theodore Ts'o
2014-04-01  2:37       ` Theodore Ts'o
2014-04-01 22:28       ` Dave Chinner
2014-04-01 22:28         ` Dave Chinner
2014-04-02 14:26         ` Theodore Ts'o
2014-04-03  1:14           ` Dave Chinner
2014-04-03  1:14             ` Dave Chinner
2014-04-03 10:26             ` Lukáš Czerner
2014-04-03 17:05               ` Andy Lutomirski
2014-04-03 17:35                 ` Theodore Ts'o
2014-04-03 17:35                   ` Theodore Ts'o
2014-04-03 17:42                   ` Andy Lutomirski
2014-04-03 17:42                     ` Andy Lutomirski
2014-04-03 19:06                   ` Eric Sandeen
2014-04-03 19:06                     ` Eric Sandeen
2014-04-03 19:21                     ` Andy Lutomirski
2014-04-03 19:21                       ` Andy Lutomirski
2014-04-03 21:46                       ` Eric Sandeen [this message]
2014-04-03 19:30                     ` Theodore Ts'o
2014-04-03 21:20                       ` Dave Chinner
2014-04-03 13:16           ` Mel Gorman

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=533DD6B0.6010102@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf@lists.linux-foundation.org \
    --cc=luto@amacapital.net \
    --cc=sandeen@redhat.com \
    --cc=sedat.dilek@gmail.com \
    --cc=tytso@mit.edu \
    --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.