Sponsored Content
Operating Systems Solaris How to use live-upgrade with single disk, pre-patching steps? Post 303033811 by solaris_1977 on Thursday 11th of April 2019 11:05:11 PM
Old 04-12-2019
Quote:
Originally Posted by solaris_1977
I was reading few posts and I think this could work
Code:
lucreate -c oldBE -n new-zfsBE

And then I can run patch set on new-zfsBE
All my zones are residing on rpool, as there is only one pool, so I will have option to revert to old environment, including all zones.
I am yet to test this.
*****UPDATE*****
I was able to create new-zfsBE on same disk and install patchset on that BE. After completion, I activated that and rebooted (with init 6) and all was good.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Typical steps to be followed while applying an application patch upgrade on linux

what are the typical steps used by system adminstrators while applying an application patch upgrade (1 Reply)
Discussion started by: ramky79
1 Replies

2. Solaris

Live Upgrade Patching Error: Unable to write vtoc

Attempting to patch several servers using live upgrade Release: Oracle Solaris 10 8/11 s10x_u10wos_17b X86 Error I'm receiving is in the message in the log below tail -15 /var/svc/log/rc6.log Legacy init script "/etc/rc0.d/K50pppd" exited with return code 0. Executing legacy init... (5 Replies)
Discussion started by: Siralos
5 Replies

3. Solaris

Help me with Pre Installation Steps for Patching on Solaris Servers

What are the Pre-installation steps for patching on Solaris servers in real time ? :confused: (6 Replies)
Discussion started by: vijaykrishna
6 Replies

4. Solaris

Solaris patching issue with Live Upgrade

I have Solaris-10 sparc box with ZFS file-system, which is running two non global zones. I am in process of applying Solaris Recommended patch cluster via Live Upgrade. Though I have enough space in root file-system of both zones, everytime I run installcluster, it fails with complaining less... (7 Replies)
Discussion started by: solaris_1977
7 Replies

5. Solaris

Live upgrade first steps

Hello Guys, I am a little confused about the first step in the live upgrade process. I will be glad if someone can clarify this for me. The pre-live upgrade patch, when do you add this patch to the OS you want to upgrade? 1. before creating the new boot environment? or 2. after creating... (1 Reply)
Discussion started by: cjashu
1 Replies

6. Solaris

Solaris 10 patching using live upgrade with VxVM

Hello, I was assigned some Solaris machines and need to patch them to N-1, where N is the latest OS realease, which means, upgrade till one version before the latest one. I do not now a lot about Solaris. What I only know is that need to make use of live upgrade and be careful with VxVM... (4 Replies)
Discussion started by: feroccimx
4 Replies

7. Solaris

Patching using live upgrade - with non-globalzone

Hi all, I would like to ask what will be the best practice for the following setup / - c0t0d0s0 - current BE (named First) / - c0t0d1s0 - alternate BE (name Second) i have a non-global zone with zonepath in /zones/myzone /mnt/opt - c0t0d2s6 (shared between the 2 BE)... (3 Replies)
Discussion started by: javanoob
3 Replies
GIT-QUILTIMPORT(1)						    Git Manual							GIT-QUILTIMPORT(1)

NAME
git-quiltimport - Applies a quilt patchset onto the current branch SYNOPSIS
git quiltimport [--dry-run | -n] [--author <author>] [--patches <dir>] [--series <file>] DESCRIPTION
Applies a quilt patchset onto the current Git branch, preserving the patch boundaries, patch order, and patch descriptions present in the quilt patchset. For each patch the code attempts to extract the author from the patch description. If that fails it falls back to the author specified with --author. If the --author flag was not given the patch description is displayed and the user is asked to interactively enter the author of the patch. If a subject is not found in the patch description the patch name is preserved as the 1 line subject in the Git description. OPTIONS
-n, --dry-run Walk through the patches in the series and warn if we cannot find all of the necessary information to commit a patch. At the time of this writing only missing author information is warned about. --author Author Name <Author Email> The author name and email address to use when no author information can be found in the patch description. --patches <dir> The directory to find the quilt patches. The default for the patch directory is patches or the value of the $QUILT_PATCHES environment variable. --series <file> The quilt series file. The default for the series file is <patches>/series or the value of the $QUILT_SERIES environment variable. GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-QUILTIMPORT(1)
All times are GMT -4. The time now is 07:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy