[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb7a539a-9161-4ac6-a49c-16f48d8fe4d7@auristor.com>
Date: Thu, 9 Nov 2023 13:12:08 -0500
From: Jeffrey E Altman <jaltman@...istor.com>
To: David Howells <dhowells@...hat.com>,
Marc Dionne <marc.dionne@...istor.com>
Cc: linux-afs@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 13/41] afs: Handle the VIO abort explicitly
On 11/9/2023 10:39 AM, David Howells wrote:
> When processing the result of a call, handle the VIO abort specifically
> rather than leaving it to a default case. Rather than erroring out
> unconditionally, see if there's another server if the volume has more than
> one server available, otherwise return -EREMOTEIO.
>
> Signed-off-by: David Howells <dhowells@...hat.com>
> cc: Marc Dionne <marc.dionne@...istor.com>
> cc: linux-afs@...ts.infradead.org
> ---
> fs/afs/rotate.c | 6 ++++++
> 1 file changed, 6 insertions(+)
OpenAFS fileservers can return VIO (112) either during an attempt to
load a vnode or to store a vnode. However, most IBM AFS derived cache
managers do not explicitly handle VIO errors and pass them to the vfs to
be interpreted as a local operating system error. For Linux that means
EHOSTDOWN. Therefore, AuriStorFS fileservers return UAEIO instead.
Please modify this patch to handle UAEIO the same as VIO.
Thank you.
Jeffrey Altman
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4039 bytes)
Powered by blists - more mailing lists