On Tue, Mar 13, 2018 at 10:56 PM, MASAKI haruka <y...@reasonset.net> wrote: >> On Tue, Mar 13, 2018 at 1:25 PM, MASAKI haruka <y...@reasonset.net> wrote: >> > journal(Kernel log), 7th try (to be readonly): >> > >> > --- >> > 3月 12 16:25:51 lily kernel: BTRFS info (device dm-6): creating UUID tree >> > 3月 12 16:25:53 lily iscsid[1406]: Connection-1:0 to [target: >> > iqn.1994-11.com.netgear:eggplant-01:edc9adcf:btr1group, portal: >> > 192.168.1.166,3260] through [iface: default] is shutdown. >> > 3月 12 16:25:53 lily iscsid[1406]: IPC qtask write failed: Broken pipe >> > 3月 12 16:26:18 lily kernel: connection1:0: detected conn error (1020) >> > 3月 12 16:26:19 lily iscsid[1406]: Kernel reported iSCSI connection 1:0 >> > error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3) >> > 3月 12 16:26:21 lily kernel: sd 8:0:0:0: [sdg] tag#5 UNKNOWN(0x2003) >> > Result: hostbyte=0x00 driverbyte=0x08 >> > 3月 12 16:26:21 lily kernel: sd 8:0:0:0: [sdg] tag#5 Sense Key : 0x2 >> > [current] [descriptor] >> > 3月 12 16:26:21 lily kernel: sd 8:0:0:0: [sdg] tag#5 ASC=0x8 ASCQ=0x0 >> > 3月 12 16:26:21 lily kernel: sd 8:0:0:0: [sdg] tag#5 CDB: opcode=0x8a 8a >> > 00 00 00 00 00 00 42 5c 00 00 00 34 00 00 00 >> > 3月 12 16:26:21 lily kernel: print_req_error: I/O error, dev sdg, sector >> > 4348928 >> >> >> Looks like network problems. Is one of these Btrfs volumes on an iSCSI >> device? Because there's a bunch of iSCSI errors followed by an I/O >> error with sector LBA reported, and then you get a bunch of Btrfs >> write errors. >> >> What's the relationship between /dev/sdg and device (dm-6) >> /dev/mapper/hymaster_1 ? >> > > > /dev/mapper/hymaster_1 is dm-crypt plain device. > Its real device is /dev/sdg it is an iSCSI disk > connected to NAS over GbE link local. > > If this probrem from network, it's looked difficult to solve > because I tried with two different computers without any other network > device...
There's a lot of complexity here. It might be drives on the NAS, it might networking hardware on the NAS, it could be networking hardware like switch or cables. It all has to be narrowed down. You'll need logs for the NAS and try to go from there. Maybe http://vger.kernel.org/vger-lists.html#linux-scsi is a place to start to see if these are drive or iSCSI specific problems, or network problems and then just process of elimination. But based on available information I don't think this is Btrfs. It's complaining about a preexisting problem. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
