2008/9/8 Will Murnane <[EMAIL PROTECTED]>: > replacing the > motherboard with a cheap Core 2 one significantly *improved* > performance, despite limiting the controller to vanilla-PCI speeds. > CPU usage wasn't really an issue, but speeds were nevertheless limited > to 20 MB/s or so locally. With the new motherboard I get about 70 > MB/s over network, mostly disk-limited.
That's interesting. Getting a new board and cheap modern cpu isn't really an issue so i'll most likely do that. My old fileserver was managing 500MB/sec burst and 300MB/sec sustained read (according to hdtach) so i'd not like to be going completely backwards with my new setup. > You'll have to present part of the volume via iSCSI and part via NFS; > they can't overlap. Also, you must define how large an iSCSI volume > you want up front. Although you can resize it later, this will entail > resizing the filesystem over network to allow the remote machine to > use all the new space. Sorry, I wasn't clear. I didn't mean to use both protocols on the same slice of storage > If you assign an IP address to a single NIC, then all traffic will > flow over that interface. Trunking Intel interfaces is also possible, > but if you don't want that to happen it won't by default. Yes, I understand that. However, if I have two NIC's on two seperate subnets and simply enable iSCSI, how do I bind it to only one of the NIC's? I don't want the storage to be presented at all on the other NIC(s). I'll go do some reading on it incase it's stupidly simple :) Thanks all. _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
