Mar 29, 2020
#1
Hi,
on my system (see signature), I’m running FreeNAS-11.3-U1
with Samba enabled, providing 3 SMB shares to both Windows 10 and macOS Catalina (10.15)
and I have therefore enabled in each share the VFS obejct “fruit” (plus its dependencies catia and streams_xattr).
こんにちは。
私のシステム(署名参照)では、FreeNAS-11.3-U1が動作しています。
を、Samba を有効にして、Windows 10 と macOS Catalina (10.15) の両方に、3つの SMB 共有を提供しています。
そのため、各共有でVFS obejct “fruit” (plus its dependencies catia and streams_xattr)を有効にしています。
From this article https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X
I see that
Apple extensions require support for extended attributes(xattr) – defaults to yes in Samba 4.9+:
ea support = yes
By searching on the forum, I’ve found that by default Samba in FreeNAS has
ea support = yes
store dos attributes = yes
Fascinating (anti-)little document about building a server
I’m posting this here mostly as a memory aid. http://jro.io/nas/ This guy wrote a very detailed document on how he setup his server and it’s mostly well-researched. I was going to ask him if he’d be willing to post it on the forums, since it’s an interesting document to have, but I’d like to…
www.ixsystems.com
and that, since FreeNAS 11.1, in streams_xattr the ea support has been de-coupled from Alternate Data Stream (ADS), it should be safe to set “ea support=no”
CIFS directory browsing slow? Try this
Interesting idea; since the dataset is already case-sensitive, it was just a matter of adding the option to the SMB share config and restarting samba. Making things case-sensitive has the opposite effect in Samba. It slows down performance because the server has to perform multiple lookups per…
www.ixsystems.com
However, when checking the Samba configuration with testparm -v
I see that the shares’ configuration generated by the GUI is disabling ea support
しかし、Sambaの設定をtestparm -vで確認すると
で確認すると、GUIで生成された共有の設定がeaサポートを無効にしていることがわかります。
Code:
# Global parameters
[global]
ea support = Yes
store dos attributes = Yes
[backups]
aio write size = 0
ea support = No
hide dot files = No
mangled names = illegal
path = /mnt/raid1/backups
read only = No
vfs objects = catia zfs_space zfsacl fruit streams_xattr crossrename recycle
nfs4:acedup = merge
nfs4:chown = true
recycle:subdir_mode = 0700
recycle:directory_mode = 0777
recycle:touch = yes
recycle:keepversions = yes
recycle:keeptree = yes
recycle:repository = .recycle/%U
fruit:resource = stream
fruit:metadata = stream
So, long story short:
1) Is ea support = yes still needed if streams_xattr (due to fruit) is enabled?
2) What is the reason why the share configuration is setting ea support = No, overriding the general setting?
というわけで、長くなりましたが
1) streams_xattr (due to fruit) が有効な場合、ea support = yes はまだ必要でしょうか？
2) 共有設定が一般的な設定を上書きして ea support = No を設定している理由は何でしょうか？
Thanks
HPE MicroServer Gen10
Opteron X3216
16 GB RAM ECC
2 x Broadcom BCM5720 (onboard)
1 x SATA 3 Kingston SSD 64 GB (boot only)
2 x SATA 3 WD 2 TB (RAID 1 storage)
francescocariati
Neophyte
Joined
Apr 2, 2018
Messages
6
Apr 6, 2020
#2
up
Thanks in advance
HPE MicroServer Gen10
Opteron X3216
16 GB RAM ECC
2 x Broadcom BCM5720 (onboard)
1 x SATA 3 Kingston SSD 64 GB (boot only)
2 x SATA 3 WD 2 TB (RAID 1 storage)
seanm
Senior Member
Joined
Jun 11, 2018
Messages
526
Apr 7, 2020
#3
I don’t really have any answer for you, but for me, “ea support = No” is indeed set for every share, but it’s not set to anything in my global section.
特に回答はないのですが、私の場合、「ea support = No」は確かにシェアごとに設定されていますが、グローバルセクションには何も設定されていないんです。
コメント