freebsd-fs@FreeBSD.org

Filesystems

Go to: [ monthly archives ] [ by author ] [ by date ]

October 2025 Archives by thread

Problem reports for fs@FreeBSD.org that need special attention: bugzilla-noreply_at_FreeBSD.org (Sun, 05 Oct 2025 21:00:39 UTC)
realpath() leakage and unix socket collision in -o union mounts + jails: David 'equinox' Lamparter (Tue, 07 Oct 2025 18:49:27 UTC)

Re: realpath() leakage and unix socket collision in -o union mounts + jails: Konstantin Belousov (Wed, 08 Oct 2025 04:37:49 UTC)

Re: realpath() leakage and unix socket collision in -o union mounts + jails: David 'equinox' Lamparter (Wed, 08 Oct 2025 07:36:26 UTC)

Re: realpath() leakage and unix socket collision in -o union mounts + jails: Konstantin Belousov (Wed, 08 Oct 2025 15:03:42 UTC)

Re: realpath() leakage and unix socket collision in -o union mounts + jails: Konstantin Belousov (Wed, 08 Oct 2025 16:13:52 UTC)

getfsstat(2) MNT_NOWAIT & stale data for zpool: Dave Cottlehuber (Wed, 08 Oct 2025 15:59:12 UTC)

Re: getfsstat(2) MNT_NOWAIT & stale data for zpool: Peter Jeremy (Wed, 08 Oct 2025 17:57:13 UTC)

Re: getfsstat(2) MNT_NOWAIT & stale data for zpool: Dave Cottlehuber (Thu, 09 Oct 2025 07:23:02 UTC)

Re: getfsstat(2) MNT_NOWAIT & stale data for zpool: Konstantin Belousov (Thu, 09 Oct 2025 13:53:09 UTC)

Re: getfsstat(2) MNT_NOWAIT & stale data for zpool: Dave Cottlehuber (Thu, 09 Oct 2025 21:19:30 UTC)

Re: getfsstat(2) MNT_NOWAIT & stale data for zpool: Konstantin Belousov (Thu, 09 Oct 2025 22:34:13 UTC)

ZFS: corrupted file entry is invisible, but still there somehow, nevertheless undeletabe...: Nils Beyer (Thu, 09 Oct 2025 11:24:04 UTC)
Problem reports for fs@FreeBSD.org that need special attention: bugzilla-noreply_at_FreeBSD.org (Sun, 12 Oct 2025 21:00:28 UTC)
openat("./...", O_CREAT) fails even though the directory exists: Lexi Winter (Mon, 13 Oct 2025 08:32:45 UTC)

Re: openat("./...", O_CREAT) fails even though the directory exists: Olivier Certner (Mon, 13 Oct 2025 09:19:54 UTC)

Re: openat("./...", O_CREAT) fails even though the directory exists: Lexi Winter (Mon, 13 Oct 2025 09:27:20 UTC)

Re: openat("./...", O_CREAT) fails even though the directory exists: Olivier Certner (Mon, 13 Oct 2025 09:57:14 UTC)

Re: openat("./...", O_CREAT) fails even though the directory exists: Lexi Winter (Mon, 13 Oct 2025 10:23:00 UTC)

Re: openat("./...", O_CREAT) fails even though the directory exists: Adrian Chadd (Mon, 13 Oct 2025 18:06:02 UTC)

Re: openat("./...", O_CREAT) fails even though the directory exists: Dag-Erling_Smørgrav (Tue, 14 Oct 2025 00:48:07 UTC)

