Reply to post: Ah, SCSI

Who needs the A-Team or MacGyver when there's a techie with an SCSI cable?

ShortLegs

Ah, SCSI

Many moons ago my nickname was "SCSI Al", or more likely "Scuzzy Al". Absolutely loved SCSI, and from 1996 every box I had was SCSI based. Usually based around "God's Own Controller", the Adaptec 2940UW until U160/320 came about (I had one U2 controller, but really skipped that generation), and some form of RAID, be it Compaq SMART-2DH or LSI boards.

*never* had an issue with termination, mixing devices (even 8-bit devices on a 16-bit bus - just install the narrow devices at the end of the chain and use the correct terminator).

The only problem I ever experienced wasn't really SCSI related. Large *cough cough* multinational, migrating from Netware 3 to Netware 4. B and I working late to migrate data from old to new servers. Large company, IT recognised as mission-critical and *no* expense was spared; Compaq shop through and through, mahoosive quad PPro boxes, loads RAM, mirrored RAID5 arrays 5x9GB UW drives (largest capacity one could buy at the time), spare components AND servers in server room "just in case".

Its the last weekend of the project, and we migrating over the main site file-and-print server and backup, which also provided Bindery services for network login. And the darn migration fails. Every. Single. Time. The new server runs out of disk space, despite having a [slightly] larger partition.

Those of you who remember Netware 3 and Netware 4 are nodding in anticipation. NW3 defaulted to a 4KB block size, although 16KB could be specified - but with a large number of small (<16kb) files, or filesize not a multilple of 16, disk space would be wasted. NW4 used a block size dependant on volume size. IIRC we had 32KB blocks, and no sub-block allocation...

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon