Question - zones / zonecfg

Thread Tools Search this Thread
Operating Systems Solaris Question - zones / zonecfg
# 1  
Old 08-05-2009
Question - zones / zonecfg

Hi all

Can someone give me a quick `simple man` run down on the various FS types / paramters which you need to configure.

E.g. special, raw, match, type

I understand raw, the raw filesystem, type is the lofs, zfs,ufs, but match ? special ?

When would you use lofs, over ufs filesystem types ? Ok for cdroms, or drives other zones may want to also see.

What is the best practise of presenting SAN storage to zones ? Do I mount them in the Global Zone and then lofs them int oa zone ?? Or do I mount them, then special / raw them int oa zone ?

Just cant seem to find anything on how to set up a zone, with SAN storage, best practises.

Any help gents ? Advice ?

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers


haven't work with zones in a while. when shutting down zones from solaris 10 I have to do it from the global zone, but can I just shutdown the global zone and all non global zones will shutdown or do I have to zoneadm -z zonename shutdown for all the non global zones ,then shutdown... (2 Replies)
Discussion started by: goya
2 Replies

2. Solaris

Zones: Exclusive IP question

Hi there when setting my zone config file up, I would naturally set 'set ip-type=exclusive' but I wanted to know, whether on the 'set physical=' line whether I could use a virtual interface that ive created in the global zone such as bge0:1. for example create -b set... (5 Replies)
Discussion started by: rethink
5 Replies

3. Solaris

Zonecfg equivalent properties for projects related controls

Hi All, In our project we are often using projects related control parameter, in a zone, for example below : bash-3.00# projadd -U xyz bash-3.00# projmod -sK"process.max-sem-nsems=(priv,2048,deny)" bash-3.00# projmod -sK"project.max-sem-ids=(priv,1024,deny)" (0 Replies)
Discussion started by: srajv
0 Replies

4. Solaris


how can we know zone is migrate and which files going to update (3 Replies)
Discussion started by: nsusheelgoud
3 Replies

5. Solaris


Hi Everyone, How to create a loopback filesystem in a running non golbalzone? and how to share a diskgroup in veritas ? Thanks & Regards Padmaja (1 Reply)
Discussion started by: padmaja
1 Replies

6. Solaris


Hi Everyone, I need the process of how to add a cpu to a non-global zone or how to add a resource to non-globalzone. Thanks & Regards Padmaja (2 Replies)
Discussion started by: padmaja
2 Replies

7. Solaris


Hi guys Im using VMware and ive installed solaris 10 in that..ive configured virtual disks in that n im using question is if im gona configure zones in it do i need a seperate NIC virtual interface name is pcn0 and if i create zones can i give pcn0:1 n allocate a seperate... (1 Reply)
Discussion started by: madanmeer
1 Replies

8. Solaris


Hi I need a help in creating a zones.I am trying to create zone in Sun fire T1000 server with single cpu / 8 gb Ram / 73 gb hdd.I am planning to install java based application on two different zones. iam planning to install solaris 10. Can some one suggest what is the best way to create two... (5 Replies)
Discussion started by: solaris8in
5 Replies

9. Solaris


what are the files related to dns zones database file management ? (1 Reply)
Discussion started by: tirupathi
1 Replies

10. Solaris


Hi, I want to wheather there is any command by using that we can reboot all the zones , Example : I have 10 zones, I can reboot all 10 zones by using one command (2 Replies)
Discussion started by: manoj.solaris
2 Replies
Login or Register to Ask a Question
RAW(8)							       System Administration							    RAW(8)

raw - bind a Linux raw character device SYNOPSIS
raw /dev/raw/raw<N> <major> <minor> raw /dev/raw/raw<N> /dev/<blockdev> raw -q /dev/raw/raw<N> raw -qa DESCRIPTION
raw is used to bind a Linux raw character device to a block device. Any block device may be used: at the time of binding, the device driver does not even have to be accessible (it may be loaded on demand as a kernel module later). raw is used in two modes: it either sets raw device bindings, or it queries existing bindings. When setting a raw device, /dev/raw/raw<N> is the device name of an existing raw device node in the filesystem. The block device to which it is to be bound can be specified either in terms of its major and minor device numbers, or as a path name /dev/<blockdev> to an existing block device file. The bindings already in existence can be queried with the -q option, which is used either with a raw device filename to query that one device, or with the -a option to query all bound raw devices. Unbinding can be done by specifying major and minor 0. Once bound to a block device, a raw device can be opened, read and written, just like the block device it is bound to. However, the raw device does not behave exactly like the block device. In particular, access to the raw device bypasses the kernel's block buffer cache entirely: all I/O is done directly to and from the address space of the process performing the I/O. If the underlying block device driver can support DMA, then no data copying at all is required to complete the I/O. Because raw I/O involves direct hardware access to a process's memory, a few extra restrictions must be observed. All I/Os must be cor- rectly aligned in memory and on disk: they must start at a sector offset on disk, they must be an exact number of sectors long, and the data buffer in virtual memory must also be aligned to a multiple of the sector size. The sector size is 512 bytes for most devices. OPTIONS
-q Set query mode. raw will query an existing binding instead of setting a new one. -a With -q , specify that all bound raw devices should be queried. -h Provide a usage summary. BUGS
The Linux dd(1) command should be used without the bs= option, or the blocksize needs to be a multiple of the sector size of the device (512 bytes usually), otherwise it will fail with "Invalid Argument" messages (EINVAL). Raw I/O devices do not maintain cache coherency with the Linux block device buffer cache. If you use raw I/O to overwrite data already in the buffer cache, the buffer cache will no longer correspond to the contents of the actual storage device underneath. This is deliberate, but is regarded either a bug or a feature depending on who you ask! AUTHOR
Stephen Tweedie ( AVAILABILITY
The raw command is part of the util-linux package and is available from util-linux August 1999 RAW(8)