Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Wanted: Geographically distributed filesystem solution Post 302247138 by otheus on Wednesday 15th of October 2008 04:01:49 AM
Old 10-15-2008
Wanted: Geographically distributed filesystem solution

I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices.

I want to evaluate several solutions, and I'm open to solutions ranging from free, off-the-shelf, off-the-top-shelf (ie, really expensive), to custom designed by leading tech suppliers.

(Please help)
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Distributed

I've downloaded distributed latest build for dnetc, and I think i installed it. Not sure where the excicuteable would be. Any help? i realize this is a little ambigious, so I can allways reintstall it if i know how to put it in a specific directory.. does anyone know if VNC works for the Intel... (3 Replies)
Discussion started by: veitcha
3 Replies

2. UNIX for Dummies Questions & Answers

hwo to find shared filesystem and local filesystem in AIX

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

3. Solaris

Solaris Filesystem vs. Windows FileSystem

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

4. AIX

Mount Filesystem in AIX Unable to read /etc/filesystem

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

5. Filesystems, Disks and Memory

distributed filesystem over internet/VPN

On this forum was already posted similar question, but it was 4 years ago and didn't give me answers. I have two groups of engineers that works in far locations connected via VPN. Physically, the connection is a DSL. Currently we have a linux server in one location that provide files over... (4 Replies)
Discussion started by: Domino
4 Replies
aoe-stat(8)						      System Manager's Manual						       aoe-stat(8)

NAME
aoe-stat - print aoe device status report SYNOPSIS
modprobe aoe aoe-stat env sysfs_dir=/sys aoe-stat DESCRIPTION
The aoe-stat script collects information on ATA over Ethernet devices from sysfs. For each AoE device the kernel has discovered, there is one row in the script's output. Each row has the following columns. devicename The device name is of the form eX.Y, with X being the AoE device shelf address, and Y being the AoE slot address. size The size of the AoE device is in gigabytes (billions of bytes). ifname The network interface name is printed in the third column. payload The number of bytes read from or written to the storage target in each AoE packet appears in the fourth column, unless the aoe driver does not export this information. status The device status is in the last column. Possible values are up, down, and down,closewait. The "up" status means the aoe driver considers this device ready for I/O. The "down" status means the opposite. The "down,closewait" status means that some software still has the device open, and when this straggler closes the device, it will enter the "down" state. ENVIRONMENT VARIABLES
If the sysfs_dir variable is set in the environment, it will override the default location where aoe-stat will look for sysfs, namely /sys. WARNINGS
If the minor device number of a device node does not match that of its namesake, aoe-stat will print a warning as shown below. nai:~# aoe-stat e0.3 0.104GB eth0 up e0.4 4398.046GB eth0 up e20.0 1000.215GB eth0 up e42.0 2000.431GB eth0 up aoe-stat Warning: device node /dev/etherd/e45.1 has wrong minor device number e45.1 1152.874GB eth0 up Using such a device node is dangerous, because its name doesn't match the actual device that you would be reading from and writing to. Such a broken device node should be removed. Device nodes are created by udev or (on systems without udev) by aoe-mkdevs. EXAMPLE
In this example, the root user on a host named nai loads the aoe driver module and then prints a list of all the available aoe devices. Then he remembers to bring up the storage network interfaces, does an AoE discovery, and prints the list again. This time the list shows all the devices in shelf seven. nai:~# modprobe aoe nai:~# aoe-stat nai:~# ifconfig eth3 up nai:~# aoe-discover nai:~# aoe-stat e0.0 10995.116GB eth0 up e0.1 10995.116GB eth0 up e0.2 10995.116GB eth0 up e1.0 1152.874GB eth0 up e7.0 370.566GB eth0 up nai:~# SEE ALSO
aoe-discover(8), aoe-interfaces(8), aoe-mkdevs(8), aoe-mkshelf(8), aoetools(8), udev(7). AUTHOR
Ed L. Cashin (ecashin@coraid.com) aoe-stat(8)
All times are GMT -4. The time now is 09:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy