References: <4bcd585d099ecec086b99cfa5c23cc38@assyoma.it> <5739B848.3060505@redhat.com> <573B1812.3080802@assyoma.it> <573B213E.7060807@redhat.com> <573C726B.6020209@assyoma.it> <4d91c4c59b86f043d6a83772d8a8a2aa@assyoma.it> <323a1fe9-b750-51f3-2967-a2bdf53e259c@redhat.com> <1d48e462516f2836fd7ea96af5c9bb33@assyoma.it> From: Zdenek Kabelac Message-ID: <92b054dc-fb3b-17c9-cbd8-43f22020b7c9@gmail.com> Date: Tue, 24 May 2016 19:17:29 +0200 MIME-Version: 1.0 In-Reply-To: <1d48e462516f2836fd7ea96af5c9bb33@assyoma.it> Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] Unexptected filesytem unmount with thin provision and autoextend disabled - lvmetad crashed? 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"; format="flowed" To: LVM general discussion and development Cc: Zdenek Kabelac On 24.5.2016 16:28, Gionatan Danti wrote: > Il 24-05-2016 16:17 Zdenek Kabelac ha scritto: >> >> >> Dmeventd should not talk to lvmetad at all - I'm saying this for years.... >> >> There are some very very hard to fix (IMHO) design issues - and >> locking lvmetad in memory would be just one of wrong (IMHO) ways >> forward.... >> >> Anyway - let's see how it evolves here as there are further troubles >> with lvmetad & dmeventd - see i.e. here: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1339210 > > I'll follow it ;) > >> One more, somewhat related thing: when thin pool goes full, is a good >> thing to remount an ext3/4 in readonly mode (error=remount-ro). But >> what to do with XFS which, AFAIK, does not support a similar >> readonly-on-error policy? >> >> It is my understanding that upstream XFS has some improvements to >> auto-shutdown in case of write errors. Did these improvements already >> tickle to production kernels (eg: RHEL6 and 7)? > > Any thoughts/suggestions on that? Surely they are pushed ASAP when tests passes (upstream first policy here fully applies) So yes 6.8 has surely improvements. Regards Zdenek