Re: xfsprogs 4.16.0 format change, GRUB error unknown filesystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 14, 2018 at 11:36 AM, Darrick J. Wong
<darrick.wong@xxxxxxxxxx> wrote:
> On Mon, May 14, 2018 at 11:15:27AM -0600, Chris Murphy wrote:
>> Downstream bug, Fedora Rawhide being a canary in the coal mine!
>> https://bugzilla.redhat.com/show_bug.cgi?id=1575797
>>
>> Comment 8 about the kernel warning related to freeze/thaw is curious
>> but ends up being unrelated to this problem.
>>
>> The gist is that xfsprogs 4.16.0 formatted volumes aren't recognized
>> by either GRUB user space tools, or the GRUB core.img (whether of the
>> embedded BIOS variety or the grubx64.efi variety)
>>
>> Anyway, open question for XFS devs if this should be fixed in xfsprogs
>> or GRUB. I haven't tested this with syslinux to know if it has a
>> similar problem.
>
> mkfs.xfs 4.16 enables sparse inodes by default, which is why grub
> doesn't recognise the boot fs.  grub needs fixing, or $installer needs
> to disable sparse inodes, I think.

Is there a reason why this was made default before GRUB was fixed? Or
would XFS devs prefer to not support /boot on XFS?

-- 
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux