On Mon, Apr 24, 2023 at 9:49 PM Charlie Li wrote:
> Charlie Li wrote:
> > Pete Wright wrote:
> >> i've seen a few threads about the block_cloning feature causing data
> >> corruption issues on CURRENT and have been keen to avoid enabling it
> >> until the dust settles. i was under the
Charlie Li wrote:
Pete Wright wrote:
i've seen a few threads about the block_cloning feature causing data
corruption issues on CURRENT and have been keen to avoid enabling it
until the dust settles. i was under the impression that we either
reverted or disabled block_cloning on CURRENT, but
Pete Wright wrote:
i've seen a few threads about the block_cloning feature causing data
corruption issues on CURRENT and have been keen to avoid enabling it
until the dust settles. i was under the impression that we either
reverted or disabled block_cloning on CURRENT, but when i ran "zpool
hi everyone,
i've seen a few threads about the block_cloning feature causing data
corruption issues on CURRENT and have been keen to avoid enabling it
until the dust settles. i was under the impression that we either
reverted or disabled block_cloning on CURRENT, but when i ran "zpool
On Sun, Apr 23, 2023 at 10:22 PM Mark Millard wrote:
> [Warner answered my specific question separately. This is about
> something else.]
>
> On Apr 23, 2023, at 20:57, Warner Losh wrote:
>
> > On Sun, Apr 23, 2023 at 9:40 PM Simon J. Gerraty
> wrote:
> >> Mark Millard wrote:
> >> > I will
On 4/18/23, Pawel Jakub Dawidek wrote:
> On 4/18/23 05:14, Mateusz Guzik wrote:
>> On 4/17/23, Pawel Jakub Dawidek wrote:
>>> Correct me if I'm wrong, but from my understanding there were zero
>>> problems with block cloning when it wasn't in use or now disabled.
>>>
>>> The reason I've
unsubscribe
On Mon, Apr 24, 2023 at 10:02 AM Lizbeth Mutterhunt, Ph.D
wrote:
>
>
>
> Wenn einem gar niets meer einfällt, schreit man auch nix. Mijn mute reminder!
>
> Begin doorgestuurd bericht:
>
> Van: "Lizbeth Mutterhunt, Ph.D"
> Datum: 24 april 2023 om 08:58:54 CEST
> Aan:
Wenn einem gar niets meer einfällt, schreit man auch nix. Mijn mute reminder!
Begin doorgestuurd bericht:
> Van: "Lizbeth Mutterhunt, Ph.D"
> Datum: 24 april 2023 om 08:58:54 CEST
> Aan: current-us...@freebsd.org
> Onderwerp: dbus broken?
>
> As I tried the CURRENT Image from Aor., 4th, I
Warner Losh wrote:
> > ld-elf.so.1: /usr/local/bin/git: Undefined symbol "__libc_start1@FBSD_1.7"
>
> This is a symptom of trying to run a prog built for target on a host
> which is not the same.
> Your path is messed up then. We always run (a copy of) the host's binaries
I wasn't using the
