SMB2FS volume name query

Hi there,

I wasn't sure which forum to put this in, so hopefully it is okay in the Amiga General Forum.

I've installed SMB2FS, set up the DOSDriver and everything is working fine with connecting to my NAS drive. However, I would like to name the volume to something like "Network Drive", but I can't figure out how to have a name that includes spaces.

The DOSDriver has an entry something like this:



How can I include a volume name with spaces in it?

Kind regards,

Francis

@dfstudios

if you a tlking about "smb2-handler" then here is my mount file:



EDIT: ooops, you want a blank space on your name? Maybe it doesn't support space. Or try to enclose the vol name between *" or '"

something like:

@jabirulo

Yes, it's the smb2-handler I'm mounting.

I had already tried what you suggested amongst other things, but I wasn't able to get them to work. I did however just find a solution which was to remove the startup section from the SMB2 DOS driver file and include it as part of the Mount command, something like this:



Kind regards,

Francis

@dfstudios

I know this is not exactly what you are looking for as an answer (Network folder with spaces) but I wanted to show you briefly how I did it.

The network share should only be available when I really need it, so I removed the handler, gave it an icon and put it in the dock. As soon as I need the network folder I just start it from AmiDock which works really well. With "dismount smb2:" I can then log the whole thing off again.



The transfer rates are about max 2.5 MB/sec, more is not possible?

@Maijestro

I did consider having the handler started from the dock, but I prefer it being started at boot time.

Quote:

I'm getting ~15 MB/s for copying from my NAS drive and ~17 MB/s copying to the NAS drive:



This was copying a file that was >1 GB. If I'm copying a lot of small files, it can be quite a bit slower.

For comparison, I can get more than 100 MB/s transferring files between my PC and the NAS drive. I don't have my Mac configured for using the NAS yet.

I'm using the A1222eth.device driver. I don't know what difference using the P1022eth.device driver would have.

Kind regards,

Francis

EDIT: Out of curiousity, I've just tried the P1022eth.device driver doing the same test as before:



Although the max. upload speed is about the same, the max. download speed is seeing a significant improvement at ~22 MB/s. I wasn't expecting there to be as much of a difference as this.

@dfstudios
Quote:According to the sources in https://github.com/salass00/smb2fs/blob/master/src/main.c, which removes the first and last " from startup and then uses IDOS->ReadArgs(), using something likeorshould work.

@joerg

I've tried this, but I just get errors saying things like "VOLUME" is not a valid keyword.

Kind regards,

Francis

@dfstudios

These are amazing values that you receive. And yes, the P1022eth.device driver is a bit faster than the A1222eth.device driver, but also a bit more prone to crashing in my tests.

I myself do not use a NAS drive but have only provided a shared folder under MacOs which I mount or make available with smb2fs on my A1222 and here only max 3MB/sec are possible or maybe I have done something wrong. Everything is directly connected via network cable, no WIFI.

@dfstudios

iirc it doesn't work when = is missing

works here, albeit in a mount file

While smb2fs does not have any problem with double-quote characters being used inside the startup string, it appears that the mount command does which I find strange given that it doesn't even bother to remove the surrounding quote characters before passing the string to smb2fs.

I will have to see if mount allows some way to escape the quotes and if not see about allowing the quotes to be written some way (f.i. as two single quotes).

@salass00
If it's using the standard dos.library functions (ReadArgs(), ReadLineItem(), ...) something likeshould work and set the STARTUP string to.

@joerg

I tried using asterisk (*") and also backslash (\") to escape the quotes but neither helped.

@MaijestroQuote:
I'm curious as to what tests have you done that cause the P1022eth.device driver to crash, or is it just general usage you've noticed this? I've been using it in place of the A1222eth.device driver for a few days now and haven't noticed any difference in that regard.

The only issue I have noticed with the P1022eth.device is if I have both the ethernet ports active then I get an error message on boot-up, something about allocating an IP address of 0.0.0.0. I haven't looked into why this happens yet and have opted to disable the second ethernet port for now. Despite the error message, when I do have both ports active with the P1022eth.device driver I seem to be able to use both of them whereas I only seem to be able to use one with the A1222eth.device driver.

Overall I've noticed a big difference using the P1022eth.device driver. My NAS drive appears on the Workbench in less than a second after booting up. Previously it would be about 20-30 seconds before it would appear with the A1222eth.device driver. I've also noticed that things like AmiUpdate startup a lot faster too.

Kind regards,

Francis

@dfstudios

I have opened an extra thread for this. Yes, the p1022 driver is also much faster for my Internet/SMB2 connections.

I also don't use any unusual setup that could cause errors. The A1222 is connected directly to my router via unit 1 network port and that's all. This is a normal usage.

The version I am using is p1022eth.device (53.3)