[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mv: preserving permissions for `./file': Invalid argument
From: |
Jim Meyering |
Subject: |
Re: mv: preserving permissions for `./file': Invalid argument |
Date: |
Sat, 28 Feb 2009 10:29:50 +0100 |
Richard Leeden wrote:
> Jim Meyering wrote:
>>
>> Thanks for the report.
>> However we'll need more information.
>> For example, what is the type of your destination file system?
>> If it's a local file system, "df -hT ." will tell you.
>> If it's NFS, it'd be good if you could tell us the OS of the server
>> as well as the type of disk it exports.
>>
>> What are the permissions of the source and destination files
>> and the destination directory? I.e., run this after the mv:
>>
>> ls -ld /tmp/a a .
>>
>> Also, please rerun your example under "truss", to see what system
>> calls are used i.e.,
>>
>> rm -f a
>> truss -o log mv /tmp/a .
>>
>> and post the log.
>>
>> Caveat: Solaris 8 and 9 are on the way out, in my mind.
>> I haven't had access to those types of systems for at least
>> three years now, and that's a pretty serious impediment to
>> maintaining portability to them.
>>
>
> Thanks for the reply. And, yes I agree Solaris 8 and 9 are on the way out,
> but unfortunately we're going to be stuck with them at work for some time to
> come yet. :(
>
> Anyway, here's the info you asked for.
> The destintation FS is a local FS: output from df -hT .
>
> Filesystem Type Size Used Avail Use% Mounted on
> /dev/md/dsk/d24
> ufs 481M 209M 225M 49% /usr/home
>
> Full details of all permissions, before and after the move:
>
> root>rm -f a
> root>touch /tmp/a
> root>
> root>ls -ld /tmp /tmp/a . a
> ls: cannot access a: No such file or directory
> drwxr-xr-x 5 rleeden admin 8192 Feb 28 09:05 .
> drwxrwxrwt 11 root sys 4484 Feb 28 09:05 /tmp
> -rw-r--r-- 1 root other 0 Feb 28 09:05 /tmp/a
> root>
> root>mv /tmp/a .
Thanks. One more question.
Does the same thing happen when you do this as a normal user?
I have to admit that this is low priority, so
it may be a week or two before I investigate.
In the mean time, try building without ACL support:
./configure --disable-acl
and see if the "mv" you get from that works better.