03-09-2011
for the use of all, please state what the problem was...
10 More Discussions You Might Find Interesting
1. Solaris
Is it possible to create zfs pools and filesystems using the profile file in jumpstart?
edit to add: using Solaris 10 Release 11/06 (1 Reply)
Discussion started by: dangral
1 Replies
2. Solaris
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)
Discussion started by: fugitive
0 Replies
3. Solaris
I have created a solaris10 update9 zfs root flash archive for sun4v environment which i 'm tryin to use for upgrading solaris10 update8 zfs root based server using live upgrade.
following is my current system status
lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now... (0 Replies)
Discussion started by: fugitive
0 Replies
4. Solaris
Keep getting this message after system identification portion.
Search complete.
Discovering additional network configuration...
Completing system identification...
Starting remote procedure call (RPC) services:Assertion failed: *count <= max, file ns_dns_misc.c, line 189
Abort - core dumped... (0 Replies)
Discussion started by: soupbone38
0 Replies
5. Solaris
Has anyone tried Jumpstart with installing a ZFS root pool? I have read the docs (Custom Jumpstart and Advanced Install Guide(doc:821-1911);Network-Based Installations(doc:821-1909)).
My issue is that I get prompted for information each time I boot the client system. My goal is to get the... (8 Replies)
Discussion started by: bluescreen
8 Replies
6. Solaris
I jumpstarted a solaris sun4u box from WANboot and it completed but while coming up it gives following error and panics
Use is subject to license terms.
NOTICE: zfs_parse_bootfs: error 48
Cannot mount root on rpool/47 fstype zfs
panic/thread=180e000: vfs_mountroot: cannot mount root
... (0 Replies)
Discussion started by: fugitive
0 Replies
7. Solaris
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
8. Solaris
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies
9. Solaris
I've followed a few guides and have what appears to be a working jumpstart server. I can PXE boot a bare system, it gets an IP and launches the installer. However, it takes me to the screen:
SunOS Release 5.10 Version generic-147148-26 64 bit
Copyright (c) 1983, 2013, Oracle and/or its... (1 Reply)
Discussion started by: jnojr
1 Replies
10. Solaris
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... (1 Reply)
Discussion started by: NoelzeN
1 Replies
t_sync(3) Library Functions Manual t_sync(3)
NAME
t_sync() - synchronize transport library
SYNOPSIS
DESCRIPTION
For the transport endpoint specified by fd, the function synchronizes the data structures managed by the transport library with information
from the underlying transport provider. In doing so, it can convert an uninitialized file descriptor (obtained via or as a result of a and
to an initialized endpoint, assuming that the file descriptor referenced a transport endpoint, by updating and allocating the necessary
library data structures. This function also allows two cooperating processes to synchronize their interaction with a transport provider.
For example, if a process forks a new process and issues an the new process must issue a to build the private library data structure asso-
ciated with a transport endpoint and to synchronize the data structure with the relevant provider information.
It is important to remember that the transport provider treats all users of a transport endpoint as a single user. If multiple processes
are using the same endpoint, they should coordinate their activities so as not to violate the state of the transport endpoint. The func-
tion returns the current state of the transport endpoint to the user, thereby enabling the user to verify the state before taking further
action. This coordination is only valid among cooperating processes; it is possible that a process or an incoming event could change the
endpoint's state after a is issued.
If the transport endpoint is undergoing a state transition when is called, the function will fail.
Valid States
All - apart from
Fork Safety
is not fork-safe.
RETURN VALUE
returns the state of the transport connection endpoint on successful completion and -1 on failure, and is set to indicate the error. The
state returned is one of the following:
Unbound
Idle
Outgoing connection pending
Incoming connection pending
Data transfer
Outgoing orderly release (waiting for an orderly release indication)
Incoming orderly release (waiting for an orderly release request)
ERRORS
On failure, is set to one of the following:
[TBADF] The specified file descriptor does not refer to a transport endpoint. This error may be returned when the fd has been
previously closed or an erroneous number may have been passed to the call.
[TSTATECHNG] The transport endpoint is undergoing a state change.
[TSYSERR] A system error has occurred during execution of this function.
[TPROTO] (XTI only) This error indicates that a communication problem has been detected between XTI and the transport provider for
which there is no other suitable XTI (
SEE ALSO
t_open(3), t_getstate(3), dup(2), exec(2), fork(2), open(2), thread_safety(5).
STANDARDS CONFORMANCE
t_sync(3)