Sponsored Content
Full Discussion: Linux os clustering
Operating Systems Linux Linux os clustering Post 302659577 by thmnetwork on Thursday 21st of June 2012 07:15:39 AM
Old 06-21-2012
so to clarify neither node is coming up? Are you able to comment the relevant lines out in fstab and boot successfully. If so what is the result of trying to manually mount the LUNs?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Clustering solution for RH Linux AS and Solaris x86/AMD 64

Dear All Experts, Would like to know the maturity/ stability of Redhat Linux AS 3.0 and Solaris. My organization need to setup cluster solution. We are well-versed with Veritas Cluster on Solaris. We are thinking of waiting for certification support of the various ISV like Oracle, Veritas... (3 Replies)
Discussion started by: izy100
3 Replies

2. UNIX for Dummies Questions & Answers

Clustering or not

I woulld like to use the JDE newest version, but I am considering whether using 2 X Wintel server with clustering or 1 Unix server without clustering. Is Unix stable enough to except the clustering? (0 Replies)
Discussion started by: superlouis
0 Replies

3. UNIX for Advanced & Expert Users

Mirroring and Clustering with Veritas

Can anybody help me how to mirror the solaris 10 step-by-step with veritas. Have two disks. Then how can I cluster with veritas (1 Reply)
Discussion started by: karole
1 Replies

4. Red Hat

Clustering Red Hat Enterprise linux Advanced Platform 5.2 (x86-64 bit)

Hello Professionals, We have high-end HP rack servers. We need to provide application fail-over for business continuity. We have done benchmarking of the application on RHEL 5.2 on HP servers to estimate the hardware requirement so as to meet next 3-5 years business growth. Presently we... (1 Reply)
Discussion started by: kgayyar
1 Replies

5. HP-UX

need to recall my hp serviceguard clustering

hi, do u know any link that will get back to me up to speed on hp serviceguard on clustering? thanks and much appreciated, itik (2 Replies)
Discussion started by: itik
2 Replies

6. Solaris

Clustering filesystems

SunOS 5.10 Generic_142900-15 sun4u sparc SUNW,SPARC-Enterprise How can I tell if "clustering" is being used in my shop? I have to file systems that are identical. These filesystems are nfs mounted. But how can I tell if they are being kept in sync as a result of clustering or some other... (2 Replies)
Discussion started by: Harleyrci
2 Replies

7. UNIX for Dummies Questions & Answers

Linux Clustering

hi guys Some time ago I used Linux HA(Heartbeat) to setup like 3 cluster. Now I have to install another 2 cluster and was checking more info to be sure HA was still used but I found some other stuff like OpenAIS - Corosync - Pacemaker to tell you the truth I am kinda confused here I get... (0 Replies)
Discussion started by: karlochacon
0 Replies

8. Ubuntu

Application clustering in Linux Ubuntu

Dear, Please help me to configure application clustering in linux ubuntu. Application is running apache server. Please help Jewel ---------- Post updated at 01:07 PM ---------- Previous update was at 12:48 PM ---------- linuxvirtualserver dot org in this link i go there's three... (2 Replies)
Discussion started by: Jewel100
2 Replies

9. HP-UX

HP-UX Clustering

Hello guys, I would like to ask for your assistance, since i am new to HP-UX. Please give me some documentation about clustering in HP-UX. More precisely design,architecture, configuring etc. I am working on my master thesis right now and would like to include some guidance about that.... (1 Reply)
Discussion started by: bazillion
1 Replies

10. Ubuntu

Newbie With Linux Clustering, Need Help!!

Hi All, I am new user here and a new one to try clustering with Ubuntu nodes, and need help. If I should be in another place please mention. I have a two nodes with Ubuntu 14.04 installed on them. I need to make a cluster consisting of these two nodes with purpose of experimentation with... (3 Replies)
Discussion started by: IncognitoExpert
3 Replies
SYSTEMD-FSTAB-GENERATOR(8)				      systemd-fstab-generator					SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 04:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy