10-12-2009
Does anybody has any idea?
6 More Discussions You Might Find Interesting
1. Red Hat
Hello;
I have 2 node Redhat Cluster (RHEL4 U4 and Cluster Suite) I'm using mc_data fiber channel switch for fencing
when I want to fence manually using
fence_mcdata -a x.x.x. -l xxx -p xxxx -n 5 -o disable
following messages appears
fencing node "test1"
agent "fence_mcdata" reports:... (0 Replies)
Discussion started by: sakir19
0 Replies
2. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
4. Red Hat
I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online.
I have the cluster... (1 Reply)
Discussion started by: mrmurdock
1 Replies
5. Solaris
I build up two node cluster (node1, node2) in virtualbox. For these two nodes I add 5 shared disk. (Also each node have own OS disk).
1 shared disk for vtoc
2 shared disk for NFS resource group
2 shared disk for WEB resource group
When I finished my work; two nodes was ok and shared disk... (4 Replies)
Discussion started by: sonofsunra
4 Replies
6. Solaris
Greetings!
Will be firing up the good ole pizza box, soon. Does anyone know if Solaris 7 is still okay to use? Last time I attempted was 2006.
Thank you in advance,
ControlTomato (6 Replies)
Discussion started by: ControlTomato
6 Replies
LEARN ABOUT CENTOS
mkfs.bfs
MKFS.BFS(8) System Administration MKFS.BFS(8)
NAME
mkfs.bfs - make an SCO bfs filesystem
SYNOPSIS
mkfs.bfs [options] device [block-count]
DESCRIPTION
mkfs.bfs creates an SCO bfs filesystem on a block device (usually a disk partition or a file accessed via the loop device).
The block-count parameter is the desired size of the filesystem, in blocks. If nothing is specified, the entire partition will be used.
OPTIONS
-N, --inodes number
Specify the desired number of inodes (at most 512). If nothing is specified, some default number in the range 48-512 is picked
depending on the size of the partition.
-V, --vname label
Specify the volume label. I have no idea if/where this is used.
-F, --fname name
Specify the filesystem name. I have no idea if/where this is used.
-v, --verbose
Explain what is being done.
-c This option is silently ignored.
-l This option is silently ignored.
-h, --help
Display help text and exit.
-V, --version
Display version information and exit. Option -V only works as --version when it is the only option.
EXIT CODES
The exit code returned by mkfs.bfs is 0 when all went well, and 1 when something went wrong.
SEE ALSO
mkfs(8)
AVAILABILITY
The mkfs.bfs command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.
util-linux July 2011 MKFS.BFS(8)