How does readahead(2) affects a iscsi device
Hi folks, Sorry but not so firm in kernel hacking and structures, but if I've understood this correctly it should perform normally?! The problem is that I do a readahead (the tool) on a iscsi device with infortrend iscsi san as backend to warm up caches and my connection died, correctly the whole controller died and have to be reseted. Has anyone an idea? Cheers Maddin --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
fwparam_ibft and IPv6 support
I see that a couple of ways are being used to get the ibft data from memory - 1) iscsiadm -m fw Which relies on /sys/firmware/ibft/* files to create the record and thus login. 2) fwparam_ibft -b This relies on opening /dev/mem and getting all the parameters and thus login I am seeing a few problems/discrepancies with the fwparam_ibft tool - 1) It is not able to fetch the chap info 2) It lacks IPv6 support. I believe open-suse and sles are some of the distros using this tool. Not sure of debian/ubuntu and others. Hannes - Do you have already fixed patches for these in your suse tree ? -Shyam Iyer --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
