Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NasMounts config.json missing 'Path' variable #104

Closed
ecto1a2003 opened this issue Nov 26, 2015 · 14 comments
Closed

NasMounts config.json missing 'Path' variable #104

ecto1a2003 opened this issue Nov 26, 2015 · 14 comments

Comments

@ecto1a2003
Copy link

the 'Name' is used as a path leading to mounts that are multiple folders deep. for example 'e/music' is the path to the share but the mount folder is created with the same path

@balbuze
Copy link
Contributor

balbuze commented Nov 26, 2015

yep it's a known problem. Name is used as path... you can edit config.json to correct it, waiting for a fix.

@volumio
Copy link
Owner

volumio commented Nov 27, 2015

Yep, I accept suggestion on how the input fields should be named, and how many of them ...

@balbuze
Copy link
Contributor

balbuze commented Dec 30, 2015

1 - There is still a problem mounting nfs share : name is used as path.
2 -And it is not possible to mount the same folder once with cifs, once with nfs (to compare cpu use because cifs seems use up to 3% with a rpi2) because the mount path cannot be define properly ( trough webUI)

@mpasteur
Copy link
Contributor

mpasteur commented Jan 8, 2016

For me we should have :

  • an host (IP adress or hostname) eg : 192.168.0.10 or mynas
  • a path which is relative to the host : mp3/classical
  • a name - fixed by user to easily find their shares : NAS1, NAS2 ...
  • maybe a login /password

did i miss something ? i can work on this this wek-end i think.. (mostly with NFS i don't know if i can mount a cifs share to test)

@balbuze
Copy link
Contributor

balbuze commented Jan 12, 2016

With the last built (from today 12/01/16) I think that network drive configuration is not clear. With cifs files, it's rather easy even if the name of the share and the path should be separate. With nfs same thing but path is much more complicated.
How I see the configuration window :

  • name ( it appears in music library) ex : Rock
  • ip ex : 192.168.0.17
  • path ex : /mnt/HD/HD_a2/musique
  • advanced setting (as it already exists)
    A other point, when the config is edited, previous setting does not appear.

@balbuze
Copy link
Contributor

balbuze commented Jan 12, 2016

Mpasteur I read your comment after I post...

@mpasteur
Copy link
Contributor

no problem. If you have some time to test my PR i would be glad to have some feedbacks...

@balbuze
Copy link
Contributor

balbuze commented Jan 13, 2016

I'll try tonight. But I see a lot of activities !

@balbuze
Copy link
Contributor

balbuze commented Jan 13, 2016

@mpasteur
There is something I don't understand, with your last PR I see no difference. Maybe I miss something but I thought you add field to configure as you wrote above

@volumio
Copy link
Owner

volumio commented Jan 13, 2016

You need to update both the UI and the Backend, plus you need to delete /data/configuration and reboot

@balbuze
Copy link
Contributor

balbuze commented Jan 15, 2016

Hello,
I have tested the PR from mpasteur. For me, it's good, understandable settings etc. Some minor improvements : window is not refreshed when adding or removing share. We should disallow the use of space in name as it use to create the mount point and does not work.

@ecto1a2003
Copy link
Author

i think im running the latest build and i dont see an option in the ui for path, how do i update both the backend and the ui.

@ecto1a2003
Copy link
Author

... and it just magically fixed itself. weird?

@balbuze
Copy link
Contributor

balbuze commented Jan 17, 2016

@ecto1a2003 you'll find some useful information here : https://gitter.im/volumio/Volumio2

@volumio volumio closed this as completed Jan 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants