Re: F22 -> F23 -> F24 ?

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

 



On Fri, Aug 12, 2016 at 4:03 PM, Jon LaBadie <jonfu@xxxxxxxxxx> wrote:
> On Fri, Aug 12, 2016 at 02:59:49PM -0400, Jon LaBadie wrote:
>> Planning on taking my F22 desktop to F24 soon.
>>
>> Just want to confirm that trying to skip a
>> release ist verboten. :(
>>
> Love it!!  First three responses are:
>
>  1. Yes, designed to work that way
>  2. Not recommended
>  3. Better do a fresh install
>
> :)

Well you could read mine as "upgrade should work, but might have a
rough edge here and there". The upgrade process is tested as part of
release criteria, and if it doesn't work it is release blocking. But
there's always a need for more testing of such things to find the edge
cases. And the difficulty there is most of that testing is done on
cleanly installed n-1 version. Not as much testing happens on aged n-1
systems before running the n version upgrade.

A conservative approach would be to tar up /boot and then snapshot the
'fedora-root' LV before doing the upgrade (or for Btrfs users tar
/boot and then snapshot the 'root' subvolume). I guess the drawback is
conventional LVM snapshots is that they are tedious to use: you have
to have free space in the VG already, which is not a Fedora
installation default, so that the CoW changes to the original volume
during the upgrade have somewhere to go, it's slow, and you have to
commit or reject changes at some point which is also confusing (to me
anyway). LVM thinp snapshots and Btrfs snapshots are way easier to
work with, with LVM thinp LV's totally obviating any future need to
shrink a file system as well - just fstrim it and any unused logical
extents are returned to the VG for reallocation to any other LV.

Or the conservative conventional approach is to back it all up and be
prepared to restore it if it goes badly.

So I'd say I'm closer to opinion 1 than opinion 2.


-- 
Chris Murphy
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux