linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Salah Triki <salah.triki@acm.org>,
	Javier Martinez Canillas <javier@osg.samsung.com>,
	Richard Weinberger <richard@nod.at>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Volunteering for BeFS maintainership
Date: Wed, 27 Jul 2016 09:23:38 -0400	[thread overview]
Message-ID: <20160727132338.GA20032@thunk.org> (raw)
In-Reply-To: <57989EE0.9070003@osg.samsung.com>

On Wed, Jul 27, 2016 at 12:45:36PM +0100, Luis de Bethencourt wrote:
> Support for BeFS in Linux is read-only. So there are no tools to create
> BeFS file systems. I have a bunch of BeFS images created from Haiku OS
> that cover most things.

Ah, well, pretty much all of the xfstests assume the ability to write
into the file system.  So it may be a while before using xfstests will
make sense for BeFS.

> There is no reason a consistency check tool can't be written. I think this
> could be a fun exercise, I am tempted to add it to my task list :)
> However this tool can only inform if the file system is consistent, and not
> really fix it.  Similar to "e2fsck -n".

That's all which is necessary for xfstests --- the idea is that the
test will make various changes to the file system, and then
correctness is checked both by whether the expected output is printed
as the test probes changed the file system state, and by the
consistency checker confirming that the file system is in a consistent
sane state after each test completes.

> Salah told me he is planning to slowly work on adding read support in the
> future. But don't want to make any promises/plans on his behalf.

I assume you mean write support in the above paragraph.  :-)

Cheers,

						- Ted

  reply	other threads:[~2016-07-27 13:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 17:21 Volunteering for BeFS maintainership Luis de Bethencourt
2016-07-25 21:23 ` Greg KH
2016-07-25 23:16   ` Luis de Bethencourt
2016-07-26 17:56     ` Theodore Ts'o
2016-07-26 20:30       ` Luis de Bethencourt
2016-07-27  3:05         ` Theodore Ts'o
2016-07-27 11:45           ` Luis de Bethencourt
2016-07-27 13:23             ` Theodore Ts'o [this message]
2016-07-27 14:39               ` Luis de Bethencourt
2016-07-27  2:01       ` Salah Triki
2016-07-26 23:54   ` Salah Triki

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=20160727132338.GA20032@thunk.org \
    --to=tytso@mit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=javier@osg.samsung.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luisbg@osg.samsung.com \
    --cc=richard@nod.at \
    --cc=salah.triki@acm.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).