From: Carlos Maiolino <cem@kernel.org>
To: Steve Shoecraft <spshoecraft@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [RFC] MXFS: a shared-disk clustered filesystem derived from XFS
Date: Wed, 30 Sep 2026 11:01:28 +0200 [thread overview]
Message-ID: <arzPGSQWTot6vmU0@cronus.toxiclabs.cc> (raw)
In-Reply-To: <1B01BE22-06A8-412D-B141-CD94026E0A39@gmail.com>
On Tue, Sep 29, 2026 at 09:19:39AM -0400, Steve Shoecraft wrote:
> I’m disappointed in your responses. I would have thought that you’d at least be interested in how well the AI did.
And I'm disappointed how you didn't get the point you should not demand
others to validate code you didn't bother reading yourself.
>
> It’s going to get better — not worse.
>
> Since the initial 2-node TCP/DLM release (0.89.77 on September 23), Fable and Astra have completed 2-node CAW (0.90.7 on September 26), and 4-node TCP and CAW (0.90.24) have now been released on:
> • Proxmox VE 9 (kernels 6.17 and 7.0)
> • RHEL / AlmaLinux / Rocky 9.8
> • Ubuntu 24.04 LTS (GA kernel 6.8)
> • Debian 13 (kernel 6.12)
>
> All are distributed as native DEB/RPM packages, with the kernel module built against the target kernel via DKMS.
>
> The 0.90.24 release passed the complete release criteria: 4-node TCP 31/31, 4-node CAW 30/30, 2-node TCP 31/31, and 2-node CAW 30/30. All four platforms passed their packaged installation and validation runs.
>
> The goal is full 32-node support for both TCP and CAW DLM.
>
>
>
> The next project is OSN — a fully AI-written OS from scratch.
>
>
> > On Sep 27, 2026, at 7:03 AM, Carlos Maiolino <cem@kernel.org> wrote:
> >
> > On Sat, Sep 26, 2026 at 07:32:27AM -0500, Steve Shoecraft wrote:
> >>
> >> Good catch on the magic - I had it changed in previous attempts and forgot on this one - release 0.90.0 has MXFS unique magic.
> >>
> >> I’ve been writing device drivers since the 90s on FreeBSD. This was a research project to see if an LLM could do it with the right harness.
> >>
> >> Release conditions of course included 100% data integrity and 100% stability. XFS was the right choice for the base.
> >>
> >> Intent is a good clustered FS for Proxmox to compete with vSphere and VMFS. Yes, I’m aware of the differences in implementations.
> >
> > If you are not even bothering reviewing your own project source code as
> > you stated, don't expect anybody else to spend their time or have
> > interest on it.
> >
> >
> >>
> >>
> >>> On Sep 26, 2026, at 1:07 AM, Christoph Hellwig <hch@infradead.org> wrote:
> >>>
> >>> I don't think too many people are going to care about your LLM dump,
> >>> or even review it. But please make sure you use different magic numbers
> >>> so that a mxfs image left in the wild is not mistaken for an xfs one.
>
>
next prev parent reply other threads:[~2026-09-30 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 21:25 [RFC] MXFS: a shared-disk clustered filesystem derived from XFS Steve Shoecraft
2026-09-26 6:07 ` Christoph Hellwig
2026-09-26 12:32 ` Steve Shoecraft
2026-09-27 11:03 ` Carlos Maiolino
2026-09-29 13:19 ` Steve Shoecraft
2026-09-29 15:00 ` Darrick J. Wong
2026-09-29 15:07 ` Steve Shoecraft
2026-09-29 22:34 ` Eric Sandeen
2026-09-30 9:01 ` Carlos Maiolino [this message]
2026-09-30 13:24 ` Emmanuel Florac
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=arzPGSQWTot6vmU0@cronus.toxiclabs.cc \
--to=cem@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=spshoecraft@gmail.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