public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: jas88@cam.ac.uk, Rik van Riel <riel@conectiva.com.br>
Cc: Jan Kara <jack@suse.cz>, Neil Brown <neilb@cse.unsw.edu.au>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: RFC - tree quotas for Linux (2.4.12, ext2)
Date: Wed, 24 Oct 2001 13:44:27 -0500 (CDT)	[thread overview]
Message-ID: <200110241844.NAA32059@tomcat.admin.navo.hpc.mil> (raw)

James Sutherland <jas88@cam.ac.uk>:
> 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?

There still remains the problem of hard links... They could be counted
in two or more trees as long as two or more trees exist on one filesystem.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-10-24 18:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24 18:44 Jesse Pollard [this message]
2001-10-25  6:15 ` RFC - tree quotas for Linux (2.4.12, ext2) Albert D. Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2001-10-19  3:00 Toivo Pedaste
2001-10-19  4:39 ` Neil Brown
2001-10-18  5:06 Neil Brown
2001-10-18  5:53 ` Ben Greear
2001-10-18  8:38   ` James Sutherland
2001-10-18 20:20     ` Mike Fedyk
2001-10-18 20:47       ` Tim Walberg
2001-10-19  1:07         ` Neil Brown
2001-10-19  3:03           ` Rik van Riel
2001-10-19 11:50             ` Horst von Brand
2001-10-19 17:00               ` Mike Fedyk
2001-10-18 21:17       ` Andreas Dilger
2001-10-18 22:56         ` Mike Fedyk
2001-10-19  0:14           ` Horst von Brand
2001-10-19  0:51             ` Mike Fedyk
2001-10-19  1:13         ` Neil Brown
2001-10-19  0:53       ` Neil Brown
2001-10-24 15:16 ` Jan Kara
2001-10-24 15:34   ` James Sutherland
2001-10-24 15:39     ` Jan Kara
2001-10-24 15:50       ` James Sutherland
2001-10-24 17:41         ` Rik van Riel
2001-10-24 18:08           ` James Sutherland
2001-10-26 11:25     ` Pavel Machek
2001-10-24 21:24   ` Neil Brown
2001-10-25 15:48     ` Jan Kara
2001-10-26  4:36       ` Neil Brown
2001-10-29 14:06         ` Jan Kara
2001-10-29 23:23           ` Neil Brown
2001-10-30 12:33             ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200110241844.NAA32059@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=jack@suse.cz \
    --cc=jas88@cam.ac.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=riel@conectiva.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox