Skip to main content

Fedora Upgrade with LVM Snapshots

Fedora 31 has been released at the end of October 2019 so it's time for me to update. Fedora Updates have proven to be reliable but Updates can go wrong and for that case, I want to have a fallback that I can utilize to restore my system without much of a hassle. I use LVM for all my Storage so the solution for me was fairly easy: LVM Snapshots.

I'm using one volume group for the system named 'vg_base'. If you are copy-pasting the commands, this is the one parameter you'll have to adjust. Without further ado, let's get through the upgrade scenario. While these commands can be executed as user with sudo privileges, I find it easier to do these as root.


Install the system-upgrade plugin
 [root@castle-bravo ~]# dnf -y install dnf-plugin-system-upgrade  
Now create the snapshots of all the system lvs. Note that you would only need to snapshot the rpmdb as well as the logical volumes containing /etc/, /bin, /sbin, /usr/bin and /usr/sbin but to be on the safe side I usually snapshot all the volumes required to run the system.
 [root@castle-bravo ~]# for lv in $(lvs vg_base | awk '{print $1}' | grep -vE '^LV$|^lv_swap$'); do echo "lvcreate -s -n "$lv"_snapshot -L 20G /dev/vg_base/"$lv | bash -x; done  
Let's break this command down a bit. This is a simple for-loop in bash that creates a snapshot with a Copy-On-Write capacity of 20G for every item in the output of 'lvs vg_base'. If you do not want to run it instantly but want to see what this would do, sort of a dry-run, remove the 'bash -x' part.
Here's an example:
 [root@castle-bravo ~]# # for lv in $(lvs vg_base | awk '{print $1}' | grep -vE '^LV$|^lv_swap$'); do echo "lvcreate -s -n "$lv"_snapshot -L 20G /dev/vg_base/"$lv; done  
 lvcreate -s -n lv_home_snapshot -L 20G /dev/vg_base/lv_home  
 lvcreate -s -n lv_root_snapshot -L 20G /dev/vg_base/lv_root  
 lvcreate -s -n lv_tmp_snapshot -L 20G /dev/vg_base/lv_tmp  
 lvcreate -s -n lv_usr_snapshot -L 20G /dev/vg_base/lv_usr  
 lvcreate -s -n lv_var_snapshot -L 20G /dev/vg_base/lv_var  
 lvcreate -s -n lv_var_log_snapshot -L 20G /dev/vg_base/lv_var_log  

The creation of the snapshots will take only a few seconds. Once this loop is done, you can download the new release version of fedora using dnf. This might take a while depending on your connection speed.
 [root@castle-bravo ~]# dnf system-upgrade download --releasever=31  
Once everything is downloaded and the transaction checks have passed successfully, you can start the upgrade by rebooting.
 [root@castle-bravo ~]# dnf system-upgrade reboot  
The update can go two ways, either successfully or it can fail. In case of success, you can delete the snapshots by running this command
 [root@castle-bravo ~]# for snapshot in $(lvs vg_base | awk '{print $1}' | grep -iE 'snapshot'); do lvremove -f /dev/vg_base/$snapshot; done  
If the update fails and you want to revert to the snapshot you've taken, you'll have to boot your machine using a live environment, such as the installer, or any other live distribution with lvm support (or availability in the repos) and run this command
 [root@castle-bravo ~]# for snapshot in $(lvs vg_base | awk '{print $1}' | grep -iE 'snapshot'); do lvconvert --mergesnapshot /dev/vg_base/$snapshot; done  
This will merge the snapshots you've taken back to the original volumes and restore your system to the point where you've taken the snapshot.

Feel free to comment and / or suggest a topic.

Comments

Popular posts from this blog

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but  for a detailed comparison check out this  article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). recently went over my network configuration and I noticed that I've never put my My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key&quo

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the