From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 13 Mar 2014 23:35:13 -0400 From: Mike Snitzer Message-ID: <20140314033512.GA9754@redhat.com> References: <0c0501cf3e39$0e82e0f0$2b88a2d0$@acm.org> <20140312233505.GA1660@redhat.com> <20140313172025.GA6835@redhat.com> <0d2401cf3f2f$13648000$3a2d8000$@acm.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <0d2401cf3f2f$13648000$3a2d8000$@acm.org> Subject: Re: [linux-lvm] thinpool metadata size Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Paul B. Henson" Cc: Zdenek Kabelac , 'LVM general discussion and development' On Thu, Mar 13 2014 at 10:42pm -0400, Paul B. Henson wrote: > > From: Mike Snitzer > > Sent: Thursday, March 13, 2014 10:20 AM > > > > Yes, we're still unable to resize after metadata has been completely > > exhausted: > [...] > > Good news is online metadata resize works fine as long as metadata space > > hasn't been exhausted: > > Hmm, then it seems it would be wise to keep an eye on utilization ;). Looks > like there are some munin plug-ins for lvm, hopefully one of them already > has metadata usage support or can be easily extended. lvm2 should/could monitor for metadata low water mark threshold events, which the kernel will trigger, much like it does for data low water mark. But since the kernel internalizes the metadata low water mark I'm not sure if lvm2 has taken this on. Zdenek?