public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Saravanan Shanmugham (sarvi)" <sarvi@cisco.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: Snapshot/Cloned workspace with changed file/directory ownership for all files in clone
Date: Fri, 1 May 2020 11:25:48 -0700	[thread overview]
Message-ID: <20200501182548.GZ6742@magnolia> (raw)
In-Reply-To: <DE682B09-7215-41EB-9D1F-25BFB41410E5@cisco.com>

On Fri, May 01, 2020 at 05:40:45PM +0000, Saravanan Shanmugham (sarvi) wrote:
> One use case for "cloned" workspaces or "seeded" workspaces, is "prebuilt workspaces" for very large builds.
> 
> What would it take to add this capability to the xfs roadmap? This would be very usefull.
> 
> Our use case is as following
>    1. Our fully built software build workspaces can be 800GB+
>    2. We have a nightly build that builds the whole workspace 800GB, done by a generic user "buildusr"
>    3. We then snapshot that workspace with xfs snapshotting capability.

What xfs snapshotting 'capability' is that?

Or, since you've already asked this on the btrfs list, chown -R the
directory tree after you receive the fs image from the build system.

(Maybe the answer you want is shiftfs...)

--D

>    3. We want the developer, "sarvi", to be able to clone from that snapshot and be able to incremental software build and development in the cloned workspace or the seeded filesystem/workspace.
> 
> Problem: 
> All the content, files, directories in the cloned workspace are still owned by "buildusr" and not "sarvi", which causes my builds to fail with permission problems.
> Is there anything in xfs that can help. 
> For that matter any of the open source filesystems support seeding or snapshot/cloning that you might be aware of.
> 
> So far the only filesystem that seems have the capability map/change the file ownership as part of the clone operation is Netapp. 
> And unfortunately that isn’t open source and wont serve our purpose.
> 
>  
> Thanks,
> Sarvi
> Occam’s Razor Rules
> 

      reply	other threads:[~2020-05-01 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 17:40 Snapshot/Cloned workspace with changed file/directory ownership for all files in clone Saravanan Shanmugham (sarvi)
2020-05-01 18:25 ` Darrick J. Wong [this message]

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=20200501182548.GZ6742@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@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