From: Jeff King <peff@peff.net>
To: Dmitriy Panteleyev <dpantel@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] commit fails with 'bus error' when working directory is on an NFS share
Date: Sat, 30 Nov 2024 11:38:01 -0500 [thread overview]
Message-ID: <20241130163801.GA110697@coredump.intra.peff.net> (raw)
In-Reply-To: <CAJ-DG_DpNVmn1e=8hBX4YbEhzgX4xxn7AVBQnhKJOvHX4hx7kA@mail.gmail.com>
On Fri, Nov 29, 2024 at 09:58:51PM -0700, Dmitriy Panteleyev wrote:
> I've recently upgraded my (Linux Mint) distribution version, which
> came with git v2.43.0 and I noticed that I can no longer `commit` on
> any working directory which resides on an NFS share mount.
>
> Git reports "Bus error (core dumped)" and dmesg shows multiple "NFS:
> server error: fileid changed. fsid 0:68: expected fileid
> 0xf8e3d8e80230ddb5, got 0xeeb48230d99ed0d4" messages.
>
> This does not happen if I move the working directory off the NFS share.
I can't reproduce any problems here on a test NFS mount. But since the
old version works here:
> I attempted to upgrade git to v2.47.1, with the same result.
>
> I then downgraded git to v2.34.1 (the version for the previous
> distribution release) and the error has resolved.
Can you try bisecting between v2.34.1 and v2.43.0 to see which commit
introduces the problem for you?
-Peff
next prev parent reply other threads:[~2024-11-30 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 4:58 [BUG] commit fails with 'bus error' when working directory is on an NFS share Dmitriy Panteleyev
2024-11-30 16:38 ` Jeff King [this message]
2024-12-01 17:17 ` Dmitriy Panteleyev
2024-12-01 21:36 ` Jeff King
2024-12-01 22:24 ` Dmitriy Panteleyev
2024-12-02 20:34 ` Jeff King
2024-12-03 2:48 ` Dmitriy Panteleyev
2024-12-03 21:18 ` Jeff King
2024-12-05 2:21 ` Dmitriy Panteleyev
2024-12-05 3:22 ` Jeff King
2024-12-05 3:59 ` Dmitriy Panteleyev
2024-12-05 4:58 ` Dmitriy Panteleyev
2024-12-05 19:13 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2025-05-18 22:56 Evaldas Svidras
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=20241130163801.GA110697@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=dpantel@gmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).