- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Moving one share to another with cp --reflink
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Moving one share to another with cp --reflink
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Moving one share to another with cp --reflink
I have done it, though I did delete the file(s) from the original location before I destroyed the volume. It may not have been necessary (really shouldn't be), but I thought it best to do so.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Moving one share to another with cp --reflink
@ipb_uk wrote:
that there are a few arguments that can be add to cp -reflink, but what are they and which do I need?
just -r (recursive) and -p (preserve). BTW, you need --reflink, not -reflink.
@ipb_uk wrote:
Any other thoughts?
Snapshots won't be copied, so you will lose them when you destroy the original share.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Moving one share to another with cp --reflink
@StephenB wrote:
@ipb_uk wrote:
that there are a few arguments that can be add to cp -reflink, but what are they and which do I need?
Doh! Blimey Ian two typos in one line. I'll have a serious talk with my fingers!
Take two " added to cp --reflink".
Anyway lets see if I can get my finger working right (yep I'm embarrassed).
I did find --reflink=always & --reflink=auto. Which prompted my question. Are there more? Do i even need these switches? And what is the difference? As I'm not sure what the help file meant.
"When --reflink[=always] is specified, perform a lightweight copy, where the
data blocks are copied only when modified. If this is not possible the copy
fails, or if --reflink=auto is specified, fall back to a standard copy."
I'll give it a go tonight without any arguments added, on a small folder.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Moving one share to another with cp --reflink
@ipb_uk wrote:
"When --reflink[=always] is specified, perform a lightweight copy, where the
data blocks are copied only when modified. If this is not possible the copy
fails, or if --reflink=auto is specified, fall back to a standard copy."
I've always entered --reflink w/o the parameter. I believe it defaults to auto (which is what you want), but explicitly using--reflink=auto should be fine.
Make sure that Copy-on-Write is enabled on both the source and destination shares before you do the copy.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content