12-25-2014
Whenever you ask about block size, fragment size, and how blocks are allocated to files; you need to tell us what type of filesystem you're using. Different filesystems use different methods of allocating blocks for files.
I'm certainly not an expert on HP-UX filesystems, but I would suggest that you also specify the HP-UX release you're using to help volunteers here who may be able to help you respond appropriately.
Happy holidays...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: Dilippatel
1 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
drwxr-xr-x 2 root root 4096 May 31 14:47 test
Please let me know here 4096 indicating what?
Thanks & Regards,
Bache (1 Reply)
Discussion started by: bache_gowda
1 Replies
3. 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
4. AIX
Hi, I try to change the block size from 512 to 0, but it send this message:
0514-068 Cause not know
Can someone help me whith this? (3 Replies)
Discussion started by: Ruben78
3 Replies
5. Solaris
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)
Discussion started by: sparcman
6 Replies
6. 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
7. Shell Programming and Scripting
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)
Discussion started by: welldone
5 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. Red Hat
Hi Guys,
I am running Linux 2.6.18-164.el x86_64 how do i check the block size?
Thanks in advance... (1 Reply)
Discussion started by: Phuti
1 Replies
10. 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
LEARN ABOUT REDHAT
e2image
E2IMAGE(8) System Manager's Manual E2IMAGE(8)
NAME
e2image - Save critical ext2 filesystem data to a file
SYNOPSIS
e2image [ -r ] device image-file
DESCRIPTION
The e2image program will save critical filesystem data on the ext2 filesystem located on device to a file specified by image-file. The
image file may be examined by dumpe2fs and debugfs, by using the -i option to those programs. This can be used by an expert in assisting
the recovery of catastrophically corrupted filesystems. In the future, e2fsck will be enhanced to be able to use the image file to help
recover a badly damaged filesystem.
If image-file is -, then the output of e2image will be sent to standard output.
The -r option will create a raw image file instead of a normal image file. A raw image file differs from a normal image file in two ways.
First, the filesystem metadata is placed in the proper position so that e2fsck, dumpe2fs, debugfs, etc. can be run directly on the raw
image file. In order to minimize the amount of disk space consumed by a raw image file, the file is created as a sparse file. (Beware of
copying or compressing/decompressing this file with utilities that don't understand how to create sparse files; the file will become as
large as the filesystem itself!) Secondly, the raw image file also includes indirect blocks and data blocks, which the current image file
does not have, although this may change in the future.
It is a very good idea to periodically (at boot time and every week or so) to create image files for all of filesystems on a system, as
well as saving the partition layout (which can be generated using the using fdisk -l command). Ideally the image file should be stored on
some filesystem other that the filesystem whose data it contains, to ensure that its data is accessible in the case where the filesystem
has been badly damaged.
To save disk space, e2image creates the image file as a sparse file. Hence, if the image file needs to be copied to another location, it
should either be compressed first or copied using the --sparse=always option to GNU version of cp.
The size of an ext2 image file depends primarily on the size of the filesystems and how many inodes are in use. For a typical 10 gigabyte
filesystem, with 200,000 inodes in use out of 1.2 million inodes, the image file be approximately 35 megabytes; a 4 gigabyte filesystem
with 15,000 inodes in use out of 550,000 inodes will result in a 3 megabyte image file. Image files tend to be quite compressible; an
image file taking up 32 megabytes of space on disk will generally compress down to 3 or 4 megabytes.
AUTHOR
e2image was written by Theodore Ts'o (tytso@mit.edu).
AVAILABILITY
e2image is part of the e2fsprogs package and is available from anonymous http://e2fsprogs.sourceforge.net.
SEE ALSO
dumpe2fs(8), debugfs(8)
E2fsprogs version 1.32 November 2002 E2IMAGE(8)