linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Perepechko <Andrew.Perepechko@sun.com>,
	linux-fsdevel@vger.kernel.org,
	Johann Lombardi <Johann.Lombardi@sun.com>,
	Zhiyong Landen tian <Zhiyong.Tian@sun.com>
Subject: Re: [PATCH] quota: additional range checks and mem_dqblk updates to handle 64-bit limits
Date: Fri, 07 Mar 2008 14:10:39 -0700	[thread overview]
Message-ID: <20080307211039.GC1881@webber.adilger.int> (raw)
In-Reply-To: <20080307160043.GA16967@duck.suse.cz>

On Mar 07, 2008  17:00 +0100, Jan Kara wrote:
> On Fri 07-03-08 03:29:29, Andrew Perepechko wrote:
>   Great, thanks. The patch is fine. Yesterday evening I got an idea, how to
> solve your problem with too low limits even easier. What we could do is to
> introduce a "block-limit-scale" and "inode-limit-scale" parameter to the
> quota info and we keep the rest of the file format the same. Now, the meaning
> of this parameter would simply be a unit in which space and inode limits
> are specified. When you have a filesystem where you'd like to set quotas
> over 4 TB, you probably don't want to specify limits with 1KB precision
> anyway... So you can just set scale to 1MB or even 16MB (giving you maximal
> limit of 64 PB) and 10000 files or so. This has two advantages - only a few
> trivial modifications to current kernel code, no change in quota file space
> usage. We could then provide a way to set this scale via setquota / edquota
> (which would have to convert the whole file but that should be no big deal).
>   What do you think about such solution? Would it fit your needs? Sorry,
> that I haven't through of this solution earlier...

I can't speak fully for Andrew, as he is one of our quota gurus, but my
thought is that there is a risk of introducing corruption into the quota
file while it is entirely being rewritten and the system crashes or is
rebooted because the admin is impatient if this takes a long time.

Moving to a second quota file is pretty safe, can be done incrementally
(i.e. check new file and then old file, if it exists) and allows a fallback
if the update fails in the middle.


Also, while the "scale" parameter has merit in allowing the upper limit
of quota to be changed, the problem still exists on how to measure the
actual quota usage in that case.  If we assume a scale of 1MB (which is
fine for Lustre, that is the minimum we grant quota to different servers
anyways :-) but some user is only consuming 100k of quota at a time, then
this will continually be rounded down to 0 quota usage...

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


  reply	other threads:[~2008-03-07 21:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  0:29 [PATCH] quota: additional range checks and mem_dqblk updates to handle 64-bit limits Andrew Perepechko
2008-03-07 16:00 ` Jan Kara
2008-03-07 21:10   ` Andreas Dilger [this message]
2008-03-10 14:54     ` Jan Kara
2008-03-08  0:56   ` Andrew Perepechko
2008-03-10 15:20     ` [PATCH] quota: additional range checks and mem_dqblk updates?to " Jan Kara
2008-03-10 22:46       ` Andrew Perepechko
2008-03-11  3:16       ` Zhiyong Landen tian
2008-03-10 16:28 ` [PATCH] quota: additional range checks and mem_dqblk updates to " Jan Kara
2008-03-10 21:25   ` Andrew Perepechko
2008-03-12 17:21     ` [PATCH] quota: additional range checks and mem_dqblk updates?to " Jan Kara
2008-03-12 22:35       ` Andrew Perepechko

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=20080307211039.GC1881@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=Andrew.Perepechko@sun.com \
    --cc=Johann.Lombardi@sun.com \
    --cc=Zhiyong.Tian@sun.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).