This discussion is locked
Skroo

Q: Sticky, recurring permission problem

I've got 5 edit rooms talking to an Xsan with roughly 15Tb of disk space. One of the edit machines died on me and needed an OS and software reinstall. I rebuilt the machine and brought it back online with the SAN. A few days later, editors were noticing they couldn't make changes to directories that were created in other edit booths. In addition, they would get errors that files were locked. You can force a recursive perm change in the finder that lets you save or delete, but it doesn't stick.

 

I noticed in the Xsan Admin on one of the MDCs that this edit booth was showing up in the Computer list mulitple times, and it kept multiplying while I watched (hit 22 at one point). I removed the computer from the Xsan entirely and then re-attached it. This fixed the permission error ... for a while. Now it's happening all over again. In addition, now one project created in an entirely different booth is having issues. An editor reports he created a project, was working on it, and got a permission error when he tried to save the file he already had open and had created in that booth.

 

I feels like there are two permission layers I'm not really understanding here, and one of them is taking precidence and overwriting the other. The machine level perm seems to be getting overwritten with something else, maybe on the SAN side?

 

This was all set up years before I started working here, but the config doesn't seem overly complicated. There's one disk pool that 5 edit booths are supposed to have full access to. No quotas, and a simple ACL that gives all but admin access to everyone in the Editor group (which everyone is a member of).

 

Would it make sense or be safe to just make a new ACL with full access for Everyone?

Xsan Server, Mac OS X (10.5.8)

Posted on Feb 28, 2013 8:51 AM