Re: [linux-lvm] System completely unstable after migrating to thin pools

From: "John Stoffel" <john@stoffel.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] System completely unstable after migrating to thin pools
Date: Mon, 30 Nov 2020 17:24:33 -0500	[thread overview]
Message-ID: <24517.28961.127885.638522@quad.stoffel.home> (raw)
In-Reply-To: <CAMaziXtCk662ZfaG-crzrrKpi_efQqqOLbVCnSvLDsCOpLS0zw@mail.gmail.com>

Sreyan> I have migrated to thin pools using partclone.

I suspect you're toast.  What are you trying to accomplish here
though?  Trying to stuff 10 pounds of data into a 5 pound bag?  *grin*

Or are you trying to have the ability to take snapshots of your system
to make rollbacks easier?  

Sreyan> But now that I am using thin pools my system is completely unstable.

You need to post the output of your configuration in more detail, with
dmesg output, logs, lvs, pvs, vgs output, etc. 

But really, you do have backups?

Sreyan> My swap is not activated :

Sreyan> swapon[1004]: swapon: /fedora.swap: read swap header failed
Sreyan> systemd[1]: fedora.swap.swap: Swap process exited, code=exited, status=255/EXCEPTION

Sreyan> systemd[1]: fedora.swap.swap: Failed with result 'exit-code'.
Sreyan>  Failed to activate swap /fedora.swap.
Sreyan>  Dependency failed for Swap.
Sreyan>  swap.target: Job swap.target/start failed with result 'dependency'.

Sreyan> My System logging service is not started:

Sreyan> rsyslog.service: Failed with result 'core-dump'.
Sreyan>  Failed to start System Logging Service.
Sreyan>  SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=
Sreyan> 'unit=rsyslog comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=
Sreyan> failed'
Sreyan>  rsyslog.service: Scheduled restart job, restart counter is at 1.

Sreyan> And device mapper gives me weird messages during startup like:

Sreyan>  kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075
Sreyan>  kernel: device-mapper: block manager: btree_node validator check failed for block 220
Sreyan>  kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075
Sreyan>  kernel: device-mapper: block manager: btree_node validator check failed for block 220
Sreyan>  kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075
Sreyan>  kernel: device-mapper: block manager: btree_node validator check failed for block 220
Sreyan>  kernel: device-mapper: btree spine: node_check failed: csum 3318704195 != wanted 3318554075
Sreyan>  kernel: device-mapper: block manager: btree_node validator check failed for block 220

Sreyan> Also some dracut module is missing:

Sreyan> dracut-initqueue[867]: /usr/sbin/thin_check: execvp failed: No such file or directory
Sreyan>  dracut-initqueue[867]: WARNING: Check is skipped, please install recommended missing binary /usr/
Sreyan> sbin/thin_check!

Sreyan> In short my system has gone to hell.

Sreyan> This all started when I did a fstrim like this:

Sreyan> sudo fstrim -v /

Sreyan> And it returned an input/output error.

Sreyan> My logical volumes were marked with two 'XX', I don't know what that means. After that I
Sreyan> restarted.

Sreyan> What can I do to get my system back to normal ?

Sreyan> Please help.

Sreyan> --
Sreyan> Regards,
Sreyan> Sreyan Chakravarty

Sreyan> _______________________________________________
Sreyan> linux-lvm mailing list
Sreyan> linux-lvm@redhat.com
Sreyan> https://www.redhat.com/mailman/listinfo/linux-lvm
Sreyan> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/