First i would ask why the hell ? The netapp filer is a very good CIFS/SMB share server. Using it as an iSCSI target -- which is not is primary function (netapp filer are more NAS than SAN) -- will only create limitations (unable to resize volume on the fly, unable to use wafl attributes to store windows security acl, ...) with no visible gain ...
Also your server seem very overkill to me, i must hope it won't have to be just a samba<=>iscsi interface ... For iSCSI and netapp in general, first make sure that you have at least 10% of free space inside the volume, and 10% of free space inside the aggregate or else perf could suffer and more important you won't be able to launch the reallocate process ("defrag"). The following is the recommended netapp/iscsi optimisations, however open-iscsi doesn't support multiple connections per session now (iirc), so the best way to have parallel access is to use multipath iscsi.iswt.max_ios_per_session 64 iscsi.max_connections_per_session 16 iscsi.max_ios_per_session 64 2009/4/14 Frank Bonnet <f.bon...@esiee.fr> > > Hello > > I'm setting up a Samba server that will use iSCSI to access > some shares on a NetAPP filer ( FAS 2050 ) > > I would like to know if some of you has already build such > configuration and if there are some tricks to optimize it. > > The Linux server is a HP Proliant quad CPU and runs > Debian Lenny, it has 16 Gb of RAM. > > Thanks a lot. > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---