When moving (or cp'ing with --preserver=all) read-only files out of a lustre filesystem, errors are produced as follows

% touch /p/lscratcha/bass6/asdf
% chmod 400 /p/lscratcha/bass6/asdf
% mv /p/lscratcha/bass6/asdf /tmp
mv: setting attribute `lustre.lov' for `lustre.lov': Permission denied
mv: setting attribute `lustre.lov' for `lustre.lov': Permission denied

This isn't really a bug, but rather an unfortunate consequence of the design decision to use the 'lustre' namespace for extended attributes. If Lustre instead used the conventional 'system' namespace then the utilities wouldn't try to preserve them and the errors would be avoided. While harmless, the errors do cause some alarm to users who then wonder if their files have been corrupted. It would be nice to handle this more gracefully in future designs.