From: Vitaly Chikunov <vt@altlinux.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
Shivasharan S <shivasharan.srikanteshwara@broadcom.com>,
Chandrakanth patil <chandrakanth.patil@broadcom.com>
Subject: Re: megaraid_sas: multiple FALLOC_FL_ZERO_RANGE causes timeouts and resets on MegaRAID 9560-8i 4GB since 5.19
Date: Fri, 16 Feb 2024 13:08:44 +0300 [thread overview]
Message-ID: <20240216100844.aabjlexbwq6ggzs2@altlinux.org> (raw)
In-Reply-To: <yq18r3lful5.fsf@ca-mkp.ca.oracle.com>
Martin,
On Thu, Feb 15, 2024 at 01:42:35PM -0500, Martin K. Petersen wrote:
>
> I'd appreciate it if you could test the patch Bart referred you to.
>
> > I am reported that bisect found this commit to cause above mentioned
> > problem:
>
> Also, I would like to understand why things fail as a result of the
> original change.
>
> Could you please send me the output of:
>
> # sg_readcap -l /dev/sdc
> # sg_vpd -l /dev/sdc
> # sg_vpd -p 0xb0 /dev/sdc
> # sg_vpd -p 0xb1 /dev/sdc
> # sg_vpd -p 0xb2 /dev/sdc
Here it is:
# sg_readcap -l /dev/sdc
Read Capacity results:
Protection: prot_en=0, p_type=0, p_i_exponent=0
Logical block provisioning: lbpme=0, lbprz=0
Last LBA=3907029167 (0xe8e088af), Number of logical blocks=3907029168
Logical block length=512 bytes
Logical blocks per physical block exponent=0
Lowest aligned LBA=0
Hence:
Device size: 2000398934016 bytes, 1907729.1 MiB, 2000.40 GB, 2.00 TB
# sg_vpd -l /dev/sdc
Supported VPD pages VPD page:
[PQual=0 Peripheral device type: disk]
0x00 Supported VPD pages [sv]
0x80 Unit serial number [sn]
0x83 Device identification [di]
0x87 Mode page policy [mpp]
0x89 ATA information (SAT) [ai]
0x8a Power condition [pc]
0xb0 Block limits (SBC) [bl]
0xb1 Block device characteristics (SBC) [bdc]
0xb2 Logical block provisioning (SBC) [lbpv]
0xb6 Zoned block device characteristics [zbdch]
# sg_vpd -p 0xb0 /dev/sdc
Block limits VPD page (SBC):
Write same non-zero (WSNZ): 1
Maximum compare and write length: 0 blocks [Command not implemented]
Optimal transfer length granularity: 0 blocks [not reported]
Maximum transfer length: 0 blocks [not reported]
Optimal transfer length: 0 blocks [not reported]
Maximum prefetch transfer length: 0 blocks [ignored]
Maximum unmap LBA count: 0 [Unmap command not implemented]
Maximum unmap block descriptor count: 0 [Unmap command not implemented]
Optimal unmap granularity: 0 blocks [not reported]
Unmap granularity alignment valid: false
Unmap granularity alignment: 0 [invalid]
Maximum write same length: 0xffff blocks
Maximum atomic transfer length: 0 blocks [not reported]
Atomic alignment: 0 [unaligned atomic writes permitted]
Atomic transfer length granularity: 0 [no granularity requirement
Maximum atomic transfer length with atomic boundary: 0 blocks [not reported]
Maximum atomic boundary size: 0 blocks [can only write atomic 1 block]
# sg_vpd -p 0xb1 /dev/sdc
Block device characteristics VPD page (SBC):
Nominal rotation rate: 7200 rpm
Product type: Not specified
WABEREQ=0
WACEREQ=0
Nominal form factor: 3.5 inch
MACT=0
ZONED=0
RBWZ=0
BOCS=0
FUAB=0
VBULS=0
DEPOPULATION_TIME=0 (seconds)
# sg_vpd -p 0xb2 /dev/sdc
Logical block provisioning VPD page (SBC):
Unmap command supported (LBPU): 0
Write same (16) with unmap bit supported (LBPWS): 0
Write same (10) with unmap bit supported (LBPWS10): 0
Logical block provisioning read zeros (LBPRZ): 0
Anchored LBAs supported (ANC_SUP): 0
Threshold exponent: 0 [threshold sets not supported]
Descriptor present (DP): 0
Minimum percentage: 0 [not reported]
Provisioning type: 0 (not known or fully provisioned)
Threshold percentage: 0 [percentages not supported]
About the patch it will be tested later today.
Thanks,
>
> Thanks!
>
> --
> Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-02-16 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 1:18 megaraid_sas: multiple FALLOC_FL_ZERO_RANGE causes timeouts and resets on MegaRAID 9560-8i 4GB since 5.19 Vitaly Chikunov
2024-02-15 15:18 ` Vitaly Chikunov
2024-02-15 18:42 ` Martin K. Petersen
2024-02-16 10:08 ` Vitaly Chikunov [this message]
2025-03-09 13:55 ` Samy Lahfa
2025-03-11 2:24 ` Martin K. Petersen
2025-03-15 17:12 ` Ryan Lahfa
2025-03-18 1:38 ` Martin K. Petersen
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=20240216100844.aabjlexbwq6ggzs2@altlinux.org \
--to=vt@altlinux.org \
--cc=chandrakanth.patil@broadcom.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@broadcom.com \
/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