On Mon, 13 Jul 2020 23:57:45 -0700
Lew Wolfgang
On 07/13/2020 11:32 PM, Per Jessen wrote:
Lew Wolfgang wrote:
Today I booted the 15.1 rescue system and determined that mount works! It reported:
4096 byte physical blocks 574218043392 blocks for sda1 (drive lettering changed) 273437163520 blocks for sdb1
Back running 15.2, fdisk reports the same block counts as 15.1.
Note that 15.1 was able to mount the XFS partitions created by 15.2's mks.xis.
This implies to me that the problem is probably in the 15.2 XIS kernel module? I would be tempted to think so too, yes. OTOH, I went and googled it -
https://bugzilla.kernel.org/show_bug.cgi?id=202127 (also large XFS filesystem on hardware RAID).
I only skimmed it quickly, but they seem to be thinking it is a config issue at time of filesystem creation.
Wow, thanks Per! That sure looks like my problem. It may be a Broadcom controller firmware bug that was revealed with more recent Linux kernels. I'll look into updating the firmware, tomorrow. I just finished 16-oz of sangria with frozen blueberries, and it's 11:52-PM. One should not do root-ish things when drinking wine!
Regards, Lew
It appears you may need to add your data and customer opinion weight to daimh's bug report to Broadcom. It sounds like you can fix the new filesystems by overriding the firmware's buggy values as described in #23, #24 and if you have any existing filesystems, you'll be able to mount them as described in #30 That kind of response from Eric and Dave is why I like XFS! :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org