Re: Possible bug in zfs send or pipe implementation?

On Mon, Jul 15, 2024 at 9:50 AM Mark Johnston wrote: > On Sun, Jul 14, 2024 at 03:14:44PM -0700, Rick Macklem wrote: > > On Sun, Jul 14, 2024 at 10:32 AM Garrett Wollman > > > wrote: > > > > > < rick.mack...@gmail.com> > > > said: > > > > > > > Just to clarify it, are you saying zfs is sleeping

Re: Change to FreeBSD release scheduling etc.

On 7/15/24 15:59, Warner Losh wrote: On Mon, Jul 15, 2024 at 4:20 PM Colin Percival > wrote: On 7/15/24 15:05, Warner Losh wrote: > Ideally, we'd keep the same KBI per major release, but that ideal has fallen > short. Having a stable KBI only s

Re: Change to FreeBSD release scheduling etc.

On Mon, Jul 15, 2024 at 4:20 PM Colin Percival wrote: > On 7/15/24 15:05, Warner Losh wrote: > > On Mon, Jul 15, 2024 at 3:57 PM Colin Percival > > wrote: > > Flavouring kernel module ports for each minor release -- possibly > building in > > in an oldest-sup

Re: Change to FreeBSD release scheduling etc.

On 7/15/24 15:05, Warner Losh wrote: On Mon, Jul 15, 2024 at 3:57 PM Colin Percival > wrote: Flavouring kernel module ports for each minor release -- possibly building in in an oldest-supported-release jail but with the relevant /usr/src/sys tree -- migh

Re: Change to FreeBSD release scheduling etc.

On Mon, Jul 15, 2024 at 3:57 PM Colin Percival wrote: > On 7/15/24 14:33, Tomoaki AOKI wrote: > > On Mon, 15 Jul 2024 11:58:16 -0700 > > Colin Percival wrote: > >> Extending the minor-release support period might be possible, but that > >> would depend on portmgr and secteam and I can't speak fo

Re: Change to FreeBSD release scheduling etc.

On 7/15/24 14:33, Tomoaki AOKI wrote: On Mon, 15 Jul 2024 11:58:16 -0700 Colin Percival wrote: Extending the minor-release support period might be possible, but that would depend on portmgr and secteam and I can't speak for them. One issue which would certainly come up is kernel module package

Re: Change to FreeBSD release scheduling etc.

On Mon, 15 Jul 2024 11:58:16 -0700 Colin Percival wrote: > On 7/14/24 05:18, Peter wrote: > > In short, it takes me about 3 months to catch the surprizes[*] and fix > > (or find out how to cope with) the concerning issues, regressions et > > al. that come along with a new release. Up to now that

Re: FreeBSD Errata Notice FreeBSD-EN-23:21.tty

What exactly does the "Announced: 2023-11-24" date refer to? It isn't the date that the patch got applied to the main or stable branch, nor the date that the email alert was sent out, nor the date that anything changed in Bugzilla. On Tue, Dec 5, 2023 at 3:23 PM FreeBSD Errata Notices wrote: > >

Re: Change to FreeBSD release scheduling etc.

On 7/14/24 05:18, Peter wrote: In short, it takes me about 3 months to catch the surprizes[*] and fix (or find out how to cope with) the concerning issues, regressions et al. that come along with a new release. Up to now that would then give another 9 months during which the systems can be operat

Re: Possible bug in zfs send or pipe implementation?

On Sun, Jul 14, 2024 at 03:14:44PM -0700, Rick Macklem wrote: > On Sun, Jul 14, 2024 at 10:32 AM Garrett Wollman > wrote: > > > < > > said: > > > > > Just to clarify it, are you saying zfs is sleeping on "pipewr"? > > > (There is also a msleep() for "pipbww" in pipe_write().) > > > > It is sleepi

Re: Change to FreeBSD release scheduling etc.

On 7/15/24 12:24, Anton Shepelev wrote: In my limited experice with some *nix-like OSes, they have to be updated more or less regularly lest they "sink" into an obsolete state whence it is /very/ difficult to restore them back up into updated and workable condition, what with dependency hell and

Re: Change to FreeBSD release scheduling etc.

Andrea Venturoli to Peter: > > In short, it takes me about 3 months to catch the > > surprizes[*] and fix (or find out how to cope with) the > > concerning issues, regressions et al. that come along > > with a new release. Up to now that would then give > > another 9 months during which the system

Re: Possible bug in zfs send or pipe implementation?

On 15/07/2024 9:35 am, Garrett Wollman wrote: I'm currently running syncoid with `--quiet`, which removes `pv` from the pipeline. It seems to be moving along, but of course I can't easily tell what it's doing. Without `pv` in the way, the process reading the pipe is `lzop` instead, which doesn