System completely unstable after migrating to thin pools

[Sreyan Chakravarty <sreyan32@xxxxxxxxx>]

Hi,

I have migrated to thin pools using partclone.

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

My swap is not activated :

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

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

My System logging service is not started:

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

And device mapper gives me weird messages during startup like:

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

Also some dracut module is missing:

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

In short my system has gone to hell.

This all started when I did a fstrim like this:

sudo fstrim -v /

And it returned an input/output error.

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

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

Please help.

--

Regards,

Sreyan Chakravarty

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