Comments on: Home Fileserver: ZFS File Systems

By: Simon

Simon — Tue, 08 Jun 2010 09:23:09 +0000

Glad to hear it worked.

Cheers,
Simon

By: shaky

shaky — Mon, 07 Jun 2010 12:02:35 +0000

I created a new filesystem, set the ACLs per your instructions, copied the files into the new fs and it all worked. Just took 30 hours to do the copy. Luckily I had enough spare space to duplicate.

cheers

By: Simon

Simon — Mon, 07 Jun 2010 11:21:38 +0000

I’ve not seen the problem you mention.
For your old file system, your example shows what looks to be like all permissions allowed for owner, group and everyone.
So perhaps you just had undesirable ACLs setup for this old file system? The fix might be to review what you want and then check it out by cloning the old file system, then setting the ‘right’ file system properties (aclmode, aclinherit etc), on the clone, then resetting the ACLs for each directory and file within the clone.

Another slight possibility is that there’s a problem of zfs version for the old file system, but that sounds less likely than what I mentioned above.

ZFS has pool versions and file system versions.
See here for version information:
http://docs.sun.com/app/docs/doc/819-5461/appendixa-1?a=view

Let me know if you discover anything.

Cheers,
Simon

By: shaky

shaky — Fri, 04 Jun 2010 12:20:42 +0000

It’s something to do with the perms and the old user. If I create a new filesystem, share, user (your fred example) it all works – and I get 45MB/s

So something is up with my old pool permissions.

By: shaky

shaky — Fri, 04 Jun 2010 11:37:17 +0000

It’s strange. This are my perms:

james@dusky:/tank# ls -dV pool
drwxrwxrwx+ 5 james james 8 May 2 21:12 pool
owner@:rwxpdDaARWcCos:fd—–:allow
group@:rwxpdDaARWcCos:fd—–:allow
everyone@:rwxpdDaARWcCos:fd—–:allow

By: shaky

shaky — Fri, 04 Jun 2010 03:02:20 +0000

Very strange – I upgraded to 2009.06 (so much smoother than my previous experiences!)

I’m going to create a new filesystem and try that out.

By: Simon

Simon — Thu, 03 Jun 2010 18:49:49 +0000

Hi Shaky, no not seen that one before. I’m using CIFS shares and using ACLs as per above and haven’t seen this problem before.

Cheers,
Simon

By: shaky

shaky — Tue, 01 Jun 2010 17:09:43 +0000

Does this sound like something you have come across before:

When I mount my ZFS shares to my Mac over NFS – I can list and write. When I mount over CIFS – I can write but not list the current files.

thanks

By: William David Armstrong

William David Armstrong — Thu, 25 Mar 2010 00:09:14 +0000

I resolve this issue configuring in this form :

chmod -R A=\
owner@:rwxpdDaARWcCos:fd—–:allow,\
group@:rwxpdDaARWcCos:fd—–:allow,\
everyone@:-wxpdDaARWcCos:fd—–:allow \
/raid5

I allow everyone for all users, if user is in valid group he can list a directory,

I know this is not a best form to resolve this but a windows office 2007 and 2003 is is working fine now.

By: William David Armstrong

William David Armstrong — Tue, 23 Mar 2010 20:03:12 +0000

I have a estrange behavior on SVN_124 a go to OpenSolaris svn_134. I try set set a simple server for a hybrid MAC and windows XP on same LAN and access a a same server via CIFS and same configurations on your’s manual.

But a have a issue on file is create from windows XP a initial set of attributes and ACL is set
Ok

id finance
uid=104(finance) gid=101(jamute)
groups finance
jamute publico fdocs financ

-rwxrwx—+ 1 finance jamute 49664 mar 23 2010 Ficha_SPOT_ALLIANZ_troca_loc2.xls
owner@:rwxpdDaARWcCos:——I:allow
group@:rwxpdDaARWcCos:——I:allow
everyone@:rwxpdDaARWcCos:——I:deny

Now a get access from Mac OS X 10.5 open a file on Excel:MAC 2008 modify a file and save in same name. the file continue ok attrib’s and acl

-rwxrwx—+ 1 coordena jamute 49692 mar 23 2010 Ficha_SPOT_ALLIANZ_troca_loc2.xls
owner@:rwxpdDaARWcCos:——I:allow
group@:rwxpdDaARWcCos:——I:allow
everyone@:rwxpdDaARWcCos:——I:deny

try access again via Windows XP and modify a file again and save. but now a attributes are vanished and acl continue Ok.

