/Documentation/aoe/aoe.txt

https://bitbucket.org/evzijst/gittest · Plain Text · 91 lines · 68 code · 23 blank · 0 comment · 0 complexity · 535dcf88921cf12add3d100f0ccd527d MD5 · raw file

  1. The EtherDrive (R) HOWTO for users of 2.6 kernels is found at ...
  2. http://www.coraid.com/support/linux/EtherDrive-2.6-HOWTO.html
  3. It has many tips and hints!
  4. CREATING DEVICE NODES
  5. Users of udev should find the block device nodes created
  6. automatically, but to create all the necessary device nodes, use the
  7. udev configuration rules provided in udev.txt (in this directory).
  8. There is a udev-install.sh script that shows how to install these
  9. rules on your system.
  10. If you are not using udev, two scripts are provided in
  11. Documentation/aoe as examples of static device node creation for
  12. using the aoe driver.
  13. rm -rf /dev/etherd
  14. sh Documentation/aoe/mkdevs.sh /dev/etherd
  15. ... or to make just one shelf's worth of block device nodes ...
  16. sh Documentation/aoe/mkshelf.sh /dev/etherd 0
  17. There is also an autoload script that shows how to edit
  18. /etc/modprobe.conf to ensure that the aoe module is loaded when
  19. necessary.
  20. USING DEVICE NODES
  21. "cat /dev/etherd/err" blocks, waiting for error diagnostic output,
  22. like any retransmitted packets.
  23. "echo eth2 eth4 > /dev/etherd/interfaces" tells the aoe driver to
  24. limit ATA over Ethernet traffic to eth2 and eth4. AoE traffic from
  25. untrusted networks should be ignored as a matter of security.
  26. "echo > /dev/etherd/discover" tells the driver to find out what AoE
  27. devices are available.
  28. These character devices may disappear and be replaced by sysfs
  29. counterparts, so distribution maintainers are encouraged to create
  30. scripts that use these devices.
  31. The block devices are named like this:
  32. e{shelf}.{slot}
  33. e{shelf}.{slot}p{part}
  34. ... so that "e0.2" is the third blade from the left (slot 2) in the
  35. first shelf (shelf address zero). That's the whole disk. The first
  36. partition on that disk would be "e0.2p1".
  37. USING SYSFS
  38. Each aoe block device in /sys/block has the extra attributes of
  39. state, mac, and netif. The state attribute is "up" when the device
  40. is ready for I/O and "down" if detected but unusable. The
  41. "down,closewait" state shows that the device is still open and
  42. cannot come up again until it has been closed.
  43. The mac attribute is the ethernet address of the remote AoE device.
  44. The netif attribute is the network interface on the localhost
  45. through which we are communicating with the remote AoE device.
  46. There is a script in this directory that formats this information
  47. in a convenient way.
  48. root@makki root# sh Documentation/aoe/status.sh
  49. e10.0 eth3 up
  50. e10.1 eth3 up
  51. e10.2 eth3 up
  52. e10.3 eth3 up
  53. e10.4 eth3 up
  54. e10.5 eth3 up
  55. e10.6 eth3 up
  56. e10.7 eth3 up
  57. e10.8 eth3 up
  58. e10.9 eth3 up
  59. e4.0 eth1 up
  60. e4.1 eth1 up
  61. e4.2 eth1 up
  62. e4.3 eth1 up
  63. e4.4 eth1 up
  64. e4.5 eth1 up
  65. e4.6 eth1 up
  66. e4.7 eth1 up
  67. e4.8 eth1 up
  68. e4.9 eth1 up