Sponsored Content
Operating Systems Solaris Error trying to promote ZFS clone - what do I need to do to troubleshoot this? Post 303014207 by psychocandy on Wednesday 7th of March 2018 09:06:01 AM
Old 03-07-2018
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.


Code:
 #zfs list -rt all /rpool/ai 
 NAME                         USED  AVAIL  REFER  MOUNTPOINT 
 rpool/ai                    28.2G  26.3G  19.3G  /rpool/ai 
 rpool/ai@aisnap               54K      -  19.3G  - 
 rpool/ai/aiclone            8.98G  26.3G  27.2G  /rpool/ai/aiclone 
 rpool/ai/aiclone@clonesnap      0      -  27.2G  - 
 rpool/ai/aiclone%               -      -      -  /rpool/ai/aiclone

Code:
# zfs promote rpool/ai/aiclone 
 cannot determine dependent datasets: recursive dependency at 'rpool/ai'

Moderator's Comments:
Mod Comment Please use code tags


---------- Post updated at 09:06 AM ---------- Previous update was at 06:07 AM ----------

Ah doesnt work if you create a clone that is sub-directory of the existing one. i.e. rpool/ai/clone from rpool/ai. Only works if you use /rpool/aiclone.

Last edited by jim mcnamara; 03-07-2018 at 08:23 AM..
 

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... (7 Replies)
Discussion started by: fugitive
7 Replies

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 :-) (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies

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... (1 Reply)
Discussion started by: moraks007
1 Replies

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... (2 Replies)
Discussion started by: vikkash
2 Replies

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? (1 Reply)
Discussion started by: os2mac
1 Replies
reboot(1M)						  System Administration Commands						reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] /usr/sbin/reboot [-f [-e environment]] [-dlnq] [boot_arguments] DESCRIPTION
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. On x86 systems, when the -f flag is specified, the running kernel will load the next kernel into memory, then transfer control to the newly loaded kernel. This form of reboot is shown in the second synopsis, above. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On x86 systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. OPTIONS
The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -e If -f is present, reboot to the specified boot environment. -f Fast reboot, bypassing firmware and boot loader. The new kernel will be loaded into memory by the running kernel, and control will be transferred to the newly loaded kernel. If disk or kernel arguments are specified, they must be specified before other boot arguments. This option is currently available only on x86 systems. See EXAMPLES for details. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. OPERANDS
The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list. EXAMPLES
Example 1 Passing the -r and -v Arguments to boot In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M). example# reboot -dl -- -rv Example 2 Rebooting Using a Specific Disk and Kernel The following example reboots using a specific disk and kernel. example# reboot disk1 kernel.test/unix Example 3 Fast Rebooting The following examples use the f option to perform fast reboots. The following command reboots to the same kernel. example# reboot -f The following command reboots to another UFS root disk. example# reboot -f -- '/dev/dsk/c1d0s0' The following command reboots to another ZFS root pool. example# reboot -f -- 'rpool/ROOT/root2' The following command reboots to mykernel on the same disk with -k option. example# reboot -f -- '/platform/i86pc/mykernel/amd64/unix -k' The following command reboots to mykernel off another root disk mounted on /mnt. example# reboot -f -- '/mnt/platform/i86pc/mykernel/amd64/unix -k' The following command reboots to /platform/i86pc/kernel/$ISADIR/unix on another boot environment named second_root. example# reboot -f -e second_root The following command reboots to the same kernel with -kv options. example# reboot -f -- '-kv' FILES
/var/adm/wtmpx login accounting file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2), reboot(3C), attributes(5) NOTES
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system. SunOS 5.11 29 Sep 2008 reboot(1M)
All times are GMT -4. The time now is 05:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy