From: Jan Kara <jack@suse.cz>
To: tytso@mit.edu
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH,RFC] Adding quotacheck functionality to e2fsck
Date: Tue, 30 Mar 2010 02:55:05 +0200 [thread overview]
Message-ID: <20100330005504.GJ5835@quack.suse.cz> (raw)
In-Reply-To: <20100326133856.GE21658@thunk.org>
On Fri 26-03-10 09:38:56, tytso@mit.edu wrote:
> 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.
I see. Thanks for info.
> > 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?
Yes, hopefully.
> 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.
Currently it does not work at all. I didn't get to writing it when
writing original quota support for OCFS2 because the inferface won't be
completely trivial and it would be complicated for OCFS2 to expose the
file directly. Probably the interface will have to be something like
readdir but then you have to have some "handles" and state associated
with them and it gets complicated. Maybe we could make our life simpler
by returning an read-only unseekable fd from repquota quotactl and reading
from it would pass quota structures. But I haven't thought too much about
it.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2010-03-30 0:54 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
2010-03-30 0:55 ` Jan Kara [this message]
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=20100330005504.GJ5835@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).