Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
Miguel Figueiredo wrote: > Às 21:43 de 13/03/21, Paul Gevers escreveu: > [...] >> + The XFS file system has removed the barrier >> + and nobarrier mount options. > > How about: The mount options were removed from the XFS file system ? Oh, yes, it's true that it was the developers who did the removing, not the software... but phrasing it like that makes it sound as if we were talking about one particular XFS-formatted partition that was at some point given different options in /etc/fstab. How about: Support for the barrier and nobarrier mount options has been removed from the XFS file system. (Or we could even just say The XFS file system no longer supports the barrier and nobarrier mount options. except that when I go and look at the context I see this is more or less identical to the title line, so no, don't use that.) -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
Às 21:43 de 13/03/21, Paul Gevers escreveu: [...] + The XFS file system has removed the barrier + and nobarrier mount options. [...] How about: The mount options were removed from the XFS file system ? -- Best regards / Melhores cumprimentos, Miguel Figueiredo
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
Paul Gevers wrote: > Control: tag -1 patch > > Hi, > > How's this? > > + > +The XFS file system no longer supports barrier/nobarrier > +option > + > + The XFS file system has removed the barrier > + and nobarrier mount options. It is > + recommended to check /etc/fstab for the > + presence of either keyworrd and remove if. XFS will fail to start ^ ^ > + when mounted with either option. > + > + Make that presence of either keyword and remove it. XFS will fail to start ^ ^ And I'm not sure about "start"... maybe it should be swapped around to "Partitions using these options will fail to mount". -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
Control: tag -1 patch Hi, How's this? + +The XFS file system no longer supports barrier/nobarrier +option + + The XFS file system has removed the barrier + and nobarrier mount options. It is + recommended to check /etc/fstab for the + presence of either keyworrd and remove if. XFS will fail to start + when mounted with either option. + + Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
Hendrik Boom: > On Sun, May 03, 2020 at 09:34:34AM +0200, Niels Thykier wrote: >> [...] > > Would that refer to the write battier on the hard drive? Isn't that > essential to the safe operation of XFS? > > -- hendrik > Not any longer AFAICT. The following patch discussion in the Linux kernel suggests that it was a "no-op" for some time up to its removal: * https://patchwork.kernel.org/patch/9486549/ ~Niels
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
On Sun, May 03, 2020 at 09:34:34AM +0200, Niels Thykier wrote: > 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: : wrong fs type, bad option, bad superblock on , > missing codepage or helper program, or other error. > """ > > (using mount -o ...,barrier - I don't remember if the fstab message is > better) Would that refer to the write battier on the hard drive? Isn't that essential to the safe operation of XFS? -- hendrik
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
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: : wrong fs type, bad option, bad superblock on , missing codepage or helper program, or other error. """ (using mount -o ...,barrier - I don't remember if the fstab message is better) ~Niels
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
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 signature.asc Description: OpenPGP digital signature
Bug#956877: release-notes: Upgrade from XFS removes mount option "barrier|nobarrier"
Package: release-notes Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** 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. -- System Information: Debian Release: 9.12 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-0.bpo.6-amd64 (SMP w/32 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) -- Benedikt Tuchen | https://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
