On 2013-12-04 13:19, Christoph Hellwig wrote:
On Wed, Dec 04, 2013 at 01:15:41PM +0200, Antti T?nkyr? wrote:
>On 2013-12-04 10:31, Christoph Hellwig wrote:
> >Please just fix ntfs to do the mapping for you, EILSEQ is not an
> >error the VFS or applications expect either.
> >
>How would you propose the mapping to be done? Are you sure about
>EILSEQ not being an error that VFS/applications expect, my userspace
>tools seem to handle local filesystem returning EILSEQ just fine?
EILSEQ doesn't have a specified meaning for VFS operations. Of course
your app could handle it in some way, but that's your implementation
specific way that has not base for it.
Okay, I understand your point. However, in this case I was referring to
basic GNU/Linux userspace tools which I can hardly call my own apps :)
All in all I guess we could keep the current mapping path which
eventually leads into I/O error. Next we should understand why the share
fails when I/O error is emitted...
- Antti
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
