Date: Thu, 18 Dec 2025 21:29:07 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230779] Broadcom 9480 (using SAS3516) requires newer mrsas and not mpr in kernel Message-ID: <bug-230779-227-WQQVp0mUYw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230779-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230779 --- Comment #7 from adamz@olympustechgroup.com --- (In reply to Michael Osipov from comment #6) Not to derail this bug report but to answer your question: I know I didn't file a bug as I was too busy dealing with massive recovery efforts and I haven't had success filing reports historically. The issue was similar to https://forums.freebsd.org/threads/fsck-on-big-filesystems-100tb.77305/ and I had reached out to mckusick@FreeBSD.org via email with no response. It looks like there were still 32bit references in the UFS2 code that effectively results in running out of inodes even though df says otherwise. My specific error on two independant filesystems that both crashed at similar times (one was an rsync backup of the other) is below: fsck_ufs: inoinfo: inumber 18446744071562078208 out of range The end result was we lost all of our data due to corruption, even though recovery tools could see files, nothing was recoverable. There was no hardware failure and the exact same hardware was ultimately reused again once we moved on to other OS and filesystems. That reason alone resulted in us dropping FreeBSD from every system we use and moving off of UFS. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230779-227-WQQVp0mUYw>