On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote:
> Please see/test: https://github.com/openzfs/zfs/pull/15732 .
Looks like that has landed in current:
commit f552d7adebb13e24f65276a6c4822bffeeac3993
Merge: 13720136fbf a382e21194c
Author: Martin Matuska
John,
On 04.01.2024 09:20, John Kennedy wrote:
On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote:
On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote:
On 01.01.2024 08:59, John Kennedy wrote:
...
My poudriere build did eventually fail as well:
...
On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote:
> On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote:
> > On 01.01.2024 08:59, John Kennedy wrote:
> > > ...
> > >My poudriere build did eventually fail as well:
> > > ...
> > > [05:40:24] [01] [00:17:20] Finished d
On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote:
> On 01.01.2024 08:59, John Kennedy wrote:
> > ...
> >My poudriere build did eventually fail as well:
> > ...
> > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success
> > [05:40:24] Stopping 2 buil
On 01.01.2024 08:59, John Kennedy wrote:
On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
markj@ pointed me in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
to
https://github.com/openzfs/zfs/pull/15719
So it will probably be fixed sooner or later.
The other ZFS crashes I
Am 2024-01-02 08:22, schrieb Kurt Jaeger:
Hi!
The sysctl for block cloning is vfs.zfs.bclone_enabled.
To check if a pool has made use of block cloning:
zpool get all poolname | grep bclone
One more thing:
I have two pools on that box, and one of them has some bclone files:
# zpool get a
Hi!
> The sysctl for block cloning is vfs.zfs.bclone_enabled.
> To check if a pool has made use of block cloning:
> zpool get all poolname | grep bclone
One more thing:
I have two pools on that box, and one of them has some bclone files:
# zpool get all ref | grep bclone
ref bcloneused
Hi!
> Am 2023-12-31 19:34, schrieb Kurt Jaeger:
> > I already have
> >
> > vfs.zfs.dmu_offset_next_sync=0
> >
> > which is supposed to disable block-cloning.
>
> It isn't. This one is supposed to fix an issue which is unrelated to block
> cloning (but can be amplified by block cloning). This is
Am 2023-12-31 19:34, schrieb Kurt Jaeger:
I already have
vfs.zfs.dmu_offset_next_sync=0
which is supposed to disable block-cloning.
It isn't. This one is supposed to fix an issue which is unrelated to
block cloning (but can be amplified by block cloning). This issue is
fixed since some week
On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote:
> > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> > > markj@ pointed me in
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> > > to
> > > https://github.com/openzfs/zfs/pull/15719
> > >
> > > So it will p
On Mon, Jan 01, 2024 at 08:42:26AM -0800, John Kennedy wrote:
> Applying the two ZFS kernel patches fixes that issue:
commit 09af4bf2c987f6f57804162cef8aeee05575ad1d (zfs: Fix SPA sysctl handlers)
landed too.
root@bsd15:~ # sysctl -a | grep vfs.zfs.zio
vfs.zfs.zio.deadman_log_a
On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> > > I can crash mine with "sysctl -a" as well.
>
> markj@ pointed me in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> to
> https://github.com/openzfs/zfs/pull/15719
>
> So it will probably be fixed sooner or later.
>
On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote:
> Do you have
>vfs.zfs.dmu_offset_next_sync=0
I didn't initially, I do now. Like I said, I haven't been following that one
100%. I know it isn't block-clone per say, so much as some underlying problem
it pokes with a pointy s
Hi!
> On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> > markj@ pointed me in
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> > to
> > https://github.com/openzfs/zfs/pull/15719
> >
> > So it will probably be fixed sooner or later.
> >
> > The other ZFS crashes I've
On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> markj@ pointed me in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> to
> https://github.com/openzfs/zfs/pull/15719
>
> So it will probably be fixed sooner or later.
>
> The other ZFS crashes I've seen are still an issue
Hi!
> > I can crash mine with "sysctl -a" as well.
markj@ pointed me in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
to
https://github.com/openzfs/zfs/pull/15719
So it will probably be fixed sooner or later.
The other ZFS crashes I've seen are still an issue.
--
p...@freebsd.or
> I can crash mine with "sysctl -a" as well.
Smaller test, this is sufficient to crash things:
root@bsd15:~ # sysctl vfs.zfs.zio
vfs.zfs.zio.deadman_log_all: 0
vfs.zfs.zio.dva_throttle_enabled: 1
vfs.zfs.ziopanic: sbuf_clear makes no sense on sbuf 0xf8002c8
On Sun, Dec 31, 2023 at 07:34:45PM +0100, Kurt Jaeger wrote:
> Hi!
>
> Short overview:
> - Had CURRENT system from around September
> - Upgrade on the 23th of December
> - crashes in ZFS, see
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538
> for details
> - Reinstalled from scratch
Hi!
Short overview:
- Had CURRENT system from around September
- Upgrade on the 23th of December
- crashes in ZFS, see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538
for details
- Reinstalled from scratch with new SSDs drives from
https://download.freebsd.org/snapshots/amd64/amd64/IS
Fixed in r247540. If you are using a post-247265 zfs module please
install the new module first.
On 27.2.2013 22:56, Derrick Dantavious Edwards wrote:
> I updated sources a couple of days ago and when I rebooted to continue
> to
> the upgrade process I received errors when I attempted to m
On Wed, Feb 27, 2013 at 05:09:02PM -0800, Xin Li wrote:
> Martin actually have done very good job maintaining ioctl
> compatibility when we jumped from v15 to v28 that most people didn't
> even notice that the ioctl was changed.
>
As one who has gone through that upgrade on head/, stable/9/, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/27/13 16:44, Glen Barber wrote:
> On Wed, Feb 27, 2013 at 04:37:47PM -0800, Xin Li wrote:
>>> In mid-February, zpool version was upgraded to include
>>> lz4_compress. My understanding was that changing from the
>>> OpenSolaris ZFS version nu
On Wed, Feb 27, 2013 at 04:37:47PM -0800, Xin Li wrote:
> > In mid-February, zpool version was upgraded to include
> > lz4_compress. My understanding was that changing from the
> > OpenSolaris ZFS version number scheme (i.e., "v28") to what we have
> > on -CURRENT (i.e., "5000") was so that we can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/27/13 16:33, Glen Barber wrote:
> Hi Martin,
>
> On Wed, Feb 27, 2013 at 07:21:39PM -0500, Derrick Dantavious
> Edwards wrote:
> [...] I updated sources a couple of days ago and when I
> rebooted to continue to the upgrade process I re
Hi Martin,
On Wed, Feb 27, 2013 at 07:21:39PM -0500, Derrick Dantavious Edwards wrote:
> > >> [...]
> > >> I updated sources a couple of days ago and when I rebooted to continue to
> > >> the upgrade process I received errors when I attempted to mount zfs
> > >> filesystem. The error looked like t
On Wednesday, February 27, 2013 02:59:16 PM you wrote:
> On Wed, Feb 27, 2013 at 2:44 PM, Steven Hartland
>
> wrote:
> > - Original Message - From: "Derrick Dantavious Edwards"
> >
> >> I updated sources a couple of days ago and when I rebooted to continue to
> >> the upgrade process I r
On Wednesday, February 27, 2013 02:59:16 PM you wrote:
> On Wed, Feb 27, 2013 at 2:44 PM, Steven Hartland
>
> wrote:
> > - Original Message - From: "Derrick Dantavious Edwards"
> >
> >> I updated sources a couple of days ago and when I rebooted to continue to
> >> the upgrade process I r
On Wed, Feb 27, 2013 at 02:59:16PM -0800, sean bruno wrote:
> Yup, totally hit this today and was yelling at various people about it.
>
> the Kernel and the ZFS tools in userland need to be updated at the same time.
>
> Boot back into the old kernel and (cd /usr/src/cddl && make install)
> to upd
On Wed, Feb 27, 2013 at 2:44 PM, Steven Hartland
wrote:
> - Original Message - From: "Derrick Dantavious Edwards"
>
>
>> I updated sources a couple of days ago and when I rebooted to continue to
>> the upgrade process I received errors when I attempted to mount zfs
>> filesystem. The error
- Original Message -
From: "Derrick Dantavious Edwards"
I updated sources a couple of days ago and when I rebooted to continue to
the upgrade process I received errors when I attempted to mount zfs
filesystem. The error looked like this.
zpool mount -a
internal error: Invalid arugme
I updated sources a couple of days ago and when I rebooted to continue
to
the upgrade process I received errors when I attempted to mount zfs
filesystem. The error looked like this.
zpool mount -a
internal error: Invalid arugment
pid 25 (zfs), uid 0, exited on signal 6
Abort trap
I ge
31 matches
Mail list logo
