11-22-2004
If the rsync man pages have not been installed, then you'll see nothing.
If you've not got it already, check out
rsync HERE!.
9 More Discussions You Might Find Interesting
1. Linux
Hi Linux Admin Guys
My onsite server is always 15 min slow and seems like NTPD (Network Time Protocol (NTP) daemon) not running properly. can anyone suggest me how to rectify this problem? we can't seem to get NTP to properly sync the clock.
Any help is resolving the issue will be helpful.... (12 Replies)
Discussion started by: csaha
12 Replies
2. Solaris
Hi all,
currently , my root filesystem already reach 90 ++%
I already add more cylinder in the root partition as below
Part Tag Flag Cylinders Size Blocks
0 root wm 67 - 5086 38.46GB (5020/0/0) 80646300
1 swap wu 1 - ... (11 Replies)
Discussion started by: SmartAntz
11 Replies
3. Filesystems, Disks and Memory
Hi all,
I tried setting up RAID between 2 partitions and it was success.
If I write some things on /dev/md0, both partition got affected.
Then I stop the RAID, and I mounted one of my partition and I created a file in it.
Now I started the RAID (mdadm --assemble --scan)
What I expected... (1 Reply)
Discussion started by: lakshmananindia
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local.
Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies
5. Solaris
Hi guys!
Could you tell me what's the difference of filesystem of Solaris to filesystem of Windows? I need to compare both.
I have read some over the net but it's so much technical. Could you explain it in a more simpler term? I am new to Solaris. Hope you help me guys.
Thanks! (4 Replies)
Discussion started by: arah
4 Replies
6. AIX
Dear all,
We are facing prolem when we are going to mount AIX filesystem, the system returned the following error
0506-307The AFopen call failed
: A file or directory in the path name does not exist.
But when we ls filesystems in the /etc/ directory it show
-rw-r--r-- 0 root ... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies
7. Solaris
We have 2 Data centers in different part of the world , and we are in need to sync our home directory in both the locations .. that is if a file is written to my home dir in DC1 ..i want the file to be there in my home dir at DC2 systems too and vice versa ... the home dir content is stored in... (1 Reply)
Discussion started by: skamal4u
1 Replies
8. UNIX for Advanced & Expert Users
I am trying to sync the source tree into backup and somehow
this one file dumper.c is not in sync, see below after running the script:
/u/prj/dir$ l -tr dumper.c /v/tmp/prj_src/dir/dumper.c
-rw-rw-r-- 1 prj group 15635 Jun 20 16:28 /v/tmp/prj_src/dir/dumper.c
-rw-rw-r-- 1 prj ... (2 Replies)
Discussion started by: migurus
2 Replies
9. Red Hat
dear experts linux
i am using RHEL 5.5 run on a physical server.
i am front of a big trouble, the Rhel can't run correctly , it show me this error message in black screen:
reading all physical volumes. this my take a while ..
found volume group "VolGroup00" using metadata type lvm2
9... (1 Reply)
Discussion started by: wassimpb
1 Replies
LEARN ABOUT DEBIAN
gfs_jadd
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)