From: Christoph Hellwig <hch@infradead.org>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 4/5] ext4: add isolated project support
Date: Thu, 11 Mar 2010 07:07:47 -0500 [thread overview]
Message-ID: <20100311120747.GD4706@infradead.org> (raw)
In-Reply-To: <1267727677-11956-5-git-send-email-dmonakhov@openvz.org>
On Thu, Mar 04, 2010 at 09:34:36PM +0300, Dmitry Monakhov wrote:
> PROJECT_ISOLATION
> This feature allows to create an isolated project subtrees.
> Isolation means what:
> 1) directory subtree has no common inodes (no hadlinks across subtrees)
> 2) All descendants belongs to the same subtree.
>
> Project subtree's isolation assumptions:
> 1)Inode can not belongs to different subtree trees
> Otherwise changes in one subtree result in changes in other subtree
> which contradict to isolation criteria.
>
> *Usage*
> We already has bind mounts which prevent link/remount across mounts.
> But if user has isolated project which consists of several subtrees
> and he want link/renames to work between subtrees(but in one project)
>
> Since this feature is non obvious it controlled by mount option.
Making this a mount option is even more non-obvious. Unless you have
very good reason to support both and not just stick to the existing
"isolated" semantics make it a chattr option so we can easily check
out what kind of subtree we deal with.
next prev parent reply other threads:[~2010-03-11 12:07 UTC|newest]
Thread overview: 22+ 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 [this message]
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
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
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=20100311120747.GD4706@infradead.org \
--to=hch@infradead.org \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--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 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.