[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160727132338.GA20032@thunk.org>
Date: Wed, 27 Jul 2016 09:23:38 -0400
From: Theodore Ts'o <tytso@....edu>
To: Luis de Bethencourt <luisbg@....samsung.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Al Viro <viro@...IV.linux.org.uk>,
Salah Triki <salah.triki@....org>,
Javier Martinez Canillas <javier@....samsung.com>,
Richard Weinberger <richard@....at>,
linux-fsdevel@...r.kernel.org
Subject: Re: Volunteering for BeFS maintainership
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
Powered by blists - more mailing lists