From: Alasdair G Kergon Subject: Re: Barriers still not passing on simple dm devices... Date: Thu, 9 Apr 2009 11:28:51 +0100 Message-ID: <20090409102851.GT5688@agk.fab.redhat.com> References: <20090325152751.GV27476@kernel.dk> <20090326084205.GG27476@kernel.dk> <20090331104933.GJ5178@kernel.dk> <20090403081131.GP5178@kernel.dk> <1239240440.11220.3.camel@think.oraclecorp.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1239240440.11220.3.camel@think.oraclecorp.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Chris Mason Cc: device-mapper development , ak@linux.intel.com, Mikulas Patocka , Linux Kernel Mailing List , Jens Axboe List-Id: dm-devel.ids On Wed, Apr 08, 2009 at 09:27:20PM -0400, Chris Mason wrote: > I'm afraid expecting barriers forever in the future isn't completely > compatible with dm or md. Both of these allow the storage to change > over time, and the filesystem needs to handle this without corruptions. The missing piece of the jigsaw is notification to upper layers *ahead* of such reconfigurations. (We have similar notification issues when devices are resized - the current approach is to leave the sysadmin responsible for co-ordinating changes through userspace.) Alasdair -- agk@redhat.com