Sponsored Content
Full Discussion: ZFS receive error
Operating Systems Solaris ZFS receive error Post 302912101 by jim mcnamara on Tuesday 5th of August 2014 09:41:23 PM
Old 08-05-2014
It is telling you this object
Code:
root/branch@snapshot

is from a filesystem with no parent e.g. / - the root directory. You cannot "fix" it AFAIK.

There are workarounds like clone.

Code:
zfs snapshot root/branch@snapshot  zfs clone root/branch@snapshot root/newbranch/


This copies the whole dataset from root/branch to root/newbranch # -> root/newbranch is the new dataset

Last edited by jim mcnamara; 08-05-2014 at 10:47 PM..
 

9 More Discussions You Might Find Interesting

1. Programming

Is it possible to receive emails from my computer?

Could someone help me receive emails sent to my ip address with a c program? (5 Replies)
Discussion started by: Errigour
5 Replies

2. UNIX for Dummies Questions & Answers

How to receive mails in unix .....

HI experts, By using mailx command i can send mails to any email id. and my DNS is like oper@xyz.com ..... but if someone replied to the mail sent earlier using mailx command. then how to recieve or view that mail ... Is dre any command to do the same ... Im working on some project and got... (7 Replies)
Discussion started by: ankitknit
7 Replies

3. Solaris

zfs send receive performance issues

I 'm trying to clone a zfs file system pool/u01 to a new file system called newpool/u01 using following commands zfs list zfs snapshot pool/u01@new zfs send pool/u01@new | zfs -F receive newpool/u01 Its a 100G file system snapshot and copied to same server on different pool and... (9 Replies)
Discussion started by: fugitive
9 Replies

4. Solaris

ZFS flash install "Unable to create Filesystem error"

Hi, I am trying to get an HPz420 workstation instaled (zfs root pool) via a jump-start server. I have a zfs image (from this workstation) the Solaris release is 10 1/13 update 11. I use a sparc U25 install server, upgraded to the same solaris build 10 1/13. This server is configured to install... (8 Replies)
Discussion started by: sc0rpie
8 Replies

5. Forum Support Area for Unregistered Users & Account Problems

Have yet to receive activation email

Good Afternoon, I attempted to register on this forum yesterday using the username 'DBirks', however I have yet to receive the required activation email. I have checked both my inbox and junk e-mail folder on my email client as well as on owa, but I have not seen any sign of it. I have... (1 Reply)
Discussion started by: Unregistered
1 Replies

6. Solaris

ERROR: ZFS pool <Pool_Name> does not support boot environments

Hello, I am a newbie to the world of Solaris. so please ignore if I make any silly point. Recently I was trying to migrate UFS file system to ZFS on Solaris 10 (x86 platform). I have followed standard procedures/documents available online ... (4 Replies)
Discussion started by: Kumar07
4 Replies

7. Solaris

Error trying to promote ZFS clone - what do I need to do to troubleshoot this?

Steps taken:- 1. Snapshot an existing ZFS filesystem. 2. Created clone from snapshot. 3. Updated files on cloned ZFS filesystem. 4. Snapshot of cloned ZFS filesystem. 5. Attempted to promote clone ZFS and get error message. See below. #zfs list -rt all /rpool/ai NAME ... (2 Replies)
Discussion started by: psychocandy
2 Replies

8. Solaris

Zfs send & receive with encryption - how to retrieve data?

Good morning everyone, I'm looking for some help to retrieve data in a scenario where I might have made a big mistake. I'm hoping to understand what I did wrong. My system is made of two Solaris 11 Express servers (old free version for evaluation). The first if for data and the second is... (7 Replies)
Discussion started by: rnd
7 Replies

9. UNIX for Beginners Questions & Answers

Can ping out but cannot receive

Hi there, I am able to ping google.com However, I am able to see like google.com (172.xx.xx.xx). When the ping is done, like 5 packet transmitted but zero packet recieved. How do I go about re-mediating it? (6 Replies)
Discussion started by: alvinoo
6 Replies
STG-BRANCH(1)							   StGit Manual 						     STG-BRANCH(1)

NAME
stg-branch - Branch operations: switch, list, create, rename, delete, ... SYNOPSIS
stg branch stg branch <branch> stg branch --list stg branch --create <new-branch> [<committish>] stg branch --clone [<new-branch>] stg branch --rename <old-name> <new-name> stg branch --protect [<branch>] stg branch --unprotect [<branch>] stg branch --delete [--force] <branch> stg branch --description=<description> [<branch>] DESCRIPTION
Create, clone, switch between, rename, or delete development branches within a git repository. stg branch Display the name of the current branch. stg branch <branch> Switch to the given branch. OPTIONS
-l, --list List each branch in the current repository, followed by its branch description (if any). The current branch is prefixed with >. Branches that have been initialized for StGit (with linkstg:init[]) are prefixed with s. Protected branches are prefixed with p. -c, --create Create (and switch to) a new branch. The new branch is already initialized as an StGit patch stack, so you do not have to run linkstg:init[] manually. If you give a committish argument, the new branch is based there; otherwise, it is based at the current HEAD. StGit will try to detect the branch off of which the new branch is forked, as well as the remote repository from which that parent branch is taken (if any), so that running linkstg:pull[] will automatically pull new commits from the correct branch. It will warn if it cannot guess the parent branch (e.g. if you do not specify a branch name as committish). --clone Clone the current branch, under the name <new-branch> if specified, or using the current branch's name plus a timestamp. The description of the new branch is set to tell it is a clone of the current branch. The parent information of the new branch is copied from the current branch. -r, --rename Rename an existing branch. -p, --protect Prevent StGit from modifying a branch -- either the current one, or one named on the command line. -u, --unprotect Allow StGit to modify a branch -- either the current one, or one named on the command line. This undoes the effect of an earlier stg branch --protect command. --delete Delete the named branch. If there are any patches left in the branch, StGit will refuse to delete it unless you give the --force flag. A protected branch cannot be deleted; it must be unprotected first (see --unprotect above). If you delete the current branch, you are switched to the "master" branch, if it exists. -d DESCRIPTION, --description DESCRIPTION Set the branch description. --force Force a delete when the series is not empty. STGIT
Part of the StGit suite - see linkman:stg[1] StGit 03/13/2012 STG-BRANCH(1)
All times are GMT -4. The time now is 03:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy