From: Atsawin C. <jo...@na...> - 2012-04-22 12:15:36
Attachments:
ietd.error
|
Hello, I recently upgrade iet from r.467 to r.480. I found that when image file is unavailable, ietd error. Setup: Ietd share Windows' image file base on disk mapper (use Copy-on-Write) --- Excerpt from /etc/iet/ietd.conf --- Target iqn.1999-06.net.nakhon.disksrv2:spice01 Lun 0 Path=/dev/mapper/spice01,Type=fileio Lun 1 Path=/space/diskless/image/spice01e1.img,Type=fileio --- Here's relevant config: --- root@disksrv2:/# dmsetup table spice01 0 390621184 snapshot 7:0 7:1 P 64 root@disksrv2:/# losetup -a /dev/loop0: [097f]:32 (/image/disk1.img) /dev/loop1: [0801]:12 (/cow/spice01.cow) --- /dev/mapper/spice01 is a snapshot mapper. When the snapshot file is full, disk mapper error and subsequently iet error as in attached file. In r.467, the target simply unusable. After clear snapshot and remap, I can recreate LUN without interrupt other target. Thanks, Joke. -- Atsawin Chaowanakritsanakul System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ Email: jo...@na... -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Arne R. <arn...@go...> - 2012-04-22 18:13:14
|
2012/4/22 Atsawin Chaowanakritsanakul <jo...@na...>: > Hello, > > I recently upgrade iet from r.467 to r.480. I found that when image file is > unavailable, ietd error. > > Setup: Ietd share Windows' image file base on disk mapper (use Copy-on-Write) > > --- Excerpt from /etc/iet/ietd.conf --- > Target iqn.1999-06.net.nakhon.disksrv2:spice01 > Lun 0 Path=/dev/mapper/spice01,Type=fileio > Lun 1 Path=/space/diskless/image/spice01e1.img,Type=fileio > --- > > Here's relevant config: > --- > root@disksrv2:/# dmsetup table spice01 > 0 390621184 snapshot 7:0 7:1 P 64 > root@disksrv2:/# losetup -a > /dev/loop0: [097f]:32 (/image/disk1.img) > /dev/loop1: [0801]:12 (/cow/spice01.cow) > --- > > /dev/mapper/spice01 is a snapshot mapper. When the snapshot file is full, disk > mapper error and subsequently iet error as in attached file. > > In r.467, the target simply unusable. After clear snapshot and remap, I can > recreate LUN without interrupt other target. Thanks for reporting this bug. It might be related to r479 "refactor tio.c" - CC'ing Yucong. Just to verify: Apr 22 12:10:28 disksrv2 kernel: [16142.245110] device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception. Apr 22 12:10:28 disksrv2 kernel: [16142.245141] quiet_error: 136 callbacks suppressed Apr 22 12:10:28 disksrv2 kernel: [16142.245143] Buffer I/O error on device dm-8, logical block 26190728 Apr 22 12:10:28 disksrv2 kernel: [16142.245144] lost page write due to I/O error on dm-8 [....] Apr 22 12:10:28 disksrv2 kernel: [16142.245188] iscsi_trgt: fileio_sync(84) I/O error: syncing pages failed: -5 Apr 22 12:10:28 disksrv2 kernel: [16142.245548] iscsi_trgt: fileio_sync(84) I/O error: syncing pages failed: -5 Apr 22 12:10:28 disksrv2 kernel: [16142.245735] iscsi_trgt: fileio_sync(84) I/O error: syncing pages failed: -5 Apr 22 12:10:28 disksrv2 kernel: [16142.246457] iscsi_trgt: fileio_sync(84) I/O error: syncing pages failed: -5 I assume you saw the above error messages with r467 as well, only the oops below is new, right? Apr 22 12:10:28 disksrv2 kernel: [16142.255768] iscsi_trgt: BUG at /space/src/iscsitarget-480/kernel/file-io.c:61 assert(!size) Apr 22 12:10:28 disksrv2 kernel: [16142.255940] Pid: 9826, comm: istiod10 Tainted: G O 3.2.13 #1 Apr 22 12:10:28 disksrv2 kernel: [16142.255941] Call Trace: Apr 22 12:10:28 disksrv2 kernel: [16142.255947] [<ffffffffa021d1b4>] fileio_make_request+0x1e4/0x1f0 [iscsi_trgt] Apr 22 12:10:28 disksrv2 kernel: [16142.255950] [<ffffffffa02133e0>] tio_write+0x30/0x60 [iscsi_trgt] Apr 22 12:10:28 disksrv2 kernel: [16142.255954] [<ffffffffa021df37>] build_write_response+0x47/0xe0 [iscsi_trgt] Apr 22 12:10:28 disksrv2 kernel: [16142.255958] [<ffffffffa021491b>] send_scsi_rsp+0x1b/0x70 [iscsi_trgt] Apr 22 12:10:28 disksrv2 kernel: [16142.255962] [<ffffffffa021dacf>] disk_execute_cmnd+0x27f/0x2d0 [iscsi_trgt] Apr 22 12:10:28 disksrv2 kernel: [16142.255966] [<ffffffffa021902e>] worker_thread+0x14e/0x2b0 [iscsi_trgt] Apr 22 12:10:28 disksrv2 kernel: [16142.255970] [<ffffffff81048a00>] ? try_to_wake_up+0x280/0x280 Apr 22 12:10:28 disksrv2 kernel: [16142.255975] [<ffffffffa0218ee0>] ? stop_one_worker_thread+0xc0/0xc0 [iscsi_trgt] Apr 22 12:10:28 disksrv2 kernel: [16142.255979] [<ffffffff81073096>] kthread+0x96/0xa0 Apr 22 12:10:28 disksrv2 kernel: [16142.255982] [<ffffffff8168f8f4>] kernel_thread_helper+0x4/0x10 Apr 22 12:10:28 disksrv2 kernel: [16142.255984] [<ffffffff81073000>] ? kthread_worker_fn+0x1a0/0x1a0 Apr 22 12:10:28 disksrv2 kernel: [16142.255987] [<ffffffff8168f8f0>] ? gs_change+0xb/0xb Apr 22 12:10:28 disksrv2 kernel: [16142.256001] ------------[ cut here ]------------ Apr 22 12:10:28 disksrv2 kernel: [16142.256161] kernel BUG at /space/src/iscsitarget-480/kernel/file-io.c:61! Thanks, Arne |
From: Atsawin C. <jo...@na...> - 2012-04-23 02:23:45
|
Arne, Here's error from r.467. ----- Mar 31 15:56:01 disksrv2 kernel: [366060.398092] device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception. Mar 31 15:56:01 disksrv2 kernel: [366060.398160] Buffer I/O error on device dm-3, logical block 27954056 Mar 31 15:56:01 disksrv2 kernel: [366060.398162] lost page write due to I/O error on dm-3 [...] Mar 31 15:56:01 disksrv2 kernel: [366060.398193] Buffer I/O error on device dm-3, logical block 27954065 Mar 31 15:56:01 disksrv2 kernel: [366060.398194] lost page write due to I/O error on dm-3 Mar 31 15:56:01 disksrv2 kernel: [366060.398199] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.398876] iscsi_trgt: fileio_make_request(63) I/O error 512, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.399267] iscsi_trgt: fileio_make_request(63) I/O error 512, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.400530] iscsi_trgt: fileio_make_request(63) I/O error 512, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.400555] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.400913] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.401290] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.401696] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.402105] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.402375] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.402920] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.403331] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.403741] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.404149] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.404405] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.404974] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.405415] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.405794] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.406201] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.406452] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.407017] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.407429] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.407838] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.408247] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.408499] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.409064] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.409476] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.409885] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.410295] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.410546] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.411110] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.411523] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.411932] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.412358] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.412589] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.413152] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.413562] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.413970] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.414386] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.414649] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.416683] iscsi_trgt: fileio_make_request(63) I/O error 512, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.416686] iscsi_trgt: fileio_make_request(63) I/O error 4096, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.416689] iscsi_trgt: fileio_make_request(63) I/O error 4096, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.416701] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.417227] iscsi_trgt: fileio_make_request(63) I/O error 512, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.417231] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.417638] iscsi_trgt: fileio_make_request(63) I/O error 512, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.417641] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.418048] iscsi_trgt: fileio_make_request(63) I/O error 3584, -5 Mar 31 15:56:01 disksrv2 kernel: [366060.474216] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.474219] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.474242] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.474596] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.475048] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 Mar 31 15:56:01 disksrv2 kernel: [366060.475455] iscsi_trgt: fileio_sync(94) I/O error: syncing pages failed: -5 [...] ----- Those two errors kept go on for another second (maybe to the point when client hang.) And there is no OOPs. More information for r.480. After ietd error: - I can't cat /proc/net/iet/volume and /proc/net/iet/session. Cat simply stall. - I can't remove iscsi_trgt. (Something like module is in used.) In mean time, I revert to r.478. Tomorrow, I'll test its behavior again with r.478. Regards, Atsawin. -- Atsawin Chaowanakritsanakul System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ Email: jo...@na... ---------- Original Message ----------- From:Arne Redlich <arn...@go...> To:Atsawin Chaowanakritsanakul <jo...@na...> Cc:isc...@li..., sun...@gm... Sent:Sun, 22 Apr 2012 20:13:05 +0200 Subject:Re: [Iscsitarget-devel] Ietd error when file is unavailable > I assume you saw the above error messages with r467 as well, only the > oops below is new, right? > > Thanks, > Arne > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. ------- End of Original Message ------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Yucong S. (叶. <sun...@gm...> - 2012-04-24 05:18:56
|
Thanks for the report, I will try to look at it tomorrow, it's normal that it become unresponsive after the kernel oops, you will have to reboot to make it work again. On Sun, Apr 22, 2012 at 7:23 PM, Atsawin Chaowanakritsanakul <jo...@na...> wrote: > Arne, > > Here's error from r.467. > ----- > Mar 31 15:56:01 disksrv2 kernel: [366060.398092] device-mapper: snapshots: > Invalidating snapshot: Unable to allocate exception. > Mar 31 15:56:01 disksrv2 kernel: [366060.398160] Buffer I/O error on device > dm-3, logical block 27954056 > Mar 31 15:56:01 disksrv2 kernel: [366060.398162] lost page write due to I/O > error on dm-3 > [...] > Mar 31 15:56:01 disksrv2 kernel: [366060.398193] Buffer I/O error on device > dm-3, logical block 27954065 > Mar 31 15:56:01 disksrv2 kernel: [366060.398194] lost page write due to I/O > error on dm-3 > Mar 31 15:56:01 disksrv2 kernel: [366060.398199] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.398876] iscsi_trgt: > fileio_make_request(63) I/O error 512, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.399267] iscsi_trgt: > fileio_make_request(63) I/O error 512, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.400530] iscsi_trgt: > fileio_make_request(63) I/O error 512, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.400555] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.400913] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.401290] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.401696] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.402105] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.402375] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.402920] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.403331] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.403741] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.404149] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.404405] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.404974] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.405415] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.405794] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.406201] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.406452] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.407017] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.407429] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.407838] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.408247] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.408499] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.409064] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.409476] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.409885] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.410295] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.410546] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.411110] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.411523] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.411932] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.412358] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.412589] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.413152] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.413562] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.413970] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.414386] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.414649] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.416683] iscsi_trgt: > fileio_make_request(63) I/O error 512, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.416686] iscsi_trgt: > fileio_make_request(63) I/O error 4096, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.416689] iscsi_trgt: > fileio_make_request(63) I/O error 4096, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.416701] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.417227] iscsi_trgt: > fileio_make_request(63) I/O error 512, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.417231] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.417638] iscsi_trgt: > fileio_make_request(63) I/O error 512, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.417641] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.418048] iscsi_trgt: > fileio_make_request(63) I/O error 3584, -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.474216] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.474219] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.474242] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.474596] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.475048] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > Mar 31 15:56:01 disksrv2 kernel: [366060.475455] iscsi_trgt: fileio_sync(94) > I/O error: syncing pages failed: -5 > [...] > ----- > Those two errors kept go on for another second (maybe to the point when client > hang.) And there is no OOPs. > > More information for r.480. After ietd error: > - I can't cat /proc/net/iet/volume and /proc/net/iet/session. Cat simply stall. > - I can't remove iscsi_trgt. (Something like module is in used.) > > In mean time, I revert to r.478. Tomorrow, I'll test its behavior again with > r.478. > > Regards, > Atsawin. > -- > Atsawin Chaowanakritsanakul > System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ > Email: jo...@na... > > ---------- Original Message ----------- > From:Arne Redlich <arn...@go...> > To:Atsawin Chaowanakritsanakul <jo...@na...> > Cc:isc...@li..., sun...@gm... > Sent:Sun, 22 Apr 2012 20:13:05 +0200 > Subject:Re: [Iscsitarget-devel] Ietd error when file is unavailable > >> I assume you saw the above error messages with r467 as well, only the >> oops below is new, right? >> >> Thanks, >> Arne >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. > ------- End of Original Message ------- > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > |
From: Yucong S. (叶. <sun...@gm...> - 2012-04-24 05:23:57
|
it's actually a easy one.. and it's not affecting any normal condition, only I/O error would crash, I will send a patch tomorrow. On Mon, Apr 23, 2012 at 10:18 PM, Yucong Sun (叶雨飞) <sun...@gm...> wrote: > Thanks for the report, I will try to look at it tomorrow, it's normal > that it become unresponsive after the kernel oops, you will have to > reboot to make it work again. > > On Sun, Apr 22, 2012 at 7:23 PM, Atsawin Chaowanakritsanakul > <jo...@na...> wrote: >> Arne, >> >> Here's error from r.467. >> ----- >> Mar 31 15:56:01 disksrv2 kernel: [366060.398092] device-mapper: snapshots: >> Invalidating snapshot: Unable to allocate exception. >> Mar 31 15:56:01 disksrv2 kernel: [366060.398160] Buffer I/O error on device >> dm-3, logical block 27954056 >> Mar 31 15:56:01 disksrv2 kernel: [366060.398162] lost page write due to I/O >> error on dm-3 >> [...] >> Mar 31 15:56:01 disksrv2 kernel: [366060.398193] Buffer I/O error on device >> dm-3, logical block 27954065 >> Mar 31 15:56:01 disksrv2 kernel: [366060.398194] lost page write due to I/O >> error on dm-3 >> Mar 31 15:56:01 disksrv2 kernel: [366060.398199] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.398876] iscsi_trgt: >> fileio_make_request(63) I/O error 512, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.399267] iscsi_trgt: >> fileio_make_request(63) I/O error 512, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.400530] iscsi_trgt: >> fileio_make_request(63) I/O error 512, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.400555] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.400913] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.401290] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.401696] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.402105] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.402375] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.402920] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.403331] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.403741] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.404149] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.404405] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.404974] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.405415] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.405794] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.406201] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.406452] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.407017] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.407429] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.407838] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.408247] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.408499] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.409064] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.409476] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.409885] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.410295] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.410546] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.411110] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.411523] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.411932] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.412358] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.412589] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.413152] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.413562] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.413970] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.414386] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.414649] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.416683] iscsi_trgt: >> fileio_make_request(63) I/O error 512, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.416686] iscsi_trgt: >> fileio_make_request(63) I/O error 4096, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.416689] iscsi_trgt: >> fileio_make_request(63) I/O error 4096, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.416701] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.417227] iscsi_trgt: >> fileio_make_request(63) I/O error 512, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.417231] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.417638] iscsi_trgt: >> fileio_make_request(63) I/O error 512, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.417641] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.418048] iscsi_trgt: >> fileio_make_request(63) I/O error 3584, -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.474216] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.474219] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.474242] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.474596] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.475048] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> Mar 31 15:56:01 disksrv2 kernel: [366060.475455] iscsi_trgt: fileio_sync(94) >> I/O error: syncing pages failed: -5 >> [...] >> ----- >> Those two errors kept go on for another second (maybe to the point when client >> hang.) And there is no OOPs. >> >> More information for r.480. After ietd error: >> - I can't cat /proc/net/iet/volume and /proc/net/iet/session. Cat simply stall. >> - I can't remove iscsi_trgt. (Something like module is in used.) >> >> In mean time, I revert to r.478. Tomorrow, I'll test its behavior again with >> r.478. >> >> Regards, >> Atsawin. >> -- >> Atsawin Chaowanakritsanakul >> System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ >> Email: jo...@na... >> >> ---------- Original Message ----------- >> From:Arne Redlich <arn...@go...> >> To:Atsawin Chaowanakritsanakul <jo...@na...> >> Cc:isc...@li..., sun...@gm... >> Sent:Sun, 22 Apr 2012 20:13:05 +0200 >> Subject:Re: [Iscsitarget-devel] Ietd error when file is unavailable >> >>> I assume you saw the above error messages with r467 as well, only the >>> oops below is new, right? >>> >>> Thanks, >>> Arne >>> >>> -- >>> This message has been scanned for viruses and >>> dangerous content by MailScanner, and is >>> believed to be clean. >> ------- End of Original Message ------- >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> |
From: Yucong S. (叶. <sun...@gm...> - 2012-04-24 20:35:57
|
let me know if the new patch didn't work for you. On Mon, Apr 23, 2012 at 10:23 PM, Yucong Sun (叶雨飞) <sun...@gm...> wrote: > it's actually a easy one.. and it's not affecting any normal > condition, only I/O error would crash, I will send a patch tomorrow. > > On Mon, Apr 23, 2012 at 10:18 PM, Yucong Sun (叶雨飞) <sun...@gm...> wrote: >> Thanks for the report, I will try to look at it tomorrow, it's normal >> that it become unresponsive after the kernel oops, you will have to >> reboot to make it work again. >> >> On Sun, Apr 22, 2012 at 7:23 PM, Atsawin Chaowanakritsanakul >> <jo...@na...> wrote: >>> Arne, >>> >>> Here's error from r.467. >>> ----- >>> Mar 31 15:56:01 disksrv2 kernel: [366060.398092] device-mapper: snapshots: >>> Invalidating snapshot: Unable to allocate exception. >>> Mar 31 15:56:01 disksrv2 kernel: [366060.398160] Buffer I/O error on device >>> dm-3, logical block 27954056 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.398162] lost page write due to I/O >>> error on dm-3 >>> [...] >>> Mar 31 15:56:01 disksrv2 kernel: [366060.398193] Buffer I/O error on device >>> dm-3, logical block 27954065 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.398194] lost page write due to I/O >>> error on dm-3 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.398199] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.398876] iscsi_trgt: >>> fileio_make_request(63) I/O error 512, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.399267] iscsi_trgt: >>> fileio_make_request(63) I/O error 512, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.400530] iscsi_trgt: >>> fileio_make_request(63) I/O error 512, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.400555] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.400913] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.401290] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.401696] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.402105] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.402375] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.402920] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.403331] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.403741] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.404149] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.404405] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.404974] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.405415] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.405794] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.406201] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.406452] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.407017] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.407429] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.407838] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.408247] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.408499] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.409064] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.409476] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.409885] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.410295] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.410546] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.411110] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.411523] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.411932] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.412358] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.412589] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.413152] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.413562] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.413970] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.414386] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.414649] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.416683] iscsi_trgt: >>> fileio_make_request(63) I/O error 512, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.416686] iscsi_trgt: >>> fileio_make_request(63) I/O error 4096, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.416689] iscsi_trgt: >>> fileio_make_request(63) I/O error 4096, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.416701] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.417227] iscsi_trgt: >>> fileio_make_request(63) I/O error 512, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.417231] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.417638] iscsi_trgt: >>> fileio_make_request(63) I/O error 512, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.417641] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.418048] iscsi_trgt: >>> fileio_make_request(63) I/O error 3584, -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.474216] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.474219] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.474242] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.474596] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.475048] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> Mar 31 15:56:01 disksrv2 kernel: [366060.475455] iscsi_trgt: fileio_sync(94) >>> I/O error: syncing pages failed: -5 >>> [...] >>> ----- >>> Those two errors kept go on for another second (maybe to the point when client >>> hang.) And there is no OOPs. >>> >>> More information for r.480. After ietd error: >>> - I can't cat /proc/net/iet/volume and /proc/net/iet/session. Cat simply stall. >>> - I can't remove iscsi_trgt. (Something like module is in used.) >>> >>> In mean time, I revert to r.478. Tomorrow, I'll test its behavior again with >>> r.478. >>> >>> Regards, >>> Atsawin. >>> -- >>> Atsawin Chaowanakritsanakul >>> System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ >>> Email: jo...@na... >>> >>> ---------- Original Message ----------- >>> From:Arne Redlich <arn...@go...> >>> To:Atsawin Chaowanakritsanakul <jo...@na...> >>> Cc:isc...@li..., sun...@gm... >>> Sent:Sun, 22 Apr 2012 20:13:05 +0200 >>> Subject:Re: [Iscsitarget-devel] Ietd error when file is unavailable >>> >>>> I assume you saw the above error messages with r467 as well, only the >>>> oops below is new, right? >>>> >>>> Thanks, >>>> Arne >>>> >>>> -- >>>> This message has been scanned for viruses and >>>> dangerous content by MailScanner, and is >>>> believed to be clean. >>> ------- End of Original Message ------- >>> >>> >>> -- >>> This message has been scanned for viruses and >>> dangerous content by MailScanner, and is >>> believed to be clean. >>> |
From: Atsawin C. <jo...@na...> - 2012-04-27 02:36:32
|
Yuchong, Today I've tested on r.478. IETD does not cause OOP when file is unavailable. Unfortunately, I didn't have enough time to test on r.481, yet. It is a server for Internet Cafe Shop and I have to wait until there is no customer to test the system. I'lll test on r.481 as soon as possible. Regards, Atsawin. -- Atsawin Chaowanakritsanakul System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ Email: jo...@na... ---------- Original Message ----------- From:Yucong Sun (叶雨飞) <sun...@gm...> To:Atsawin Chaowanakritsanakul <jo...@na...> Cc:Arne Redlich <arn...@go...>, isc...@li... Sent:Tue, 24 Apr 2012 13:35:24 -0700 Subject:Re: [Iscsitarget-devel] Ietd error when file is unavailable > let me know if the new patch didn't work for you. > > On Mon, Apr 23, 2012 at 10:23 PM, Yucong Sun (叶雨飞) > <sun...@gm...> wrote: > > it's actually a easy one.. and it's not affecting any normal > > condition, only I/O error would crash, I will send a patch tomorrow. > > > > On Mon, Apr 23, 2012 at 10:18 PM, Yucong Sun (叶雨飞) <sun...@gm...> wrote: > >> Thanks for the report, I will try to look at it tomorrow, it's normal > >> that it become unresponsive after the kernel oops, you will have to > >> reboot to make it work again. > >> ------- End of Original Message ------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
From: Atsawin C. <jo...@na...> - 2012-05-06 02:24:45
|
Hi, Yesterday, I have tested on r.481 and IETD work properly after file was unavailable. Regards, Atsawin. -- Atsawin Chaowanakritsanakul System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ Email: jo...@na... ---------- Original Message ----------- From:Atsawin Chaowanakritsanakul <jo...@na...> To:Yucong Sun (叶雨飞) <sun...@gm...> Cc:Arne Redlich <arn...@go...>, isc...@li... Sent:Fri, 27 Apr 2012 09:36:01 +0700 Subject:Re: [Iscsitarget-devel] Ietd error when file is unavailable Yuchong, Today I've tested on r.478. IETD does not cause OOP when file is unavailable. Unfortunately, I didn't have enough time to test on r.481, yet. It is a server for Internet Cafe Shop and I have to wait until there is no customer to test the system. I'lll test on r.481 as soon as possible. Regards, Atsawin. -- Atsawin Chaowanakritsanakul System Engineer, J and P Solution Co., Ltd., http://www.jandp.co.th/ Email: jo...@na... ---------- Original Message ----------- From:Yucong Sun (叶雨飞) <sun...@gm...> To:Atsawin Chaowanakritsanakul <jo...@na...> Cc:Arne Redlich <arn...@go...>, isc...@li... Sent:Tue, 24 Apr 2012 13:35:24 -0700 Subject:Re: [Iscsitarget-devel] Ietd error when file is unavailable > let me know if the new patch didn't work for you. > > On Mon, Apr 23, 2012 at 10:23 PM, Yucong Sun (叶雨飞) > <sun...@gm...> wrote: > > it's actually a easy one.. and it's not affecting any normal > > condition, only I/O error would crash, I will send a patch tomorrow. > > > > On Mon, Apr 23, 2012 at 10:18 PM, Yucong Sun (叶雨飞) <sun...@gm...> wrote: > >> Thanks for the report, I will try to look at it tomorrow, it's normal > >> that it become unresponsive after the kernel oops, you will have to > >> reboot to make it work again. > >> ------- End of Original Message ------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |