09-26-2018
Whoa!! Hang on a minute. Let's explain some things here.
Any one filesystem can only be mounted by one operating system at a time. Mounting the same filesystem on multiple machines is an instant recipe for corruption.
Sometimes storage systems (SANs, NAS's, etc) can be dual-tailed into two different machines but only when a suitable software suite (cluster software) is managing the ownership (at any one time) of each filesystem on the storage. Then, when a failover occurs, the (expensive) cluster suite will swap over the mounted filesystems from one system to another.
As Jim eluded to, the filesystem(s) can only be mounted by one O/S which controls file locking, file access (read/write), etc, and any second node needs to access those filesystems over the network (via NFS). So, repeat, mounting a filesystem on more than one system at the same time is big trouble. Make no mistake about that.
Last edited by hicksd8; 09-26-2018 at 04:25 PM..
This User Gave Thanks to hicksd8 For This Post:
7 More Discussions You Might Find Interesting
1. HP-UX
Im trying to simply share a directory on one unix server and mount that share on a different unix server.
There is no "share" command like on sun. What is the command to create a share on HP-UX? (2 Replies)
Discussion started by: bski
2 Replies
2. IP Networking
Sometimes you get the tiger...but sometimes he get you and this latest home network “project” of mine has gnawed on me pretty badly. Perhaps you can offer some technical help. It will be heartily appreciated.
I have a small home network initially comprising two computers running Windows... (1 Reply)
Discussion started by: Annatar
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
Im running 32-bit solaris on sparc. We have a NAS(Network attached drive), with its IP address, username and password.
I'd like to be able to mount it on the solaris machine, and unmount it.
The best possibility would be able to mount it simulataneously on 2 or more systems.
Please... (9 Replies)
Discussion started by: 0ktalmagik
9 Replies
4. Solaris
How to move home directory of NIS user from one system to another system in Solaris.
Thanks & Regards
Durgaprasad (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have two machines. M1 and M2 and having a generic id catadm, these two machines having common mount of /u/catadm directory.
with this setup, ssh autologin is failing for me and asking me to enter password when i try autologin using this generc id from M1 to M2
catadm-M1$ ssh... (3 Replies)
Discussion started by: rbalaj16
3 Replies
6. Solaris
Hi,
I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name
here is what i did :
On the machine holding the internal disk
in vfstab i added the line
/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Discussion started by: zionassedo
2 Replies
7. Solaris
Hi,
I am having some NFS directory consistency problems with the below setup on a local (192.) network:
1. Different permissions (chmod) for the same NFS dir are reflected on different clients.
2. (more serious) an NFS dir created on client1 cannot be accessed on client2; this applies to some... (10 Replies)
Discussion started by: cosmojetz
10 Replies
LEARN ABOUT CENTOS
gfs2_jadd
gfs2_jadd(8) System Manager's Manual gfs2_jadd(8)
NAME
gfs2_jadd - Add journals to a GFS2 filesystem
SYNOPSIS
gfs2_jadd [OPTION]... <DEVICE|MOINTPOINT>...
DESCRIPTION
gfs2_jadd is used to add journals (and a few other per-node files) to a GFS2 filesystem. 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 unaffected.
You may only run gfs2_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run
gfs2_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 gfs2_jadd. The gfs2_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.
OPTIONS
-c MegaBytes
Initial size of each journal's quota change file
-D Print out debugging information about the filesystem layout.
-h Prints out a short usage message and exits.
-J size
The size of the new journals in megabytes. The defaults to 32MB (the minimum size allowed is 8MB). If you want to add journals of
different sizes to the filesystem, you'll need to run gfs2_jadd once for each different size of journal.
-j num The number of new journals to add.
-q Be quiet. Don't print anything.
-V Version. Print version information, then exit.
SEE ALSO
mkfs.gfs2(8) gfs2_grow(8)
gfs2_jadd(8)