9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Team,
I need to determine whether my OS is 32 bit or 64 bit.
For linux I am running :-
bash$ uname -a
Linux xxxx 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/LinuxThis tells me that Linux is 64 bit as it is x86_64.
For Solaris
bash$ uname -a... (4 Replies)
Discussion started by: Raj999
4 Replies
2. Shell Programming and Scripting
Need help with the script, I am trying to include this script as part of kickstart profile.
based of the host's IP address, in this case if the host is IP starting with 10.10.3.* or 10.10.6.*, I will be pushing appropriate routing file from my web server.
I validate host IP from nslookup.
... (3 Replies)
Discussion started by: bobby320
3 Replies
3. Shell Programming and Scripting
A regular ebcdic mainframe tape usually contains header information the 1st three blocks of the tape. The header information tells the computer/user more information about what is on tape. The header info is 240 bytes in length at 80 bytes each header. The 1st block/header is volume name or... (1 Reply)
Discussion started by: Linux-wannabe
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
i have a script called a.sh and within a.sh it calls b.sh.
when i do a ps -ef | grep a.sh, i get two sets of number
user_test 4225 3250 0 10:31 pts/1 00:00:00 a.sh
when i do a ps -ef | grep b.sh, i get two sets of number
user_test 4269 4225 22 10:31 pts/1 00:00:45... (17 Replies)
Discussion started by: new2ss
17 Replies
5. Programming
Hello all! I've searched the archives, google, documentation and I can't seem to find any answer regarding my question.
Our code has to be lint free and due to the following lint warning ---> logical expression always true: op "||" <--- we are forced to #include <note.h > (which appears to be... (3 Replies)
Discussion started by: quattro20v
3 Replies
6. UNIX for Advanced & Expert Users
Hi,
when I execute some simple commands on my solaris system, I am getting the following warning message:
Could anybody tell me what could be the reason
Ex:- If I give the command,
which ls
Warning: cannot determine current directory
... (15 Replies)
Discussion started by: axes
15 Replies
7. UNIX for Dummies Questions & Answers
Hi guys.
Hopefully someone can help me.
We have a old Unix box for the accounts people. What id like to do is query it for the intranet. Trouble is im not sure what type of database the server uses.
How would i go about finding out what it is? I have complete access to the hardrive and... (2 Replies)
Discussion started by: RageMonkey
2 Replies
8. IP Networking
Given the interfaces on a firewall:
eth0 Link encap:Ethernet HWaddr 02:40:67:34:F5:47
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
eth1 Link encap:Ethernet HWaddr 86:23:98:45:35:56
inet addr:123.45.240.69 Bcast:255.255.255.255 ... (2 Replies)
Discussion started by: kikikaka
2 Replies
9. UNIX for Dummies Questions & Answers
I have a console server that runs some form of UNIX/Linux, but I get a bash shell, and I want to determine how many processor (what speed) and them amount of RAM in the system. (2 Replies)
Discussion started by: bbrandeb49
2 Replies
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)
