Paul Gevers: > Dear Benedikt, all, > > On 16-04-2020 10:44, Benedikt Tuchen wrote: >> While doing an upgrade from Stretch to Buster on a Laptop with XFS >> Filesystem in use. After the upgrade the laptop doesn't boot into >> the system because of the removed "barrier|nobarrier" mount option >> for XFS in version 4.19. >> >> I think this issue should be mentioned in the "5. Issues to be aware >> of for buster" part of the release-notes in Buster. > > What is exactly the problem? Does everybody with XFS run into this > issue? Do you have a solution for the problem that we can mention? Or, > phrased differently, what should the user do if they have an XFS > filesystem and want to upgrade to buster? > > Paul >
They would have to remove the "barrier" or "nobarrier" keyword if they use either in their fstab (or in scripts that passes that mount option explicitly). If I try to mount an XFS file system with "barrier" (or "nobarrier"), I get cryptic errors like this: """ mount: <path>: wrong fs type, bad option, bad superblock on <path>, missing codepage or helper program, or other error. """ (using mount -o ...,barrier - I don't remember if the fstab message is better) ~Niels
