Re: handling error on RECLAIM_COMPLETE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Jan 24, 2017, at 14:40, Olga Kornievskaia <aglo@xxxxxxxxx> wrote:
> 
> On Tue, Jan 24, 2017 at 2:12 PM, Trond Myklebust
> <trondmy@xxxxxxxxxxxxxxx> wrote:
>> 
>>> On Jan 24, 2017, at 14:06, Olga Kornievskaia <aglo@xxxxxxxxx> wrote:
>>> 
>>> Hi Trond,
>>> 
>>> Is there a reason that nfs4_proc_reclaim_complete() isn't  wrapped
>>> with a do while() to handle errors?
>> 
>> What do we not already handle correctly in nfs4_reclaim_complete_done()?
> 
> Could this be because when an error occurs rpc_done isn't called
> (rpc_release is called)? What I see is that if RECLAIM_COMPLETE gets
> an error (BAD_SESSION) the client just ignores it.
> 

That’s correct. Why do we need to handle BAD_SESSION there? We’re done with state recovery, so if the server rebooted, we can catch that later.��.n��������+%������w��{.n�����{��w���jg��������ݢj����G�������j:+v���w�m������w�������h�����٥




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux