On Sun, Nov 15, 2020 at 4:12 AM Zbigniew Jędrzejewski-Szmek
<zbyszek(a)in.waw.pl> wrote:
On Wed, Nov 04, 2020 at 01:12:44PM -0500, Ben Cotton wrote:
> * Name: [[User:dkeefe|Dennis Keefe]], [[User:mulhern|Anne Mulhern]],
> [[User:jbaublitz|John Baublitz]]
> * Email: dkeefe(a)redhat.com, amulhern(a)redhat.com, jbaublitz(a)redhat.com
> == Upgrade/compatibility impact ==
>
> Stratis symlinks have moved. Existing symlinks in /stratis/<pool
> name>/<filesystem name> will need to be migrated to
> /dev/stratis/<pool name>/<filesystem name>. This is accomplished by
> running the migration script (stratis_migrate_symlinks.sh) that comes
> with the
> 2.2.0 release of Stratis or rebooting the system. Any configurations
> that make use of the old symlink locations will
> need to be updated to use the new location. So, if there has been
> manual changes to systemd unit files or /etc/fstab
> for automatically mounting Stratis filesystems, then these will need
> to be updated to reflect the change.
How large is the risk that systems that were using the old /stratis/foo
paths will fail to mount the filesystems, and possibly fail to boot, after
the upgrade? (Sorry, I have never used stratis, so I don't know how often
those migration steps would be necessary.)
Shouldn't /startis symlink be created for compatibility on *upgrades* ?
It's not supported for booting yet. But if there's an fstab entry
using a path from /stratis, and also doesn't include the nofail or
noauto mount options, boot can fail waiting indefinitely on a file
system that won't ever appear
--
Chris Murphy