Date: Thu, 23 Oct 2025 11:29:18 -0700 From: Bakul Shah <bakul@iitbombay.org> To: Rick Macklem <rick.macklem@gmail.com> Cc: Peter 'PMc' Much <pmc@citylink.dinoex.sub.org>, freebsd-fs@freebsd.org Subject: Re: Why does rangelock_enqueue() hang for hours? Message-ID: <A087581B-7F88-4CC2-8B8B-0B70DC71C5EF@iitbombay.org> In-Reply-To: <CAM5tNy5od=uNAy4ysXSjXBgV1M38mAJvXqtOVuTeaS_JKZe_PQ@mail.gmail.com> References: <aPeEVSamcdKSoF5N@disp.intra.daemon.contact> <CAM5tNy6n5QJpRpkCJFHK=_5dWT=EZqkjztAfZHdqREKYSby55g@mail.gmail.com> <BC3B5D56-7DAD-4090-A25F-91640CFEE28D@iitbombay.org> <CAM5tNy5od=uNAy4ysXSjXBgV1M38mAJvXqtOVuTeaS_JKZe_PQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Oct 22, 2025, at 8:52 AM, Rick Macklem <rick.macklem@gmail.com> wrote: > > Peter, you could try the attached trivial patch (untested). > > I'm not sure if this is a reasonable thing to do, but at least you can report > back to let us know if it fixes your problem? One thing I had suggested was to use multiple copy_file_range() calls, say 4MB each in cp or cat as neither provide any atomic guarantees -- normally they would repeat read && write until done. At the very least this kicks the can down the road! This way reads would be blocked only when they catch up with writes.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A087581B-7F88-4CC2-8B8B-0B70DC71C5EF>