[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 11:37:27 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 12:26:06 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 12:34:50 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 12:50:04 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 13:16:22 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 14:05:09 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 14:29:07 UTC)
[Bug 290205] ZFS: file stuck in delete queue: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 14:33:34 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 14:52:26 UTC)
[Bug 275594] High CPU usage by arc_prune; analysis and fix: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 14:54:49 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 14:55:33 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 16:13:15 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 16:46:37 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Mon, 13 Oct 2025 17:06:40 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Tue, 14 Oct 2025 17:52:02 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Tue, 14 Oct 2025 17:52:35 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Tue, 14 Oct 2025 17:52:59 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Tue, 14 Oct 2025 17:53:16 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Tue, 14 Oct 2025 17:53:34 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Tue, 14 Oct 2025 17:53:55 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Wed, 15 Oct 2025 11:39:12 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Wed, 15 Oct 2025 11:45:25 UTC)
[Bug 283224] zpool import concurrent imports will deadlock: bugzilla-noreply_at_freebsd.org (Thu, 16 Oct 2025 19:21:53 UTC)
Problem reports for fs@FreeBSD.org that need special attention: bugzilla-noreply_at_FreeBSD.org (Sun, 19 Oct 2025 21:00:50 UTC)
Why does rangelock_enqueue() hang for hours?: Peter 'PMc' Much (Tue, 21 Oct 2025 13:02:13 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Rick Macklem (Tue, 21 Oct 2025 13:28:20 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Peter 'PMc' Much (Tue, 21 Oct 2025 14:29:00 UTC)
Re: Why does rangelock_enqueue() hang for hours?: Bakul Shah (Tue, 21 Oct 2025 14:49:55 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Rick Macklem (Wed, 22 Oct 2025 15:52:00 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Peter 'PMc' Much (Thu, 23 Oct 2025 09:49:23 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Rick Macklem (Thu, 23 Oct 2025 14:21:56 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Konstantin Belousov (Thu, 23 Oct 2025 14:49:27 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Bakul Shah (Thu, 23 Oct 2025 18:29:18 UTC)

Re: Why does rangelock_enqueue() hang for hours?: Rick Macklem (Fri, 24 Oct 2025 02:03:51 UTC)

[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host: bugzilla-noreply_at_freebsd.org (Wed, 22 Oct 2025 19:21:47 UTC)
Re: openat("./...", O_CREAT) fails even though the directory exists: Lexi Winter (Thu, 23 Oct 2025 15:22:00 UTC)
[Bug 273772] zpool nested in ZVOL becomes inaccessible when zfsd(8) is running on the host: bugzilla-noreply_at_freebsd.org (Sun, 26 Oct 2025 17:05:56 UTC)
Problem reports for fs@FreeBSD.org that need special attention: bugzilla-noreply_at_FreeBSD.org (Sun, 26 Oct 2025 21:00:14 UTC)
[Bug 290550] [lor] lock order reversal - zfs and devfs/nullfs: bugzilla-noreply_at_freebsd.org (Mon, 27 Oct 2025 11:22:50 UTC)
[Bug 290570] [zfs] panic: buffer modified while frozen!: bugzilla-noreply_at_freebsd.org (Mon, 27 Oct 2025 12:27:43 UTC)
[Bug 290571] [zfs] panic: Memory modified after free 0xfffffe0184c00000(8192) val=80bef961b6c4beea @ 0xfffffe0184c00000: bugzilla-noreply_at_freebsd.org (Mon, 27 Oct 2025 12:31:38 UTC)
[Bug 290579] Strange statistics zpool iostat on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Mon, 27 Oct 2025 18:27:04 UTC)
[Bug 290579] Strange statistics zpool iostat on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Mon, 27 Oct 2025 18:35:40 UTC)
[Bug 290579] Strange statistics zpool iostat on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Wed, 29 Oct 2025 15:09:07 UTC)
[Bug 290579] zpool iostat values never change, even on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Wed, 29 Oct 2025 15:09:56 UTC)
[Bug 290579] zpool iostat values never change, even on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Wed, 29 Oct 2025 15:39:06 UTC)
[Bug 290579] zpool iostat values never change, even on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Wed, 29 Oct 2025 15:47:00 UTC)
NFS + nobody user? (was: Re: poudriere + ZFS + NFS -> chown: /usr/local/poudriere/data/.m/rpi5-freebsd143-custom/01/.npkg: Operation not permitted): Ronald Klop (Thu, 30 Oct 2025 09:59:28 UTC)

Re: NFS + nobody user? (was: Re: poudriere + ZFS + NFS -> chown: /usr/local/poudriere/data/.m/rpi5-freebsd143-custom/01/.npkg: Operation not permitted): Rick Macklem (Thu, 30 Oct 2025 13:52:52 UTC)

[Bug 271925] chflags(1) fails to remove uarch flag with hardlinked files (ZFS): bugzilla-noreply_at_freebsd.org (Thu, 30 Oct 2025 14:19:44 UTC)
[Bug 228197] panic: solaris assert: arc_buf_alloc_impl: bugzilla-noreply_at_freebsd.org (Thu, 30 Oct 2025 15:17:39 UTC)
[Bug 271925] chflags(1) fails to remove uarch flag with hardlinked files (ZFS): bugzilla-noreply_at_freebsd.org (Thu, 30 Oct 2025 16:52:56 UTC)
[Bug 271925] chflags(1) fails to remove uarch flag with hardlinked files (ZFS): bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 02:43:25 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 03:08:01 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 13:06:59 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 13:25:38 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 13:27:52 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 13:35:46 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 13:41:49 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 13:46:55 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 13:56:36 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 14:08:36 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 14:36:50 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 15:08:25 UTC)
[Bug 290579] zpool iostat values never change, even on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 16:16:03 UTC)
[Bug 290579] zpool iostat values never change, even on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 16:16:08 UTC)
[Bug 271925] chflags(1) fails to remove uarch flag with hardlinked files (ZFS): bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 16:22:09 UTC)
[Bug 290579] zpool iostat values never change, even on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 17:13:08 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 17:49:43 UTC)
[Bug 290207] [ZFS] lowering "vfs.zfs.arc.max" to a low value causes kernel threads of "arc_evict" to use 91% CPU and disks to wait. System gets unresponsive...: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 21:49:23 UTC)
[Bug 290579] zpool iostat values never change, even on a heavily loaded system: bugzilla-noreply_at_freebsd.org (Fri, 31 Oct 2025 22:40:33 UTC)

Go to: [ monthly archives ] [ by author ] [ by date ]