[nfsv4] question about OPEN (for truncate), and OPEN_CONFIRM

cburnett@us.ibm.com

Message-ID: <OF088967E6.77EE909B-ON87256D13.00509E73@us.ibm.com>
From: Carl Burnett <cburnett@us.ibm.com>
Subject: [nfsv4] question about OPEN (for truncate), and OPEN_CONFIRM
Date: Fri, 25 Apr 2003 10:32:58 -0500

If the server receives an OPEN for an unchecked create that indicates the 
file should be truncated (size attribute 0), and the file exists, and the 
OPEN requires an OPEN_CONFIRM, it is assumed that the truncate should not 
occur. I think this means the server (state manager) must record that the 
file should be truncated when the OPEN_CONFIRM is sent by the client.

Assuming that is correct, what should happen if the truncate fails (for 
example EACCES)?

Should the state manager cleanup up the pending open state?

What error should be returned? The OPEN_CONFIRM return values are pretty 
limited (no NFS4ERR_EACCESS).

Thanks,
Carl

Carl Burnett
AIX Kernel Architecture - Distributed File Systems
(512) 838-8498, TL 678-8498
(please reply to cburnett@us.ibm.com)

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4