Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Looks like a viable way to create a SAN' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Looks like a viable way to create a SAN
Authored by: _iCeb0x_ on Jul 27, '08 06:16:37PM
Firewire was conceived as a sucessor to SCSI, but implemented as a serial bus and with more features, like hot-plugging and self-configuration.

From Wikipedia's page on Firewire (http://en.wikipedia.org/wiki/Firewire):

1. It does not need a computer host;

2. It allows peer-to-peer device communication — such as communication between a scanner and a printer — to take place without using system memory or the CPU;

3. FireWire also supports multiple hosts per bus;

4. FireWire devices are organized at the bus in a tree topology. Each device has a unique self-id. One of the nodes is elected root node and always has the highest id;

5. [An IP] network can be set up between two computers using a single standard FireWire cable, or by multiple computers through use of a hub.

So, it seems to me that it could be possible for multiple computers to access multiple drives on a Firewire network, but IP is not really useful for that, because most of the Firewire external drives are not capable of running IP over Firewire.

The question is: what's preventing us from a cheap SAN system? Lack of IP support on Firewire bridge chips? Or the Firewire stack implementation on most OS's is lacking support for this?

[ Reply to This | # ]