From: Theodore Ts'o Subject: Re: A warning from 3.6+ with bigalloc and delalloc when running xfstest Date: Sat, 13 Oct 2012 22:18:34 -0400 Message-ID: <20121014021834.GA4418@thunk.org> References: <20121009054820.GA8028@thunk.org> <20121009062931.GA29314@gmail.com> <20121009135152.GA29156@thunk.org> <20121011155708.GA9480@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-ext4@vger.kernel.org To: Andrey Sidorov Return-path: Received: from li9-11.members.linode.com ([67.18.176.11]:55435 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753737Ab2JNOlw (ORCPT ); Sun, 14 Oct 2012 10:41:52 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On Sat, Oct 13, 2012 at 02:29:48PM -0400, Andrey Sidorov wrote: > I didn't see it as well, but wanted to be sure it won't break file > system once occurred. > Our use-case is mostly dio and pre-fallocated writes, so I think we'll be fine. > Thanks! Yes, that will work just fine. That in fact was the use case I was primarily interested in when I did the bigalloc work. The main weaknesses come from using buffered writes with delayed allocation and when the disk is almost full. - Ted