linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Sreyan Chakravarty <sreyan32@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] System completely unstable after migrating to thin pools
Date: Thu, 26 Nov 2020 20:15:10 +0530	[thread overview]
Message-ID: <CAMaziXtCk662ZfaG-crzrrKpi_efQqqOLbVCnSvLDsCOpLS0zw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2259 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 2959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 197 bytes --]

_______________________________________________
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/

             reply	other threads:[~2020-11-30  7:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 14:45 Sreyan Chakravarty [this message]
2020-11-30 22:24 ` John Stoffel
2020-12-01 14:25   ` Sreyan Chakravarty
2020-12-04 21:27     ` John Stoffel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMaziXtCk662ZfaG-crzrrKpi_efQqqOLbVCnSvLDsCOpLS0zw@mail.gmail.com \
    --to=sreyan32@gmail.com \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] System completely unstable after migrating to thin pools' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).