From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from ec2-52-27-115-49.us-west-2.compute.amazonaws.com ([52.27.115.49]:51714
	"EHLO s-opensource.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753954AbcG0Ojz (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 27 Jul 2016 10:39:55 -0400
Message-ID: <5798C7B4.8090607@osg.samsung.com>
Date: Wed, 27 Jul 2016 15:39:48 +0100
From: Luis de Bethencourt <luisbg@osg.samsung.com>
MIME-Version: 1.0
To: Theodore Ts'o <tytso@mit.edu>,
	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
References: <57964A8F.2010104@osg.samsung.com> <20160725212331.GB32464@kroah.com> <57969DC8.5090008@osg.samsung.com> <20160726175656.GC9284@thunk.org> <5797C855.8090005@osg.samsung.com> <20160727030551.GD9284@thunk.org> <57989EE0.9070003@osg.samsung.com> <20160727132338.GA20032@thunk.org>
In-Reply-To: <20160727132338.GA20032@thunk.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On 27/07/16 14:23, Theodore Ts'o wrote:
> 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.
> 

Right. It will still be valuable for me to run xfstests for ext4 and btrfs.

Thanks for the advice.

>> 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.  :-)
> 

You assume correctly :) Sorry for the typo.

> Cheers,
> 
> 						- Ted
> 

Thanks,
Luis