Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
In my case i don't want to install clustering . I just wanted to connect all those two RHEL 5 servers with the SAN. Mainly , in the SAN device , i wanted to create a partition and needed to get mounted to RHEL 5 servers. SAN i'm using for a database. for this database needed to have write permission from RHEL servers.
For example : if i write a file in the First RHEL machine in the SANSs database , that file should be visible for the other RHEL machine as well.
Actually i'm a beginner , could you please give me step by step how to guide coz this implementation is bit critical and i dont have chance to trial run .
You need to make sure you have an HBA installed on the redhat servers. If the hba is there you should see the device under /proc/scsi/... Qlogic HBA's are listed as /proc/scsi/ql***.
Once you have that done and you have zoned the server properly on the fabric you should be able to run system-config-lvm and see the uninitialized disk. You can then initialize the disk, create a partition, and set it to mount.
It is not recommended to have 2 servers mount the same volume without clustering (GFS). You could wind up corrupting the files as nothing will be controlling lock access to the files.
@luke: If this is critical (as in your job is on the line), and you're a beginner, and you have no testing environment, I recommend that you have a frank talk with your boss about hiring a contractor to perform the install / configuration.
You are going to need GFS (or some other clustering file system), or else you'll run into data integrity issues.
run "mount -a" on each server (this should mount everything) and then just "mount" on each server you should see the same mount point (/database on /somedevice) listed on each server. If you dont see the mount for "/database" listed on each server you do not have it mounted on both nodes. That would explain why you can see the directory under /database on one server and not the other.
At this point you might as well just install the rest of the packages for RHCS and configure the cluster software. You can have each node access the disk and file access will be controlled by the lock mechanism you choose (DLM or whatever). You can then have the mounts controlled by the cluster manager (rmanager, cman etc...).
he mentioned he did not want to install clustering which rules out what he was trying to do with standard filesystems with out some type of shared file system management Like NFS or CIFS
Not true. You can install a clustered, non-network filesystem without formally setting up "clustering" (resources, fencing, and the like). It might not be particularly wise in most circumstances, but it can be done.