———-+ 1 finance jamute 49975 mar 23 2010 Ficha_SPOT_ALLIANZ_troca_loc2.xls
owner@:rwxpdDaARWcCos:——I:allow
group@:rwxpdDaARWcCos:——I:allow
everyone@:rwxpdDaARWcCos:——I:deny

I can’t access a file from MAC.

always access via CIFS.

a zfs set is same on this manual

===================================================================
raid5 aclmode passthrough local
raid5 aclinherit passthrough local

===================================================================
raid5/Financeiro aclmode passthrough inherited from raid5
raid5/Financeiro aclinherit passthrough inherited from raid5
raid5/Financeiro casesensitivity mixed -
raid5/Financeiro sharesmb name=Financeiro local

By: Simon

Simon — Sun, 31 Jan 2010 21:10:59 +0000

Thanks Christoph. It’s a while back now and I can’t remember, but I think I set “casesensitivity=mixed” when I was setting up the file system that was to be used for a Windows user.

Cheers,
Simon

By: Christoph Jahn

Christoph Jahn — Sat, 30 Jan 2010 07:41:47 +0000

All your ZFS stuff is very nice, thanks for this.

I was just going over this post again, as I am currently changing my file system structure. What strikes me is that only in one place you create the file system with “casesensitivity=mixed”. Is there any particular reason for that?

FYI: It seems that with snv_131 the “set sharesmb=name=xxxxx” is broken.

Cheers,
Christoph

By: Simon

Simon — Sat, 14 Nov 2009 00:48:33 +0000

Thanks Bart.

When you boot your client OS, such as Windows, Mac OS or Linux etc, you need to connect to the shared media file systems using the ‘media’ user.

Cheers,
Simon

By: Bart

Bart — Tue, 10 Nov 2009 12:21:01 +0000

Hi Simon,

Thanks for this great guide for a linux starter like me! I still have one problem: i created a user – like Fred. But everything Fred creates in the media-filesystem is not visible for other users (like wilma), because the files are owned by Fred and the group is also Fred (instead of the media group). How can i change this, so that everything Fred does in the media-filesystem is created with group media ?

Many thanks,
Bart

By: svrocket

svrocket — Thu, 22 Oct 2009 05:50:36 +0000

Simon,

fascinating ACL writeup, it looks daunting. In my shop they did it bass-ackwards and windows is the (normal) SMB server and NFS server. My sun boxes are the dummy nfs clients. I’m thinking of reversing the roles and making opensolaris the cifs/smb server, and nixing the nfs.

But what I wanted to comment on, was “setting ‘copies’ attribute to 2″ ZFS. Dude – zfs snapshot trump copies=x. zfs clones trump snapshots. zfs SEND to another opensolaris server or offsite trumps clones.

ps – your captachas are too hard!

By: Simon

Simon — Thu, 23 Jul 2009 18:32:00 +0000

Hi fyleow,

Thanks for the info. If you mount the shares for (1) tank/home/fred/projects, (2) tank/home/fred/photo & (3) tank/home/fred/video as three separate shares on the client OS then it works fine, at least it works fine for me.

Simon

By: fyleow

fyleow — Thu, 23 Jul 2009 04:53:15 +0000

Hi Simon,

Sorry about that I did a hack job of copy and pasting. It turns out that what I’m describing is a known limitation in ZFS.

If I create a series of file systems like your fred example and navigate to the parent fred file system over the share (/tank/home/fred) I can only have read/write access to that file system. I will still see the mounted child file systems (e.g. /tank/home/fred/projects) as folders but if I try to read/write to them I will get an access denied message.

Anyway this bug report filed explains it much better than I can.

http://bugs.opensolaris.org/view_bug.do?bug_id=6820940

By: Simon

Simon — Sun, 19 Jul 2009 10:21:43 +0000

Hi fyleow,

I updated your original comment with your corrections.

A couple of points:

1. I presume you are using SMB/CIFS protocol from your client computer to connect to your shares, and not the actual Samba software which is a free software re-implementation of SMB/CIFS networking protocol?

2. Also, it appears that the ‘zfs set sharesmb=name=fyleow’ within the two blocks above are identical. I presume this is a typo and you have, in fact, used different names for your shares — e.g.:
zfs set sharesmb=name=fyleow tank/home/fyleow
zfs set sharesmb=name=fyleow_music tank/home/fyleow/music

By: fyleow

fyleow — Sat, 18 Jul 2009 23:33:09 +0000

Whoops a few typos in my post. That should read tank/home/fyleow/music and the chmod on the commands should be /tank/home/fyleow/music on the second set.

By: fyleow

fyleow — Sat, 18 Jul 2009 23:31:14 +0000

