Return-Path: Received: from mx3.molgen.mpg.de ([141.14.17.11]:42874 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751118AbdFULsH (ORCPT ); Wed, 21 Jun 2017 07:48:07 -0400 Subject: Full volume causes some NFS clients to get client ID expired responses To: linux-nfs@vger.kernel.org Cc: it+linux-nfs@molgen.mpg.de References: <03f0da7e-99c1-a015-c701-b8c8f4a6ec85@molgen.mpg.de> From: Paul Menzel Message-ID: <6c0fa7f4-a179-4b7e-9f52-abfa80df3bb4@molgen.mpg.de> Date: Wed, 21 Jun 2017 13:48:05 +0200 MIME-Version: 1.0 In-Reply-To: <03f0da7e-99c1-a015-c701-b8c8f4a6ec85@molgen.mpg.de> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: [Sorry, wrong subject.] Dear NFS folks, We experience the following behavior with the Linux series 4.4 and 4.9. When the exported directory on the server gets full to 100 % some NFS clients are unable to access the server anymore, but others can. The error is, that the server says the client ID has expired. The server, on which the client runs on, needs to be restarted. Then it works again. Can you think of an error path causing such a failure? What would be the right way to deal with this error? Kind regards, Paul