NAS²: Less Redundant With A Rant

It didn’t take long for me to have some major issues with the Remote² storage setup. So I cleaned some things up and wound up getting pissed off enough I’m going to go on a rant.

Please stop using open-source projects as a thin veil for your donationware.

So this rant goes back about two days. I had decided to install Debian on to my Seagate PersonalCloud in an attempt to make it an iSCSI target for the NAS VM I had at the other end. While I did get it working, the performance was crap. I got told the drive I had probably sucked for the type of stuff iSCSI wanted to do…and came to that conclusion myself. I got rid of all the iSCSI stuff, repartitioned it as a standard drive, and set up NFS between the VMs.

It sucked. It still sucked. I’ll tell you right now that part of my problem is I never babysat the initial load of data to see how fast it went and most of it was done incrementally in “the background”. Most of what I saw was yanking data off the drive. To make that long story short; I was seeing the actual speeds for the first time due to the fact I was pulling and pushing almost 2TB of data en masse for the first time.

Anyway…on my journey I came across this “vfdw-sl” (plugout.net if you want to attempt to read anything by those assholes) thing that has angered me more than the corrupted data I’m finding on my drives. It’s an “alternate firmware” for a couple of NAS devices, with the PersonalCloud being one. I decided to install it because I thought…maybe it might be more optimized than vanilla Debian if Seagate did something funky.

Well…this is where the problems started; because the first problem I had was I couldn’t flip to Samba 4 and disable CIFS1 sharing. In fact I had to activate the legacy shit in Win10 and deal with it’s pathetic performance. There were also a number of things that didn’t seem to work. I posted on the forum; set up an NFS share; and got on with restoring data. It took me about 7 hours to copy the 1.8TB of data off the drive to start with. It took me about 3 hours to upload the first 450 gigs to the VM; then another 7 hours for rsync to push it over NFS. Then there were permissions errors…other stuff…I wasn’t in the best mood. Then I went back to that forum.

Samba 4 support requires a donation.

What the literal fuck? I have to “donate” to activate a newer version of a component? I have to donate to activate plugin support too? This angers me. It angers me because I think it’s bullshit. The point of donations is building something, asking for nothing in return, and having someone appreciate you so much they want to give you money. Giving me a functionally limited product…and telling me I get full functionality if I “donate”…that is not a donation. At that point, I’m not donating money. I am paying. I am paying to activate features that shouldn’t be charged for.

No sir. A donation is something I give because I enjoy something and/or I support the cause. I donate to charities to do good work, I donate to open-source projects because I’ve gotten real use out of them.

I do not donate to activate features. I do not donate to activate features on a project that has no website, requires forum registration to even read about it, uses multi-part RAR downloads as a distribution, and further adds a password to make the installer run that’s “for security”. I don’t expect a lot of professionalism with open-source; but you do manage to find a way to drop below whatever bar I’ve set. I will pay for support. I will pay for things related to the project. But forcing me to use outdated software unless I “donate” without even knowing if it’s going to work?

It’s not a donation; you’re selling a product. I don’t pay for open-source software. While what you’re doing is probably not against the licenses, and I’m sure there are loads of people who disagree with me; whatever. That’s how I feel about it, and I don’t give a shit if you disagree.


Anyway….I wound up taking the original instructions I used for Debian 9 and found they had all the same files for Debian 10. The plain vanilla install is doing better performance-wise than vfdw-sl “free” firmware. I bridged the interfaces together on the NAS VM so the other VMs can talk directly to the NFS share over its internal network, with the NAS machine largely just handling Samba. It’s…a little better. The speed tanks when you get a bunch of small files.