• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (2)

1 AnthonyEnglish commented Permalink

Chris, <div>&nbsp;</div> Do you think this could be done without rebooting the VIOS? Could the same thing be achieved just by removing the devices from the virtual server adapter? <div>&nbsp;</div> Also, Technote T1010944 ​"Unable to See New VSCSI Disk on Existing vhost" provides a bit of relevant information <br /> http://goo.gl/MwGtp <div>&nbsp;</div> Anthony

2 cggibbo commented Permalink

Well, actually I'm not sure. But based on the data we collected, no, I think you need to either reboot the VIOS (or perhaps remove and reconfigure) the associated vhost adapter. The vtopt device was assigned to the vhost adapter (vhost0) first i.e. before any SAN hdisks. This seems to have had an impact on the allowable max_tranfer size on vhost0: <div>&nbsp;</div> vhost0 V1-C20, max_xfer_size: 40000 <div>&nbsp;</div> Yes, that Technote does indeed discuss a similar scenario. But I must say we never considered the vtopt device had the potential to introduce a similar challenge! But it all makes perfect sense in hindsight. <div>&nbsp;</div> This was also the first time I'd ever tried changing the max_transfer attribute on a VSCS hdisk. <div>&nbsp;</div> There is always something new to learn!

Add a Comment Add a Comment