BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Thin Provisioned LVM
- Subject: [Discuss] Thin Provisioned LVM
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- Date: Wed, 11 Mar 2015 15:04:55 -0400
- In-reply-to: <55007E04.2030601@gmail.com>
- References: <9add572f6d172df6ae1d292b42ee10b6.squirrel@mail.mohawksoft.com> <54FF4556.5040107@gmail.com> <dfce4b3cdeafb3342a1b505319cf3683.squirrel@mail.mohawksoft.com> <55005473.2030908@gmail.com> <2a0abeb4977f9dec804ba8215393e8dd.squirrel@mail.mohawksoft.com> <55007E04.2030601@gmail.com>
> On 3/11/2015 1:13 PM, markw at mohawksoft.com wrote: >> Yes, please, oh please, put some links that describe "best practices" >> that >> address my "complaints" as there are none that anyone I have ever known > > http://lmgtfy.com/?q=zfs+best+practices+memory > http://lmgtfy.com/?q=zfs+best+practices+database > http://lmgtfy.com/?q=zfs+best+practices+sparse+volumes Again, like I said, these do not address the problems. Specifically, the post about sparse volumes says nothing about how to keep a ZFS pool from growing out of control on a sparse presented to it from a SAN. It merely says give ZFS whole disks, which is stupid. The performance "best practice" show how to improve performance on ZFS, but not how to make the performance on ZFS equivalent to much thinner volume management. ZFS has a lot of good qualities for a number of applications, but it is just bad for a lot of other applications. > > Was that so hard? Yes, because it didn't have any usable information. > > -- > Rich P. > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://lists.blu.org/mailman/listinfo/discuss >
- Follow-Ups:
- [Discuss] Thin Provisioned LVM
- From: hag at linnaean.org (Daniel Hagerty)
- [Discuss] Thin Provisioned LVM
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] Thin Provisioned LVM
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Thin Provisioned LVM
- References:
- [Discuss] Thin Provisioned LVM
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] Thin Provisioned LVM
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Thin Provisioned LVM
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] Thin Provisioned LVM
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Thin Provisioned LVM
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] Thin Provisioned LVM
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Thin Provisioned LVM
- Prev by Date: [Discuss] pulse files in /tmp on RHEL 6
- Next by Date: [Discuss] pulse files in /tmp on RHEL 6
- Previous by thread: [Discuss] Thin Provisioned LVM
- Next by thread: [Discuss] Thin Provisioned LVM
- Index(es):