From: "John Stoffel" <john@stoffel.org>
To: Xen <list@xenhideout.nl>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] cache on SSD makes system unresponsive
Date: Thu, 19 Oct 2017 17:14:27 -0400 [thread overview]
Message-ID: <23017.5555.200654.218469@quad.stoffel.home> (raw)
In-Reply-To: <90cb544ffa100a862f503528ba5bf73f@xenhideout.nl>
>>>>> "Xen" == Xen <list@xenhideout.nl> writes:
Xen> John Stoffel schreef op 19-10-2017 21:09:
>> How did you setup your LVM config and your cache config? Did you
>> mirror the two SSDs using MD
Xen> He said he used hardware RAID to mirror the devices.
Ok, missed that. But still we need the LVM config info and details on
the system config to address these issues. I suspect he's not running
with any swap configured as well, and something is pushing the system
over the line. But it's hard to know.
Any output from 'dmesg' you can share? The more detailed the better.
>> I ask because I'm running lvcache at home on my main file/kvm server
>> and I've never seen this problem. But! I suspect you're running a
>> much older kernel, lvm config, etc.
Xen> lvm2-2.02.171-8.el7.x86_64
Xen> CentOS 7.4 was released a month ago.
And RHEL7.4/CentOS 7 is all based on kernel 3.14 (I think) with lots
of RedHat specific backports. So knowing the full details will only
help us provide help to him.
next prev parent reply other threads:[~2017-10-19 21:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 17:54 [linux-lvm] cache on SSD makes system unresponsive Oleg Cherkasov
2017-10-19 18:13 ` Xen
2017-10-20 10:21 ` Oleg Cherkasov
2017-10-20 10:38 ` Xen
2017-10-20 11:41 ` Oleg Cherkasov
2017-10-19 18:49 ` Mike Snitzer
2017-10-20 11:07 ` Joe Thornber
2017-10-19 19:09 ` John Stoffel
2017-10-19 19:46 ` Xen
2017-10-19 21:14 ` John Stoffel [this message]
2017-10-20 6:42 ` Xen
2017-10-19 21:59 ` Oleg Cherkasov
2017-10-20 19:35 ` John Stoffel
2017-10-21 3:05 ` Mike Snitzer
2017-10-21 14:33 ` Oleg Cherkasov
2017-10-23 10:58 ` Zdenek Kabelac
2017-10-21 2:55 ` Mike Snitzer
2017-10-21 14:10 ` Oleg Cherkasov
2017-10-23 20:45 ` John Stoffel
2017-10-20 16:20 ` lejeczek
2017-10-20 16:48 ` Xen
2017-10-20 17:02 ` Bernd Eckenfels
2017-10-24 14:51 ` lejeczek
[not found] <640472762.2746512.1508882485777.ref@mail.yahoo.com>
2017-10-24 22:01 ` matthew patton
2017-10-24 23:10 ` Chris Friesen
[not found] <1928541660.2031191.1508802005006.ref@mail.yahoo.com>
2017-10-23 23:40 ` matthew patton
2017-10-24 15:36 ` Xen
[not found] <1714773615.1945146.1508792555922.ref@mail.yahoo.com>
2017-10-23 21:02 ` matthew patton
2017-10-23 21:54 ` Xen
2017-10-24 2:51 ` John Stoffel
[not found] <1540708205.1077645.1508602122091.ref@mail.yahoo.com>
2017-10-21 16:08 ` matthew patton
[not found] <1244564108.1073508.1508601932111.ref@mail.yahoo.com>
2017-10-21 16:05 ` matthew patton
2017-10-24 18:09 ` Oleg Cherkasov
[not found] <541215543.377417.1508458336923.ref@mail.yahoo.com>
2017-10-20 0:12 ` matthew patton
2017-10-20 6:46 ` Xen
2017-10-20 9:59 ` Oleg Cherkasov
-- strict thread matches above, loose matches on Subject: below --
2017-10-19 10:05 Oleg Cherkasov
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=23017.5555.200654.218469@quad.stoffel.home \
--to=john@stoffel.org \
--cc=linux-lvm@redhat.com \
--cc=list@xenhideout.nl \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).