Hi Steffen,
Once a new arrived LUN mapped we will do rescan by "echo '- - -' >
/sys/class/scsi_host/host2/scan". After rescan only the scsi_id tool give the
right serial id, udevadm still got the prvious one.
I have monitor the udev event by udevadm monitor while mapping a new LUN to the
host, w
Bart,
On 7/11/17 01:25, Bart Van Assche wrote:
> On Mon, 2017-07-03 at 15:44 +0900, Damien Le Moal wrote:
>> A zone ID is a 32 bits unsigned int which can overflow when doing the
>> bit shifts calculations in dmz_start_sect(). With a 256 MB zone size
>> drive, the overflow happens for a zone ID >=
Hi Martin,
Thanks for the response.
I built multipath using the latest code to test, but I also see this issue in
our product environment(multipath-tools v0.4.9 (05/33, 2016)).
I use getuid_callout is due to the id_serial is not correct as following:
[root@localhost ~]# multipath -ll
360050763008
On Mon, 2017-07-10 at 17:58 +0800, liuq...@huayun.com wrote:
> Dear list,
> We have a FC storage and using multipathd to manager the FC paths.
> I've met an issue in this environment. The following is how to
> recreate the issue.
Which version of multipath-tools have you been using? Could you plea
>From 2/2:
"""
There are quite a number of occurrences in the kernel of the pattern
if (dst != src)
memcpy(dst, src, walk.total % AES_BLOCK_SIZE);
crypto_xor(dst, final, walk.total % AES_BLOCK_SIZE);
or
crypto_xor(keystream, src, nbytes);
memcpy(dst, keystream, nbyte
There are quite a number of occurrences in the kernel of the pattern
if (dst != src)
memcpy(dst, src, walk.total % AES_BLOCK_SIZE);
crypto_xor(dst, final, walk.total % AES_BLOCK_SIZE);
or
crypto_xor(keystream, src, nbytes);
memcpy(dst, keystream, nbytes);
where crypt
In preparation of updating crypto_xor() [which is what the crypto API
exposes to other subsystems] to use separate operands for input and
output, first modify the __crypto_xor() implementation that provides
the actual functionality when not using the inline version.
Signed-off-by: Ard Biesheuvel
On 07/10/2017 11:58 AM, liuq...@huayun.com wrote:
Dear list,
We have a FC storage and using multipathd to manager the FC paths.
I've met an issue in this environment. The following is how to recreate the
issue.
===
1. Map a LUN to host with LUN ID 0,
2. rescan fc_host, a new path will be fo
Dear list,
We have a FC storage and using multipathd to manager the FC paths.
I've met an issue in this environment. The following is how to recreate the
issue.
===
1. Map a LUN to host with LUN ID 0,
2. rescan fc_host, a new path will be found by multipath.
3. Unmap LUN 0. path will failed
1. And in this (
https://kernel.googlesource.com/pub/scm/linux/kernel/git/kasatkin/linux-digsig/+/2dfa67a1a4c049fd33fcc6abcb1c8ca57b17a268/Documentation/device-mapper/dm-integrity.txt
) implementation gives variant to use external device for metadata and
journal. It really affect perfomance, I t
10 matches
Mail list logo
