Re: NFSv2/3 vs v4 error codes?

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

 



On Wed, Sep 10, 2014 at 03:16:50PM -0700, Christoph Hellwig wrote:
> As a followup to the fallocate discussion I checked what we map ENODEV
> to in nfsd.  Turns out we map it to NFSERR_NODEV, which doesn't exist
> in eiter NFSv4.0 nor NFSv4.1 despite the comment in
> include/uapi/linux/nfs.h claiming otherwise.

That's interesting.  Is there a reasonable alternative, or is this a
protocol bug?

> I also just ran into another issue where nfserrno translates a large
> lits of errors into NFSERR_JUKEBOX, but for v4 we'd really want
> NFSERR_DELAY instead for most of them.

The distinction is academic as they're both 10008.

> Is it time for a version specific errno mapping?

I'm certainly not opposed if it turns out to be necessary.

--b.
--
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




[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