[OpenIndiana-discuss] file corruption with nfs sharing

[Richard PALO]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quite concerned about a recent problem with NFS sharing under the
latest prestable of OI, in this particular case the server and the LAN
client workstation are both upgraded to
OpenIndiana Build oi_151a3 32-bit (illumos 022f1af9e21c)

the server and the workstation are static ip addresses, both are
listed in /etc/hosts
nfs share looks like zfs/rpool/export/dossiers nfs=() smb=()
nfs:sys=(rw="@192.168.0.0/24:@192.168.1.0/24")
/export/dossiers
Dossiers=/export/dossiers smb=(guestok="true")

from sharemgr

the bug report:
https://www.illumos.org/issues/2644#change-6883

I'd like to track this quickly down to see if I need to rollback or if
there is something I can do to avoid data corruption.

On the server:
$ pfexec sharectl get nfs
servers=16
lockd_listen_backlog=32
lockd_servers=20
lockd_retransmit_timeout=5
grace_period=90
server_versmin=2
server_versmax=4
client_versmin=2
client_versmax=4
server_delegation=on
nfsmapid_domain=
max_connections=-1
protocol=ALL
listen_backlog=32
device=

I have the following ACL on the share directory (now both CIFS and NFS)
$ pfexec /usr/bin/ls -adv <share directory>/
drwxrwxrwx+  8 nobody   nobody     53 avr. 20 10:40 <share directory>/
     0:everyone@:list_directory/read_data/add_file/write_data
         /add_subdirectory/append_data/read_xattr/write_xattr/execute
         /delete_child/read_attributes/write_attributes/delete/read_acl
         /write_acl/write_owner/synchronize:file_inherit/dir_inherit:allow

The file itself seems to have inherited correctly the ACL
$ pfexec /usr/bin/ls -adv <share directory>/<file>.ods
- -rwxrwxrwx+  1 nobody   nobody    104328 avr. 20 09:29 <share
directory>/<file>.ods
     0:everyone@:read_data/write_data/append_data/read_xattr/write_xattr
         /execute/delete_child/read_attributes/write_attributes/delete
         /read_acl/write_acl/write_owner/synchronize:file_inherit
         /dir_inherit:allow

as stated in the problem report, using OpenOffice 3.3, opened the
file, made some substantial changes, closed the file , no problem.

BUT, the next time I opened the file, it was irrecoverably corrupted.
Happen to notice the following in the client workstation"s
/var/adm/messages logfile:
Apr 20 09:29:03 x3200 nfs: [ID 897781 kern.notice] NFS write error on
host smicro: Permission denied.
Apr 20 09:29:03 x3200 nfs: [ID 702911 kern.notice] (file handle:
58b0f1aa 50a83908 27c2000a 0 2a1708 4000a 0 5ee45 0)
Apr 20 09:29:03 x3200 nfs: [ID 897781 kern.notice] NFS write error on
host smicro: Permission denied.
Apr 20 09:29:03 x3200 nfs: [ID 702911 kern.notice] (file handle:
58b0f1aa 50a83908 27c2000a 0 2a1708 4000a 0 5ee45 0)
Apr 20 09:29:03 x3200 nfs: [ID 897781 kern.notice] NFS write error on
host smicro: Permission denied.
Apr 20 09:29:03 x3200 nfs: [ID 702911 kern.notice] (file handle:
58b0f1aa 50a83908 27c2000a 0 2a1708 4000a 0 5ee45 0)
Apr 20 09:29:03 x3200 nfs: [ID 897781 kern.notice] NFS write error on
host smicro: Permission denied.
Apr 20 09:29:03 x3200 nfs: [ID 702911 kern.notice] (file handle:
58b0f1aa 50a83908 27c2000a 0 2a1708 4000a 0 5ee45 0)

Any pointers on how to track this down, or is this more probably a
hint of prestable instability, in which case I need to quickly rollback.

Thanks in advance
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPkkNeAAoJECAB22fHtp272DwH+wctdzoFgwsY/6pJAtZBodMs
kvGTF16ja4gECxeM/hiAzJEP2APUjas1T2glYOw/1Ojj/F0F1ygY8Nv6tFpByJoW
uOnO0/k5793aQ25/o89wos3Kjy3sjtv8itN+RlCbfvtxwzJPbelabLsJ78V49d0h
K7LBz5Tqj3Ybyijc3XTpylDl4zoNa2zNmRPHjUcfMcv1FLxupBg7Cw064x63Ari7
UkxOPPpp0NZGcHOVyqGfDj2SSCNW9d7Bg/Ak54rnkMSbwErF7cz7RiS2uUAEsJJ3
AIWp/JW9YL2sAfcA5SEncDIxV9szkmZ0yfhhKGt3h7uspGkQhBb47tlC7N52CZ4=
=usdU
-----END PGP SIGNATURE-----