10-25-2013
10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I am attempting to install a newly configured Solaris 9 zone using the flash archive image provided on the sun website. Each time I run the install I get a failure during the Postprocess: Creating mount points. Following is the log:
Log File: /var/tmp/s9-zone.install.25457.log... (0 Replies)
Discussion started by: brialt1
0 Replies
2. Solaris
Hi guys.
We have filesystems resources taken from tha NAS nettap ; but the filesystem inside the solaris zone with some frecuency is unable.This filesystems are critical and we need constantly remount them.
Someone know if there are problems with the NFS resources in zones?
Where are... (3 Replies)
Discussion started by: aggadtech08
3 Replies
3. Solaris
1. i read that VxFS (3.x) installed on a solaris 8 will not work on a branded zone. fair enough, but what is the impact of having the packages installed when the flarcreate is done? will the container fail to boot with those packages installed?
2. NTP client and server doesnt work on branded... (11 Replies)
Discussion started by: frustin
11 Replies
4. Solaris
Dear all,
we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message:
***The image patch level is downrev for running in a solaris10 branded zone***
The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed.
Does the... (0 Replies)
Discussion started by: xunil321
0 Replies
5. Solaris
I have a T5220 running Solaris 10. I have a application that can only run on Solaris 9. I want to build a branded Solaris 9 zone for this application on the Solaris 10 Server.
What steps would I need to accomplish this? (2 Replies)
Discussion started by: soupbone38
2 Replies
6. Solaris
I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate.
#zonecfg -z <device>
>create -b
>set brand=solaris10
>set zonepath=/zonez/<device>
>set ip-type=exclusive
>add net... (1 Reply)
Discussion started by: aeroforce
1 Replies
7. Solaris
All.
I am trying to create a 10 branded zone on a Sol 11.1 T5. The Global is using IPMP...so aggregating is out of the question. Has anyone successfully created a branded zone with IPMP? If they have can you please show me the steps you took to get this to run.
Thanks (4 Replies)
Discussion started by: aeroforce
4 Replies
8. Solaris
Hi,
I want to install branded zone sol 9 in sol 10. I keep getting same error. Please advice me.
Thanks. (12 Replies)
Discussion started by: mzainal
12 Replies
9. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
10. Solaris
So I started with following the example on the omnios page for bhyve (sorry, I can't provide the link because I'm a post shy of the 5 to give a URL):
And found that in the end I was able to create a running bhyve zone, but accessing it via zlogin results in a blank console. I've tried Debian 9... (14 Replies)
Discussion started by: stratacast1
14 Replies
nfsd(8) System Manager's Manual nfsd(8)
NAME
nfsd - The remote NFS compatible server
SYNOPSIS
/usr/sbin/nfsd [-t num_tcpthreads] [-u num_udpthreads]
The following form of the nfsd command is not recommended and is supported only for backward compatibility:
/usr/sbin/nfsd [numthreads]
FLAGS
Specifies a number of TCP server threads (per RAD) to spawn. A value of 8 is recommended as a start. Specifies a number of UDP server
threads (per RAD) to spawn. A value of 8 is recommended as a start.
DESCRIPTION
The nfsd daemon runs on a server machine to service NFS requests from client machines. The daemon spawns a number of server threads that
process NFS requests from client machines. At least one server thread must be running for a machine to operate as a server.
There are two types of server threads: a server thread that processes NFS requests sent using TCP and a server thread that processes NFS
requests sent using UDP. This is necessary because the kernel paths for UDP and TCP NFS messages are different. The -t option specifies
the number of TCP threads to run and the -u option specifies the number of UDP threads to run.
On systems that support Cache Coherent NUMA, the number of threads is per Resource Affinity Domain (RAD). As you add RADs, the NFS server
will automatically scale by creating additional threads. NFS requests are processed by a particular RAD based on the file being accessed;
this confines cached information about a file to a single RAD for efficiency. See numa_intro(3) for more information on the NUMA architec-
ture.
If you use the SysMan Menu to configure NFS, it sets the default at 8 UDP and 8 TCP threads. However, a user can have any number of TCP
and UDP nfsd threads running up to a maximum of 128 threads. The optimal number of TCP server threads and UDP server threads depends on
many factors. See nfsiod(8) for more information.
The server threads are implemented as kernel threads; they are part of Process ID 0, not the nfsd process. The ps axml command displays
idle server threads under PID 0. Idle threads will be waiting on nfs_udp_wait or nfs_tcp_wait. Therefore, if 16 server threads are config-
ured, only one nfsd process is displayed in the output from the ps command, although 16 server threads are available to handle NFS
requests.
Files that are larger than 2 gigabytes are exported as 2 gigabyte files when accessed by NFS Version 2. NFS Version 2 is a 32-bit proto-
col, therefore, the size and offset fields are 32-bit quantities (on Alpha UFS they are 64-bit quantities). Use caution when accessing
files larger than 2 gigabytes from NFS clients.
EXAMPLES
In the following example, 16 threads are run (8 for TCP and 8 for UDP): nfsd -t 8 -u 8
FILES
Specifies the command path Specifies the file for logging startup errors (before the server threads are started). Specifies the file for
logging NFS errors (after the server threads are started).
RELATED INFORMATION
Commands: mount(8), mountd(8), nfsconfig(8), nfsstat(8), portmap(8)
System calls: nfssvc(2) delim off
nfsd(8)