03-26-2006
we initially screwed up the hotpsares when we set it up. we did'nt assign enough inodes to the hotspares. so, we had to newfs it again to assign more inodes.
10 More Discussions You Might Find Interesting
1. Solaris
Hello,
I am trying to do mirror in solaris 9. I have total 0-7 disks
4 5 6 7
0 1 2 3
Drive 0 and Drive 4 = Boot Drives
Need to Mirror following drives.
Drive 1 and Drive 5 = Need to mirror
Drive 1 was mounted on: /prod1, /prod2, /prod3, /prod4, /prod5.
Then i... (3 Replies)
Discussion started by: deal732
3 Replies
2. Solaris
Hi all,
I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume.
Please find a sutable solutions.
Thanks and Regards
B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies
3. Solaris
Hello friends,
I need to test some of the solaris 10 concepts and veritas volume manager.i want to know ,where i get the testing labs or E-labs(online) for this practice.i ready to pay for this labs.pls kindly help me to get the details or website names...Thanks in Advance
-Jay (6 Replies)
Discussion started by: rjay.com
6 Replies
4. Solaris
what is the command to see the veritas volume manager 3.0.4 license..in solaris 8.I wnat to see the license number (3 Replies)
Discussion started by: tv.praveenkumar
3 Replies
5. Solaris
Can you please let me know the certification code for veritas volume manager in solaris ? Thanks in advance. (2 Replies)
Discussion started by: gowthamakanthan
2 Replies
6. Solaris
Hello All,
I have small doubt. It's related to SVM in solaris 10. I have created raid 0 (striping) using 3 slices of 500 MB size (default interlace value as 32KB)
d2: Concat/Stripe ---- Interlace value is 32 KB
Size: 2923830 blocks (1.4 GB)
Stripe 0: (interlace: 64 blocks)
Device Start... (1 Reply)
Discussion started by: vaibhav.kanchan
1 Replies
7. Solaris
Hi Friends,
I have to migrate my raid-1 volume to raid -5 online.
Can anyone please help me, If possible then send me the step by step commands for online migration.
Thanks in advance. (2 Replies)
Discussion started by: rajaramrnb
2 Replies
8. Solaris
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
9. Solaris
Hello Admins..
I am going through solaris volume manager guide for RAID-0 concatenation and stripes, I do not understand the concept of stripe from following example of concatenation.
There is an eample for concatenation:
# metainit d25 1 1 c0t1d0s2
d25: Concat/Stripe is setup
the... (5 Replies)
Discussion started by: snchaudhari2
5 Replies
10. Solaris
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
bash-3.2# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c0t0d0s7
a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
LEARN ABOUT FREEBSD
fsirand
FSIRAND(8) BSD System Manager's Manual FSIRAND(8)
NAME
fsirand -- randomize inode generation numbers
SYNOPSIS
fsirand [-b] [-f] [-p] special [special ...]
DESCRIPTION
The fsirand utility installs random generation numbers on all the inodes for each file system specified on the command line by special. This
increases the security of NFS-exported file systems by making it difficult to ``guess'' filehandles.
Note: newfs(8) now does the equivalent of fsirand itself so it is no longer necessary to run fsirand by hand on a new file system. It is
only used to re-randomize or report on an existing file system.
The fsirand utility should only be used on an unmounted file system that has been checked with fsck(8) or a file system that is mounted read-
only. The fsirand utility may be used on the root file system in single-user mode but the system should be rebooted via ``reboot -n'' after-
wards.
OPTIONS
The available options are as follows:
-b Use the default block size (usually 512 bytes) instead of the value gleaned from the disklabel.
-f Force fsirand to run even if the file system on special is not marked as clean.
-p Print the current generation numbers for all inodes instead of generating new ones.
SEE ALSO
fs(5), fsck(8), newfs(8)
HISTORY
The fsirand utility appeared in SunOS 3.x.
This version of fsirand first appeared in OpenBSD 2.1.
A FreeBSD version first appeared in FreeBSD 2.2.5.
AUTHORS
Todd C. Miller <Todd.Miller@courtesan.com>
CAVEATS
Since fsirand allocates enough memory to hold all the inodes in a given cylinder group it may use a large amount of memory for large disks
with few cylinder groups.
BSD
January 25, 1997 BSD