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

Sponsored Content

Operating Systems Solaris Error trying to promote ZFS clone - what do I need to do to troubleshoot this? Post 303014233 by Peasant on Wednesday 7th of March 2018 11:14:21 PM

03-08-2018

Moderator

Which is understandable.
You have created a clone of rpool/ai filesystem as a descendant filesystem of of rpool/ai filesystem.
While this is possible and working, you will not be able to promote that filesystem rpool/ai/my_new_ai_clone due to above condition.
But you will be able to use it as you see fit.

This will work, as you noticed :

Code:

somezpool/ai/filesystem1 # filesystem1 is mounted under /somezpool/ai/filesystem1 and contains data.
somezpool/ai/filesystem1@today # take snap
somezpool/ai/filesystem1_clone # create clone under somezpool/ai/filesystem1_clone

zfs promote of filesystem1_clone to filesystem1 will now work.

Do not confuse directories and filesystems in zfs.
zfs will create nested filesystems on top of each other and mount them like that due to mount point inheritance behavior.
/mypool -> zfs create mypool/dump/somefilesystem

Result :

A zfs filesystem mypool/dump/somefilesystem is created and mounted under /mypool/dump/somefilesystem, unless overridden with -o mountpoint=/some/other/mountpoint during zfs create command.

Of course, mountpoint can be changed anytime with zfs set, as long as nothing is accessing the mountpoint.

rollback/promotion/cloning of entire filesystem hierarchy (dataset) is not possible, only one filesystem at the time.
While snapshots, destroy and sending will work on entire dataset recursively if -r is ran against the parent dataset.

Hope that helps
Regards
Peasant.

Peasant

View Public Profile for Peasant

Find all posts by Peasant

5 More Discussions You Might Find Interesting

1. Solaris

Remove the zfs snapshot keeping the original volume and clone

I created a snapshot and subsequent clone of a zfs volume. But now i 'm not able to remove the snapshot it gives me following error zfs destroy newpool/ldom2/zdisk4@bootimg cannot destroy 'newpool/ldom2/zdisk4@bootimg': snapshot has dependent clones use '-R' to destroy the following...

2. AIX

troubleshoot

Dear friends, is there any kind of scripts that will damage aix than we can troubleshoot what was the reason :-) just for having fun :-)

3. UNIX for Dummies Questions & Answers

Help to troubleshoot and correct

Reference (to previous post title): Help_Beginner in Unix I need assistance in terms of troubleshooting this codes.Though it not complete for the required task,shedding of any idea will be appreciated. the information about the code is the thread referenced above Code: #!/bin/ksh touch...

4. Solaris

Repeated error - "se_hdlc: clone device must be attached before use" in /var/adm/messages

Below is the error being repeated on my Solaris 9 Sun-Fire-V890 machine. SAN team confirmed as everything is fine from their end. I did google and found that some people say its a known Oracle bug when you have Oracle 10G installed on your system but I kind of disagree with them. Please see below...

5. Solaris

ZFS receive error

trying to clone a zfs file system on the same system using zfs send -r root/branch@snapshot |zfs receive root/newbranch and get the following error :parent does not exist. How do I fix this?

LEARN ABOUT FREEBSD

zfsboot

ZFSBOOT(8)						    BSD System Manager's Manual 						ZFSBOOT(8)

NAME

     zfsboot -- bootcode for ZFS on BIOS-based computers

DESCRIPTION

     zfsboot is used on BIOS-based computers to boot from a filesystem in a ZFS pool.  zfsboot is installed in two parts on a disk or a partition
     used by a ZFS pool.  The first part, a single-sector starter boot block, is installed at the beginning of the disk or partition.  The second
     part, a main boot block, is installed at a special offset within the disk or partition.  Both areas are reserved by the ZFS on-disk specifi-
     cation for boot use.  If zfsboot is installed in a partition, then that partition should be made bootable using appropriate configuration and
     boot blocks described in boot(8).

BOOTING

     The zfsboot boot process is very similar to that of gptzfsboot(8).  One significant difference is that zfsboot does not currently support the
     GPT partitioning scheme.  Thus only whole disks and MBR partitions, traditionally referred to as slices, are probed for ZFS disk labels.  See
     the BUGS section in gptzfsboot(8) for some limitations of the MBR scheme support.

USAGE

     zfsboot supports all the same prompt and configuration file arguments as gptzfsboot(8).

FILES

     /boot/zfsboot  boot code binary
     /boot.config   parameters for the boot block (optional)
     /boot/config   alternative parameters for the boot block (optional)

EXAMPLES

     zfsboot is typically installed using dd(1).  To install zfsboot on the ada0 drive:

	   dd if=/boot/zfsboot of=/dev/ada0 count=1
	   dd if=/boot/zfsboot of=/dev/ada0 iseek=1 oseek=1024

     If the drive is currently in use, the GEOM safety will prevent writes and must be disabled before running the above commands:

	   sysctl kern.geom.debugflags=0x10

     zfsboot can also be installed in an MBR slice:

	   gpart create -s mbr ada0
	   gpart add -t freebsd ada0
	   gpart create -s BSD ada0s1
	   gpart bootcode -b /boot/boot0 ada0
	   gpart set -a active -i 1 ada0
	   dd if=/boot/zfsboot of=/dev/ada0s1 count=1
	   dd if=/boot/zfsboot of=/dev/ada0s1 iseek=1 oseek=1024

     Note that commands to create and populate a pool are not shown in the example above.

SEE ALSO

     dd(1), boot.config(5), boot(8), gptzfsboot(8), loader(8), zfsloader(8), zpool(8)

HISTORY

     zfsboot appeared in FreeBSD 7.3.

AUTHORS

     This manual page was written by Andriy Gapon <avg@FreeBSD.org>.

BUGS

     Installing zfsboot with dd(1) is a hack.  ZFS needs a command to properly install zfsboot onto a ZFS-controlled disk or partition.

BSD
								September 15, 2014							       BSD