From: "J. Bruce Fields" <bfields@fieldses.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: tytso@mit.edu, Andreas Dilger <adilger@sun.com>,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem
Date: Fri, 12 Mar 2010 15:07:29 -0500 [thread overview]
Message-ID: <20100312200728.GA13448@fieldses.org> (raw)
In-Reply-To: <87pr39evhi.fsf@openvz.org>
On Fri, Mar 12, 2010 at 12:32:09PM +0300, Dmitry Monakhov wrote:
> tytso@mit.edu writes:
>
> > On Thu, Mar 11, 2010 at 12:54:46PM -0700, Andreas Dilger wrote:
> >> A second possibility (if there is really no desire to have more than
> >> a single project ID per inode) is to add a field to the "large"
> >> inode for ext4, though that doesn't help filesystems that were not
> >> formatted that way, and it also consumes space in all inodes even if
> >> this feature is not used.
> >
> > The big question that I'm still uncertain about is how often are
> > people going to be using this feature, and how many project ID's do we
> > really need? I know Dimitry believes this is going to be the greatest
> > thing since sliced bread, but even for people running virtualization,
> > I'm not sure how many folks really will consider it critical.
> Most of our customers (hosting providers) use quota, otherwise
> it is impossible to restrict disk usage. Currently they have to
> perform full quotecheck after power failure. Which result in huge
> service down time. If we able to use journalled quota all problems
> will be solved.
> Also NFS people was interesting in projectid feature. They want to
> use it for creating safe file-handles.
> http://marc.info/?l=linux-fsdevel&m=126634832431306&w=2
By the way, have you looked at all at what it would take to be able to
encode and decode filehandles with projectid's in them?
--b.
next prev parent reply other threads:[~2010-03-12 20:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 18:34 [PATCH 0/5] RFC: introduce extended inode owner identifier v5 Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 1/5] vfs: Add additional owner identifier Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 2/5] quota: Implement project id support for generic quota Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 4/5] ext4: add isolated project support Dmitry Monakhov
2010-03-04 18:34 ` [PATCH 5/5] ext4: add project quota support Dmitry Monakhov
2010-03-04 20:07 ` [PATCH 4/5] ext4: add isolated project support Jan Kara
2010-03-04 20:34 ` Dmitry Monakhov
2010-03-11 12:07 ` Christoph Hellwig
2010-03-11 12:06 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Christoph Hellwig
2010-03-11 13:30 ` Dmitry Monakhov
2010-03-11 19:54 ` Andreas Dilger
2010-03-11 22:01 ` tytso
2010-03-12 9:32 ` Dmitry Monakhov
2010-03-12 20:07 ` J. Bruce Fields [this message]
2010-03-11 12:03 ` [PATCH 2/5] quota: Implement project id support for generic quota Christoph Hellwig
2010-03-11 13:17 ` Dmitry Monakhov
2010-03-11 12:01 ` [PATCH 1/5] vfs: Add additional owner identifier Christoph Hellwig
2010-03-11 13:11 ` Dmitry Monakhov
2010-03-11 18:51 ` J. Bruce Fields
2010-03-11 19:40 ` Andreas Dilger
2010-03-12 8:47 ` Dmitry Monakhov
-- strict thread matches above, loose matches on Subject: below --
2010-03-18 14:02 [PATCH 0/5] RFC: introduce extended inode owner identifier v6 Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 1/5] vfs: Add additional owner identifier Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 2/5] quota: Implement project id support for generic quota Dmitry Monakhov
2010-03-18 14:02 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2010-03-18 21:25 ` Andreas Dilger
2010-03-19 8:16 ` Dmitry Monakhov
2012-06-21 9:08 [PATCH 0/5] RFC: introduce extended inode owner identifier v9 Dmitry Monakhov
2012-06-21 9:08 ` [PATCH 3/5] ext4: Implement project ID support for ext4 filesystem Dmitry Monakhov
2012-06-21 23:51 ` Jan Kara
2012-07-03 18:46 ` Dmitry Monakhov
2012-06-22 3:07 ` Dave Chinner
2012-06-28 10:16 ` Jan Kara
2012-07-03 19:11 ` Dmitry Monakhov
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=20100312200728.GA13448@fieldses.org \
--to=bfields@fieldses.org \
--cc=adilger@sun.com \
--cc=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).