That does indeed show a "fragment size" of 8 KB, which is the "fundamental file system block size", i.e. the minimum block size that can be used on a file system..
Quote:
[CODE]
[..]
I think it's somehow related that root VG supposed to be on a contiguous LVM logical volume. But I'm not sure.
It is important to get the terms right. A VG can not be on a LVM volume. What you mean is the root filesystem (in this case of type VXFS) that gets mounted on /. The root filesystem is usually on one of the logical volumes (typically lvol3) on vg00.
If there needs to be a contiguous LVM, then that typically pertains to the swap volume ( typically lvol2 on vg00), but that does not contain a VXFS file system and so does not have a block size / fragment size..). The contiguousness has to do with physical extents, not filesystem blocks / fragments..
Last edited by Scrutinizer; 12-26-2014 at 03:17 AM..
Hello Unix guru's
I want to check my OS Block size for the Solaris 8
Following is one of the line from df -g command.
Can anybody help to interpret the same.
/u03 (/dev/vx/dsk/oradg/vol03): 8192 block size 8192 frag size
205463552 total blocks 50433792... (1 Reply)
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)
Hi,
We currently have an Oracle database running and it is creating lots of processes in the /proc directory that are 1000M in size. The size of the /proc directory is now reading 26T. How can this be if the root file system is only 13GB?
I have seen this before we an Oracle temp file... (6 Replies)
#!/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)
Hi Experts,
I have a script like
$ORACLE_HOME/bin/sqlplus username/password # << ENDSQL
set pagesize 0 trim on feedback off verify off echo off newp none timing off
set serveroutput on
set heading off
spool Schemaerrtmp.txt
select ' TIMESTAMP COMPUTER NAME ... (5 Replies)
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)
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
LEARN ABOUT OPENSOLARIS
size
size(9P) Kernel Properties for Drivers size(9P)NAME
size, Nblock, blksize, device-nblocks, device-blksize - device size properties
DESCRIPTION
A driver can communicate size information to the system by the values associated with following properties. Size information falls into two
categories: device size associated with a dev_info_t node, and minor node size associated with a ddi_create_minor_node(9F) dev_t (parti-
tion).
device size property names:
device-nblocks An int64_t property representing device size in device-blksizeblocks.
device-blksize An integer property representing the size in bytes of a block. If defined, the value must be a power of two. If not
defined, DEV_BSIZE is implied.
minor size property names:
Size An int64_t property representing the size in bytes of a character minor device (S_IFCHR spec_type in ddi_create_minor_node).
Nblocks An int64_t property representing the number blocks, in device-blksize units, of a block minor device (S_IFBLK spec_type in
ddi_create_minor_node).
blksize An integer property representing the size in bytes of a block. If defined, the value must be a power of two. If not defined,
DEV_BSIZE is implied.
A driver that implements both block and character minor device nodes should support both "Size" and "Nblocks". Typically, the following is
true: Size = Nblocks * blksize.
A driver where all ddi_create_minor_node(9F) calls for a given instance are associated with the same physical block device should implement
"device-nblocks". If the device has a fixed block size with a value other than DEV_BSIZE then "device-blksize" should be implemented.
The driver is responsible for ensuring that property values are updated when device, media, or partition sizes change. For each represented
item, if its size is know to be zero, the property value should be zero. If its size is unknown, the property should not be defined.
A driver may choose to implement size properties within its prop_op(9E) implementation. This reduces system memory since no space is used
to store the properties.
The DDI property interfaces deal in signed numbers. All Size(9P) values should be considered unsigned. It is the responsibility of the code
dealing with the property value to ensure that an unsigned interpretation occurs.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
SEE ALSO attach(9E), detach(9E), prop_op(9E), ddi_create_minor_node(9F), inquiry-vendor-id(9P)
Writing Device Drivers
SunOS 5.11 23 Janl2008 size(9P)