Hi,
I'm trying to get a Flash Archive Jumpstart Running with ZFS Filesystem. For Testing I set up a VirtualBox VM with 2 Disks attached. On the first disk I have the ZFS root pool, on the second Disk I have some more ZFS Pools which I use for 2 additional Zones I've set up. Restoring works fine if I just restore the Root pool since in the config File I can just mention the root pool, otherwise I get an error when booting saying something like multiple root pools are not allowed. Config looks like this:
When I add the line
I get the following error when restoring:
Error: Field 1 - Multiple root pool keywords not allowed
Solaris Installation Program exited
Is there any way to do the Flash Archive Jumpstart with attitional Zones?
Last edited by MadeInGermany; 02-22-2018 at 02:20 PM..
Reason: added code tags
Ladies and Gentlemen:
I am short on time and need to get up to speed fast on the use of flash archives. I am very familiar with Jumpstart and have used it successfully for the past 5 years. The current project I am working on requires optimization of time and speed when deploying systems which is... (0 Replies)
I get following error while doing a flash installation. I 'm trying to deploy a flash archive created by our engineering team. I 'm trying to install it with ZFS root and the profile which i using is as following
#more flash_profile_test
install_type flash_install
archive_location nfs... (3 Replies)
Has ZFS root is being supported in flash archive in the recently released update 7 .. i read a specific patch has been released for this , can anyone let me know that , and have anybody tested it if its working fine or not ? (1 Reply)
Hi,
Can anyone explains me the difference between solaris flash archive and jumpstart installation. Both are used to install many systems frm a centralized location , correct me if am wrong,.
Clear view on this is really appreciable. Thanks in advance (3 Replies)
I have created a flash archive from a Ldom on T5220 with zfs root solaris 10_u8. But after creation of flar the info shows the
content_architectures=sun4c,sun4d,sun4m,sun4u,sun4us,sun4s
but not sun4v due to which i 'm unable to install this flash archive on another Ldom on the same host. Is... (0 Replies)
Hi All!
I have been tasked with creating a clustered file system for two systems running Sol 10 u8. These systems have 3 zones each and the global zone has ZFS on the boot disk. We currently have one system sharing an NFS mount to both of these systems.
The root zfs pool status (on the... (2 Replies)
Hi ,
I am facing this issue while restoring flash archive from jumpstart server.The image was aroung 9 gb (5.9 release) and we have restored the other images successfully bigger than this size to other machines we have never faced this issue .Please advice me on this issue .
Extracted 100 %... (0 Replies)
I am building a new server on sol10_X86.
I am new to ZFS, this will be one of the first systems to use it.
I would like to have /opt /usr and a /u01 as separate file systems from the main ZFS pool. I know that this goes against the basic idea of ZFS, but this is so I can restrict the size/usage... (1 Reply)
Discussion started by: robsonde
1 Replies
LEARN ABOUT PLAN9
poolbind
poolbind(1M)poolbind(1M)NAME
poolbind - bind processes, tasks, or projects or query binding of processes to resource pools
SYNOPSIS
/usr/sbin/poolbind -p poolname [ -i idtype] id...
/usr/sbin/poolbind -q pid...
/usr/sbin/poolbind -Q pid...
The poolbind command allows an authorized user to bind zones, projects, tasks, and processes to pools. It can also allow a user to query a
process to determine which pool the process is bound to.
The following options are supported:
-i idtype
This option, together with the idlist arguments, specifies one or more processes to which the poolbind command is to apply. The inter-
pretation of idlist depends on the value of idtype. The valid idtype arguments and corresponding interpretations of idlist are as fol-
lows:
pid
idlist is a list of process IDs. Binds the specified processes to the specified pool. This is the default behavior if no idtype is
specified.
taskid
idlist is a list of task IDs. Bind all processes within the list of task IDs to the specified pool.
projid
idlist is a list of project IDs. Bind all processes within the list of projects to the specified pool. Each project ID can be spec-
ified as either a project name or a numerical project ID. See project(4).
zoneid
idlist is a list of zone IDs. Bind all processes within the list of zones to the specified pool. Each zone ID can be specified as
either a zone name or a numerical zone ID. See zones(5).
-p poolname
Specifies the name of a pool to which the specified zone, project, tasks, or processes are to be bound.
-q pid ...
Queries the pool bindings for a given list of process IDs. If the collection of resources associated with the process does not corre-
spond to any currently existing pool, or if there are multiple pools with the set of resources that the process is bound to, the query
fails for that particular process ID.
-Q pid ...
Queries the resource bindings for a given list of process IDs. The resource bindings are each reported on a separate line.
Example 1: Binding All Processes
The following command binds all processes in projects 5 and 7 to the pool web_app:
example# /usr/sbin/poolbind -p web_app -i projid 5 7
Example 2: Binding the Running Shell
The following command binds the running shell to the pool web_app:
example# /usr/sbin/poolbind -p web_app $$
Example 3: Querying the Pool Bindings
The following command queries the bindings to verify that the shell is bound to the given pool:
example# /usr/sbin/poolbind -q $$
Example 4: Querying the Resource Bindings
The following command queries the bindings to verify that the shell is bound to the given resources:
example# /usr/sbin/poolbind -Q $$
The following exit values are returned:
0 Successful completion.
1 Requested operation could not be completed.
2 Invalid command line options were specified.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWpool |
+-----------------------------+-----------------------------+
|Interface Stability | See below. |
+-----------------------------+-----------------------------+
The invocation is Evolving. The output is Unstable.
pooladm(1M), poolcfg(1M), libpool(3LIB), project(4), attributes(5), zones(5)
System Administration Guide: N1 Grid Containers, Resource Management, and Solaris Zones
3 Feb 2005 poolbind(1M)