Hi,
Does anyone have any idea where I can find the upstream multipath-tool
git repository including the lately fixed issues?
Thanks,
Changwei
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
On Thu, Oct 26 2017 at 6:18am -0400,
Muneendra Kumar M wrote:
>Hi ,
>
>
>
>We are working on the SAN fabric side to collect and present the multipath
>status information to the SAN administrators.
>
>So, I am looking forward to push the multipath state
Hi ,
We are working on the SAN fabric side to collect and present the multipath
status information to the SAN administrators.
So, I am looking forward to push the multipath state information to the fabric
in the form of CT (Common Transport) frames, by using the libhba APIs.
Since the multipath
Add a test that exercises DAX's new MAP_SYNC flag.
This test creates a file and writes to it via an mmap(), but never syncs
via fsync/msync. This process is tracked via dm-log-writes, then replayed.
If MAP_SYNC is working the dm-log-writes replay will show the test file
with 1MiB of on-media
Hello
I find an issue when use dmsetup in the situation udev event timeout.
Dmsetup use the dm_udev_wait function sync with udev event.When use the dmsetup
generate a new dm-disk, if the raw disk is abnormal(for example ,a ipsan disk
hung IO request), the udevd daemon handle the dm-disk udev
On Sun, Oct 22, 2017 at 9:56 AM, Amir Goldstein wrote:
> On Sat, Oct 21, 2017 at 12:25 AM, Ross Zwisler
> wrote:
>> Add a test that exercises DAX's new MAP_SYNC flag.
>>
>> This test creates a file and writes to it via an mmap(), but never syncs
On Wed, Oct 25, 2017 at 11:47 PM, Ross Zwisler
wrote:
> Add a test that exercises DAX's new MAP_SYNC flag.
>
> This test creates a file and writes to it via an mmap(), but never syncs
> via fsync/msync. This process is tracked via dm-log-writes, then replayed.
>
>
On Wed, Oct 25, 2017 at 03:19:22PM +0300, Amir Goldstein wrote:
> On Sun, Oct 22, 2017 at 9:56 AM, Amir Goldstein wrote:
> > On Sat, Oct 21, 2017 at 12:25 AM, Ross Zwisler
> > wrote:
> >> Add a test that exercises DAX's new MAP_SYNC flag.
> >>
>