Sponsored Content
Top Forums UNIX for Dummies Questions & Answers vol group - physical partition size Post 29721 by Kelam_Magnus on Thursday 10th of October 2002 03:38:11 PM
Old 10-10-2002
depends on data size

This is a classic question. It really depends on the size of your data. If your data is in hundreds of small files, then a smaller size will allow you to waste less space because there will be a smaller amount of left over disk per chunk when the chunks are smaller.

If you have large data chunks (files), then larger sizes for pp will be just fine. It really depends on your data. It is usually good to pick the default size or a little larger.

This question is very similar to the Extent size for Volumes. On my HPUX system the default size is 4MB. Which is fine for most cases, however, I have seen cases where it was 8MB and even 2MB. All depending on the data.

Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

understanding logical partition, physical partition

hi, 1) is logical partition the same as physical partition except that one is physical and the other is logical? 2) then it must a one to one ratio? (3 Replies)
Discussion started by: yls177
3 Replies

2. HP-UX

determine the physical size of the hard disk

Hi is there a cmd in hpux 11 to determine the physical size of the hard disk. not bdf command. i have searched the other threads here but cant find an answer. thank you guys (4 Replies)
Discussion started by: hoffies
4 Replies

3. AIX

max size of a group in /etc/group

I have several AIX servers running 5.2. What is the default max size for a group in /etc/group? How do I change the default max size for a group to be unlimited (if possible)? Thanks (4 Replies)
Discussion started by: antalexi
4 Replies

4. HP-UX

Unmount and remove all Logical vol.Volume group and physical disk

Hi, Someone please help me with how i can unmount and remove all the files systems from a cluster. This is being shared by two servers that are active_standby. (3 Replies)
Discussion started by: joeli
3 Replies

5. IP Networking

IPMI - Get physical memory size

Hi, Does anybody know how to get the RAM size of a powerless server (OS off), with a network hardware management protocol like IPMI ??? Thx (0 Replies)
Discussion started by: sncr24
0 Replies

6. AIX

changing Physical Partition (PP)

Hi all, I am trying to replace an old 9gb hard disk for a 36gb hard drive on an AIX 4.3.2 system (can't update) I was thinking of doing this by doing a dd from the 9gb to the 36gb hard drive and then resize the Logical Volumes. However, lspv <36gb hard disk> gives me the folowing: #lrnt>... (4 Replies)
Discussion started by: eRJe
4 Replies

7. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

8. Solaris

ZFS : Can arc size value exceed Physical RAM ?

Hi, kstat -p -m zfs -n arcstats -s size returns zfs:0:arcstats:size 8177310584 this values is approx (7.61 GB) but my Physical Memory size is only 6144 Megabytes. Can this happen ? if yes, then how can I find free memory on the system. BTW, I ran the kstat commands from a Non... (2 Replies)
Discussion started by: sapre_amit
2 Replies

9. UNIX for Advanced & Expert Users

Physical disk IO size smaller than fragment block filesystem size ?

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

10. AIX

Trouble removing Physical Disk from Volume Group

I want to remove hdisk1 from volume group diskpool_4 and migrate PV from hdisk1 to hdisk2 , but facing problems, so what is the quickest way to migratepv and remove hdisk1 -- # lspv | grep diskpool_4 hdisk1 00c7780e2e21ec86 diskpool_4 active hdisk2 ... (2 Replies)
Discussion started by: filosophizer
2 Replies
AFS_CACHE(5)							AFS File Reference						      AFS_CACHE(5)

NAME
afs_cache - Format of data stored in an AFS client disk cache DESCRIPTION
The disk cache on a client machine is composed of multiple Vn files that contain the data, a CacheItems file that records index information for all of the Vn files, and a VolumeItems file that records the mapping between volume name and mount point for volumes. When it initializes, the Cache Manager creates the cache files in the configured cache location. The standard directory name is /usr/vice/cache, but it is acceptable to use a directory on a partition with more available space. To designate a different directory, change the value in the second field of the /etc/openafs/cacheinfo file before issuing the afsd command, or include the -cachedir argument to the afsd command. CacheItems The CacheItems file records information about each file in the disk cache on a client machine (each Vn file). The information includes the file ID number and associated volume version number of the AFS file currently stored in the Vn file, which enables the Cache Manager to determine which Vn file contains the AFS data it needs to present to an application. As it initializes, the Cache Manager creates the binary-format CacheItems file in the same local disk cache directory as the Vn files that the CacheItems file describes, and it must always remain there. VolumeItems The VolumeItems file records the mapping between volume name and mount point for each volume that the Cache Manager has accessed since it initialized on a client machine using a disk cache. The Cache Manager uses the mappings to respond correctly to queries about the current working directory, which can come from the operating system or commands such as the UNIX pwd command. As it initializes, the Cache Manager creates the binary-format VolumeItems file in the local disk cache directory, and it must always remain there. Vn A Vn file can store a chunk of cached AFS data on a client machine that is using a disk cache. As the Cache Manager initializes, it verifies that the local disk cache directory houses a number of Vn files equal to the largest of the following: o 100 o One and a half times the result of dividing the cache size by the chunk size (cachesize/chunksize * 1.5). o The result of dividing the cache size by 10 MB (10,240). The Cache Manager determines the cache size from the -blocks argument to the afsd command, or if the argument is not included, from the third field of the /etc/openafs/cacheinfo file. The default chunk size is 64 KB; use the -chunksize argument to the afsd command to override it. To override the default number of chunks resulting from the calculation, include the -files argument to the afsd command. afsd(8) describes the restrictions on acceptable values for each of the arguments. If the disk cache directory houses fewer Vn files than necessary, the Cache Manager creates new ones, assigning each a unique integer n that distinguishes it from the other files; the integers start with 1 and increment by one for each Vn file created. The Cache Manager removes files if there are more than necessary. The Cache Manager also adds and removes Vn files in response to the fs setcachesize command, which can be used to alter the cache size between reboots. Vn files expand and contract to accommodate the size of the AFS directory listing or file they temporarily house. As mentioned, by default each Vn file holds up to 64 KB (65,536 bytes) of a cached AFS element. AFS elements larger than 64 KB are divided among multiple Vn files. If an element is smaller than 64 KB, the Vn file expands only to the required size. A Vn file accommodates only a single element, so if there many small cached elements, it is possible to exhaust the available Vn files without reaching the maximum cache size. CAUTIONS
Editing or removing the CacheItems or VolumeItems files or a Vn file can cause a kernel panic. If the contents of Vn files seem out of date, clear the files by using the fs flush or fs flushvolume command. If any of the cache files are accidentally modified or deleted, rebooting the machine usually restores normal performance. To alter cache size (and thus the number of Vn files) between reboots, use the fs setcachesize command. Alternatively, alter the value of the -blocks, -files or -chunksize arguments to the afsd command invoked in the machine's AFS initialization file, and reboot. To refresh the contents of one or more Vn files, use the fs flush or fs flushvolume command. SEE ALSO
cacheinfo(5), afsd(8), fs_checkvolumes(1), fs_flush(1), fs_flushvolume(1), fs_setcachesize(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 AFS_CACHE(5)
All times are GMT -4. The time now is 04:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy