Pnfs Release Notes 3.1.9
News
Compatibility
No problem coming from 3.1.3 or later. For earlier versions consult
V3.1.3.
BUT all binaries must be 3.1.9.
Bug Fixes
File name length
File names and link names may now have up to 199 characters without the
special pnfs characters ".(...". This is not true for
directory names. Directory names are limited to 199 characters,
pnfs specials included.
Removing level files
When removing special pnfs level files, the file itself wasn't changed
but the contents of the different levels were written into the
trash directories as if the master (level 0) had been removed.
This caused the backend HSM to remove the file from tape without
changing the pnfs filesystem entry. (very nasty problem).
Has been fixed.
Modifications for dCache compatibility
Some pnfs special commands modify file attributes like filesize or
uid/gid by pnfsId after the object has been created. Unfortunately
the solaris nfs clients send a nfs command setting the group id
after doing the required operation to the id of the sender of the
command, which in terms of the dCache is wrong because the cache
always is running as root. The oberved effect was that after
successfully creating a file with the correct uid/gid of the
user, the file suddenly changed to the gid to 1 or 0 as soon as the
dCache has set the correct filesize. Something similiar happens if
the dCache has to create the file entry. It will do so as root and
later on uses a special pnfs command to change the uid/gid.
While the uid always changed sucessfully the gid never actually
changed if the dCache PnfsManager has been running on solaris machines.
Has been fixed.
Security preparation
Disabling remote remove and move operations
Pnfs now allows to block the remove resp. the move operation
on directory bases. For directories mark as non remove/move
these operations are switched off. This feature is intended to soften
the non existing nfs2/3 security mechanisms. All other nfs operations
(e.g. create, chmod, setattr) are not affected.
See Enhanced security
for more information.
Preparing dCache strong security access
In order to allow a smooth migration from the current nfs2/3 based
security mechanism to a more enhanced one (krb5 or ssl)
v3.1.9 now provides the possiblity to declare directories
as protected. Protected directories can only be modified
by trusted hosts with a trust level of at least 14.
(/pnfs/fs/admin/etc/exports/trusted/...).
It is assumed that all pnfs operations on these directories are done
through secure channels an not via the nfs protocol.
See Enhanced security
for more information.