On 2/25/21 14:12, Chaitanya Kulkarni wrote:
> On 2/25/21 13:49, Forza wrote:
>
>> The LIO target is running Fedora 33 Server with two Seagate Exos 10TB in Btrfs RAID-1 mode.
>>
>> Are there any debugging options that would help?
You can try following patch to get the more information about command
completion error :-
diff --git a/drivers/target/target_core_transport.c
b/drivers/target/target_core_transport.c
index 93ea17cbad79..f4e6e1c18867 100644
--- a/drivers/target/target_core_transport.c
+++ b/drivers/target/target_core_transport.c
@@ -873,6 +873,11 @@ void target_complete_cmd(struct se_cmd *cmd, u8
scsi_status)
cmd->transport_state |= (CMD_T_COMPLETE | CMD_T_ACTIVE);
spin_unlock_irqrestore(&cmd->t_state_lock, flags);
+ if (!success)
+ pr_err("%s %d cmd->scsi_status 0x%x"
+ "cmd->se_cmd_flags 0x%x\n", __func__, __LINE__,
+ cmd->scsi_status, cmd->se_cmd_flags);
+
INIT_WORK(&cmd->work, success ? target_complete_ok_work :
target_complete_failure_work);
queue_work_on(cmd->cpuid, target_completion_wq, &cmd->work);
> One way to go about it is to turn on the target tracing and examine the
> commands to
> see which command is failing if target has command level tracing
> implemented.
> This will allow other developers to help you more.
>
> Also if there a problem with the file system then you might want to run
> fsck before you
> establish the connection to make sure you have not encountered file
> system level errors.
>> Thanks for any advice.
> Also please mentioned that which kernel version you are using so that other
> developers can help you more.
>> ~Forza
>>
>
