Printable View
I have been playing with Open-E as a NAS but we run a Windows Enviroment and I can't get the file/folder security premissions to work for me. When I try to set only modify or write access to a file or folder it defaults to Full Control, it looks like I can set Read or Full control but not really anything in the middle. Is this a limitation of SAMBA or how Open-E is using SAMBA?
Try setting the security permissions on the share from the Windows server (login as with admin rights) also check the ACL settings in the NAS Resources.
I've had no luck on this either. Good luck, please post your fix if it works right.
Yeah at this time we present an iSCSI lun to our windows file server and use the NAS part of DSS as a Disk based backup location.
No matter what I have tried I can not get the ACLS to work correctly with windows.
it is samba limitation; there are only 3 known rights ... read / write / execute based on user|group|others-everyone.
; in order to utilize all the 13 NTFS permissions; either mount an iSCSI LUN to the server so that it is formatted to NTFS block device or share from a Windows server and define the ACL from the server and then mapped users to the folders.
Good luck.
Thank you that is what I was looking for.
we´ve got now our DSS and I´m playing with it and testing it.Quote:
Originally Posted by cre8tif
the iSCSI function works perfect and now I´m on the NAS side and have the same problems with the permissons.
what do you mean with "share from a Windows server"?
how could I share the NAS voulume from windows?
ok; sorry for the short clarification.
1. NAS with PDC/AD will still only support the RWX - Read Write Execute permission - POSIX limitation. There is no workaround this Samba POSIX limitation.
2. If u really need 2 use the NTFS permission; create an iSCSI target and mount it to your Windows Server 2000/2003 thru an iSCSI initiator.
3. Create a share folder with share permission of read and change for users.
4. Thereafter, define NTFS permission for sub-folders by choosing to inherit or not to inherit them from the top-level folders.
5. If you are planning on migrating from an NTFS drive on your Windows server to the iSCSI volume; download the Microsoft Resource Kit for Windows Server.
6. Use the ROBOCOPY.exe to effectively copy all the permission from local source folder into the iSCSI volume. This will not copy share permission; only NTFS permissions.
7. All you need to do after verifying the copy process is to compare the file/folder size/numbers.
8. Recreate some of the share permissions which should be a piece of cake by copying the former.
9. Unshare the source folder and recreate the same name; after that tell users they are ready to access the files on the larger NTFS volumes on Server 2003 ;)
Linux has had native NTFS support for a while now. Try using openSUSE as an NFS head and share your NTFS filesystem with NFS.
I have not tried this as of yet, but it should work.
-Errol
While I'm on this point, I like the idea of using a NFS head versus DSS. The reason is because you can have incredible redundancy via Heartbeat2, DRBD and multipathd.
Two SLES10 SP1 servers with the latest fuse and ntfsprogs from opensuse.org. Heartbeat2 and NFS backed by Open-E. What more can you ask for?!
We are having the same problem with the posix > windows limitations
It pretty much makes our DSS server useless for NAS SMB mounts
There are some shares that i want to publish using NAS and iscsi is not an option becuase we seperate iscsi traffic on a seperate switch the servers attached to iscsi are not an option for me to do file shares. Also we use iscsi for high throughput applications only.
For simple file shares ie word/excel docs i cant use the NAS function because the permissions just dont suit a windows environment.
Also why should i have to populate all my shares through iscsi for windows permissions to work when i bought a all in one solution that should let me use all the functions.
according to the feature list of DSS V6
Windows Active Directory / Primary Domain Controller Support
Open-E DSS V6 supports Windows Active Directory (AD), Primary Domain Controller (PDC), Lightweight Directory Access Protocol (LDAP) and AD & NIS User-/Group ID synchronization to leverage information about users, groups, systems and other resources stored in the Active Directory. The support of Access Control List (ACL) ensures that access rights of users are automatically taken over from the Domain.
Supported Network Clients and Network File Protocol
Open-E DSS V6 supports the file based protocols CIFS (Common Internet File System)/SMB, NFS (Network File System), FTP (File Transfer Protocol), FTPS and Apple Talk enabling Windows, Linux, Unix and Macintosh clients to share data on the same server.
Our limited experience with DSS as NAS in a Windows environment with a large AD has followed a similar path - struggled with it for a while then gave in & used Windows server/s as the NAS. The posix rights was sort of ok (just), but system hardware instability meant the link between user accounts & directory rights got confused more than once, & meant some stressful work to correct! There is now the ability to back & restore this mapping, and quotas too, but I'm not that confident. In simpler situations (simpler rights) I think the NAS function is just fine.
I'm working in a university which has an Active Directory with 12'000 entries. The ACL (Access control list) form shows all users and groups in a 20 lines window with only up and down arrows to find and select entries among the 12’000 entries. It’s really like looking for a needle in a haystack! This form could greatly be improved by providing a search tool.
Permissions given to a folder using ACL are propagated from the OpenE server to Windows. If you change permissions to a folder on the Windows computer which is using the share, the change is not propagated back to the OpenE server (or taken into account by it) and it is like if nothing was done.
Another weird thing with this interface is that you are automatically propagated to the root of the filesystem each time you apply a new permission to a folder bellow. You have then to go down the filesystem to make another change. Imagine doing this for more than 10 users!
We are aware of the issue this presents with a lot of users, and are working on something in the area for a future release.Quote:
Originally Posted by derochat
DSS is a linux based OS, so it will not operate as if it is a windows controller. To get the behavior you are describing, use a connection to the PDC, or ADS.Quote:
Originally Posted by derochat
Again, this can be managed if using PDC, or ADS. You can also try changed the inherit permissions options.Quote:
Originally Posted by derochat
hope this helps.
Unable to get the back-up and recovery...not even my friend can solve this!!