Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 24 Oct 2001 14:08:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 24 Oct 2001 14:08:38 -0400 Received: from green.csi.cam.ac.uk ([131.111.8.57]:55537 "EHLO green.csi.cam.ac.uk") by vger.kernel.org with ESMTP id ; Wed, 24 Oct 2001 14:08:19 -0400 Date: Wed, 24 Oct 2001 19:08:28 +0100 (BST) From: James Sutherland X-X-Sender: To: Rik van Riel cc: Jan Kara , Neil Brown , , Subject: Re: RFC - tree quotas for Linux (2.4.12, ext2) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 24 Oct 2001, Rik van Riel wrote: > On Wed, 24 Oct 2001, James Sutherland wrote: > > > Yep, you're right: you'd need to ascend the target directory tree, > > increasing the cumulative size all the way up, then do the move and > > decrement the old location's totals in the same way. All wrapped up in a > > transaction (on journalled FSs) or have fsck rebuild the totals on a dirty > > mount. Fairly clean and painless on a JFS, > > It's only clean and painless when you have infinite journal > space. When your filesystem's journal isn't big enough to > keep track of all the quota updates from an arbitrarily deep > directory tree, you're in big trouble. Good point. You should be able to do it in constant space, though: identify the directory being modified, and the "height" to which you have ascended so far. That'll allow you to back out or redo the transaction later, which is enough I think? James. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/