Sponsored Content
Operating Systems Solaris swap space in veritas file system Post 302161962 by reborg on Sunday 27th of January 2008 08:18:19 AM
Old 01-27-2008
It's exactly the same procedure. The only difference is that instead of the device being /dev/dsk/<target> it will be /dev/vx/dsk/<diskgroup>/<volume>
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Veritas File System

Hello All. I have a question concerning VFS (Veritas File System). I are attempting to upgrade Solaris 2.6 UFS to the VFS (Veritas File System). We use Veritas to perform all our backups. I have been unable to find any documentation on SUN's or Veritas's website. The server's are SUN 4500 and... (3 Replies)
Discussion started by: KaEH
3 Replies

2. Filesystems, Disks and Memory

veritas vcs \ file system docs req.

hi if anyone has docs (corporate internals on how to setup vcs mfor example, especially with Veritas VM, pleas let me know..i need exposure experience in this area of Enterprise Administration thanks jasmine (SCSA & MCSE) (2 Replies)
Discussion started by: jasmine_uk
2 Replies

3. UNIX for Dummies Questions & Answers

swap file space

I occasionally get a "out of swap file space" error. How can I fix this?????? Thanks (9 Replies)
Discussion started by: dtooth71
9 Replies

4. Solaris

/tmp: File system full, swap space limit exceeded

Can you help. My server sunning solaris 9 on x86 platform pretty much hung for a few hours... I could not use telnet or ssh to the box - it kept refusing connection. A few hours later - I was able to log in again. The server has not rebooted but here are the first errors in the messages log... (5 Replies)
Discussion started by: frustrated1
5 Replies

5. Solaris

Modify the swap on Solaris10 on a volume VERITAS

Hi Community, Do you know a procedure to modify the swap on Solaris10 on a volume VERITAS? Please help me I'm currently working on this issue. Thank you for your availability! (1 Reply)
Discussion started by: Sunb3
1 Replies

6. UNIX for Advanced & Expert Users

Swap file system

This questions only concerns Solaris 10. Let's say I have swap configured like so in /etc/vfstab: /dev/dsk/c1t0d0s1 - - swap - no - /dev/dsk/c1t1d0s1 - - swap - no - /dev/md/dsk/d1 - - swap - no - ... (1 Reply)
Discussion started by: bluescreen
1 Replies

7. Solaris

Why Veritas is not used for root file system.

Dear All, In our environment we use SDS (Solaris Vlume Manager) for root file system.So, I am wondering why Veritas is not use for the same. root@abc # df -kh Filesystem size used avail capacity Mounted on /dev/md/dsk/d10 30G 22G 6.9G 77% / /devices ... (3 Replies)
Discussion started by: Reboot
3 Replies

8. Solaris

how to restore backup from veritas vm in ufs file system

Hi all I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it? right now i don't have veritas file system setup. i have only ufs file sysytem please help some production data is to be restore. backup was taken... (0 Replies)
Discussion started by: nikhil kasar
0 Replies

9. UNIX for Dummies Questions & Answers

Swap two rows in a space delimited text file?

Hi, How do you swap two rows in a space delimited text file? Thanks! (4 Replies)
Discussion started by: evelibertine
4 Replies

10. UNIX for Dummies Questions & Answers

Question on Veritas file system..

Hi, I am on Solaris 10 server which is running Veritas. It's E420 server with two drives. I don't know much about Veritas. The other guy who works on this, on vacation this week. :-) Any way, looks like I have hard drive issue on the server. When I do iostat -E. I see this. sd0... (4 Replies)
Discussion started by: samnyc
4 Replies
volfs(7FS)                                                         File Systems                                                         volfs(7FS)

NAME
volfs - Volume Management file system DESCRIPTION
volfs is the Volume Management file system rooted at root_dir. The default location for root-dir is /vol, but this can be overridden using the -d option of vold (see vold(1M)). This file system is maintained by the Volume Management daemon, vold, and will be considered to be /vol for this description. Media can be accessed in a logical manner (no association with a particular piece of hardware), or a physical manner (associated with a particular piece of hardware). Logical names for media are referred to through /vol/dsk and /vol/rdsk. /vol/dsk provides block access to random access devices. /vol/rdsk provides character access to random access devices. The /vol/rdsk and /vol/dsk directories are mirrors of one another. Any change to one is reflected in the other immediately. The dev_t for a volume will be the same for both the block and character device. The default permissions for /vol are mode=0555, owner=root, group=sys. The default permissions for /vol/dsk and /vol/rdsk are mode=01777, owner=root, group=sys. Physical references to media are obtained through /vol/dev. This hierarchy reflects the structure of the /dev name space. The default per- missions for all directories in the /vol/dev hierarchy are mode=0555, owner=root, group=sys. mkdir(2), rmdir(2), unlink(2) (rm), symlink(2) (ln -s), link(2) (ln), and rename(2) (mv) are supported, subject to normal file and direc- tory permissions. The following system calls are not supported in the /vol filesystem: creat(2), only when creating a file, and mknod(2). If the media does not contain file systems that can be automatically mounted by rmmount(1M), users can gain access to the media through the following /vol locations: +-----------------------------------+------------------------------------+ | Location | State of Media | +-----------------------------------+------------------------------------+ |/vol/dev/diskette0/unnamed_floppy | formatted unnamed floppy-block | | | device access | +-----------------------------------+------------------------------------+ |/vol/dev/rdiskette0/unnamed_floppy | formatted unnamed floppy-raw | | | device access | +-----------------------------------+------------------------------------+ |/vol/dev/diskette0/unlabeled | unlabeled floppy-block device | | | access | +-----------------------------------+------------------------------------+ |/vol/dev/rdiskette0/unlabeled | unlabeled floppy-raw device access | +-----------------------------------+------------------------------------+ |/vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM-block device access | +-----------------------------------+------------------------------------+ |/vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM-raw device access | +-----------------------------------+------------------------------------+ For more information on the location of CD-ROM and floppy media, see System Administration Guide: Basic Administration or rmmount(1M). Partitions Some media support the concept of a partition. If the label identifies partitions on the media, the name of the media becomes a directory with partitions under it. Only valid partitions are represented. Partitions cannot be moved out of a directory. For example, if disk volume 'foo' has three valid partitions, 0, 2, and 5, then: /vol/dsk/foo/s0 /vol/dsk/foo/s2 /vol/dsk/foo/s5 for block access and /vol/rdsk/foo/s0 /vol/rdsk/foo/s2 /vol/rdsk/foo/s5 for character access. If a volume is relabeled to reflect different partitions, the name space changes to reflect the new partition layout. A format program can check to see if there are others with the volume open and not allow the format to occur if it is. Volume Management, however, does not explicitly prevent the rewriting of a label while others have the volume open. If a partition of a volume is open, and the volume is relabeled to remove that partition, it will appear exactly as if the volume were missing. A notify event will be generated and the user may cancel the operation with volcancel(1), if desired. SEE ALSO
volcancel(1), volcheck(1), volmissing(1) rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4) System Administration Guide: Basic Administration SunOS 5.10 8 Feb 1995 volfs(7FS)
All times are GMT -4. The time now is 12:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy