Windows Attributes, Archive checked? Read-only checked?

Status
Not open for further replies.

JayG30

Contributor
Joined
Jun 26, 2013
Messages
158
I'm trying to figure out what might have caused this change or if something might be wrong. I have multiple CIFS shares and permissions on the dataset are handled using Windows ACL's. I'm still on version 9.2.1.7 (updating will have to wait until the new hardware is up and running).

First thing is that I noticed that every file has the "Archive" attribute checked when right clicking -> Properties. I'm not sure why that is or if it was always like that. I don't seem to remember it.

Secondly, one of the folders (not even the whole dataset) also had "Read Only" checked as well. I found this out because a user was attempting to open a file, make changes, and save it and of course they couldn't. My guess is a user checked this option thinking that was the best way to make something "read only" to users when the way we handle it is with file/folder permissions (Everyone has read-only, a group was read/write). However is there anything freenas or I could have done to cause this to occur and I'm just unaware of it?

Thanks.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
I would not be surprised if this was a Samba quirk.
 

JayG30

Contributor
Joined
Jun 26, 2013
Messages
158
Yea it seems that Archive doesn't really "do" anything here. @cyberjock has a post here about disabling these attributes to "speed up" CIFS browsing. I don't really have a speed issue though. But he does mention that the archive attribute can sometimes get set by older backup software, but I'm not doing that (at least not to my knowledge). The only thing I'm doing now is ZFS replication. The read only attribute I really think was a user since it wasn't set on a whole dataset or a whole pool. Anyway as cyberjock said in that thread, I can disable them by putting

Code:
ea support = no
store dos attributes = no
map archive = no
map hidden = no
map readonly = no
map system = no


in the CIFS parameters. That does work. I have no need for "read-only" attributes so I might do that.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
The only reason I don't disable them is that they haven't bothered me yet.

They are pretty much archaic, as is anything that relies on them.
 
Status
Not open for further replies.
Top