Re: Error while performing writes using dd or mkfs on iSCSI initiator.
On Wednesday, February 6, 2019 at 10:41:00 PM UTC+5:30, The Lee-Man wrote: > > On Wednesday, January 23, 2019 at 1:48:19 PM UTC-8, iamlin...@gmail.com > wrote: >> >> We have a LIO target on RHEL 7.5 with the lun created using fileio >> through targetcli. We exported it >> to RHEL initiator on the same box (Tried with other box as well). >> On the lun, when we do mkfs for ext3/ext4, it fails with following >> message and can not be mounted. >> >> >> - >> [root@linux_machine /]# mkfs -t ext4 /dev/sdh >> mke2fs 1.42.9 (28-Dec-2013) >> /dev/sdh is entire device, not just one partition! >> Proceed anyway? (y,n) y >> Filesystem label= >> OS type: Linux >> Block size=4096 (log=2) >> Fragment size=4096 (log=2) >> Stride=0 blocks, Stripe width=1024 blocks >> 2621440 inodes, 10485760 blocks >> 524288 blocks (5.00%) reserved for the super user >> First data block=0 >> Maximum filesystem blocks=2157969408 >> 320 block groups >> 32768 blocks per group, 32768 fragments per group >> 8192 inodes per group >> Superblock backups stored on blocks: >> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, >> 2654208, >> 4096000, 7962624 >> >> Allocating group tables: done >> Writing inode tables: done >> Creating journal (32768 blocks): done >> Writing superblocks and filesystem accounting information: >> Warning, had trouble writing out superblocks. >> >> - >> while above task fails, /var/log/messages on initiator has following >> errors. >> >> >> - >> kernel: connection1:0: detected conn error (1020) >> Kernel reported iSCSI connection 1:0 error (1020 - >> ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) >> connection1:0 is operational after recovery (1 attempts) >> connection1:0: detected conn error (1020) >> Kernel reported iSCSI connection 1:0 error (1020 - >> ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) >> connection1:0 is operational after recovery (1 attempts) >> connection1:0: detected conn error (1020) >> kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 54 00 10 00 10 00 00 >> kernel: blk_update_request: I/O error, dev sdf, sector 5505040 >> Kernel: Buffer I/O error on dev sdf, logical block 688130, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688131, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688132, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688133, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688134, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688135, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688136, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688137, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688138, lost async >> page write >> kernel: Buffer I/O error on dev sdf, logical block 688139, lost async >> page write >> kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 50 00 10 00 10 00 00 >> kernel: blk_update_request: I/O error, dev sdf, sector 5242896 >> kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 4c 00 10 00 10 00 00 >> kernel: blk_update_request: I/O error, dev sdf, sector 4980752 >> kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 48 00 10 00 10 00 00 >> blk_update_request: I/O error, dev sdf, sector 4718608 >> sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 44 00 10 00 10 00 00 >> blk_update_request: I/O error, dev sdf, sector 4456464 >> sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 40 00 10 00 10 00 00 >> blk_update_request: I/O error, dev sdf, sector 4194320 >> kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 3c 00 10 00 10 00 00 >> kernel: blk_update_request: I/O error, dev sdf, sector 3932176 >> kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED >> driverbyte=DRIVER_OK >> kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 38 00 10 00 10 00 00 >> kernel:
Re: Error while performing writes using dd or mkfs on iSCSI initiator.
On Wednesday, January 23, 2019 at 1:48:19 PM UTC-8, iamlinonym...@gmail.com wrote: > > We have a LIO target on RHEL 7.5 with the lun created using fileio through > targetcli. We exported it > to RHEL initiator on the same box (Tried with other box as well). > On the lun, when we do mkfs for ext3/ext4, it fails with following message > and can not be mounted. > > > - > [root@linux_machine /]# mkfs -t ext4 /dev/sdh > mke2fs 1.42.9 (28-Dec-2013) > /dev/sdh is entire device, not just one partition! > Proceed anyway? (y,n) y > Filesystem label= > OS type: Linux > Block size=4096 (log=2) > Fragment size=4096 (log=2) > Stride=0 blocks, Stripe width=1024 blocks > 2621440 inodes, 10485760 blocks > 524288 blocks (5.00%) reserved for the super user > First data block=0 > Maximum filesystem blocks=2157969408 > 320 block groups > 32768 blocks per group, 32768 fragments per group > 8192 inodes per group > Superblock backups stored on blocks: > 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, > 2654208, > 4096000, 7962624 > > Allocating group tables: done > Writing inode tables: done > Creating journal (32768 blocks): done > Writing superblocks and filesystem accounting information: > Warning, had trouble writing out superblocks. > > - > while above task fails, /var/log/messages on initiator has following > errors. > > > - > kernel: connection1:0: detected conn error (1020) > Kernel reported iSCSI connection 1:0 error (1020 - > ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) > connection1:0 is operational after recovery (1 attempts) > connection1:0: detected conn error (1020) > Kernel reported iSCSI connection 1:0 error (1020 - > ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) > connection1:0 is operational after recovery (1 attempts) > connection1:0: detected conn error (1020) > kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 54 00 10 00 10 00 00 > kernel: blk_update_request: I/O error, dev sdf, sector 5505040 > Kernel: Buffer I/O error on dev sdf, logical block 688130, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688131, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688132, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688133, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688134, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688135, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688136, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688137, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688138, lost async page > write > kernel: Buffer I/O error on dev sdf, logical block 688139, lost async page > write > kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 50 00 10 00 10 00 00 > kernel: blk_update_request: I/O error, dev sdf, sector 5242896 > kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 4c 00 10 00 10 00 00 > kernel: blk_update_request: I/O error, dev sdf, sector 4980752 > kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 48 00 10 00 10 00 00 > blk_update_request: I/O error, dev sdf, sector 4718608 > sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 44 00 10 00 10 00 00 > blk_update_request: I/O error, dev sdf, sector 4456464 > sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 40 00 10 00 10 00 00 > blk_update_request: I/O error, dev sdf, sector 4194320 > kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 3c 00 10 00 10 00 00 > kernel: blk_update_request: I/O error, dev sdf, sector 3932176 > kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > kernel: sd 7:0:0:1: [sdf] CDB: Write(10) 2a 00 00 38 00 10 00 10 00 00 > kernel: blk_update_request: I/O error, dev sdf, sector 3670032 > kernel: sd 7:0:0:1: [sdf] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED > driverbyte=DRIVER_OK > kernel: sd 7:0:0:1: [sdf] CDB:
