samba instead of nfs
in [Setup]
|
Prev: Now, my Debian thinks I have SCSI for my old IDE/ATA drives after installing Kernel 2.6.32-4?
Next: Got it working! First post from inside Damn Small Linux! Needmore help pls
From: Vitus Jensen on 30 Jun 2010 01:34 Hej! As I have to open my server to windows users anyway I would like switch linux clients to cifs from nfs, too. Problem is that on each linux client there are several users who create files on the server and I need the owner of the file kept together with the file. With nfs it's "simple" by keeping uids insync between server and all clients. With cifs the file always gets the login name of client as owner :-( vitus(a)client$ touch as-vitus oe(a)client$ touch as-oe nobody(a)client$ touch as-nobody root(a)client# touch as-root ls -l -rw-r--r-- 1 vitus users 0 30. Jun 07:20 as-root Client: linux 2.6.27, mount.cifs 1.10 Server: reiserfs user_xattr, smbd Version 3.2.8 Is this possible at all? Which part is responsible? xattr, acls? On client mounts or should the server filesystem support something special? acl is currently not enabled on reiserfs mounts. Vitus -- Vitus Jensen, Hannover, Germany, Earth, Universe (current)
From: Nico Kadel-Garcia on 1 Jul 2010 21:38 On Jun 30, 1:34 am, Vitus Jensen <vi...(a)alter-schwede.de> wrote: > Hej! > > As I have to open my server to windows users anyway I would like switch > linux clients to cifs from nfs, too. Problem is that on each linux > client there are several users who create files on the server and I need > the owner of the file kept together with the file. With nfs it's "simple" > by keeping uids insync between server and all clients. With cifs the file > always gets the login name of client as owner :-( > > vitus(a)client$ touch as-vitus > oe(a)client$ touch as-oe > nobody(a)client$ touch as-nobody > root(a)client# touch as-root > > ls -l > -rw-r--r-- 1 vitus users 0 30. Jun 07:20 as-root > > Client: linux 2.6.27, mount.cifs 1.10 > Server: reiserfs user_xattr, smbd Version 3.2.8 > > Is this possible at all? Which part is responsible? xattr, acls? On > client mounts or should the server filesystem support something special? > acl is currently not enabled on reiserfs mounts. ReiserFS is deprecated, for good reason: the primary author, Hans Reiser, is in jail for treating his wife like ReiserFS treats files: making them disappear, pretending it's not his fault, and trying to conceal the evidence . No, I'm not kidding. That said, mapping Linux filesystem permissions to CIFS file access is non-trivial. Is there anyway you can assure that your Windows systems are capable of NFS? Many professional versions of Windows now support NFS.
From: Aragorn on 1 Jul 2010 22:15 On Friday 02 July 2010 03:38 in comp.os.linux.setup, somebody identifying as Nico Kadel-Garcia wrote... > ReiserFS is deprecated, for good reason: the primary author, Hans > Reiser, is in jail for treating his wife like ReiserFS treats files: > making them disappear, pretending it's not his fault, and trying to > conceal the evidence . No, I'm not kidding. Well, technically that's not why reiserfs is deprecated. It was still being maintained by the kernel developers, but only in terms of bugfixes. Nothing new was being added to reiserfs (v3.6) anymore because reiser4 (v4.0) had already officially been released by NameSys, Hans Reiser's software company, albeit that reiser4 was never adopted into the vanilla kernel source tree. I don't know the exact reason for why it wasn't included in the vanilla kernel, but it could be that Linus either deemed it insufficiently tested or that reiser4 was licensed differently. I haven't really checked, but even while Hans Reiser was still on trial, reiserfs (v3.6) was still being maintained. It is possible that this has now come somewhat to a halt, because Reiser put up NameSys for sale during his trial and nobody seemed interested in buying it. (I haven't exactly been following the events, so it's possible that as yet someone has indeed bought up the company.) That said, reiserfs wasn't all that bad, but if it did ever go wrong, then it went wrong very badly, and it lacked a decent toolchain like ext2/3/4 or XFS - I have no real experience with JFS, but I presume it also has a similarly elaborate toolchain, since it is the default filesystem in AIX. Personally, I have however never heard of reiserfs making files disappear, but I did read somewhere that it's rather prone to damaging its own internal trees in the event of an unclean shutdown. For a server - and assuming that the server is connected to a UPS, as it should be - I recommend either XFS or JFS. They are extremely fast and robust. My personal favorite is XFS, but - again - a UPS really *is* a necessity when using XFS, because it aggressively caches and delays write operations. -- *Aragorn* (registered GNU/Linux user #223157)
From: The Natural Philosopher on 2 Jul 2010 04:24 Nico Kadel-Garcia wrote: > On Jun 30, 1:34 am, Vitus Jensen <vi...(a)alter-schwede.de> wrote: >> Hej! >> >> As I have to open my server to windows users anyway I would like switch >> linux clients to cifs from nfs, too. Problem is that on each linux >> client there are several users who create files on the server and I need >> the owner of the file kept together with the file. With nfs it's "simple" >> by keeping uids insync between server and all clients. With cifs the file >> always gets the login name of client as owner :-( >> >> vitus(a)client$ touch as-vitus >> oe(a)client$ touch as-oe >> nobody(a)client$ touch as-nobody >> root(a)client# touch as-root >> >> ls -l >> -rw-r--r-- 1 vitus users 0 30. Jun 07:20 as-root >> >> Client: linux 2.6.27, mount.cifs 1.10 >> Server: reiserfs user_xattr, smbd Version 3.2.8 >> >> Is this possible at all? Which part is responsible? xattr, acls? On >> client mounts or should the server filesystem support something special? >> acl is currently not enabled on reiserfs mounts. > > ReiserFS is deprecated, for good reason: the primary author, Hans > Reiser, is in jail for treating his wife like ReiserFS treats files: > making them disappear, pretending it's not his fault, and trying to > conceal the evidence . No, I'm not kidding. > > That said, mapping Linux filesystem permissions to CIFS file access is > non-trivial. Is there anyway you can assure that your Windows systems > are capable of NFS? Many professional versions of Windows now support > NFS. Its trivial to make the CIFS clients log in as themselves surely? And the samba config files can be used to set permission masks etc.
From: Douglas Mayne on 2 Jul 2010 10:51
On Wed, 30 Jun 2010 07:34:00 +0200, Vitus Jensen wrote: > Hej! > > As I have to open my server to windows users anyway I would like switch > linux clients to cifs from nfs, too. Problem is that on each linux > client there are several users who create files on the server and I need > the owner of the file kept together with the file. With nfs it's > "simple" by keeping uids insync between server and all clients. With > cifs the file always gets the login name of client as owner :-( > > vitus(a)client$ touch as-vitus > oe(a)client$ touch as-oe > nobody(a)client$ touch as-nobody > root(a)client# touch as-root > > ls -l > -rw-r--r-- 1 vitus users 0 30. Jun 07:20 as-root > > Client: linux 2.6.27, mount.cifs 1.10 Server: reiserfs user_xattr, smbd > Version 3.2.8 > > Is this possible at all? Which part is responsible? xattr, acls? On > client mounts or should the server filesystem support something special? > acl is currently not enabled on reiserfs mounts. > > Vitus > I agree with another post on this thread that ReiserFS should get some negative points because the author is currently in prison. Does development go on with others taking over the project? Personally, I have never used ReiserFS; I have always used XFS as my preferred journalling filesystem. I have had it working for a couple of years with Samba and ACLs enabled. Here is a cut/paste version of my last post (2007-12) on this topic (I think): <quote> I have a new smb server. It uses xfs with ACLs. Everyone logs in with their own account, not with a common account as you are doing. I considered using "force user," but decided against it for now. Files created are owned by the user, and are also RW to the group. # stanza from smb.conf [ns] path = /mnt/hde5/network valid users = +smb_users read only = No create mask = 0770 security mask = 0770 directory mask = 0770 directory security mask = 0770 inherit acls = Yes ea support = Yes hide dot files = No map archive = No map readonly = no store dos attributes = Yes oplocks = No level2 oplocks = No # end smb.conf stanza </quote> Sorry, no more time right now to write more. -- Douglas Mayne |