On 11/09/2016 07:49 AM, Hannes Reinecke wrote:
> On 11/08/2016 07:52 PM, Xose Vazquez Perez wrote:
>> On 07/15/2016 08:48 AM, Hannes Reinecke wrote:
>>
>>> Recent kernels have an 'access_state' attribute which allows
>>> us to read the asymmetric access state directly from sysfs.
>>
>> Hi Hannes,
On Wed, Dec 07, 2016 at 02:42:16PM +0800, peng.lia...@zte.com.cn wrote:
>Hello, Ben
>
>Sorry for late to reply.
>
>Such is the case as you said below. If fast_io_fail_tmo is off we have to
>cap
>
>dev_loss_tmo at 600. So, this patch is a wrong guide and will be cause a
>
>
On 12/02/2016 04:52 AM, Benjamin Marzinski wrote:
> I don't really see the need for this change. But we wouldn't be pulling
> it in until the next major RHEL release [...]
BTW, do you(SUSE/RH) have any distro fixes/features pending for upstream?
--
dm-devel mailing list
dm-devel@redhat.com
On 11/11/16, 10:49 AM, "Xose Vazquez Perez" wrote:
NetApp did confirm this is not required.
Cc: Martin George
Cc: Robert Stankey
Cc: Steven Schremmer
Cc: Sean
On Mon, Dec 05, 2016 at 11:46:31AM -0800, Tim Chen wrote:
> Algorithms not compatible with mcryptd could be spawned by mcryptd
> with a direct crypto_alloc_tfm invocation using a "mcryptd(alg)" name
> construct. This causes mcryptd to crash the kernel if an arbitrary
> "alg" is incompatible and
> "Xose" == Xose Vazquez Perez writes:
Xose> NetApp did confirm this is not required.
Applied to 4.10/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
This patch avoids that the following call trace can be triggered:
[ cut here ]
WARNING: CPU: 10 PID: 19102 at drivers/md/dm-mpath.c:543
__multipath_map.isra.17+0x23a/0x370 [dm_multipath]
CPU: 10 PID: 19102 Comm: mkfs.ext4 Not tainted 4.9.0-rc8-dbg+ #4
Call Trace:
[]
On 11/25/2016 10:00 AM, Martin Wilck wrote:
> I am not sure I see the merit of these changes. If it's really
> necessary to change the wording of the log messages which people have
> got used to, the new ones should be really more self-explanatory than
> the old ones.
Some of them are a riddle,
Hello, Hannes
The kernel didn't limit the dev_loss_tmo if fast_io_fail_tmo is 0.
But multipath did. Should I leave it alone and just revert this patch?
Thanks.
原始邮件
发件人:HannesReinecke
收件人:<dm-devel@redhat.com>
日 期 :2016年12月07日 15:04
主 题 :Re: [dm-devel] [PATCH] libmultipath: ensure
On Wed, Dec 07 2016 at 7:56P -0500,
Bart Van Assche wrote:
> This patch avoids that the following call trace can be triggered:
>
> [ cut here ]
> WARNING: CPU: 10 PID: 19102 at drivers/md/dm-mpath.c:543
> __multipath_map.isra.17+0x23a/0x370
I have a dm-cache device that throws the following error when I try to
create it:
device-mapper: cache: 253:20: unable to switch cache to write mode
until repaired.
device-mapper: cache: 253:20: switching cache to read-only mode
device-mapper: table: 253:20: cache: Unable to get write
On Wed, 2016-12-07 at 16:44 +0100, Xose Vazquez Perez wrote:
> On 11/25/2016 10:00 AM, Martin Wilck wrote:
>
> > I am not sure I see the merit of these changes. If it's really
> > necessary to change the wording of the log messages which people
> > have
> > got used to, the new ones should be
12 matches
Mail list logo