Cannot do FITRIM
Hello all I am trying to fstrim a filesystem on an iSCSI disk through open-iscsi. The target is on LIO . I am receiving: fstrim: /: FITRIM ioctl failed: Operation not supported At LIO side there is nothing in dmesg, so I am supposing it's a open-iscsi problem (lack of feature?) What can you tell me? Thank you S. -- 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?hl=en.
Re: Cannot do FITRIM
On Aug 30, 2012, at 11:18 AM, Spelic spe...@shiftmail.org wrote: Hello all I am trying to fstrim a filesystem on an iSCSI disk through open-iscsi. The target is on LIO . I am receiving: fstrim: /: FITRIM ioctl failed: Operation not supported At LIO side there is nothing in dmesg, so I am supposing it's a open-iscsi problem (lack of feature?) The iscsi layer does not do anything special to support trim/discard. We just pass whatever info we have to upper layers and passes commands down to the target/disks. Does your disk support trim/discard? Are you doing passthrough to a disk that support trim/discard or is lio emulating it? -- 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?hl=en.
Re: Cannot do FITRIM
On Aug 30, 2012, at 11:49 AM, Michael Christie micha...@cs.wisc.edu wrote: On Aug 30, 2012, at 11:18 AM, Spelic spe...@shiftmail.org wrote: Hello all I am trying to fstrim a filesystem on an iSCSI disk through open-iscsi. The target is on LIO . I am receiving: fstrim: /: FITRIM ioctl failed: Operation not supported At LIO side there is nothing in dmesg, so I am supposing it's a open-iscsi problem (lack of feature?) The iscsi layer does not do anything special to support trim/discard. We just pass whatever info we have to upper layers and passes commands down to the target/disks. Does your disk support trim/discard? Are you doing passthrough to a disk that support trim/discard or is lio emulating it? When you run fstrim what errors do you see in /var/log/messages? Do you see something about a ILLEGAL_REQUEST maybe? -- 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?hl=en.
Re: Correlating TCP connections with iSCSI connections
That is exactly what I am looking for... peresently I can see something like this: # netstat -anpt snip tcp0 48 192.168.0.155:60480 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60452 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 48 192.168.0.155:60448 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60460 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60458 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60466 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60420 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60422 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60434 192.168.0.35:3260 ESTABLISHED 5658/iscsid snip I would want to associate that with a specific connection so I can analyze tcpdump output for just that one connection that is seemingly underperforming. The host has dozens of active connections and only this one is causing a problem. Without being able to identify the source port, it is difficult to determine which stream to follow. Thanks, Jeff On Tuesday, August 28, 2012 5:02:41 PM UTC-7, Mike Christie wrote: On Aug 28, 2012, at 5:39 PM, Jeffrey Caughel jcau...@gmail.comjavascript: wrote: In order to further dig into performance issues we're seeing, I am trying to correlate individual iSCSI connections with specific TCP connections. I don't want to negatively impact performance more than it already is so I was hoping to find a means for this that didn't require increasing the log level. I haven't found this recorded under /sys/class/iscsi_connection/connection[number] or under /var/lib/iscsi/nodes/[IQN]/[target_ip:port]/[interface]. I would expect it to be fairly simple and hopefully it's just eluding me - ultimately I would like to correlate this specific connection with an entry in `netstat -anvpt` that is itself associated with iscsid. I don't think we have anything. If you run iscsiadm -m session -P 2 you will see a Iface IPaddress value. This is the address that the iscsi connection uses on the local side, so it matches the ip address in the Local Address value in netstat. I could also print out the local port the iscsi connection is using so you could use both those values to match the address:port tuple you see in netstat Local Address field. Is that what you need? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/LPI8ioTXA2gJ. 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?hl=en.
Re: Correlating TCP connections with iSCSI connections
Specifically the source port opened by iscsid on the connecting host is what I can't find anywhere in the iscsi information. On Tuesday, August 28, 2012 3:39:16 PM UTC-7, Jeffrey Caughel wrote: In order to further dig into performance issues we're seeing, I am trying to correlate individual iSCSI connections with specific TCP connections. I don't want to negatively impact performance more than it already is so I was hoping to find a means for this that didn't require increasing the log level. I haven't found this recorded under /sys/class/iscsi_connection/connection[number] or under /var/lib/iscsi/nodes/[IQN]/[target_ip:port]/[interface]. I would expect it to be fairly simple and hopefully it's just eluding me - ultimately I would like to correlate this specific connection with an entry in `netstat -anvpt` that is itself associated with iscsid. Thanks in advance for any help you can provide. Regards, Jeff Caughel SUNY ITEC -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/bInby3SVzUgJ. 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?hl=en.
problem in sharing disk through iscsi
I am new to iscsi. I had one problem. I am using a NetbSD target for getting storage through iscsi protocol. I want to access this storage from two remote machines(primary and secondary). From one machine(primary) i have mounted this storage in read right mode and from another remote machine(secondary) i have mounted this storage in read-only mode. The problems i am facing are 1. When i write something from primary side then it is not visible at secondary side until and unless i remount the exported storage. 2. When writing is on from primary side and meanwhile if i try to read the exported disk from secondary side then i get the corruption in the file which i was transferring from primary side. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/e9L6wWZ4lv0J. 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?hl=en.
Re: Correlating TCP connections with iSCSI connections
Ok. Let me try to get to this over the weekend. On 08/28/2012 07:29 PM, Jeffrey Caughel wrote: That is exactly what I am looking for... peresently I can see something like this: # netstat -anpt snip tcp0 48 192.168.0.155:60480 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60452 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 48 192.168.0.155:60448 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60460 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60458 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60466 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60420 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60422 192.168.0.35:3260 ESTABLISHED 5658/iscsid tcp0 0 192.168.0.155:60434 192.168.0.35:3260 ESTABLISHED 5658/iscsid snip I would want to associate that with a specific connection so I can analyze tcpdump output for just that one connection that is seemingly underperforming. The host has dozens of active connections and only this one is causing a problem. Without being able to identify the source port, it is difficult to determine which stream to follow. Thanks, Jeff On Tuesday, August 28, 2012 5:02:41 PM UTC-7, Mike Christie wrote: On Aug 28, 2012, at 5:39 PM, Jeffrey Caughel jcau...@gmail.comjavascript: wrote: In order to further dig into performance issues we're seeing, I am trying to correlate individual iSCSI connections with specific TCP connections. I don't want to negatively impact performance more than it already is so I was hoping to find a means for this that didn't require increasing the log level. I haven't found this recorded under /sys/class/iscsi_connection/connection[number] or under /var/lib/iscsi/nodes/[IQN]/[target_ip:port]/[interface]. I would expect it to be fairly simple and hopefully it's just eluding me - ultimately I would like to correlate this specific connection with an entry in `netstat -anvpt` that is itself associated with iscsid. I don't think we have anything. If you run iscsiadm -m session -P 2 you will see a Iface IPaddress value. This is the address that the iscsi connection uses on the local side, so it matches the ip address in the Local Address value in netstat. I could also print out the local port the iscsi connection is using so you could use both those values to match the address:port tuple you see in netstat Local Address field. Is that what you need? -- 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?hl=en.
Re: problem in sharing disk through iscsi
On 08/29/2012 12:17 AM, shivraj dongawe wrote: I am new to iscsi. I had one problem. I am using a NetbSD target for getting storage through iscsi protocol. I want to access this storage from two remote machines(primary and secondary). From one machine(primary) i have mounted this storage in read right mode and from another remote machine(secondary) i have mounted this storage in read-only mode. The problems i am facing are 1. When i write something from primary side then it is not visible at secondary side until and unless i remount the exported storage. 2. When writing is on from primary side and meanwhile if i try to read the exported disk from secondary side then i get the corruption in the file which i was transferring from primary side. I think you want some sort of clustering software. open-iscsi is just a iscsi initiator. It does not handle any of those types of issues. -- 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?hl=en.
Re: problem in sharing disk through iscsi
Mike is (of course) correct. When just the iSCSI connection is in place, each host believes it owns the volume exclusively. So when you write to a volume like that, you don't first (or periodically) re-read the volume for updates. Why would you? As far as the host is concerned nothing has changed. When you use a file sharing protocol, that issue is well understood and handled by the file server. There are some clustering filesystems out there. Open source GFS is one of them. The commercial solutions are quite expensive. Running thousands of dollars per node. Best/cheap option, is mount the volume to one server and share it via the network to the others. Don On Thu, Aug 30, 2012 at 3:59 PM, Mike Christie micha...@cs.wisc.edu wrote: On 08/29/2012 12:17 AM, shivraj dongawe wrote: I am new to iscsi. I had one problem. I am using a NetbSD target for getting storage through iscsi protocol. I want to access this storage from two remote machines(primary and secondary). From one machine(primary) i have mounted this storage in read right mode and from another remote machine(secondary) i have mounted this storage in read-only mode. The problems i am facing are 1. When i write something from primary side then it is not visible at secondary side until and unless i remount the exported storage. 2. When writing is on from primary side and meanwhile if i try to read the exported disk from secondary side then i get the corruption in the file which i was transferring from primary side. I think you want some sort of clustering software. open-iscsi is just a iscsi initiator. It does not handle any of those types of issues. -- 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?hl=en. -- 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?hl=en.
Re: problem in sharing disk through iscsi
On 08/30/12 22:19, Donald Williams wrote: Mike is (of course) correct. When just the iSCSI connection is in place, each host believes it owns the volume exclusively. So when you write to a volume like that, you don't first (or periodically) re-read the volume for updates. Why would you? As far as the host is concerned nothing has changed. And the OP will soon lose all his data on that filesystem! -- 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?hl=en.
