From: Xen <list@xenhideout.nl>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] cache on SSD makes system unresponsive
Date: Fri, 20 Oct 2017 10:38:50 +0000 [thread overview]
Message-ID: <133a1f046bbd53375d8c1230b2c1660f@xenhideout.nl> (raw)
In-Reply-To: <62efc412-fd2b-5412-9de5-015dd8136bf2@member.fsf.org>
Oleg Cherkasov schreef op 20-10-2017 10:21:
> On 19. okt. 2017 20:13, Xen wrote:
>>
>> The main cause was a way too slow SSD but at the same time... that
>> sorta thing still shouldn't happen, locking up the entire system.
>>
>> I haven't had a chance to try again with a faster SSD.
>
> I have double checked with MegaRAID/CLI and all disks on that rig
> (including SSD ones of course) are SAS 6Gb/s both devices and links.
> My first thought about those SSDs was that those are slower than RAID5
> however it seems not the case.
>
> Could it be TRIMing issue because those are from 2012?
You mean that the SATA version is too low to interleave TRIMs with data
access?
Because I think that was the case with my mSata SSD.
I don't currently remember the sata version that allowed interleaving
but that SSD didn't reach or have it.
After trimming performance would go up greatly.
So I don't know about SAS but it might be similar right.
next prev parent reply other threads:[~2017-10-20 10:38 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 [this message]
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
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=133a1f046bbd53375d8c1230b2c1660f@xenhideout.nl \
--to=list@xenhideout.nl \
--cc=linux-lvm@redhat.com \
/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).