From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756293AbcG0NXt (ORCPT ); Wed, 27 Jul 2016 09:23:49 -0400 Received: from imap.thunk.org ([74.207.234.97]:48598 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756123AbcG0NXo (ORCPT ); Wed, 27 Jul 2016 09:23:44 -0400 Date: Wed, 27 Jul 2016 09:23:38 -0400 From: "Theodore Ts'o" To: Luis de Bethencourt Cc: Greg KH , Linux Kernel , Andrew Morton , Al Viro , Salah Triki , Javier Martinez Canillas , Richard Weinberger , linux-fsdevel@vger.kernel.org Subject: Re: Volunteering for BeFS maintainership Message-ID: <20160727132338.GA20032@thunk.org> Mail-Followup-To: Theodore Ts'o , Luis de Bethencourt , Greg KH , Linux Kernel , Andrew Morton , Al Viro , Salah Triki , Javier Martinez Canillas , Richard Weinberger , linux-fsdevel@vger.kernel.org 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57989EE0.9070003@osg.samsung.com> User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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