LinuxQuestions.org - Migrated files are now all read only

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Migrated files are now all read only (https://www.linuxquestions.org/questions/linux-newbie-8/migrated-files-are-now-all-read-only-262847/)

Migrated files are now all read only

I am gleefully switching as much stuff as I can away from windows and in our small office I installed Suse & Samba on a machine to be our storage server. Last nite after copying all my existing files over to samba I discovered that they now are all read only. Specifically the permissions on the files have been changed to Archived. So when I try and open an autocad file I get the msg.

Code:

The file you are trying to open is either in use or locked...

Something along those lines..... My main workstations are XP Pro and I know that sometimes when trading files amongst themselves XP will set it to read only but I havenever seen "archive" before.

Is it possible to change the attributes globally on all files I have copied in?

Is this something that happened to the files once they arrived based on my smb.conf? And can I changed/add something to each folder so all users can modify? I have set up each folder that the files are in to chmod 777.

I am at a loss ....any ideas are much appreciated

Re: Migrated files are now all read only

Quote:

Originally posted by blink_00
I am gleefully switching as much stuff as I can away from windows and in our small office I installed Suse & Samba on a machine to be our storage server. Last nite after copying all my existing files over to samba I discovered that they now are all read only. Specifically the permissions on the files have been changed to Archived. So when I try and open an autocad file I get the msg.

Code:

The file you are trying to open is either in use or locked...

Something along those lines..... My main workstations are XP Pro and I know that sometimes when trading files amongst themselves XP will set it to read only but I havenever seen "archive" before.

Is it possible to change the attributes globally on all files I have copied in?

Is this something that happened to the files once they arrived based on my smb.conf? And can I changed/add something to each folder so all users can modify? I have set up each folder that the files are in to chmod 777.

I am at a loss ....any ideas are much appreciated

You seem to have found one of the more up to date problems (IMO anyway).

XP either pro or home, are usually formatted at NTFS. NTFS partitions usually end up as read only, because write access is still being worked on.

What you might have to do, is repartition, so that you also have a FAT32 partition. You'd then move/migrate the files there, and then you can do read/write stuff.

That seems to be how a lot of people are accomplishig that at the moment - there is stuff for direct write access, but I wouldn't know how stable it is yet

regards

John

So you think it would work for me to create a fat32 partition , copy files there then migrate them to the Linux box. Its strange that they are only labeled Archive and yet thats enough to cause problems. I tried to access & change them from a win2k machine and it has no problems with the permissions. I can read from and save back to the linux box fine.....hmmm . So maybe this is an XP issue??

Folder permissions fixed

Ok.....I solved the challenge. I have been able to acccess any/all the directory folders I had set up in smb.conf but was unable to save/open or change anything from my client machines running either 2000 or XP. After many hours googling I discovered this little gem regarding permission setting for the directory AND the files inside. Simply do a chmod 766 -R /folder (or 777...whatever )the important thing is the -R ...that gives the permission to write/modify the files located inside the directory. Just thought I'd pass that along

Well done blink_00 you're better than me, I'd have still probably been sitting here scratching my ************ ?(ha, I'll leave that up to your imagination :D )

regards

John

blink_00:

To avoid this problem in the future, you may want to change the create mask for your share in smb.conf
The create mask sets the default permissions for a file that is created on a share.

I believe this has nothing to do with NTFS write access, since all operations are going through the smb protocol.

This is from man smb.conf:

Code:

create mask (S)



    When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit-wise 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit not set here will be removed from the modes set on a file when it is created.



    The default value of this parameter removes the 'group' and 'other' write and execute bits from the UNIX modes.



    Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force create mode parameter which is set to 000 by default.



    This parameter does not affect directory modes. See the parameter directory mode for details.



    Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors. If the administrator wishes to enforce a mask on access control lists also, they need to set the security mask.



    Default: create mask = 0744



    Example: create mask = 0775