Re: [PATCH] Fix bogus fsync() error

2011-02-01 Thread Corinna Vinschen
On Feb 1 10:48, Christopher Faylor wrote: > On Tue, Feb 01, 2011 at 09:47:15AM +0100, Corinna Vinschen wrote: > >On Jan 31 20:44, Christian Franke wrote: > >> If used on raw devices like /dev/sda fsync() always fails with > >> EBADRQC (54) because FlushFileBuffers() always fails with > >> ERROR_IN

Re: [PATCH] Fix bogus fsync() error

2011-02-01 Thread Christopher Faylor
On Tue, Feb 01, 2011 at 09:47:15AM +0100, Corinna Vinschen wrote: >On Jan 31 20:44, Christian Franke wrote: >> If used on raw devices like /dev/sda fsync() always fails with >> EBADRQC (54) because FlushFileBuffers() always fails with >> ERROR_INVALID_FUNCTION (1). >> >> The attached patch fixes t

Re: [PATCH] Fix bogus fsync() error

2011-02-01 Thread Corinna Vinschen
On Jan 31 20:44, Christian Franke wrote: > If used on raw devices like /dev/sda fsync() always fails with > EBADRQC (54) because FlushFileBuffers() always fails with > ERROR_INVALID_FUNCTION (1). > > The attached patch fixes this by simply ignoring this error in the > fhandler_base implementation.

[PATCH] Fix bogus fsync() error

2011-01-31 Thread Christian Franke
If used on raw devices like /dev/sda fsync() always fails with EBADRQC (54) because FlushFileBuffers() always fails with ERROR_INVALID_FUNCTION (1). The attached patch fixes this by simply ignoring this error in the fhandler_base implementation. This should not affect any real flush errors wh