From: "Michael L. Semon" <mlsemon35@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: generic/258 questions (mount issue)...
Date: Wed, 22 May 2013 12:48:14 -0400 [thread overview]
Message-ID: <519CF6CE.8020901@gmail.com> (raw)
In-Reply-To: <519CEFFB.1080209@sandeen.net>
On 05/22/2013 12:19 PM, Eric Sandeen wrote:
> On 5/22/13 11:15 AM, Michael L. Semon wrote:
>> On 05/22/2013 10:10 AM, Eric Sandeen wrote:
>>> On 5/21/13 10:03 PM, Michael L. Semon wrote:
>> One day, I would like to earn git-log fame by incorporating better
>> support for JFS and especially NILFS2 into xfstests. However,
>> that's a topic for another day. I know that I have uses for both
>> filesystems, but that doesn't mean anybody else does. Their
>> mailing lists don't give much hint of user community or progress.
>
> The generic tests hopefully work; if not, it should be a fairly
> simple fixup. And you're free to add fs-specific tests :)
>
> (I'm not sure if we fall back by default to mkfs.$FSTYP and fsck.$FSTYP;
> if so, it might just work)
>
> -Eric
They work fine--JFS currently survives all of generic/* intact--but...
JFS: The syntax for a lot of things is very close to that of ReiserFS,
ext3, and ext4 filesystems. However, before just inserting "jfs" into
the common/rc case switches, test results need to be audited for JFS.
Additionally, I don't know if the current tests use external journals
for non-XFS filesystems: My first attempt stepped all over the XFS
journal creation script, looked messy, and was probably buggy as well.
NILFS2: fsstress/fsx seems to slowly rip NILFS2 to bits, and I have
to come up with a narrower test and report bugs to those guys.
common/rc could be revised to better target filesystems with no
fsck whatsoever, such as NILFS2 and F2FS. I've been getting by with
a simple `ln -s /bin/true /sbin/fsck.nilfs2`, and really, that is the
best long-term solution from an administrative standpoint.
So you see how this might be an easy fix but still take up hours in
debugging...
Thanks again!
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-22 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 0:43 generic/258 questions (mount issue) Michael L. Semon
2013-05-22 1:26 ` 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 [this message]
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=519CF6CE.8020901@gmail.com \
--to=mlsemon35@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox