find block size of ocfs2 file system


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers find block size of ocfs2 file system
Prev   Next
# 3  
Old 06-26-2012
radoulov also please cold you explain is the output in bytes

Quote:
tunefs.ocfs2 1.2.7
block size = 4096
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Linux

Increasing total data size per file system request for block drivers

Hi All, I am writing a block driver for a 2GB SD card where i get the total amount of data per request as follows: struct request *req; uint card_addr,total_bytes; struct request_queue *rq = BlkDev->queue; req = elv_next_request(rq); .. .. card_addr = req->sector*512;... (1 Reply)
Discussion started by: amio
1 Replies

2. Solaris

Directory size larger than file system size?

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

3. Shell Programming and Scripting

find with file size and show the size

Hi All... is the below command be modified in sucha way that i can get the file size along with the name and path of the file the below command only gives me the file location which are more than 100000k...but I want the exact size of the file also.. find / -name "*.*" -size +100000k ... (3 Replies)
Discussion started by: rpraharaj84
3 Replies

4. UNIX for Advanced & Expert Users

how to find the queue size in listen system call

hi, I want to find the queue size of the listen system call which is defined as below listen(s, backlog) The backlog parameter sets the maximum number of outstanding connections which can be queued awaiting acceptance by the server. I want to know where is this... (2 Replies)
Discussion started by: sowjanya
2 Replies

5. Solaris

increasing file system size

Hi Can anyone explain me how to increase the filesystem size. We can do it when the system is running? It needs an reboot? (8 Replies)
Discussion started by: rogerben
8 Replies

6. UNIX for Advanced & Expert Users

how to find default OS block size?

Hi Can someone please guide me on how to get the default block size for all unix flavors. As per my investigation its 512 for all unix flavours other than HP for which it is 1024.However I am not sure on this. I even tried the df ommand but utt gives the output w.r.t file system created but... (1 Reply)
Discussion started by: prasi_in
1 Replies

7. Programming

how to get the file system size

I have the next code, and the output is incosistent, what is the problem: free blocks: 1201595 block size: 4096 total size(free blocks * block size): 626765824 1201595 * 4096 not is 626765824, what's the problem??? #include <sys/statvfs.h> #include <stdio.h> int main(){ ... (1 Reply)
Discussion started by: lucaxvu
1 Replies

8. AIX

file system size

Dear ALL Today I faced one problem in the file system, during invoking the command #df -k , I saw /usr reached to 95% Used, could any one give advice ? thanks & regarded (7 Replies)
Discussion started by: magasem
7 Replies

9. Solaris

command to find out total size of a specific file size (spread over the server)

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

10. AIX

How can I find the filesystem block size?

How can I find the filesystem block size in AIX? I need to check if it is the same as my DB block size. (4 Replies)
Discussion started by: progressdll
4 Replies
Login or Register to Ask a Question
debugfs.ocfs2(8)						OCFS2 Manual Pages						  debugfs.ocfs2(8)

