![]() 1 x Kingston UV400 120GB SSD - boot drive (hit the 3D NAND/TRIM bug with the original WD green selection, failing scrub and showing as corrupted OS files) Decided to go with no mirror and use the config backup script.2 x WD Green 3D NAND (120GB, 2.5") - Boot drives (maybe mess around trying out the thread to put swap here too link).1 x ASUS Z10PA-D8 (LGA 2011-v3, Intel C612 PCH, ATX) - Dual socket MoBo.# Some Wi-Fi networks advertise faster speeds than the connected wired network.Īiming to mostly replicate the build from (with some mods, hopefully around about as good as that link) # To disable multichannel support completely uncomment the next line # SMB configuration for macOS 11.3 Synology I also found the following macOS smb client settings to assist: Username map = /usr/local/etc/smbusername.map Nsupdate command = /usr/local/bin/samba-nsupdate -g Running testparm in the shell with the above produces: I'm wondering if there's enough interest in the TrueNAS community to warrant achieving a good set of configurations options for macOS clients through testing, with an idea towards establishing a recommended set of values that are considered "macOS advisable" for General file sharing and Large file sharing using Gigabit and 10Gigabit networks, so that people can build upon from there. But I'm not sure how many are actually useful, deprecated or now even detrimental to performance.Īdditionally the vfs objects attributes is one area that I personally am still not really on top of and would like to explore further. I've read a lot of the SAMBA documentation in an effort to better understand these which has been invaluable. Vfs objects=fruit streams_xattr zfsacl catia ixnas preopen Regarding setting up SMB shares (being macOS's default protocol), I've seen many options listed all over the web such as: I've got the Qnap TS 119 with Version 3.1.2 build 1014T.Just wondering if anyone is willing to help identify a good/sound set of configuration options for a predominantly macOS client environment for TrueNAS on reasonably "okay/average" hardware that people may have lying around. So i hope this issue will be fixed with the next firmware Release from Qnap. ![]() I think there will be also Problemes between Snow Leopard and Leopard, when you move a File over Netatalk (Qnap share). The Datafile and the AppleDouble (in AppleDouble). When delete all File and then Copy the same File with Leopard (also downloaded form the Internet), you only get two files: The Datafile, the resource fork, the appleDouble for the datafile and the appleDouble for the resource fork (both in. The vetofile fix is a quick fix for that, but perhaps not the best solution, because Snow Leopard and netatalk are creating 4 File on the Filesystem: So I think this issue will be fixed with a coming release. There is an threat about that in the netatalk maillinglist. IMac:Public manfred$ xattr TheUnarchiver2.1.zip IMac:Downloads manfred$ xattr TheUnarchiver2.1.zip It tries to store extra Information in the. But it seems that Netatalk has a Probleme with Snow Leopard (or Snow Leopard with Netatalk). Normally they should not appear because Netatalk (the afpd Daemon) stores them under the AppleDouble Directory. These Files are Resource Forks from Mac OS X. So here is what i found about that issue:
0 Comments
Leave a Reply. |