On Mon, Nov 16, 2020 at 1:39 AM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > > On Sun, Nov 15, 2020 at 04:28:36PM -0700, Chris Murphy wrote: > > On Sun, Nov 15, 2020 at 4:12 AM Zbigniew Jędrzejewski-Szmek > > <zbyszek@xxxxxxxxx> 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@xxxxxxxxxx, amulhern@xxxxxxxxxx, jbaublitz@xxxxxxxxxx > > > > > > > == 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 > > Right, but the question is: how common is that? Do we even have any general > idea how many people are using stratis? No idea. But I think the feature and its release notes can adequately inform users of the possibility of boot failure and whatever workaround is needed. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