NAME
debugfs.ocfs2 - OCFS2 file system debugger. SYNOPSIS
debugfs.ocfs2 [-f cmdfile] [-R command] [-s backup] [-nwV?] [device] debugfs.ocfs2 -l [tracebit ... [allow|off|deny]] ... debugfs.ocfs2 -d, --decode lockname debugfs.ocfs2 -e, --encode lock_type block_num [generation | parent] DESCRIPTION
The debugfs.ocfs2 program is an interactive file system debugger useful in displaying on-disk OCFS2 filesystem structures on the specified device. OPTIONS
-d, --decode lockname Display the information encoded in the lockname. -e, --encode lock_type block_num [generation | parent] Display the lockname obtained by encoding the arguments provided. -f, --file cmdfile Executes the debugfs commands in cmdfile. -i, --image Specifies device is an o2image file created by o2image tool. -l [tracebit ... [allow|off|deny]] ... Control OCFS2 filesystem tracing by enabling and disabling trace bits. Do debugfs.ocfs2 -l to get the list of all trace bits. -n, --noprompt Hide prompt. -R, --request command Executes a single debugfs command. -s, --superblock backup-number mkfs.ocfs2 makes upto 6 backup copies of the superblock at offsets 1G, 4G, 16G, 64G, 256G and 1T depending on the size of the vol- ume. Use this option to specify the backup, 1 thru 6, to use to open the volume. -w, --write Opens the filesystem in RW mode. By default the filesystem is opened in RO mode. -V, --version Display version and exit. -?, --help Displays help and exit. SPECIFYING FILES
Many debugfs.ocfs2 commands take a filespec as an argument to specify an inode (as opposed to a pathname) in the filesystem which is cur- rently opened by debugfs.ocfs2. The filespec argument may be specified in two forms. The first form is an inode number or lockname sur- rounded by angle brackets, e.g., <32>. The second form is a pathname; if the pathname is prefixed by a forward slash ('/'), then it is interpreted relative to the root of the filesystem which is currently opened by debugfs.ocfs2. If not, the path is interpreted relative to the current working directory as maintained by debugfs.ocfs2, which can be modified using the command cd. If the pathname is prefixed by a double forward slash ('//'), then it is interpreted relative to the root of the system directory of the filesystem opened by debugfs.ocfs2. LOCKNAMES
Locknames are specially formatted strings used by the file system to uniquely identify objects in the filesystem. Most locknames used by OCFS2 are generated using the inode number and its generation number and can be decoded using the decode command or used directly in place of an inode number in commands requiring a filespec. Like inode numbers, locknames need to be enclosed in angle brackets, e.g., <M000000000000000040c40c044069cf>. Use the encode command to generate all possible locknames for an object. COMMANDS
This is a list of the commands which debugfs.ocfs2 supports. bmap filespec logical_block Display the physical block number corresponding to the logical block number logical_block in the inode filespec. cat filespec Dump the contents of inode filespec to stdout. cd filespec Change the current working directory to filespec. chroot filespec Change the root directory to be the directory filespec. close Close the currently opened filesystem. controld dump Display information obtained from ocfs2_controld. curdev Show the currently open device. decode <lockname> Display the inode number encoded in the lockname. dirblocks <filespec> Display the directory blocks associated with the given filespec. dlm_locks [-f <file>] [-l] [<lockname(s)>]... Display the status of all lock resources in the o2dlm domain that the file system is a member of. This command expects the debugfs filesystem to be mounted as mount -t debugfs debugfs /sys/kernel/debug. Use lockname(s) to limit the output to the given lock resources, -l to include contents of the lock value block and -f <file> to specify a saved copy of /sys/ker- nel/debug/o2dlm/<DOMAIN>/locking_state. dump [-p] filespec outfile Dump the contents of the inode filespec to the output file outfile. If the -p is given, set the owner, group, timestamps and permis- sions information on outfile to match those of filespec. dx_dump filespec Display the indexed directory information for the given directory. dx_leaf <block#> Display the contents of the given indexed directory leaf block. dx_root <block#> Display the contents of the given indexed directory root block. dx_space filespec Display the directory free space list. encode filespec Display the lockname for the filespec. extent block# Display the contents of the extent structure at block#. findpath [<lockname>|<inode#>] Display the pathname for the inode specified by lockname or inode#. This command does not display all the hard-linked paths for the inode. frag filespec Display the inode's number of extents to clusters ratio. fs_locks [-f <file>] [-l] [-B] [<lockname(s)>]... Display the status of all locks known by the file system. This command expects the debugfs filesystem to be mounted as mount -t debugfs debugfs /sys/kernel/debug. Use lockname(s) to limit the output to the given lock resources, -B to limit the output to only the busy locks, -l to include contents of the lock value block and -f <file> to specify a saved copy of /sys/ker- nel/debug/ocfs2/<UUID>/locking_state. group block# Display the contents of the group descriptor at block#. hb Display the contents of the heartbeat system file. help, ? Print the list of commands understood by debugfs.ocfs2. icheck block# ... Display the inodes that use the one or more blocks specified on the command line. If the inode is a regular file, also display the corresponding logical block offset. lcd directory Change the current working directory of the debugfs.ocfs2 process to the directory on the native filesystem. locate [<lockname>|<inode#>] ... Display all pathnames for the inode(s) specified by locknames or inode#s. logdump node# Display the contents of the journal for node node#. ls [-l] filespec Print the listing of the files in the directory filespec. The -l flag will list files in the long format. ncheck [<lockname>|<inode#>] ... See locate. open device Open the filesystem on device. quit, q Quit debugfs.ocfs2. rdump [-v] filespec outdir Recursively dump directory filespec and all its contents (including regular files, symbolic links and other directories) into the outdir which should be an existing directory on the native filesystem. refcount [-e] filespec Display the refcount block, and optionally its tree, of the specified inode. slotmap Display the contents of the slotmap system file. stat [-t|-T] filespec Display the contents of the inode structure for the filespec. The -t ("traverse") option selects traversal of the inode's metadata. The extent tree, chain list, or other extra metadata will be dumped. This is the default. The -T option turns off traversal to reduce the I/O required when basic inode information is needed. stats [-h] [-s backup-number] Display the contents of the superblock. Use -s to display a specific backup superblock. Use -h to hide the inode. xattr [-v] <filespec> Display extended attributes associated with the given filespec. ACKNOWLEDGEMENT
This tool has been modelled after debugfs, a debugging tool for ext2. SEE ALSO
mkfs.ocfs2(8) fsck.ocfs2(8) tunefs.ocfs2(8) mounted.ocfs2(8) ocfs2console(8) o2image(8) o2cb(7) AUTHOR
Oracle Corporation COPYRIGHT
Copyright (C) 2004, 2010 Oracle. All rights reserved. Version 1.6.4 September 2010 debugfs.ocfs2(8)