Pourko

You can move this thead to the proper place then.

A somewhat related thought... It puzzles me that the md driver was made to work on partitions. Feels like it could have been more cleanly implemented if it worked with the raw disks instead, agnostic about partitions.

Over the years I have always known that, should such an occasion arise, I can always mount (ro) any of my data disks in a different linux computer. Yesterday I actually needed to do just that, and to my surprise, I was not able to do it: # mount -t xfs -o ro /dev/sdc1 /tmp/sdc1/ mount: /tmp/sdc1: mount(2) system call failed: Function not implemented. # tail /var/log/syslog Jun 30 00:08:05 ToyBox kernel: XFS (sdc1): device supports 4096 byte sectors (not 512) # blockdev --report /dev/sdc* RO RA SSZ BSZ StartSec Size Device rw 256 4096 4096 0 16000900661248 /dev/sdc rw 256 4096 4096 64 16000900608000 /dev/sdc1 Curiously, I noticed that the md devices are being reported as 512-byte sector deivces, and maybe that played a role in how the xfs file system was created on them: # blockdev --report /dev/md* RO RA SSZ BSZ StartSec Size Device rw 256 512 512 0 16000900608000 /dev/md1 rw 256 512 512 0 16000900608000 /dev/md2 So, is that a bug or a feature? I am wondering, how can such misrepresentation possibly be good for performance? And, are we no longer able to mount a data disk outside our unraid server? (For me, that was a big selling point back when I first learned about Unraid.) Any suggestions?

By all means, go fund yourself.

And 10 years later I will still not ike it.

Do you want to try disabling ACL in Samba config on the server? Add that line in the [global] section of /boot/config/smb-extra.conf nt acl support = No Restart Samba. Re-run your speed tests. Let us know.

I don't really get what this fuss is all about "supporting" wireless. The wheel has already been invented you know. So, a month ago, I blindly picked up a bunch of used wifi adapters from a garage sale. Having never played with wifi, I was curious to see what I can do with them on my unraid test-server. Turned out it was no big deal. What I did was, I enabled their drivers in the kernel .config, and recompiled the kernel. Then downloaded one little firmware file, installed a couple of packages from slackware.org, and everything was up and running. All and all, with googling and stuff, it took me about a day. As we speek, my Unraid test-server is running as a Wireless Access Point, with a separate smbd process configured to listen only on the wifi interface. Fun! Just a little note: I have modified all the regular Unraid services (sshd, smbd, nginx, etc) to only listen on my admin-only ethGreen ethernet interface, so at this point, no service other than that dedicated samba daemon is listening on the wifi interface. Also, for now, this box is not acting as a gateway, it's not forwarding any internet packets. May decide to do that later, after playing some more with this thing, and after setting up some sane iptables rules.