Re: NFS client fix - was NFS over-quota not detected if utimes() called before fsync()/close()

To: "J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>
Subject: Re: NFS client fix - was NFS over-quota not detected if utimes() called before fsync()/close()
From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Date: Wed, 7 Aug 2013 10:00:54 +0200

On Tue, Aug 06, 2013 at 12:32:13PM +0200, J. Hannken-Illjes wrote:
> To answer my own question: Yes, nfs_vinvalbuf() ignores errors from
> vinvalbuf() and therefore delayed write errors get lost.  Running the
> test on NFS v2 instead of NFS v3, these errors even get lost with
> fsync() or close() only.
> 
> The attached diff fixes this behaviour by keeping delayed write errors
> from vinvalbuf() for fsync() or close().
> 
> Comments or objections anyone?

I didn't try to run it, but it looks good. Thanks for looking into this !

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--

References:
- NFS over-quota not detected if utimes() called before fsync()/close()
  - From: Edgar Fuß
- Re: NFS over-quota not detected if utimes() called before fsync()/close()
  - From: Edgar Fuß
- Re: NFS over-quota not detected if utimes() called before fsync()/close()
  - From: Edgar Fuß
- Re: NFS over-quota not detected if utimes() called before fsync()/close()
  - From: Christos Zoulas
- Re: NFS over-quota not detected if utimes() called before fsync()/close()
  - From: J. Hannken-Illjes
- NFS client fix - was NFS over-quota not detected if utimes() called before fsync()/close()
  - From: J. Hannken-Illjes

Prev by Date: Re: Use of the PC value in interrupt/exception handlers
Next by Date: Failing filesystem tests
Previous by Thread: NFS client fix - was NFS over-quota not detected if utimes() called before fsync()/close()
Next by Thread: setting the quota2 grace period
Indexes:

Home | Main Index | Thread Index | Old Index