All of lore.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH,RFC] Adding quotacheck functionality to e2fsck
Date: Fri, 26 Mar 2010 09:38:56 -0400	[thread overview]
Message-ID: <20100326133856.GE21658@thunk.org> (raw)
In-Reply-To: <20100326104205.GA3055@quack.suse.cz>

On Fri, Mar 26, 2010 at 11:42:05AM +0100, Jan Kara wrote:
> > There may also be other programs that depend on the existence of
> > aquota.user, and may be reading and writing them in various random
> > ways, and there is the question of how do we provide compatibility
> > with these other programs, some of which may not be within quotatools,
> > but in various magic virtualization or container or cluster management
> > systems....
>   Yeah, this is possible, although I'm not aware of any such program -

Actually, Google's cluster management system is accessing/modifying
aquota.group file directly before and after quota is enabled.  This
may change in the future, but it's one more point of compatibility.

>   Yeah, I believe that support for the oldest quota format can be phased
> out - the new format is around for something like 10 years and it had
> it's problems at that time already. I guess I'll add a warning to the
> next release of quota-tools to the people still using it.

And if we transition to using quotactl calls to access and read the
information in the quota files, then the actual format of the quota
file won't matter any more, right?

Stupid question --- how does repquota work on OCFS2?  I don't see any
quotactl subcommands that would appear to return the functionality
needed by repquota --- unless you just assume that the only uid/gid's
in use are in /etc/passwd and /etc/group, and just call quotactl for
each uid/gid in the system passwd and group files.

     	     	    	   	      	    - Ted

  reply	other threads:[~2010-03-26 13:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26  0:20 [PATCH,RFC] Adding quotacheck functionality to e2fsck Theodore Ts'o
2010-03-26  0:47 ` Jan Kara
2010-03-26  3:38   ` tytso
2010-03-26  7:01     ` Andreas Dilger
2010-03-26  8:18       ` Dmitry Monakhov
2010-03-26 10:57         ` Jan Kara
2010-03-26 11:15           ` Dmitry Monakhov
2010-03-26 16:27             ` Dmitry Monakhov
2010-03-29  7:35               ` Jan Kara
2010-03-29  7:50                 ` dmonakhov
2010-03-26 10:54       ` Jan Kara
2010-03-26 13:51         ` tytso
2010-03-30  0:43           ` Jan Kara
2010-03-26 10:42     ` Jan Kara
2010-03-26 13:38       ` tytso [this message]
2010-03-30  0:55         ` Jan Kara
2010-03-30  5:26           ` Dmitry Monakhov
2010-03-30 12:42             ` Jan Kara
2010-03-26  8:09   ` Dmitry Monakhov
2010-03-26 11:00     ` Jan Kara
2010-03-26 13:55     ` tytso

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=20100326133856.GE21658@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.