freebsd-fs@FreeBSD.org
Filesystems
- Go to: [ monthly archives ] [ by author ] [ by thread ]
March 2026 Archives by date
- Sun, 01 Mar 2026
- Problem reports for fs@FreeBSD.org that need special attention bugzilla-noreply_at_FreeBSD.org
- Thu, 05 Mar 2026
- [Bug 293492] p9fs: VNASSERT failed: locked not true at /usr/src/sys/kern/vfs_subr.c:5816 (assert_vop_elocked) bugzilla-noreply_at_freebsd.org
- Sun, 08 Mar 2026
- Problem reports for fs@FreeBSD.org that need special attention bugzilla-noreply_at_FreeBSD.org
- Mon, 09 Mar 2026
- [Bug 293691] NFSv4.1 client trying to set |FATTR4_ARCHIVE| gets EPERM for file/dir creation attempts bugzilla-noreply_at_freebsd.org
- [Bug 293691] NFSv4.1 client trying to set |FATTR4_ARCHIVE| gets EPERM for file/dir creation attempts bugzilla-noreply_at_freebsd.org
- Tue, 10 Mar 2026
- [Bug 293492] p9fs: VNASSERT failed: locked not true at /usr/src/sys/kern/vfs_subr.c:5816 (assert_vop_elocked) bugzilla-noreply_at_freebsd.org
- Thu, 12 Mar 2026
- [Bug 293750] mv process hangs at 100% CPU (State R) in cache_fplookup / zap_lookup on ZFS bugzilla-noreply_at_freebsd.org
- [Bug 293750] mv process hangs at 100% CPU (State R) in cache_fplookup / zap_lookup on ZFS bugzilla-noreply_at_freebsd.org
- [Bug 293750] mv process hangs at 100% CPU (State R) in cache_fplookup / zap_lookup on ZFS bugzilla-noreply_at_freebsd.org
- [Bug 293492] p9fs: VNASSERT failed: locked not true at /usr/src/sys/kern/vfs_subr.c:5816 (assert_vop_elocked) bugzilla-noreply_at_freebsd.org
- Sun, 15 Mar 2026
- Problem reports for fs@FreeBSD.org that need special attention bugzilla-noreply_at_FreeBSD.org
- Tue, 17 Mar 2026
- [Bug 293492] p9fs: VNASSERT failed: locked not true at /usr/src/sys/kern/vfs_subr.c:5816 (assert_vop_elocked) bugzilla-noreply_at_freebsd.org
- [Bug 293856] p9fs: VNASSERT failed: vp->v_data == NULL not true at /usr/src/sys/kern/vfs_subr.c:2207 (freevnode) bugzilla-noreply_at_freebsd.org
- [Question] UFS/FFS: why a block is always allocated at EOF when truncating up David Timber
- Re: [Question] UFS/FFS: why a block is always allocated at EOF when truncating up Frank Leonhardt
- Re: [Question] UFS/FFS: why a block is always allocated at EOF when truncating up Konstantin Belousov
- [Bug 293856] p9fs: VNASSERT failed: vp->v_data == NULL not true at /usr/src/sys/kern/vfs_subr.c:2207 (freevnode) bugzilla-noreply_at_freebsd.org
- Wed, 18 Mar 2026
- [Bug 261212] Update the ZFS chapter of the FreeBSD Handbook, and other OpenZFS-related pages bugzilla-noreply_at_freebsd.org
- Thu, 19 Mar 2026
- Re: [Question] UFS/FFS: why a block is always allocated at EOF when truncating up Dag-Erling_Smørgrav
- Re: [Question] UFS/FFS: why a block is always allocated at EOF when truncating up Frank Leonhardt
- NFS4, RPC struct is bad? Ronald Klop
- Re: NFS4, RPC struct is bad? Rick Macklem
- Fri, 20 Mar 2026
- [Bug 293856] p9fs: VNASSERT failed: vp->v_data == NULL not true at /usr/src/sys/kern/vfs_subr.c:2207 (freevnode) bugzilla-noreply_at_freebsd.org
- [Bug 293856] p9fs: VNASSERT failed: vp->v_data == NULL not true at /usr/src/sys/kern/vfs_subr.c:2207 (freevnode) bugzilla-noreply_at_freebsd.org
- Re: [Question] UFS/FFS: why a block is always allocated at EOF when truncating up Dag-Erling_Smørgrav
- Sun, 22 Mar 2026
- Problem reports for fs@FreeBSD.org that need special attention bugzilla-noreply_at_FreeBSD.org
- Go to: [ monthly archives ] [ by author ] [ by date ]