Samba - new directories created in the disk

[wolfe4656]

You were absolutely right. I had the same issue. I renamed my drive which was Segate Expansion Drive to Segate_Expansion_Drive and it showed up on the Almond+ Saba. Thank You
Dave.

[Roger]

You know, I am really sick of this. No support, we, the clients, are doing the debugging, tests, Q&A, etc.

It seems to wotk rigth but it starts to create directories under directories in a recursive way but only in some directories. My music server could not finish reading the music.

Cīmon guys, I managed to have my Raspberry working with Samba in 30 minutes and with Securify we don't get any answer for months and the software still has a lot of problems. This recursive stuff is not new, it has been here for months and I tought it was solved.

[nonaitall]

CONFIRMED

Using USB 2.0 external HD (powered by USB, not AC) and I am able to stream videos using Plex server inside the house.
I'm very impressed.

This "spaces" in the volume name is not really that big a deal - most file systems don't allow spaces in the volume name anyway.
Is it a bug that should be fixed, yes, but if you're a backer you got a bunny of a deal on the A+.

The Raspberry Pi developer network is much larger than this one is.

[t0dd]

Sorry, I'm with Roger.   I have an NTFS drive that will not show up with the Samba enabled whether the volume name is with a space, a dash, or an underscore with the R70 firmware.

I would be a little more sympathetic if it were some obscure zigbee or z-wave device, but a Samba share is pretty basic.  It's hard to find a mid-range or better router that doesn't do shares.   This should work, and I've sat on my device since October because this doesn't.

I would like a refund OR you can pay me to do your SQA.   I'm not amused.   

 

[Roger]

No comments from Securify ?

Any plans to fix this Samba issue ?

[LGNilsson]

Apologies for the lack of replies, I was away and I guess no-one else had anything to add to this.
We're working on updating Samba to version 3.6.5, it won't make it into R071 as it's too close to release, but it should be in R072.
Hopefully this will help fix a bunch of the issues that everyone's experiencing.

[Roger]

"but it should be in R072"

When is this going to be released ?

[LGNilsson]

I'm afraid I don't have any exact deadlines. We're working on R071 and that'll be the next major release which will include further enhancements to the rules and some other improvements. We didn't want to rush this into a firmware that's about to go into release candidate testing, as that's what happened back with R067 and the Hue support and that was a total mess.