On 06/12/2012 11:22 AM, awiddersh...@hotmail.com wrote:
> I am curious to know if you were able to test this and have any of the same
> issues.
>
I am not able to hit it in upstream or rhel kernels.
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" grou
I am curious to know if you were able to test this and have any of the same
issues.
On Wednesday, March 21, 2012 2:36:36 PM UTC-4, awidde...@hotmail.com wrote:
>
> Here is the output of 'uname -a'
>
> Linux test-server 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40
> EDT 2011 x86_64 x86_6
Here is the output of 'uname -a'
Linux test-server 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT
2011 x86_64 x86_64 x86_64 GNU/Linux
Yes, I have two iSCSI disks on this test machine. When I do ' ls
/sys/block/ | grep sd' I still see all of the disks:
sda
sdb
sdc
--
You received t
On 03/21/2012 07:24 AM, awiddersh...@hotmail.com wrote:
> Mar 20 19:15:38 test-server kernel: session5: iscsi_remove_session:
> Removing session
> Mar 20 19:15:38 test-server kernel: session5: __iscsi_unbind_session:
> Unbinding session
What kernel is this with? It looks like we are getting stuc
If you kill iscsid and you get
- I was able to killall -9 iscsid which then spit this out
Logging out of session [sid: 1, target: iqn.yadayada.example.com,
portal: 192.168.2.32,3260]
iscsiadm: got read error (0/0), daemon died?
iscsiadm: Could not logout of [sid: 1, target:
iq
I am having a similar issue. When our iSCSI disconnects longer than the
node.session.timeo.replacement_timeout it then from what I understand hands
back control to multipath if you are using it or the application/kernel to
handle the case of a disk going completely missing. The typical response
An Oneironaut wrote:
> Hey all,
>
>So here is an update. I tried multi-path and it made no difference
> for my problem. I was able to get umount to work, however the problem
> just propagated over to logout. So for example here is what I would
> do in error recovery.
>
> 1. Disconnect th
Hey all,
So here is an update. I tried multi-path and it made no difference
for my problem. I was able to get umount to work, however the problem
just propagated over to logout. So for example here is what I would
do in error recovery.
1. Disconnect the iSCSI
2. Wait for the timeout.
3.
An Oneironaut wrote:
> I posted a little while back about this, but I still seem to be
> having trouble with this issue. Originally I tried to setup my iSCSI
> connection so that it had a 24 day timeout period and the no-op timers
> would be disabled. However this timeout led to a variety o
> If you guys have any advice or insight I'd appreciate the help. I
Use multipath. Install the package and your iSCSI disk will be
/dev/mapper/http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
I posted a little while back about this, but I still seem to be
having trouble with this issue. Originally I tried to setup my iSCSI
connection so that it had a 24 day timeout period and the no-op timers
would be disabled. However this timeout led to a variety of issues
including causing um
11 matches
Mail list logo
