> > The main reason that I can think of is that the I/O must be a complete > block. By making the physical block == maximum block on the track (or > nearest multiple of the "logical block"), you must read and > write the entire > track in order to get / update any "logical block" contained > within that > track. This could possibly cause excessive I/O traffic to the > disk. For > sequential type I/O, this would be excellent. For a data base > with random > I/O, however, it could be very bad. > Hmm, didn't think about random access. See...told you I was being stoopid. ;-)
Leland
