Re: [dm-devel] [PATCH] mdadm: fix compilation failure on the x32 ABI

On 11/17/22 09:28, Mariusz Tkaczyk wrote: > On Fri, 4 Nov 2022 10:01:22 -0400 (EDT) > Mikulas Patocka wrote: > >> Hi >> >> Here I'm sending a patch for the mdadm utility. It fixes compile failure >> on the x32 ABI. >> >> Mikulas >> >> >> From: Mikulas Patocka >> >> The x32 ABI has 32-bit long

Re: [PATCH v4 2/2] mdadm: Introduce new array state 'broken' for raid0/linear

the 'array_state' sysfs attribute into account instead of only rely in the MD_SB_CLEAN flag. Cc: Jes Sorensen Cc: NeilBrown Cc: Song Liu Signed-off-by: Guilherme G. Piccoli --- Applied thanks! I fixed up one minor nit rather than having to do the merry-go-round by email one more time

Re: [dm-devel] [mdadm PATCH] Fix typo in new udev rule.

On 05/05/2017 01:16 AM, NeilBrown wrote: As pointed out by Peter Rajnoha, the correct usage in udev is TEST=="file", not TEST="file". Also improve a related comment which was a bit informal. Reported-by: Peter Rajnoha Fixes: cd6cbb08c458 ("Create: tell udev md device is

Re: [dm-devel] [mdadm PATCH] Create: tell udev md device is not ready when first created.

On 05/03/2017 10:13 AM, Peter Rajnoha wrote: On 05/02/2017 03:32 PM, Jes Sorensen wrote: On 04/28/2017 05:28 AM, Peter Rajnoha wrote: On 04/28/2017 07:05 AM, NeilBrown wrote: When an array is created the content is not initialized, so it could have remnants of an old filesystem or md array

Re: [dm-devel] [mdadm PATCH] Create: tell udev md device is not ready when first created.

On 05/03/2017 10:32 AM, Peter Rajnoha wrote: On 05/02/2017 03:42 PM, Jes Sorensen wrote: On 04/28/2017 01:05 AM, NeilBrown wrote: When an array is created the content is not initialized, so it could have remnants of an old filesystem or md array etc on it. udev will see this and might try

Re: [dm-devel] [mdadm PATCH] Create: tell udev md device is not ready when first created.

On 04/28/2017 01:05 AM, NeilBrown wrote: When an array is created the content is not initialized, so it could have remnants of an old filesystem or md array etc on it. udev will see this and might try to activate it, which is almost certainly not what is wanted. So create a mechanism for mdadm

Re: [dm-devel] [mdadm PATCH 4/4] Create: tell udev device is not ready when first created.

On 05/02/2017 07:40 AM, Peter Rajnoha wrote: On 05/01/2017 06:35 AM, NeilBrown wrote: On Fri, Apr 28 2017, Peter Rajnoha wrote: Then mdadm opens the devive, clears any old content/signatures the data area may contain, then closes it - this generates the third event - which is the "synthetic

Re: [dm-devel] [mdadm PATCH] Create: tell udev md device is not ready when first created.

On 04/28/2017 05:28 AM, Peter Rajnoha wrote: On 04/28/2017 07:05 AM, NeilBrown wrote: When an array is created the content is not initialized, so it could have remnants of an old filesystem or md array etc on it. udev will see this and might try to activate it, which is almost certainly not

Re: [dm-devel] [PATCH v2] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names.

Robert LeBlanc writes: > Linux allows for 32 character device names. When using the maximum size > device name and also > storing "/dev/", devname needs to be 37 character long to store the complete > device name. > i.e. "/dev/md_abcdefghijklmnopqrstuvwxyz12\0" > >