Yes, that can happen.
Originally Posted by TnA
The theoretical limit is 10, since that is the number of different digits for a "pfs?:" device name, but in practice this is limited by what the HDD driver was compiled to support. Each simultaneous mount requires separate buffers and data structures etc in IOP memory, which is a strictly limited resource. We only have 2 MB to cover all needs of all IO drivers as well as the needs of LAN servers like those for FTP and HOST protocol.
How many devices, or partitions can be mounted simultanously
Therefore uLE does not assume more than 4 mountpoints simultaneously available.
(A common (and minimum) value for the HDD driver mountpoint limit.)
In old implementations uLE itself never needed more than two, so it was mostly fine for the FTP server to use two as well, though conflicting usage could still occur. And in new implementations this is even more likely if the user has mounted VMC in FileBrowser, as each VMC could be mounted to a different HDD partition, which can in some cases raise the usage of uLE FileBrowser to four simultaneous mountpoints. Two for VMC and two for some other file transfer. This is an extreme and unusual case, but quite possible.
For that extreme case no mountpoints will be left over for the FTP server.
As implied by the above that command will fail as the mountpoint index is higher than the maximum "3".
(that I manually mount it for example to pfs/5/ for FTP-Usage and if I use the filebrowser which mounts the partitions to one of the first then...)?
Yes, and I did say so in my earlier post.
I assume there could be conflicts too, if I mount the same partition in FTP and Filebrowser, but to different mountpoints(??!).
Each partition can only be mounted to one mountpoint at a time.
----- re: avoiding FileBrowser HDD operations during ongoing FTP sessions
Yes. And it is the only way to completely avoid such conflicts.
A good old rule. heh :D
Even having a shared mount index array through an RPC server would not help for the cases where the main program needs to use all available mountpoints differently from the FTP server. The only one who can avoid such conflicts is the user, by limiting his simultaneous operations.
----- re: ESR failures without FMCB init
TBH, I really don't remember if I tried that.
Hm,... You tried ESR-GUI also?
I suppose I should repeat some experiments to make sure of it.
Maybe later today, if I have some time left over...
Best regards: dlanor