From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Konstantin Shelekhin <k.shelekhin@yadro.com>
Cc: Martin Petersen <martin.petersen@oracle.com>,
Mike Christie <michael.christie@oracle.com>,
<target-devel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
<linux@yadro.com>, Dmitry Bogdanov <d.bogdanov@yadro.com>
Subject: Re: [PATCH 1/2] scsi: target: core: Add sense reason for space allocation errors
Date: Wed, 20 Oct 2021 23:21:54 -0400 [thread overview]
Message-ID: <yq1pmrz6pbl.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20211020184319.588002-2-k.shelekhin@yadro.com> (Konstantin Shelekhin's message of "Wed, 20 Oct 2021 21:43:18 +0300")
Konstantin,
> According to SBC-3 4.7.3.6 this sense reason shall be used in situations
> where thin provisioned logical unit cannot satisfy the write request due
> to the lack of free blocks.
> + [TCM_SPACE_ALLOCATION_FAILED] = {
> + .key = DATA_PROTECT,
> + .asc = 0x27,
> + .ascq = 0x07, /* SPACE ALLOCATION FAILED WRITE PROTECT */
> + },
How do we know this is a permanent condition and not a temporary space
exhaustion?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-10-21 3:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 18:43 [PATCH 0/2] scsi: target: iblock: Report space allocation errors Konstantin Shelekhin
2021-10-20 18:43 ` [PATCH 1/2] scsi: target: core: Add sense reason for " Konstantin Shelekhin
2021-10-21 3:21 ` Martin K. Petersen [this message]
2021-10-21 8:55 ` Konstantin Shelekhin
2021-10-20 18:43 ` [PATCH 2/2] scsi: target: iblock: Report " Konstantin Shelekhin
2021-10-22 5:27 ` kernel test robot
2021-11-08 9:59 ` kernel test robot
2021-11-23 13:29 ` kernel test robot
2021-11-25 2:36 ` kernel test robot
2021-11-25 7:26 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 14:15 [PATCH 0/2] " Konstantin Shelekhin
2023-05-17 14:15 ` [PATCH 1/2] scsi: target: core: Add sense reason for " Konstantin Shelekhin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq1pmrz6pbl.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=d.bogdanov@yadro.com \
--cc=k.shelekhin@yadro.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@yadro.com \
--cc=michael.christie@oracle.com \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox