From: Alex Tomas Subject: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation) Date: Thu, 16 Aug 2007 22:20:06 +0400 Message-ID: <46C49556.4000409@clusterfs.com> References: <1177660767.6567.41.camel@Homer.simpson.net> <20070427013350.d0d7ac38.akpm@linux-foundation.org> <698310e10704270459t7663d39dp977cf055b8db9d2a@mail.gmail.com> <20070427193130.GD5967@schatzie.adilger.int> <20070427151837.f1439639.akpm@linux-foundation.org> <463A1E02.8020506@clusterfs.com> <20070503165428.855eb7d7.akpm@linux-foundation.org> <463AD024.6060208@clusterfs.com> <20070503233804.9dace4a7.akpm@linux-foundation.org> <463AD948.9090103@clusterfs.com> <20070504001802.0e86e9dd.akpm@linux-foundation.org> <463AE32A.5000902@clusterfs.com> <20070504010212.ce6eca53.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "linux-ext4@vger.kernel.org" To: Andrew Morton Return-path: Received: from mail.rialcom.ru ([80.71.244.250]:41225 "EHLO mail.rialcom.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753292AbXHPSdb (ORCPT ); Thu, 16 Aug 2007 14:33:31 -0400 In-Reply-To: <20070504010212.ce6eca53.akpm@linux-foundation.org> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Andrew Morton wrote: >>> But under this proposal, t_sync_datalist just gets removed: the new >>> ordered-data mode _only_ need to do the sb->inode->page walk. So if I'm >>> understanding you, the way in which we'd handle any such race is to make >>> kjournald's writeback of the dirty pages block in lock_page(). Once it >>> gets the page lock it can look to see if some other thread has mapped the >>> page to disk. >> if I'm right holding number of pages locked, then they won't be locked, but >> writeback. of course kjournald can block on writeback as well, but how does >> it find pages with *newly allocated* blocks only? > > I don't think we'd want kjournald to do that. Even if a page was dirtied > by an overwrite, we'd want to write it back during commit, just from a > quality-of-implementation point of view. If we were to leave these pages > unwritten during commit then a post-recovery file could have a mix of > up-to-five-second-old data and up-to-30-seconds-old data. trying to implement this I've got to think that there is one significant difference between t_sync_datalist and sb->inode->page walk: t_sync_datalist is per-transaction. IOW, it doesn't change once transaction is closed. in contrast, nothing (currently) would prevent others to modify pages while commit is in progress. I think this is serious disadvantage of the solution. what I'd propose is sort of in-core tracker for all data-related IOs in flight (assigned to specific transaction) and wait for their completion in commit thread. thanks, Alex