Hi Simon,

I set up something in a VM using your guide but I’m having trouble with samba. I use OS X 10.5 to access the shares I have set up which are tank/home/fyleow and tank/home/fyleow/music. I use finder to mount tank/home/fyleow and I can see the music directory, but I cannot read or write to it. In order to read and write to music I have to mount tank/home/fyleow/music separately. Any idea what might be the issue here? I don’t want to have to mount each file system under /tank/home/fyleow individually.

I created the following file systems:

zfs create tank/home
zfs create tank/home/fyleow
zfs create tank/home/fyleow/music

Then I applied the following

zfs set aclinherit=passthrough tank/home/fyleow
zfs set aclmode=passthrough tank/home/fyleow
chmod A=owner@:rwxpdDaARWcCos:fd—–:allow,group@:rwxpdDaARWcCos:fd—–:allow,everyone@:rwxpdDaARWcCos:fd—–:deny /tank/home/fyleow/
chown fyleow:fyleow /tank/home/fyleow
zfs set sharesmb=name=fyleow tank/home/fyleow

zfs set aclinherit=passthrough tank/home/fyleow/music
zfs set aclmode=passthrough tank/home/fyleow/music
chmod A=owner@:rwxpdDaARWcCos:fd—–:allow,group@:rwxpdDaARWcCos:fd—–:allow,everyone@:rwxpdDaARWcCos:fd—–:deny /tank/home/fyleow/music
chown fyleow:fyleow /tank/home/fyleow/music
zfs set sharesmb=name=fyleow tank/home/fyleow/music

By: Simon

Simon — Mon, 06 Jul 2009 14:48:00 +0000

Thanks Brad, you spotted my omission Yes, I forgot to complete that part. I think what I was going to do additionally to the irreplaceable user-created content file system was to set the ‘copies’ attribute to 2, so that ZFS would create two copies of each file stored in this file system to further reduce chance of data loss. Set the copies attribute to the value of 3 for maximum protection. Thanks for pointing that out!

Cheers,
Simon

# zfs set copies=2 tank/home/fred/photo
# zfs set copies=2 tank/home/fred/video
# zfs set copies=2 tank/home/fred/projects

By: Brad

Brad — Sun, 05 Jul 2009 19:35:11 +0000

Simon,

Early in the post you seem to emphasize the relevance of the media filesystems as being replacable and the home filesystems as being irreplacable, but I don’t see any different in their creation except for access controls.

Can you expand on how else they are treated differently, or at least tell me what I’m missing?

Thanks

By: Simon

Simon — Wed, 17 Jun 2009 16:04:14 +0000

Good news and thanks a lot. Yes, the ACL stuff is not trivial and I haven’t managed to find a very informative and simple explanation with practical non-trivial examples yet… soon I hope to dig deeper into that subject…

By: fyleow

fyleow — Wed, 17 Jun 2009 04:54:06 +0000

Thanks Simon, that worked perfectly. I was actually on root but I did ’su -’ instead of just ’su’.

root@opensolaris:~# which ls
/usr/gnu/bin/ls

The ACL stuff is pure greek to me so I think I might stick to the regular permission setup for now. Your blog is a great resource for ZFS. Thanks for posting your experiences with it.

By: Simon

Simon — Mon, 15 Jun 2009 19:28:25 +0000

OK, took a look as I was curious and my earlier comments seem to be true. If you login as a non-root user, and look where ls and chmod are, you'll see that they are being found at /usr/gnu/bin:

simon@blackhole:~$ which ls
/usr/gnu/bin/ls
simon@blackhole:~$ which chmod
/usr/gnu/bin/chmod

Whereas if you login as root, you'll pick up these commands from /usr/bin:

simon@blackhole:~$ su
Password: 
simon@blackhole:~# which ls
/usr/bin/ls
simon@blackhole:~# which chmod
/usr/bin/chmod

Thanks for alerting me to this, I'll have to fix my user's path to use the more useful ones at /usr/bin which are capable of handling NFSv4 ACLs! Anyway, out of the box with the default OpenSolaris 2009.06 installation, as root you will have no problems running the commands listed above. Taking a look at the PATH environment variable for a non-root user we can see that /usr/gnu/bin precedes /usr/bin by default, so I suppose swapping them round should work, with hopefully no strange side-effects... :

simon@blackhole:~$ env | grep ^PATH
PATH=/usr/gnu/bin:/usr/bin:/usr/X11/bin:/usr/sbin:/sbin

And for root, we see this:

# env | grep ^PATH
PATH=/usr/sbin:/usr/bin

So root has no /usr/gnu/bin directory in its PATH.