sexy actress nude video here
sexy actress nude video here sexy actress nude video here http://makemoney2onlines.blogspot.com http://makemoney2onlines.blogspot.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
RE: open-iscsi and discover newly created LUN
> -Original Message- > From: open-iscsi@googlegroups.com [mailto:open-is...@googlegroups.com] > On Behalf Of Mike Christie > Sent: Saturday, June 13, 2009 8:30 AM > To: open-iscsi@googlegroups.com > Subject: Re: open-iscsi and discover newly created LUN > > > On 06/12/2009 01:16 AM, TheR wrote: > > Using open-iscsi as initiator on ubuntu 9.04. > > > > > > I want to set up virtual environment with iscsi target server which > is > > ubuntu based. On target decided to use single tid under which I > create > > multple LUN-s, which represent disks used by initiator which is KVM > > server. One LUN becomes a disk used by one virtual machine on KVM > > server. > > > > My problem is when I create new LUN on target (under same tid), this > > LUN doesn't get recognized by initiator without restarting initiator > > iscsi service. Which in return breaks all curently running machines > on > > KVM server. > > > > I have seen same behaviour on Red Hat 5.1. > > > > On RHEL 5.3 and newer, upstream and probably ubuntu (not sure what > version is in there), you can do > > iscsiadm -m session -r $SID --rescan > Mike - The target can initiates a UNIT ATTENTION with additional sense as "Report LUN data changed", I don't see that currently being handled by the SCSI-ML. A rescan may not be necessary if this information is received by the open-iscsi. Do you have a background on the SCSI-ML part ? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iscsid : mgmt_ipc_write_rsp: rsp to fd 5
Hi Mike, GOOD NEWS, even if I don't be able to change code (I have a problem with my compilator virtual (vmware) machine, stupid change I do ...) I have follow you remarks and my intuition ... lol So I have added (in first pos.) a named "root" user in the passwd file (remember Qnap has only an "admin" user)and attach this root user to the group 0 (administrators in Qnap) and the result is (iscsid run in -f -d 8) : [/etc] # iscsiadm -m discovery -t sendtargets -p 127.0.0.1 iscsid: poll result 1 iscsid: mgmt_ipc_write_rsp: rsp to fd 5 iscsid: poll result 1 iscsid: mgmt_ipc_write_rsp: rsp to fd 5 iscsid: poll result 1 iscsid: mgmt_ipc_write_rsp: rsp to fd 5 iscsid: poll result 1 iscsid: mgmt_ipc_write_rsp: rsp to fd 5 iscsid: poll result 1 iscsid: mgmt_ipc_write_rsp: rsp to fd 5 iscsid: poll result 1 iscsid: mgmt_ipc_write_rsp: rsp to fd 5 127.0.0.1:3260,1 iqn.2004-04.com.qnap:TS-219:iSCSI.testEXT3.8C3E96 127.0.0.1:3260,1 iqn.2004-04.com.qnap:TS-219:iSCSI.testNTFS.8C3E96 127.0.0.1:3260,1 iqn.2004-04.com.qnap:TS-219:iSCSI.testFAT32.8C3E96 WHAOO first step is passed even if it's not a "real" solution to have two UID 0 (root and admin), so if you have time to identified WHY you need a "root" user and not only a user with UID=0 ? (I do the search when I get back running my virtual machine with my vmware debian cross compile system). I have now a new error ... but not sure that it's not due to a mix between all modules that I will test ... I try to restart with a full coherent modules (I think I have modules in ver. 2.0-724 (native compile on another Qnap) and iscsid in 2.0-870 ... sorry for that mix, I try lot of tests . For information the error when I try to log to a target [/etc] # iscsiadm -m node -T iqn. 2004-04.com.qnap:TS-219:iSCSI.testEXT3.8C3E96 -p 127.0.0.1:3260 -l Logging in to [iface: default, target: iqn. 2004-04.com.qnap:TS-219:iSCSI.testEXT3.8C3E96, portal: 127.0.0.1,3260] iscsid: poll result 1 iscsid: in read_transports iscsid: Adding new transport tcp iscsid: sysfs_attr_get_value: open '/class/iscsi_transport/ tcp'/'handle' iscsid: sysfs_attr_get_value: new uncached attribute '/sys/class/ iscsi_transport/tcp/handle' iscsid: sysfs_attr_get_value: add to cache '/sys/class/iscsi_transport/ tcp/handle' iscsid: sysfs_attr_get_value: cache '/sys/class/iscsi_transport/tcp/ handle' with attribute value '3205089176' iscsid: sysfs_attr_get_value: open '/class/iscsi_transport/tcp'/'caps' iscsid: sysfs_attr_get_value: new uncached attribute '/sys/class/ iscsi_transport/tcp/caps' iscsid: sysfs_attr_get_value: add to cache '/sys/class/iscsi_transport/ tcp/caps' iscsid: sysfs_attr_get_value: cache '/sys/class/iscsi_transport/tcp/ caps' with attribute value '0x39' iscsid: Matched transport tcp iscsid: Allocted session 0x413f0 iscsid: no authentication configured... iscsid: resolved 127.0.0.1 to 127.0.0.1 iscsid: get conn context 0x48838 iscsid: set TCP recv window size to 524288, actually got 262142 iscsid: set TCP send window size to 524288, actually got 262142 iscsid: connecting to 127.0.0.1:3260 iscsid: sched conn context 0x48838 event 2, tmo 0 iscsid: thread 0x48838 schedule: delay 0 state 3 iscsid: Setting login timer 0x467a8 timeout 15 iscsid: thread 0x467a8 schedule: delay 60 state 3 iscsid: thread 000467a8 wait some more iscsid: exec thread 00048838 callback iscsid: put conn context 0x48838 iscsid: connected local port 36504 to 127.0.0.1:3260 iscsid: in kcreate_session iscsid: in __kipc_call iscsid: in kwritev iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: iqn. 2004-04.com.qnap:TS-219:iSCSI.testEXT3.8C3E96, portal: 127.0.0.1,3260]: iscsiadm: initiator reported error (18 - could not communicate to iscsid) [/etc] # ps -eaf | grep iscsid 17480 root548 S grep iscsid [/etc] # Thanks again for your effort ... I also continue and try to clarify all points. best regards. Philippe. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: iscsid crashes while login/logout
Hi First, no, we don't do iscsi-boots. All systems boot from local disks and attach iscsi-targets for application-specific filesystems - like / var or /opt for databases or online-content. The second use of iscsi is for Xen DomUs. We login to targets from Dom0 and let the DomUs access the blockdevices through Xen. All this is trivial and pretty much standard stuff, nowadays. BTW, the storage Lan ist likewise pretty much standard: bonded 2*gbit ethernet, static routes, sendtargets discovery. Second, I will try the patch on the upcoming monday, as soon as I get back to office. I will post the results here. Thanks for the fast patch. Would be nice if the frist try fixes the problem ;) Regards, Thomas --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: do we need a new list for kernel patches
On 06/14/2009 12:52 PM, Bart Van Assche wrote: > On Sun, Jun 14, 2009 at 11:23 AM, Boaz Harrosh wrote: >> On 06/11/2009 08:41 PM, Mike Christie wrote: >>> It seems like we have a lot of members on the list that are not kernel >>> developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i, >>> iscsi_tcp and ib_iser) with another being written. So it seems like we >>> are going to have lots of patches. I would also like to start sending my >>> kernel patches out in a way that everyone can see them. Previously to >>> avoid noise on this list, I have been pinging you guys privately which >>> just does not work so well now when we have so many people. >>> >>> What do you people think? >>> >>> Do other people on the list prefer to see everything here, so you can >>> see what features are making progress? >> I vote: One list, All patches posted > > I agree that having just one mailing list is the most convenient for > kernel developers. But not everyone who is subscribed to open-iscsi is > a kernel developer. Wouldn't it be more convenient for iSCSI users to > have two lists -- one intended for iSCSI users, and one for iSCSI > developers, such that the users can subscribe to the former only ? > Just my two cents. > > Bart. > >From my experience this makes users loos on the Kernel guys. Kernel guys are busy, and mind their own business, but if a question comes up, which they know the answer they would occasionally participate. Splitting will loos that. I think iscsi mailing-list is not that big and still easy to monitor. Just set your mailer to view by thread, and it's easy to jump over threads that are not interesting. My $0.017 Boaz --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: do we need a new list for kernel patches
On Sun, Jun 14, 2009 at 11:23 AM, Boaz Harrosh wrote: > On 06/11/2009 08:41 PM, Mike Christie wrote: >> It seems like we have a lot of members on the list that are not kernel >> developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i, >> iscsi_tcp and ib_iser) with another being written. So it seems like we >> are going to have lots of patches. I would also like to start sending my >> kernel patches out in a way that everyone can see them. Previously to >> avoid noise on this list, I have been pinging you guys privately which >> just does not work so well now when we have so many people. >> >> What do you people think? >> >> Do other people on the list prefer to see everything here, so you can >> see what features are making progress? > > I vote: One list, All patches posted I agree that having just one mailing list is the most convenient for kernel developers. But not everyone who is subscribed to open-iscsi is a kernel developer. Wouldn't it be more convenient for iSCSI users to have two lists -- one intended for iSCSI users, and one for iSCSI developers, such that the users can subscribe to the former only ? Just my two cents. Bart. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: do we need a new list for kernel patches
On 06/11/2009 08:41 PM, Mike Christie wrote: > Hey, > > It seems like we have a lot of members on the list that are not kernel > developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i, > iscsi_tcp and ib_iser) with another being written. So it seems like we > are going to have lots of patches. I would also like to start sending my > kernel patches out in a way that everyone can see them. Previously to > avoid noise on this list, I have been pinging you guys privately which > just does not work so well now when we have so many people. > > What do you people think? > > Do other people on the list prefer to see everything here, so you can > see what features are making progress? > I vote: One list, All patches posted Boaz --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: [pnfs] build open-iscsi error
On 06/12/2009 06:49 PM, sun_peix...@emc.com wrote: > I have installed the latest linux.2.6.30-pnfs on my client. All modules > and headers have been installed. > > When I was build the open-iscsi, I got the following error. > > My linux-pnfs source and open-iscsi source are all located under > /usr/src directory. > > Before install 2.6.30-pnfs, my client was running RedHat Linux2.6.18. I > am using gcc4.1.1 > > Thanks for help > > Peixing > > > make[1]: Leaving directory `/usr/src/open-iscsi-2.0-870.3/usr' > make -C kernel > make[1]: Entering directory `/usr/src/open-iscsi-2.0-870.3/kernel' > make[1]: *** No rule to make target `linux_2_6_30', needed by > `kernel_check'. Stop. > make[1]: Leaving directory `/usr/src/open-iscsi-2.0-870.3/kernel' > make: *** [all] Error 2 >From 2.6.28 open-iscsi kernel modules should not be built out-of-tree. You should only run with the iscsi modules built with your Kernel. Just go to scsi-lowlevel-drivers in your xconfig or menuconfig and enable the iscsi driver. For the user-mode iscsi utilities you do: [open-iscsi]$ make user and as su [open-iscsi]$ make install_user Cheers Boaz --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: RFC: do we need a new list for kernel patches
Mike Christie wrote: > So it seems like we are going to have lots of patches. I would also like to > start sending my kernel patches out in a way that everyone can see them. > Previously to avoid noise on this list, I have been pinging you guys > privately which just does not work so well now when we have so many people. Yes, lets have all iscsi kernel patches sent over a list and not private threads, so people can review and comment. > What do you people think? Do other people on the list prefer to see > everything here, so you can see what features are making progress? Yes, lets have all iscsi patches sent over one list, e.g as the iproute patches are sent over netdev. Or. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
