On Sat, Jun 06, 2020 at 07:23:28PM +, Martin Wilck wrote:
> On Fri, 2020-06-05 at 17:27 -0500, Benjamin Marzinski wrote:
> > On Fri, Jun 05, 2020 at 07:20:26PM +, Martin Wilck wrote:
> > > Hi Ben,
> > >
> > > On Thu, 2020-06-04 at 19:30 -0500, Benjamin Marzinski wrote:
> > > > I recently g
On Fri, 2020-06-05 at 17:27 -0500, Benjamin Marzinski wrote:
> On Fri, Jun 05, 2020 at 07:20:26PM +, Martin Wilck wrote:
> > Hi Ben,
> >
> > On Thu, 2020-06-04 at 19:30 -0500, Benjamin Marzinski wrote:
> > > I recently got a request to add the Oracle ASM filer driver
> > > devices
> > > to
> >
Hi Ben,
On Thu, 2020-06-04 at 19:30 -0500, Benjamin Marzinski wrote:
> I recently got a request to add the Oracle ASM filer driver devices
> to
> multipath's builtin devnode blacklist. However, instead of having to
> do
> always this for each device type individually, I decided to make
> multipat
On Fri, Jun 05, 2020 at 07:20:26PM +, Martin Wilck wrote:
> Hi Ben,
>
> On Thu, 2020-06-04 at 19:30 -0500, Benjamin Marzinski wrote:
> > I recently got a request to add the Oracle ASM filer driver devices
> > to
> > multipath's builtin devnode blacklist. However, instead of having to
> > do
>
I recently got a request to add the Oracle ASM filer driver devices to
multipath's builtin devnode blacklist. However, instead of having to do
always this for each device type individually, I decided to make
multipath blacklist all non scsi, nvme, and dasd devnodes by default.
This is what the mul