Re: help: Read-only file system
> Sean, hello. > > I tried to reproduce what you described. This what I installed: > > Initiator: (Redhat 5) OFED 2.1.5.1 with iscsi-initiator-utils-2.0-865 > You meant to say 1.2.5.1. Mention that this is the open-iscsi version that is shipped with 1.2.5.1. I suggest that you fix this error. Erez --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: help: Read-only file system
Erez Zilber wrote: > 노성후 wrote: > > >> I am trying to use iscsi target with iser(Infiniband), but when I >> mount it became unstable. >> >> I use OFED-1.2.5.1 , scsi-target-utils-0.2-20071227_1 and >> iscsi-initiator-utils-2.0-865. >> >> I got logs from iscsi-initiator server like below when it turn into >> Read-only file system. >> >> > > Amir from our team in Voltaire will try to help you with that. > > > Erez > > > >> [EMAIL PROTECTED] ~]# mount >> >> /dev/sda1 on / type ext3 (rw) >> >> proc on /proc type proc (rw) >> >> sysfs on /sys type sysfs (rw) >> >> devpts on /dev/pts type devpts (rw,gid=5,mode=620) >> >> tmpfs on /dev/shm type tmpfs (rw) >> >> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) >> >> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) >> >> /dev/sdd1 on /mnt/sdd1 type ext3 (rw) >> >> [EMAIL PROTECTED] ~]# time dd if=/dev/zero of=/mnt/sdd1/1G bs=1024K >> count=1000 >> >> dd: writing `/mnt/sdd1/1G': Read-only file system >> >> 126+0 records in >> >> 125+0 records out >> >> 132059136 bytes (132 MB) copied, 0.472386 seconds, 280 MB/s >> >> real 0m0.519s >> >> user 0m0.000s >> >> sys 0m0.335s >> >> [EMAIL PROTECTED] ~]# >> >> [EMAIL PROTECTED] ~]#dmesg >> >> SCSI device sdd: drive cache: write back >> >> sdd: sdd1 >> >> sd 3:0:0:2: Attached scsi disk sdd >> >> sd 3:0:0:2: Attached scsi generic sg5 type 0 >> >> kjournald starting. Commit interval 5 seconds >> >> EXT3-fs warning (device sdd1): ext3_clear_journal_err: Filesystem >> error recorded from previous mount: IO failure >> >> EXT3-fs warning (device sdd1): ext3_clear_journal_err: Marking fs in >> need of filesystem check. >> >> EXT3-fs warning: mounting fs with errors, running e2fsck is recommended >> >> EXT3 FS on sdd1, internal journal >> >> EXT3-fs: recovery complete. >> >> EXT3-fs: mounted filesystem with ordered data mode. >> >> EXT3-fs error (device sdd1): ext3_new_block: Allocating block in >> system zone - blocks from 1212424, length 1 >> >> Aborting journal on device sdd1. >> >> ext3_abort called. >> >> EXT3-fs error (device sdd1): ext3_journal_start_sb: Detected aborted >> journal >> >> Remounting filesystem read-only >> >> EXT3-fs error (device sdd1): ext3_free_blocks: Freeing blocks in >> system zones - Block = 1212424, count = 1 >> >> EXT3-fs error (device sdd1) in ext3_free_blocks_sb: Journal has aborted >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> __journal_remove_journal_head: freeing b_committed_data >> >> [EMAIL PROTECTED] ~]# >> >> [EMAIL PROTECTED] ~]#tailf /var/log/messages >> >> Apr 16 20:45:42 OSS1 kernel: EXT3-fs: mounted filesystem with ordered >> data mode. >> >> Apr 16 20:49:43 OSS1 kernel: connection2:0: iscsi: detected conn error >> (1011) >> >> Apr 16 20:49:43 OSS1 kernel: iser: iscsi_iser_ep_disconnect:ib conn >> 8101be1323c0 state 2 >> >> Apr 16 20:49:43 OSS1 kernel: iser: iser_cq_tasklet_fn:comp w. error op >> 0 status 5 >> >> Apr 16 20:49:43 OSS1 last message repeated 4 times >> >> Apr 16 20:49:43 OSS1 kernel: iser: iser_cma_handler:event 10 conn >> 8101be1323c0 id 81019ea9d800 >> >> Apr 16 20:49:43 OSS1 kernel: iser: iser_free_ib_conn_res:freeing conn >> 8101be1323c0 cma_id 81019ea9d800 fmr pool 81019f09f9c0 qp >> 81019ea9d200 >> >> Apr 16 20:49:43 OSS1 kernel: iser: iser_device_try_release:device >> 8101afa84840 refcount 1 >> >> Apr 16 20:49:44 OSS1 iscsid: Kernel reported iSCSI connection 2:0 >> error (1011) state (3) >> >> Apr 16 20:49:47 OSS1 kernel: iser: iscsi_iser_ib_conn_lookup:no conn >> exists for eph fff
Re: help: Read-only file system
노성후 wrote: > I am trying to use iscsi target with iser(Infiniband), but when I > mount it became unstable. > > I use OFED-1.2.5.1 , scsi-target-utils-0.2-20071227_1 and > iscsi-initiator-utils-2.0-865. > > I got logs from iscsi-initiator server like below when it turn into > Read-only file system. > Amir from our team in Voltaire will try to help you with that. Erez > [EMAIL PROTECTED] ~]# mount > > /dev/sda1 on / type ext3 (rw) > > proc on /proc type proc (rw) > > sysfs on /sys type sysfs (rw) > > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > > tmpfs on /dev/shm type tmpfs (rw) > > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > > sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) > > /dev/sdd1 on /mnt/sdd1 type ext3 (rw) > > [EMAIL PROTECTED] ~]# time dd if=/dev/zero of=/mnt/sdd1/1G bs=1024K count=1000 > > dd: writing `/mnt/sdd1/1G': Read-only file system > > 126+0 records in > > 125+0 records out > > 132059136 bytes (132 MB) copied, 0.472386 seconds, 280 MB/s > > real 0m0.519s > > user 0m0.000s > > sys 0m0.335s > > [EMAIL PROTECTED] ~]# > > [EMAIL PROTECTED] ~]#dmesg > > SCSI device sdd: drive cache: write back > > sdd: sdd1 > > sd 3:0:0:2: Attached scsi disk sdd > > sd 3:0:0:2: Attached scsi generic sg5 type 0 > > kjournald starting. Commit interval 5 seconds > > EXT3-fs warning (device sdd1): ext3_clear_journal_err: Filesystem > error recorded from previous mount: IO failure > > EXT3-fs warning (device sdd1): ext3_clear_journal_err: Marking fs in > need of filesystem check. > > EXT3-fs warning: mounting fs with errors, running e2fsck is recommended > > EXT3 FS on sdd1, internal journal > > EXT3-fs: recovery complete. > > EXT3-fs: mounted filesystem with ordered data mode. > > EXT3-fs error (device sdd1): ext3_new_block: Allocating block in > system zone - blocks from 1212424, length 1 > > Aborting journal on device sdd1. > > ext3_abort called. > > EXT3-fs error (device sdd1): ext3_journal_start_sb: Detected aborted > journal > > Remounting filesystem read-only > > EXT3-fs error (device sdd1): ext3_free_blocks: Freeing blocks in > system zones - Block = 1212424, count = 1 > > EXT3-fs error (device sdd1) in ext3_free_blocks_sb: Journal has aborted > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > __journal_remove_journal_head: freeing b_committed_data > > [EMAIL PROTECTED] ~]# > > [EMAIL PROTECTED] ~]#tailf /var/log/messages > > Apr 16 20:45:42 OSS1 kernel: EXT3-fs: mounted filesystem with ordered > data mode. > > Apr 16 20:49:43 OSS1 kernel: connection2:0: iscsi: detected conn error > (1011) > > Apr 16 20:49:43 OSS1 kernel: iser: iscsi_iser_ep_disconnect:ib conn > 8101be1323c0 state 2 > > Apr 16 20:49:43 OSS1 kernel: iser: iser_cq_tasklet_fn:comp w. error op > 0 status 5 > > Apr 16 20:49:43 OSS1 last message repeated 4 times > > Apr 16 20:49:43 OSS1 kernel: iser: iser_cma_handler:event 10 conn > 8101be1323c0 id 81019ea9d800 > > Apr 16 20:49:43 OSS1 kernel: iser: iser_free_ib_conn_res:freeing conn > 8101be1323c0 cma_id 81019ea9d800 fmr pool 81019f09f9c0 qp > 81019ea9d200 > > Apr 16 20:49:43 OSS1 kernel: iser: iser_device_try_release:device > 8101afa84840 refcount 1 > > Apr 16 20:49:44 OSS1 iscsid: Kernel reported iSCSI connection 2:0 > error (1011) state (3) > > Apr 16 20:49:47 OSS1 kernel: iser: iscsi_iser_ib_conn_lookup:no conn > exists for eph > > Apr 16 20:49:47 OSS1 kernel: iser: iser_connect:connecting to: > 10.1.1.146, port 0xbc0c > > Apr 16 20:49:47 OSS1 kernel: iser: iser_cma_handler:event 0 conn > 8101be1323c0 id 81019ea9d800 > > Apr 16 20:49:4
Re: help: Read-only file system [on iser]
Mike Christie wrote: > 노성후 wrote: > >> Apr 16 20:49:47 OSS1 kernel: iser: iscsi_iser_ib_conn_lookup:no conn exists >> for eph >> >> > > > This eph looks weird. Erez, have you seen this before? > I'll try to take a look at it, but it may take me some time (currently busy with other stuff). Erez --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: help: Read-only file system [on iser]
노성후 wrote: > > Apr 16 20:49:47 OSS1 kernel: iser: iscsi_iser_ib_conn_lookup:no conn exists > for eph > This eph looks weird. Erez, have you seen this before? > > Apr 16 20:49:49 OSS1 iscsid: connection2:0 is operational after recovery (2 > attempts) > > Apr 16 20:49:53 OSS1 kernel: iscsi: host reset succeeded > Erez can better tell you about the iser messages. It looks like from this message that a scsi command timed out, we could not abort it, and could not reset the lun, so we dropped the session. I am not sure if that is the cause of the iscsi connection error or if the connection error caused the command to timeout. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
help: Read-only file system
I am trying to use iscsi target with iser(Infiniband), but when I mount it became unstable. I use OFED-1.2.5.1 , scsi-target-utils-0.2-20071227_1 and iscsi-initiator- utils-2.0-865. I got logs from iscsi-initiator server like below when it turn into Read- only file system. [EMAIL PROTECTED] ~]# mount /dev/sda1 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) /dev/sdd1 on /mnt/sdd1 type ext3 (rw) [EMAIL PROTECTED] ~]# time dd if=/dev/zero of=/mnt/sdd1/1G bs=1024K count=1000 dd: writing `/mnt/sdd1/1G': Read-only file system 126+0 records in 125+0 records out 132059136 bytes (132 MB) copied, 0.472386 seconds, 280 MB/s real0m0.519s user0m0.000s sys 0m0.335s [EMAIL PROTECTED] ~]# [EMAIL PROTECTED] ~]#dmesg SCSI device sdd: drive cache: write back sdd: sdd1 sd 3:0:0:2: Attached scsi disk sdd sd 3:0:0:2: Attached scsi generic sg5 type 0 kjournald starting. Commit interval 5 seconds EXT3-fs warning (device sdd1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure EXT3-fs warning (device sdd1): ext3_clear_journal_err: Marking fs in need of filesystem check. EXT3-fs warning: mounting fs with errors, running e2fsck is recommended EXT3 FS on sdd1, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs error (device sdd1): ext3_new_block: Allocating block in system zone - blocks from 1212424, length 1 Aborting journal on device sdd1. ext3_abort called. EXT3-fs error (device sdd1): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device sdd1): ext3_free_blocks: Freeing blocks in system zones - Block = 1212424, count = 1 EXT3-fs error (device sdd1) in ext3_free_blocks_sb: Journal has aborted __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data [EMAIL PROTECTED] ~]# [EMAIL PROTECTED] ~]#tailf /var/log/messages Apr 16 20:45:42 OSS1 kernel: EXT3-fs: mounted filesystem with ordered data mode. Apr 16 20:49:43 OSS1 kernel: connection2:0: iscsi: detected conn error (1011) Apr 16 20:49:43 OSS1 kernel: iser: iscsi_iser_ep_disconnect:ib conn 8101be1323c0 state 2 Apr 16 20:49:43 OSS1 kernel: iser: iser_cq_tasklet_fn:comp w. error op 0 status 5 Apr 16 20:49:43 OSS1 last message repeated 4 times Apr 16 20:49:43 OSS1 kernel: iser: iser_cma_handler:event 10 conn 8101be1323c0 id 81019ea9d800 Apr 16 20:49:43 OSS1 kernel: iser: iser_free_ib_conn_res:freeing conn 8101be1323c0 cma_id 81019ea9d800 fmr pool 81019f09f9c0 qp 81019ea9d200 Apr 16 20:49:43 OSS1 kernel: iser: iser_device_try_release:device 8101afa84840 refcount 1 Apr 16 20:49:44 OSS1 iscsid: Kernel reported iSCSI connection 2:0 error (1011) state (3) Apr 16 20:49:47 OSS1 kernel: iser: iscsi_iser_ib_conn_lookup:no conn exists for eph Apr 16 20:49:47 OSS1 kernel: iser: iser_connect:connecting to: 10.1.1.146, port 0xbc0c Apr 16 20:49:47 OSS1 kernel: iser: iser_cma_handler:event 0 conn 8101be1323c0 id 81019ea9d800 Apr 16 20:49:47 OSS1 kernel: iser: iser_cma_handler:event 2 conn 8101be1323c0 id 81019ea9d800 Apr 16 20:49:47 OSS1 kernel: iser: iser_create_ib_conn_res:setting conn 8101be1323c0 cma_id 81019ea9d800: fmr_pool 81019eb5ecc0 qp 81019e266600 Apr 16 20:49:47 OSS1 kernel: iser: iser_cma_handler:event 9 conn 8101be1323
