From: Joel Becker <jlbec@evilplan.org>
To: Richard Weinberger <richard@nod.at>
Cc: linux-fsdevel@vger.kernel.org, Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: [PATCH] Do not check ocfs2
Date: Mon, 4 Mar 2013 14:57:24 -0800 [thread overview]
Message-ID: <20130304225724.GB7783@localhost> (raw)
In-Reply-To: <20130304230922.20f6c05a@spider.haslach.nod.at>
On Mon, Mar 04, 2013 at 11:09:22PM +0100, Richard Weinberger wrote:
> Am Mon, 4 Mar 2013 13:05:23 -0800
> schrieb Joel Becker <jlbec@evilplan.org>:
> > > Really, xfstests is not designed for testing cluster filesystems in
> > > clustered environments. If we really want to support clustered
> > > filesystems and cluster wide operations, then we need to think
> > > about how to architect multi-host support into xfstests sanely.
> > > Clustered filesystems are not the only people that could make use of
> > > such functionality (NFS and CIFS come to mind).... ;)
> >
> > I'm much happier with the "check for other cluster mounts" approach
> > rather than avoiding fsck entirely. We like xfstests in the local or
> > single-node cases to behave exactly as one would expect.
> >
> > We do run xfstests on multiple nodes in a cluster, but by hand and
> > with our own cleanup. Obviously support for automating that would be
> > awesome :-)
>
> Can you share your cleanup code?
It's not code, unless you count DNA and neuron connections...
Joel
>
> Thanks,
> //richard
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Life's Little Instruction Book #139
"Never deprive someone of hope; it might be all they have."
http://www.jlbec.org/
jlbec@evilplan.org
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Joel Becker <jlbec@evilplan.org>
To: Richard Weinberger <richard@nod.at>
Cc: Dave Chinner <david@fromorbit.com>,
Eric Sandeen <sandeen@sandeen.net>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] Do not check ocfs2
Date: Mon, 4 Mar 2013 14:57:24 -0800 [thread overview]
Message-ID: <20130304225724.GB7783@localhost> (raw)
In-Reply-To: <20130304230922.20f6c05a@spider.haslach.nod.at>
On Mon, Mar 04, 2013 at 11:09:22PM +0100, Richard Weinberger wrote:
> Am Mon, 4 Mar 2013 13:05:23 -0800
> schrieb Joel Becker <jlbec@evilplan.org>:
> > > Really, xfstests is not designed for testing cluster filesystems in
> > > clustered environments. If we really want to support clustered
> > > filesystems and cluster wide operations, then we need to think
> > > about how to architect multi-host support into xfstests sanely.
> > > Clustered filesystems are not the only people that could make use of
> > > such functionality (NFS and CIFS come to mind).... ;)
> >
> > I'm much happier with the "check for other cluster mounts" approach
> > rather than avoiding fsck entirely. We like xfstests in the local or
> > single-node cases to behave exactly as one would expect.
> >
> > We do run xfstests on multiple nodes in a cluster, but by hand and
> > with our own cleanup. Obviously support for automating that would be
> > awesome :-)
>
> Can you share your cleanup code?
It's not code, unless you count DNA and neuron connections...
Joel
>
> Thanks,
> //richard
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Life's Little Instruction Book #139
"Never deprive someone of hope; it might be all they have."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2013-03-04 22:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 0:05 [PATCH] Do not check ocfs2 Richard Weinberger
2013-03-03 0:05 ` Richard Weinberger
2013-03-03 1:19 ` Dave Chinner
2013-03-03 1:19 ` Dave Chinner
2013-03-03 9:02 ` Richard Weinberger
2013-03-03 9:02 ` Richard Weinberger
2013-03-03 22:04 ` Eric Sandeen
2013-03-03 22:19 ` Richard Weinberger
2013-03-03 22:19 ` Richard Weinberger
2013-03-03 22:40 ` Eric Sandeen
2013-03-03 22:40 ` Eric Sandeen
2013-03-03 22:53 ` Richard Weinberger
2013-03-03 22:53 ` Richard Weinberger
2013-03-03 22:57 ` Eric Sandeen
2013-03-03 22:57 ` Eric Sandeen
2013-03-04 0:42 ` Dave Chinner
2013-03-04 0:42 ` Dave Chinner
2013-03-04 21:05 ` Joel Becker
2013-03-04 21:05 ` Joel Becker
2013-03-04 22:09 ` Richard Weinberger
2013-03-04 22:09 ` Richard Weinberger
2013-03-04 22:57 ` Joel Becker [this message]
2013-03-04 22:57 ` Joel Becker
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=20130304225724.GB7783@localhost \
--to=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=richard@nod.at \
--cc=sandeen@sandeen.net \
--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.