Talk:Hot swapping

From Wikipedia, the free encyclopedia

Contents 1 Hot Swap vs Hot Swapping 2 PS/2 3 Firewire: Cold or Hot? 4 IDE hot swap bays? 5 Damage 6 Component Shutdown and Redundancy

[edit] Hot Swap vs Hot Swapping

Somehow a names needs to be chosen and hot swap and hot swapping need to be combined. Kail Ceannai 21:52, 2005 May 12 (UTC)

Hello? Merge anyone? 193.1.100.102 11:35, 18 August 2005 (UTC)

Kail, both of your links go to the same article, so, in effect, the two terms are already combined. --John R. Sellers 04:59, 24 August 2006 (UTC)

[edit] PS/2

It says PS/2 is not hot-swappable, but this is not true. I can hot-swap my keyboard and mouse on my Linux box. 70.52.147.11 00:14, 22 March 2007 (UTC)

Although rare, hotswapping PS/2 mice/keyboards may damage motherboard, most likely by blowing the fuse in-line with the power pin on the PS/2 connector. Having said that, I've also hot-plugged keyboards and mice before with no trouble. Sagsaw 19:16, 14 April 2007 (UTC)

[edit] Firewire: Cold or Hot?

In the section where true hotswappable and hotswappable where the OS must be notified by the user are compared, FireWire is used as an example of both types. Does anyone know which side is the correct one to place FireWire? I guess it should be on the "hot" side, as USB, but I'm not sure.

[edit] IDE hot swap bays?

I was looking for information on how these work: are they reliable, do they slow down the drive? It would be great if someone who knows about this filled in some info on these devices. I know pretty much nothing about it, so I won't even try to mention them.

[edit] Damage

There are two aspects here: one is whether the device(s) break, and the other is whether they work. Devices that are not designed to hot swap may permanently break if plugged or unplugged while powered (example: PS/2). Devices that are designed to hot swap generally have hardware and software aspects. The user can assume that plugging and unplugged while powered will not break them. (Example: USB) But whether they will instantly, automatically "just work" all depends on many factors -- YMMV. -69.87.204.161 01:00, 19 March 2007 (UTC)

[edit] Component Shutdown and Redundancy

The sentence: "More complex implementations may recommend that the component be shut down, but there is sufficient redundancy in the system such that if a component is removed without being shut down, operation continues."

This seems a bit confusing to me however I want to avoid altering the meaning by changing the sentence structure. Does the following sound OK?

"Whilst more complex implementations may recommend that the component be shut down, there is usually sufficient redundancy to allow operation to continue uninterrupted while the component is taken offline." Sardaukar86 22:38, 13 November 2007 (UTC)

I don't think it is quite the point being made. I think the point is that if you have hot standby type configurations then although there may be a proper way to nicely swap over, the fail over mechanism should allow for an abrupt changeover. I'd quite like to see some source examples, as this is an important point. On a SAN, you have hot standby disks and you can go through a management procedure to implement the standby disk, swapping the offline disk without the need to shutdown the SAN. If you take out the broken but active disk without first taking it out of the set, would the system survive? (Answer: I don't know and I wouldn't try it!). Spenny 09:52, 14 November 2007 (UTC)