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

hdd_replacement not working if autofs is used #337

Open
markuschen opened this issue Jan 5, 2019 · 2 comments
Open

hdd_replacement not working if autofs is used #337

markuschen opened this issue Jan 5, 2019 · 2 comments

Comments

@markuschen
Copy link

This is a mount point created by NetworkBrowser in /etc/enigma2/automounts.xml:

<autofs>
 <nfs>
  <mount>
   <active>True</active>
   <hdd_replacement>True</hdd_replacement>
   <ip>192.168.178.2</ip>
   <sharename>record</sharename>
   <sharedir>record</sharedir>
   <options>rw,nolock,tcp,rsize=32768,wsize=32768</options>
  </mount>
 </nfs>
</autofs>

The important thing here is hdd_replacement = true, so the mounted directory '/media/autofs/record' should replace the internal hdd path '/media/hdd'.
Directory '/media/hdd' is created before AutoMount.py starts and with this configuration the replacement of '/media/hdd' is not working.

@markuschen
Copy link
Author

Fix in pull #338

@markuschen markuschen mentioned this issue Jan 5, 2019
@markuschen
Copy link
Author

This is only a partial fix, because folders 'movie' and 'timeshift' are missing. These folders were created before AutoMount.py is running. A recording fails with 'write error, hdd full?'

Also, if only the gui is restarted (or init 4 + 3) the 'mount --bind' is running more than once. A 'umount' before could be the clou.

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

1 participant