+++ This bug was initially created as a clone of Bug #496142 +++
In the latest coreutils it attempts to preserve xattrs, and it can lead to very noisy output if the target filesystem does not support xattrs (or, perhaps, does not support selinux xattrs):
root@inode tmp]# mv newdir/ mnt/
mv: setting attributes for `mnt/newdir/file58': Operation not supported
mv: setting attributes for `mnt/newdir/file85': Operation not supported
mv: setting attributes for `mnt/newdir/file68': Operation not supported
mv: setting attributes for `mnt/newdir/file74': Operation not supported
mv: setting attributes for `mnt/newdir/file1': Operation not supported
mv: setting attributes for `mnt/newdir/file69': Operation not supported
mv: setting attributes for `mnt/newdir/file95': Operation not supported
mv: setting attributes for `mnt/newdir/file42': Operation not supported
mv: setting attributes for `mnt/newdir/file77': Operation not supported
mv: setting attributes for `mnt/newdir/file44': Operation not supported
mv: setting attributes for `mnt/newdir/file38': Operation not supported
mv: setting attributes for `mnt/newdir/file36': Operation not supported
mv: setting attributes for `mnt/newdir/file31': Operation not supported
mv: setting attributes for `mnt/newdir/file25': Operation not supported
mv: setting attributes for `mnt/newdir/file57': Operation not supported
mv: setting attributes for `mnt/newdir/file32': Operation not supported
mv: setting attributes for `mnt/newdir/file100': Operation not supported
mv: setting attributes for `mnt/newdir/file89': Operation not supported
.....
mv: setting attributes for `mnt/newdir/file96': Operation not supported
mv: setting attributes for `mnt/newdir': Operation not supported
[root@inode tmp]#
This would happen when copying to a filesystem that does not support selinux, or does not support xattrs - fat, cifs, nfs, mounts with selinux contexts ...
mv /home/myphotos /mnt/vfat-usbstick for example would probably trigger this.
I'm not sure it's worth issuing a warning for every file if the target doesn't support the thing mv is trying to preserve. For that matter maybe mv should stop trying after the first EOPNOTSUPP?
Thanks,
-Eric

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2009-1262.html

Note

You need to
log in
before you can comment on or make changes to this bug.