Steffen,
>> Why not just shut FCP down unconditionally on excessive bit errors?
>> What's the benefit of allowing things to continue? Are you hoping things
>> will eventually recover in a single-path scenario?
>
> Experience told me that there will be an unforeseen end user scenario
> where I ne
On 10/1/19 8:26 PM, Martin K. Petersen wrote:
Ok, then why make this a module option that you will have to support
for the next 20+ years anyway if you feel this fix is the correct way
that it should be done instead?
I agree.
Why not just shut FCP down unconditionally on excessive bit errors?
Greg,
> Ok, then why make this a module option that you will have to support
> for the next 20+ years anyway if you feel this fix is the correct way
> that it should be done instead?
I agree.
Why not just shut FCP down unconditionally on excessive bit errors?
What's the benefit of allowing thi
On Tue, Oct 01, 2019 at 05:07:50PM +0200, Steffen Maier wrote:
> On 10/1/19 4:14 PM, Greg KH wrote:
> > On Tue, Oct 01, 2019 at 12:49:49PM +0200, Steffen Maier wrote:
> > > On excessive bit errors for the FCP channel ingress fibre path, the
> > > channel
> > > notifies us. Previously, we only emit
On 10/1/19 4:14 PM, Greg KH wrote:
On Tue, Oct 01, 2019 at 12:49:49PM +0200, Steffen Maier wrote:
On excessive bit errors for the FCP channel ingress fibre path, the channel
notifies us. Previously, we only emitted a kernel message and a trace record.
Since performance can become suboptimal with
On Tue, Oct 01, 2019 at 12:49:49PM +0200, Steffen Maier wrote:
> On excessive bit errors for the FCP channel ingress fibre path, the channel
> notifies us. Previously, we only emitted a kernel message and a trace record.
> Since performance can become suboptimal with I/O timeouts due to
> bit error
On excessive bit errors for the FCP channel ingress fibre path, the channel
notifies us. Previously, we only emitted a kernel message and a trace record.
Since performance can become suboptimal with I/O timeouts due to
bit errors, we now stop using an FCP device by default on channel
notification s
7 matches
Mail list logo
