On 02.03.21 10:39, Stuart Henderson wrote:
On 2021/03/02 00:09, Mark Schneider wrote:
Hi,
Thank you for your feeeback.
Also OpenBSD 6.9beta snapshot is crashing when I setup RAID5 with three
"Samsung PRO 860 1TB" SSDs.
OpenBSD obsd69b.it-infra.org 6.9 GENERIC.MP#368 amd64
obsd69b# dmesg | gre
On Tue, Mar 02, 2021 at 09:39:15AM +, Stuart Henderson wrote:
> putting sr_validate_io+0x44 at the xs->datalen dereference,
>
> 4580 if (sd->sd_vol_status == BIOC_SVOFFLINE) {
> 4581 DNPRINTF(SR_D_DIS, "%s: %s device offline\n",
> 4582 DEVNAME(sd->sd
On 2021/03/02 00:09, Mark Schneider wrote:
> Hi,
>
> Thank you for your feeeback.
>
> Also OpenBSD 6.9beta snapshot is crashing when I setup RAID5 with three
> "Samsung PRO 860 1TB" SSDs.
> OpenBSD obsd69b.it-infra.org 6.9 GENERIC.MP#368 amd64
>
> obsd69b# dmesg | grepĀ -i bios
> bios0 at mainbu
Hi,
Thank you for your feeeback.
Also OpenBSD 6.9beta snapshot is crashing when I setup RAID5 with three
"Samsung PRO 860 1TB" SSDs.
OpenBSD obsd69b.it-infra.org 6.9 GENERIC.MP#368 amd64
obsd69b# dmesg | grepĀ -i bios
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdc312018 (61 entries)
bios0: vendor
Hi Karel,
Thank you very much for your feedback and hints.
I have already opened a bug request for this issue, however I am not
able to deliver the output of "trace" and "ps" commands from the ddb{4}>
or ddb{2}> prompts as the crashed system is frozen so I can not type or
see output typing bli
Hi Stefan
Thank you very much for your feedback, suggestions and hints.
Indeed yesterday I saw one read and one write error related to Samsung
PRO SSDs before another OS crash (I run more different tests writing big
files to the RAID5 using "dd" or "cat" commands)
Today I have installed three
On Sun, Feb 28, 2021 at 03:05:49AM +0100, Mark Schneider wrote:
> Hi again,
>
> I have repeated softraid tests using six pcs of 1TB Samsung HDD 3G SATA
> drives as RAID5 and I do not face the crash issue of the OS when using SSDs
> in the RAID5.
> Details of the RAID5 setting are in the attached f
Hi,
compile kernel with debug enabled so you will get line number from the
crash. See what's there. Go thorough git/cvs logs and see if anybody
did anything with global mutex over sata/sr raid. Read the code. The
possibility is you are hitting a bug which is there since raid5 was
added to ob
Hi again,
I have repeated softraid tests using six pcs of 1TB Samsung HDD 3G SATA
drives as RAID5 and I do not face the crash issue of the OS when using
SSDs in the RAID5.
Details of the RAID5 setting are in the attached file.
It looks like using SSD drives as RAID5 leads for some reason to t
9 matches
Mail list logo