1 |
On 27/08/2013 21:24, joost@××××××××.org wrote: |
2 |
> Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
3 |
> |
4 |
> On 27/08/2013 13:36, Tanstaafl wrote: |
5 |
> |
6 |
> On 2013-08-26 2:23 AM, Alan McKinnon <alan.mckinnon@×××××.com> |
7 |
> wrote: |
8 |
> |
9 |
> I run it on my NASes, and the thing that really sold me was |
10 |
> what it lets |
11 |
> me as the admin do: |
12 |
> |
13 |
> I get all the benefits of directories with none of the |
14 |
> downsides. |
15 |
> I get all the benefits of mount points with none of the |
16 |
> downsides. |
17 |
> I get all the benefits of discrete filesystems with none of the |
18 |
> downsides. |
19 |
> |
20 |
> Like you say, a truly modern fs built for modern needs. |
21 |
> |
22 |
> |
23 |
> Are these home-built NAS's running FreeBSD (or maybe FreeNAS)? Or |
24 |
> TrueNAS or Nexenta boxes? |
25 |
> |
26 |
> I'm wondering what the best way would be to get something set up |
27 |
> for ZFS |
28 |
> file storage. I have some older servers that I can use, so was |
29 |
> leaning |
30 |
> toward FreeNAS... |
31 |
> |
32 |
> |
33 |
> |
34 |
> Mine are HP mini-servers (the cube shaped ones) with 4 SATA bays running |
35 |
> FreeNAS 8.0.something. |
36 |
> |
37 |
> Dunno if you've worked with FreeNAS before, but it's literally a case of |
38 |
> write the image to USB or flash storage and boot off it. Then play. |
39 |
> |
40 |
> You will need to be able to boot off a USB stick, CF card or similar, |
41 |
> FreeNAS uses an entire drive for it's system partition and it's a shame |
42 |
> to waste a whole high-capacity disk just for a 2G system image |
43 |
> |
44 |
> |
45 |
> |
46 |
> Alan. |
47 |
> |
48 |
> How is the security settings on the shares now? |
49 |
> |
50 |
> I had issues when accessing through NFS and CIFS simultaneously where |
51 |
> files written over NFS had to have the permissions altered before they |
52 |
> were accessible over CIFS. |
53 |
|
54 |
I've never run into this situation myself, my shares are either accessed |
55 |
via cfs or via nfs, but never both at the same time. |
56 |
|
57 |
The permissions issue is an artifact of how NFS works. Sun designed it |
58 |
to deliver entire filesystems over the network (most often /usr and-or |
59 |
/home) to trusted clients. "trusted" being the operative word. To get |
60 |
Unix permissions to work, the uid on the share and client have to match |
61 |
- that's why we also have NIS - but I've never seen NIS actually used |
62 |
anywhere, so UIDs tend to be a mix 'n match and almost always devolves |
63 |
into "full access" to get it to work. |
64 |
|
65 |
CIFS work different, it auths users by username and supports per-field |
66 |
access control. That's how that protocol works. |
67 |
|
68 |
There is no known way to fix NFS v2 & v3 in a mixed network and still |
69 |
stay sane. NFS v4 does a good job but it's not NFS v3 :-) |
70 |
|
71 |
it's common for NAS vendors to recommend you not try share the same |
72 |
files over CIFS and NFS, especially if write access is involced. |
73 |
|
74 |
|
75 |
|
76 |
> |
77 |
> Other issue I had was inability to have users only being able to access |
78 |
> files they were allowed to. With CIFS it sort of worked. But with NFS I |
79 |
> had full access to all files. |
80 |
> |
81 |
> That is the reason why I setup my NAS manually using Gentoo. |
82 |
> |
83 |
> -- |
84 |
> Joost |
85 |
> -- |
86 |
> Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
87 |
|
88 |
|
89 |
-- |
90 |
Alan McKinnon |
91 |
alan.mckinnon@×××××.com |