Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <C96ZW60NLAQF.1JF09JLHKR51M@taiga> <YCX+Em/EUJJte3x1@mit.edu> <C97L5DF7C3QF.H25PQ5ERKEPL@taiga>
In-Reply-To: <C97L5DF7C3QF.H25PQ5ERKEPL@taiga>
From:   harshad shirwadkar <harshadshirwadkar@gmail.com>
Date:   Fri, 12 Feb 2021 08:11:02 -0800
Message-ID: <CAD+ocbxUz1kA_7F3f_xXS6_eVt1c0NeMoMXsBQ7z2LbmrMjgMg@mail.gmail.com>
Subject: Re: j_recover_fast_commit: : failed on musl-riscv64
To:     Drew DeVault <sir@cmpwn.com>
Cc:     "Theodore Ts'o" <tytso@mit.edu>,
        Ext4 Developers List <linux-ext4@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Drew,

I'd be happy to take a look at this and if you could provide shell
access, that would be great. From the logs you shared above, it looks
like e2fsck is crashing resulting in fast commit recovery being
aborted.

Thanks,
Harshad

On Fri, Feb 12, 2021 at 5:30 AM Drew DeVault <sir@cmpwn.com> wrote:
>
> On Thu Feb 11, 2021 at 11:03 PM EST, Theodore Ts'o wrote:
> > Can you try using glibc on RiscV and see if it passes with glibc?
>
> Hm, I don't have a glibc+RISC-V setup readily available for testing, nor
> could I obtain one easily. But I would be open to offering shell access
> in my musl environment for troubleshooting purposes - would you (or
> any other maintainers) find that helpful?