2023/freebsd-fs/20230611.freebsd-fs
Messages: 36, sorted by subject
|
Last update: Thu Nov 6 9:30:08 UTC 2025
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Jun 4 bugzilla-noreply@freebsd.o [Bug 224292] processes are hanging in state ufs / possible deadlock in file system 2. Jun 7 bugzilla-noreply@freebsd.o [Bug 255201] [panic] handle_written_inodeblock: Invalid link count -1 for inodedep 3. Jun 4 bugzilla-noreply@freebsd.o [Bug 264234] "zpool get autotrim" displays propety as default regardless of value 4. Jun 4 bugzilla-noreply@freebsd.o [Bug 264234] "zpool get autotrim" displays propety as default regardless of value 5. Jun 7 bugzilla-noreply@freebsd.o [Bug 271312] inum > maxino should probably be inum >= maxino in fsck_ffs 6. Jun 8 bugzilla-noreply@freebsd.o [Bug 271312] inum > maxino should probably be inum >= maxino in fsck_ffs 7. Jun 7 bugzilla-noreply@freebsd.o [Bug 271351] fsck_ffs can crash if fs_size < fs_ncg*fs_fpg 8. Jun 8 bugzilla-noreply@freebsd.o [Bug 271351] fsck_ffs can crash if fs_size < fs_ncg*fs_fpg 9. Jun 7 bugzilla-noreply@freebsd.o [Bug 271354] reachable directory with zero link count can cause fsck to deref NULL 10. Jun 8 bugzilla-noreply@freebsd.o [Bug 271354] reachable directory with zero link count can cause fsck to deref NULL 11. Jun 7 bugzilla-noreply@freebsd.o [Bug 271378] negative jt_size in ffs truncate journal record causes fsck to crash 12. Jun 8 bugzilla-noreply@freebsd.o [Bug 271378] negative jt_size in ffs truncate journal record causes fsck to crash 13. Jun 7 bugzilla-noreply@freebsd.o [Bug 271383] negative jb_blk in a JOP_FREEBLK ffs journal record can cause fsck to crash 14. Jun 8 bugzilla-noreply@freebsd.o [Bug 271383] negative jb_blk in a JOP_FREEBLK ffs journal record can cause fsck to crash 15. Jun 7 bugzilla-noreply@freebsd.o [Bug 271414] negative root i-node size can cause crash in fsck_ffs's iblock() if journaling 16. Jun 8 bugzilla-noreply@freebsd.o [Bug 271414] negative root i-node size can cause crash in fsck_ffs's iblock() if journaling 17. Jun 8 bugzilla-noreply@freebsd.o [Bug 271480] background fsck_ffs fails due to improper attempts to update directory depth 18. Jun 3 bugzilla-noreply@freebsd.o [Bug 271766] dumpfs fails on geli devices: cylinder group checks failed 19. Jun 6 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 20. Jun 8 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed
21. Jun 9 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 22. Jun 9 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 23. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 24. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 25. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 26. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 27. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 28. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 29. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 30. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 31. Jun 10 bugzilla-noreply@freebsd.o [Bug 271772] ZFS with L2ARC: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 32. Jun 4 bugzilla-noreply@freebsd.o [Bug 271772] ZFS: panic: VERIFY3(dev->l2ad_hand <= dev->l2ad_evict) failed 33. Jun 6 bugzilla-noreply@freebsd.o [Bug 271835] 13.0-RELEASE-p13: seeing inode issues/ file corruption on long run 34. Jun 5 bugzilla-noreply@freebsd.o [Bug 271835] seeing inode issues/ file corruption in freeBSD13 on long run 35. Jun 6 bugzilla-noreply@freebsd.o [Bug 271835] seeing inode issues/ file corruption in freeBSD13 on long run 36. Jun 4 bugzilla-noreply@FreeBSD.o Problem reports for fs@FreeBSD.org that need special attention
home | up | archive sorted by: subject | author | date | reverse date
