> On Wed, Feb 15, 2023 at 3:44 AM Roger Heflin wrote:
>
> I think he is wanting the parity across the data blocks on the
> separate filesystems (some sort of parity across fs[1-8]/block0 to
> parity/block0).
Correct.
> On Wed, Feb 15, 2023 at 3:44 AM Roger Heflin wrote:
> it is not clear to me
> On Tue, Feb 14, 2023 at 2:28 PM Roger Heflin wrote:
>
> Such that you can lose any one data disk and parity can rebuild that
> disk. And if you lose several data diskis, then you have intact
> non-striped data for the remaining disks.
>
> It would almost seem that you would need to put a
> On Mon, Feb 13, 2023 at 11:40 AM John Stoffel wrote:
>
> >>>>> "Kyle" == Kyle Sanderson writes:
>
> > hi DM and Linux-RAID,
> > There have been multiple proprietary solutions (some nearly 20 years
> > old now) with a number of (userspace
hi DM and Linux-RAID,
There have been multiple proprietary solutions (some nearly 20 years
old now) with a number of (userspace) bugs that are becoming untenable
for me as an end user. Basically how they work is a closed MD module
(typically administered through DM) that uses RAID4 for a
> Makes sense. I'm going to send it upstream and Cc stable as documented
> in
> https://www.kernel.org/doc/html/v4.10/process/stable-kernel-rules.html#option-1
> I will then revert this change in the set that fixes the problem.
Did this go anywhere? I'm still not seeing it in any of the stable
on/qat_algs.c#L1022
> [2] https://elixir.bootlin.com/linux/latest/source/drivers/md/dm-crypt.c#L1584
> [3]
> https://01.org/sites/default/files/downloads//336211qatsoftwareforlinux-rn-hwversion1.7021.pdf
> - page 25
>
> --
> Giovanni
>
>
> On Sat, Feb 19, 2022 at 03:
ated.
Kyle.
On Sat, Feb 19, 2022 at 1:03 PM Dave Chinner wrote:
>
> On Fri, Feb 18, 2022 at 09:02:28PM -0800, Kyle Sanderson wrote:
> > A2SDi-8C-HLN4F has IQAT enabled by default, when this device is
> > attempted to be used by xfs (through dm-crypt) the entire kernel
> >
A2SDi-8C-HLN4F has IQAT enabled by default, when this device is
attempted to be used by xfs (through dm-crypt) the entire kernel
thread stalls forever. Multiple users have hit this over the years
(through sporadic reporting) - I ended up trying ZFS and encryption
wasn't an issue there at all
