On Tue, May 29, 2012 at 12:10:31PM -0700, Ray Van Dolson wrote: | On Tue, May 29, 2012 at 11:07:57AM -0700, Kevin Glueck wrote: | > which qtree security model are you using? unix? ntfs? | > what's the actual permissions on the file/dir you're trying to | > write to? (acls?) | > | > I've seen an error similar to this when writing over nfs to a | > share that using ntfs qtrees and the permissions were too restrictive | > to allow the user to write... I didn't do a packet trace, so not | > positive it's actually 100% alike, but anecdotally, it sounds | > alike. | > | > Kevin | | Yes, I believe it's NTFS. We shied away from using "mixed" based on | reading here and in some TR documents. Perhaps we should revisit. | | Will review the NTFS permissions to look for any issues. You don't | happen to recall any specific bits you had to adjust? Ours are fairly | permissive by default... | | Thanks, | Ray
Watch whatever your "nobody" user is doing wrt the cifs side of things and all. We don't run cifs shares much, nor use ntfs qtrees at all, so in my case it was an accidental setup of a volume. I'd also recommend steering clear of "mixed" qtrees if at all possible...