From: Bernd Eckenfels <ecki@zusammenkunft.net>
To: "linux-lvm@redhat.com" <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] cache on SSD makes system unresponsive
Date: Fri, 20 Oct 2017 17:02:05 +0000 [thread overview]
Message-ID: <AM4PR08MB1219C0524F7BEAC7575DD297FF430@AM4PR08MB1219.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <7ad2a4bffddffb25a1e90ba7e95af523@xenhideout.nl>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
Not sure if this is on-topic but there is a reason for software solutions. The days for super properties and faulty hardware is over. You put Software like lvm on top of mass market stupid hardware exactly to reduce complexity.
Gruss
Bernd
--
http://bernd.eckenfels.net
________________________________
From: linux-lvm-bounces@redhat.com <linux-lvm-bounces@redhat.com> on behalf of Xen <list@xenhideout.nl>
Sent: Friday, October 20, 2017 6:48:31 PM
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] cache on SSD makes system unresponsive
lejeczek schreef op 20-10-2017 16:20:
> I would - if bigger part of a storage subsystem resides in the
> hardware - stick to the hardware, use CacheCade, let the hardware do
> the lot.
In other words -- keep it simple (smart person) ;-).
Complicatedness is really the biggest reason for failure everywhere....
_______________________________________________
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/
[-- Attachment #2: Type: text/html, Size: 2386 bytes --]
next prev parent reply other threads:[~2017-10-20 17:02 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
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 [this message]
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=AM4PR08MB1219C0524F7BEAC7575DD297FF430@AM4PR08MB1219.eurprd08.prod.outlook.com \
--to=ecki@zusammenkunft.net \
--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).