Lustre: Failure Getting or Setting Attributes

When using the mv (move) command on fish, you may receive errors similiar to this:

fish2 % mv: getting attribute `wrfout_d05_2013-06-11_12:00:00' of `trusted.lma': Operation not permitted mv: getting attribute `wrfout_d05_2013-06-11_12:00:00' of `trusted.link': Operation not permitted mv: getting attribute `wrfout_d05_2013-06-11_12:00:00' of `trusted.lov': Operation not permitted mv: setting attributes for `/archive/u1/uaf/user/example/201316212/wrfout_d05_2013-06-11_12:00:00': Operation not supported

This is due to a mismatch in software versions between our Lustre file system servers and clients, which unfortunately we are not able to fix at the present time. The errors are harmless and the move operation should complete without any other issues.

Here is a more detailed explanation from one of our staff technicians:

It's due to the way the Lustre clients less than version 1.8.9 deal with the
extended attributes of the Lustre 2.x servers. Fortunately, the file is
moved as you would expect, and there is no issue with the file after
movement, but it does show disconcerting error messages to the end-user.
Instead of moving, if you copy and remove the file from $CENTER, these
errors do not appear... It's only when using the move command on Fish.
The issue is unresolvable so long as Cray has the Lustre clients at 1.8.6
without the appropriate patch included in the build.

For more information, you may view the related Lustre bug report:

Back to Top