From: Andrei Borzenkov <arvidjaar@gmail.com>
To: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Change of Ownership of the filesystem content when cloning a volume
Date: Sat, 10 Mar 2018 08:48:02 +0300 [thread overview]
Message-ID: <5c0915bb-96bf-00a5-53d9-c511de8ed4b3@gmail.com> (raw)
In-Reply-To: <DD5148B6-42C8-4598-A1E5-D652C6CF10E1@cisco.com>
10.03.2018 02:13, Saravanan Shanmugham (sarvi) пишет:
>
> Netapp’s storage system, has the concept of snapshot/clones.
> And when I create a clone from a snapshot, I can give/change ownership of entire tree in the volume to a different userid.
You are probably mistaken. NetApp FlexClone (which you probably mean)
does not have any ways to change volume content. Of course you can now
mount this clone and do whatever you like from host, but that is
completely unrelated to NetApp itself and can just as well be done using
btrfs subvolume.
>
> Is something like that possible in BTRFS?
>
> We are looking to use CopyOnWrite to snapshot nightly build workspace and clone as developer workspaces to avoid building from scratch for developers,
> And move directly for incremental builds.
> For this we would like the clone workspace/volume to be instantly owned by the developer cloning the workspace.
>
> Thanks,
> Sarvi
> -----
> Occam's Razor Rules
>
>
> N�����r��y���b�X��ǧv�^�){.n�+����{�n�߲)���w*\x1fjg���\x1e�����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a��\x7f��\x1e�G���h�\x0f�j:+v���w�٥
>
next prev parent reply other threads:[~2018-03-10 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 23:13 Change of Ownership of the filesystem content when cloning a volume Saravanan Shanmugham (sarvi)
2018-03-10 5:48 ` Andrei Borzenkov [this message]
2018-03-10 14:57 ` Saravanan Shanmugham (sarvi)
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=5c0915bb-96bf-00a5-53d9-c511de8ed4b3@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sarvi@cisco.com \
/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