|
@@ -1,3 +1,8 @@
|
|
|
+ATA over Ethernet is a network protocol that provides simple access to
|
|
|
+block storage on the LAN.
|
|
|
+
|
|
|
+ http://support.coraid.com/documents/AoEr11.txt
|
|
|
+
|
|
|
The EtherDrive (R) HOWTO for 2.6 and 3.x kernels is found at ...
|
|
|
|
|
|
http://support.coraid.com/support/linux/EtherDrive-2.6-HOWTO.html
|
|
@@ -26,20 +31,12 @@ CREATING DEVICE NODES
|
|
|
There is a udev-install.sh script that shows how to install these
|
|
|
rules on your system.
|
|
|
|
|
|
- If you are not using udev, two scripts are provided in
|
|
|
- Documentation/aoe as examples of static device node creation for
|
|
|
- using the aoe driver.
|
|
|
-
|
|
|
- rm -rf /dev/etherd
|
|
|
- sh Documentation/aoe/mkdevs.sh /dev/etherd
|
|
|
-
|
|
|
- ... or to make just one shelf's worth of block device nodes ...
|
|
|
-
|
|
|
- sh Documentation/aoe/mkshelf.sh /dev/etherd 0
|
|
|
-
|
|
|
There is also an autoload script that shows how to edit
|
|
|
/etc/modprobe.d/aoe.conf to ensure that the aoe module is loaded when
|
|
|
- necessary.
|
|
|
+ necessary. Preloading the aoe module is preferable to autoloading,
|
|
|
+ however, because AoE discovery takes a few seconds. It can be
|
|
|
+ confusing when an AoE device is not present the first time the a
|
|
|
+ command is run but appears a second later.
|
|
|
|
|
|
USING DEVICE NODES
|
|
|
|
|
@@ -54,9 +51,9 @@ USING DEVICE NODES
|
|
|
"echo > /dev/etherd/discover" tells the driver to find out what AoE
|
|
|
devices are available.
|
|
|
|
|
|
- These character devices may disappear and be replaced by sysfs
|
|
|
- counterparts. Using the commands in aoetools insulates users from
|
|
|
- these implementation details.
|
|
|
+ In the future these character devices may disappear and be replaced
|
|
|
+ by sysfs counterparts. Using the commands in aoetools insulates
|
|
|
+ users from these implementation details.
|
|
|
|
|
|
The block devices are named like this:
|
|
|
|
|
@@ -79,8 +76,8 @@ USING SYSFS
|
|
|
The netif attribute is the network interface on the localhost
|
|
|
through which we are communicating with the remote AoE device.
|
|
|
|
|
|
- There is a script in this directory that formats this information
|
|
|
- in a convenient way. Users with aoetools can use the aoe-stat
|
|
|
+ There is a script in this directory that formats this information in
|
|
|
+ a convenient way. Users with aoetools should use the aoe-stat
|
|
|
command.
|
|
|
|
|
|
root@makki root# sh Documentation/aoe/status.sh
|
|
@@ -124,3 +121,21 @@ DRIVER OPTIONS
|
|
|
usage example for the module parameter.
|
|
|
|
|
|
modprobe aoe_iflist="eth1 eth3"
|
|
|
+
|
|
|
+ The aoe_deadsecs module parameter determines the maximum number of
|
|
|
+ seconds that the driver will wait for an AoE device to provide a
|
|
|
+ response to an AoE command. After aoe_deadsecs seconds have
|
|
|
+ elapsed, the AoE device will be marked as "down".
|
|
|
+
|
|
|
+ The aoe_maxout module parameter has a default of 128. This is the
|
|
|
+ maximum number of unresponded packets that will be sent to an AoE
|
|
|
+ target at one time.
|
|
|
+
|
|
|
+ The aoe_dyndevs module parameter defaults to 1, meaning that the
|
|
|
+ driver will assign a block device minor number to a discovered AoE
|
|
|
+ target based on the order of its discovery. With dynamic minor
|
|
|
+ device numbers in use, a greater range of AoE shelf and slot
|
|
|
+ addresses can be supported. Users with udev will never have to
|
|
|
+ think about minor numbers. Using aoe_dyndevs=0 allows device nodes
|
|
|
+ to be pre-created using a static minor-number scheme with the
|
|
|
+ aoe-mkshelf script in the aoetools.
|