Konrad Rzeszutek schrieb:
> On Tue, Aug 26, 2008 at 11:37:46PM -0700, An Oneironaut wrote:
>> Hey all,
>>     I was wondering if anyone out there had tested open-iscsi with a
>> variety of Linux filesystems to see what works best.  Currently I am
>> using the ext3 fs and for months now have been suffering problems.
>> Anytime the iSCSI connection is dropped a variety of bad things can
>> happen.  The fs will get corrupted, I/O errors will occur when doing
>> shell operations on the volume, kernel oopses will occur, and so on.
>> Most of this is probably related to the state of the iSCSI device.
>> However tools like e2fsck take forever to fix a volume if it is 500
>> Gigs and up.
>>     Are there any suggestions out there for alternatives?  Or are
> Use multipath and make your iSCSI target use the 'queue_if_no_path' 
> configuration.
> Then you can use any filesystem on top of multipath and it won't matter
> that the underlaying connection is disconnected - the machine will
> just block the I/Os until it the iSCSI target is reconnected.
>> there better ext3 tools that can fix the fs quicker?  How are the rest
>> of you dealing with loss of connection and data corruption?
> multipath.

I think the easiest it to increase the 
node.session.timeo.replacement_timeout in /etc/iscsi/iscsid.conf to 
something more than default 120 seconds (which means that the connection 
is dropped after 2 minutes; if you want to upgrade your target server 
and change the cabling, you may need more time than two minutes).

Tomasz Chmielewski

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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi

Reply via email to