01-17-2013
Issue about PP size
Hello everyone,
I have many VGs on my system. I have created them whith the same command. I haven't specified the PP size while creating them. Logically, the PP size should be the same (default value) in all the VGs. However, I have different PP size : 32 MB, 256 MB, 64 MB and 128 MB.
Can anyone explain why I haven't the same PP size ? what's the PP size default value ?
What's the utility of having small PP size rather than big PP size ?
Thank you
10 More Discussions You Might Find Interesting
1. Red Hat
Can anyone tell me how to read and change the tape block size attached to a ultrium 2 (Faststor-2 tapedrive). I am using Redhat Linux AS 3.0 Update 7. :cool:
I had a problem doing a recover with our backup software which is AS 3.0 Update 7. The message I received was:
Failed to read 65536... (1 Reply)
Discussion started by: rcarpent
1 Replies
2. Solaris
hi all,
in my server there are some specific application files which are spread through out the server... these are spread in folders..sub-folders..chid folders...
please help me, how can i find the total size of these specific files in the server... (3 Replies)
Discussion started by: abhinov
3 Replies
3. Solaris
Hi Gurus,
An Application is not able to create files above 2.14gb in size in my Sol5.9 server. I have checked the file limit of the user running the Application and am attaching the same:
boiadm: ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) ... (4 Replies)
Discussion started by: Hari_Ganesh
4 Replies
4. IP Networking
I am currently experiencing the file size being added to the file extension when transfering information from Command Line Client to a UNIX server. Does anyone know why this is happening and how do I stop the file size being added to the file extension.
Example: football.pqt.11108... (1 Reply)
Discussion started by: Skeeterrock
1 Replies
5. Shell Programming and Scripting
#!/bin/sh
##########################################################################################################
#This script is being used for AOK application for cleaning up the .out files and zip it under logs directory.
# IBM
# Created
#For pdocap201/pdoca202 .out files for AOK
#1.... (0 Replies)
Discussion started by: mridul10_crj
0 Replies
6. HP-UX
I have 2 files; one file (say, details.txt) contains the details of employees and another file (say, emp.txt) has some selected employee names. I am extracting employee details from details.txt by using emp.txt and the corresponding code is:
while read line
do
emp_name=`echo $line`
grep -e... (7 Replies)
Discussion started by: arb_1984
7 Replies
7. AIX
HI, I have had an issue last night while trying to extend a filesystsem . chvg -g <vg> command cameback with an error
0516-1790 chvg: Failed bootinfo -s hdisk9.
Ensure the physical volume is available and try again.
0516-732 chvg: Unable to change volume group u01vg.
the VG has 1... (1 Reply)
Discussion started by: xmen01
1 Replies
8. UNIX for Advanced & Expert Users
Hello,
in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies
9. UNIX for Dummies Questions & Answers
I have been searching both on Unix.com and Google and have not been able to find the answer to my question. I think it is partly because I can't come up with the right search terms.
Recently, my virtual server switched storage devices and I think the problem may be related to that change.... (2 Replies)
Discussion started by: jmgibby
2 Replies
10. AIX
Hi,
Need help with following case. I am trying to shring filesystem size and reduce few luns from volume group. Situation looks like that :
#
lsvg -l data1vg
data1vg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
data1 jfs2 3200 3200 ... (5 Replies)
Discussion started by: borek
5 Replies
mkfs_udfs(1M) System Administration Commands mkfs_udfs(1M)
NAME
mkfs_udfs - construct a udfs file system
SYNOPSIS
mkfs -F udfs [generic_options] [-o specific_options] raw_device_file [size]
DESCRIPTION
This is the universal disk format file system (udfs) -specific module of the mkfs command. mkfs constructs a udfs file system with a root
directory.
OPTIONS
See mkfs(1M) for the list of supported generic_options.
The following options are supported:
-o specific_options Specify a udfs-specific option. Specify udfs file system specific options in a comma-separated list with no inter-
vening spaces. If invalid options are specified, a warning message is printed and the invalid options are ignored.
The following specific_options are available:
N
Print the file system parameters without actually creating the file system.
label=string
Specify the label to be written into the volume header structures. Specify string as the name of the label. If
string is not specified, a default string is generated in the form of *NoLabel*.
OPERANDS
The following operands are supported:
raw_device_file Specify the disk partition on which to write.
size Specify the number of 512-byte blocks in the file system.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWudf |
+-----------------------------+-----------------------------+
SEE ALSO
fsck(1M),mkfs(1M), attributes(5)
DIAGNOSTICS
not currently a valid file system
The specified device does not contain a valid udfs file system.
Invalid size: larger than the partition size
Number of blocks given as parameter to create the file system is larger than the size of the device specified.
is mounted can't mkfs
Device is in use, cannot create file system when the device is in use.
preposterous size
Negative size parameter provided is invalid.
sector size must be between 512, 8192 bytes
Sector size given is not in the valid range.
Volume integrity sequence descriptors too long
File set descriptor too long.
Not enough space to create volume integrity sequence or file set descriptor.
mkfs: argument out of range
One of the arguments is out of range.
mkfs: bad numeric arg
One of the arguments is potentially a bad numeric.
NOTES
You can use lofiadm to create a file that appears to a mkfs command (for example, mkfs_pcfs or mkfs_ufs) as a raw device. You can then use
a mkfs command to create a file system on that device. See lofiadm(1M) for examples of creating a UFS and a PC (FAT) file system on a
device created by lofiadm.
SunOS 5.10 17 Nov 2000 mkfs_udfs(1M)