gfs(8) System Manager's Manual gfs(8)NAME
gfs - GFS reference guide
SYNOPSIS
Overview of manpages and their locations
DESCRIPTION
The GFS documentation has been split into a number of sections. Please refer to the table below to determine which man page coincides with
the command/feature you are looking for.
gfs GFS overview (this man page)
mount.gfs Mounting a GFS file system
fsck.gfs The GFS file system checker
gfs_grow Growing a GFS file system
gfs_jadd Adding a journal to a GFS file system
mkfs.gfs Make a GFS file system
gfs_quota Manipulate GFS disk quotas
gfs_tool Tool to manipulate a GFS file system
gfs(8)
Check Out this Related Man Page
gfs_jadd(8) System Manager's Manual gfs_jadd(8)NAME
gfs_jadd - Add journals to a GFS filesystem
SYNOPSIS
gfs_jadd [OPTION]... <DEVICE|MOINTPOINT>...
DESCRIPTION
gfs_jadd is used to add journals to a GFS filesystem after the device upon which the filesystem resides has been grown. By running
gfs_jadd on a GFS filesystem, you are filling in space between the current end of the filesystem and the end of the device upon which the
filesystem resides. When this operation is complete, the journal index is updated so that machines mounting the filesystem at a later date
will see the newly created journals in addition to the journals already there. Machines which are already running in the cluster are unaf-
fected.
gfs_jadd will not use space that has been formatted for filesystem data even if that space has never been populated with files.
You may only run gfs_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run
gfs_jadd on one node in the cluster. All the other nodes will see the expansion has occurred when required.
You must be superuser to execute gfs_jadd. The gfs_jadd tool tries to prevent you from corrupting your filesystem by checking as many of
the likely problems as it can. When growing a filesystem, only the last step of updating the journal index affects the currently mounted
filesystem and so failure part way through the expansion process should leave your filesystem in its original state.
You can run gfs_jadd with the -Tv flags to get a display of the current state of a mounted GFS filesystem. This can be useful to do after
the journal addition process to see if the changes have been successful.
OPTIONS -j num The number of new journals to add. This defaults to 1.
-J size
The size of the new journals in megabytes. The defaults to 128MB (the minimum size allowed is 32MB). If you want to add journals of
different sizes to the filesystem, you'll need to run gfs_jadd once for each different size of journal. The size you specify here
will be rounded down so that it is a multiple of the journal segment size which was specified at filesystem creation time.
-h Help. Prints out a short usage message and exits.
-q Quiet. Turns down the verbosity level.
-T Test. Do all calculations, but do not write any data to the disk and do not add journals. This is used to discover what the tool
would have done were it run without this flag. You probably want to turn the verbosity level up in order to gain most information
from this option.
-V Version. Print version information, then exit.
-v Verbose. Turn up verbosity of messages.
SEE ALSO mkfs.gfs(8)gfs_grow(8)gfs_jadd(8)
using debugfs we can restore the deleted file provided if we know the inode no. of the same file
can anyone tell me how to use this command in practically.Below the inode of a file caled minfo.txt.I m using IBM AIX 5.3
90139 minfo.txt
-------------------------------- (3 Replies)
I have a CentOS release 5.2 (Final)host running kernel 2.6.18-92.el5 with at raid 10 that had two mirrored drives fail. The drives were re-inserted and now the raid shows healthy (for now). I tried to mount but got an Input/output error. I then attempted a fsck:
fsck.gfs2 -y /dev/vg_01/uss_vol... (0 Replies)
Looking for suggestions as to which filesystem to go with. I currently use gfs2 on hosts with 3.4tb useable. I understand gfs2 is being left behind but xfs and ext4 are not quite certified completely on CentOS 5.2. I have email storage hosts that have a decent i/o requirement and 12TB usable after... (12 Replies)
Hi,
I have a bit knowledge of GFS. As per my understanding it is the file system used in the cluster environment.
I have a question. Is GFS 6.2 same as GFS 2 files system?
Please some one clear my confusion.
Thanks in advance. (1 Reply)
Hey everyone. I am in the process of setting up an iSCSI SAN to function as a log storage device for a number of servers. All of the initiators see the volume, and originally I formatted it with ext3 and went on my merry way. However after some research I'm having concerns that I should nuke the... (1 Reply)
My code
Hi All,
I am having redhat linux 5.3 (Tikanga) with GFS file system and its very very slow for executing ls -ls command also.Please see the below for 2minits 12 second takes.
Please help me to fix the issue.
$ sudo time ls -la BadFiles |wc -l
0.01user 0.26system... (3 Replies)
Hi all,
I'm a bit new to advanced filesystem types. I've just only learned that if you wish to share a single fibre channel extent with many servers you need to use a clustered filesystem to prevent data corruption.
looking through a list of clustered file systems I saw gfs2 which I thought... (1 Reply)
Hi Guys,
Greetings!.
I have executed the cronjob that runs the shell script which is in directory.When the cronjob was executed , I found that the directory where the script resides has got deleted.
Note: The directory was deleted with other use not root user.
The... (9 Replies)