lu_disk_write() failed

Status
Not open for further replies.
Joined
Oct 25, 2013
Messages
2
I just started getting these errors last night:

Oct 25 13:00:00 freenas istgt[2207]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Oct 25 13:00:00 freenas istgt[2207]: istgt_lu_disk.c:6313:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed

I'm new to freenas and am not sure what to even post to try and ask for help much less a solution? Can anyone point me in the correct direction?

Thanks much for any assistance.
 
D

dlavigne

Guest
Did you ever sort this?

If not, is this in a virtual machine or a hardware install?
 
Joined
Oct 25, 2013
Messages
2
I did. This is primarily used as an iscsi target and there were also some smb shares with it. I deleted the smb shares (the zfs volume underlying them) and the problem went away. It is a hardware install in use mostly as an iscsi target for backup storage from a virtual machine. Was about the only way to get a decent 9 tb backup drive to function without constant supervision.
 

atlantauser

Cadet
Joined
Jan 15, 2014
Messages
6
I've been using FreeNAS for a few months. In the last couple weeks I created some zVOL backed iSCSI Targets and have 3 ESXi hosts pointed at them. As of last night something happened (no log entries to detail what), but now I'm seeing these messages continuously even after a reboot. The iSCSI LUNs are formatted with VMFS5.

Jan 31 09:14:53 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:53 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed
Jan 31 09:14:53 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:53 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed
Jan 31 09:14:56 freenas istgt[53069]: istgt_lu_disk.c:4234:istgt_lu_disk_lbwrite_same: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:56 freenas istgt[53069]: istgt_lu_disk.c:6488:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite_same() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed
Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:4130:istgt_lu_disk_lbwrite: ***ERROR*** lu_disk_write() failed

Jan 31 09:14:57 freenas istgt[53069]: istgt_lu_disk.c:6239:istgt_lu_disk_execute: ***ERROR*** lu_disk_lbwrite() failed


I'm also getting weird responses from the command line.

[root@freenas] ~# iscontrol -h
iscontrol: sysctlbyname("net.iscsi_initiator.driver_version") failed; is the iscsi driver loaded?

[root@freenas] ~# iscsictl -L
Target name Target addr State

[root@freenas] ~# istgtcontrol list
empty config




The only thing different between yesterday and today is that I moved from a single NIC to an LACP link of 2 NICs with 9000 mtu. That worked fine all day yesterday and these issues didn't occur until sometime in the middle of the night last night (and there shouldn't have been any major operations going on).
 
Status
Not open for further replies.
Top