My ISCSI disk has been going into a read-only state due to some network flooding issues. While I wait for the network team to fix things on their end (and this may take some time) is it possible to have the disk come back online read/write instead of read-only? More details.. Here is what I'm seeing in the "messages" log... Aug 30 06:49:00 node1 kernel: qla3xxx eth0: Link is down. Aug 30 06:49:08 node1 kernel: connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 5988451077, last ping 5988456077, now 5988461077 Aug 30 06:49:08 node1 kernel: connection1:0: detected conn error (1011) Aug 30 06:49:09 node1 kernel: qla3xxx eth0: Link is down. Aug 30 06:49:09 node1 iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Aug 30 06:49:14 node1 iscsid: connect to 10.1.1.1:3260 failed (No route to host) Aug 30 06:51:08 node1 kernel: session1: session recovery timed out after 120 secs Aug 30 06:51:08 node1 kernel: sd 9:0:0:0: SCSI error: return code = 0x000f0000 Aug 30 06:51:08 node1 kernel: end_request: I/O error, dev sdd, sector 1061945423 Aug 30 06:51:08 node1 kernel: printk: 4 messages suppressed. Aug 30 06:51:08 node1 kernel: Buffer I/O error on device sdd1, logical block 132743170 Aug 30 06:51:08 node1 kernel: lost page write due to I/O error on sdd1 <similar stuff deleted> And here is where the network must have came back online (although I never did see a "Link up", but it's definitely up) and mounted the disk read-only... Aug 30 06:51:08 node1 kernel: ext3_abort called. Aug 30 06:51:08 node1 kernel: EXT3-fs error (device sdd1): ext3_journal_start_sb: Detected aborted journal Aug 30 06:51:08 node1 kernel: Remounting filesystem read-only Aug 30 06:51:08 node1 kernel: __journal_remove_journal_head: freeing b_frozen_data So my question is, to help get us through these trying times, is it possible to make it so that the disk automatically comes back online read-write? And/Or, is there a certain timeout value I can increase? I'm running RHEL 5.5 and iscsi-initiator-utils.x86_64 6.2.0.871-0.16.el5 Thanks, Nic -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
