I am dual booting win10 and either Opensuse or Ubuntu if I can solve this problem. I have an NTFS partition labeled "K" where I keep all my docs and such. In linux I am attempting to bind my /home/michael/Documents to K Documents folder with this command

/run/media/michael/K/Documents /home/michael/Documents none bind
or

/run/media/michael/K/Documents /home/michael/Documents ntfs-3g rbind,user,umask=0775,defaults 0 0

This works great until I reboot and find the Linux has created "K1" and That is where all my files are. When I re edit fstab to reflect this, linux simply creates "K2" and so on....

Can someone help? Thanks

I found nothing in your reply answering my question. When I BIND /media/michael/K/Documents to home/michael/Documents in fstab it works great. Upon reboot linux has created a /media/michael/K1 where my Documents now reside. /media/michael/K is empty. Re-editing fstab to reflect the change from /media/michael/K to /media/michael/K1 works great until reboot when there is now a /media/michael/K2 where my Documents are. This process repeats over and over. I have tried the following as my fstab entries with the same results

/media/michael/K/Documents /home/michael/Documents none bind
or
/media/michael/K/Documents /home/michael/Documents none bind 0 0
or
/media/michael/K/Documents /home/michael/Documents ntfs-3g rbind,user,umask=0775,defaults 0 0

How can I prevent this problem?

Thanks

I didn't write that paper -- just shared it with you.

the way this reads is

the orginal is moved to somewhere else and name changed to var_log

then another directory is created where it use to be using the same name
the orginal is bound to the new empty directory.
in fstab the orginal with a new name is first, and the new empty dir with old name is second, then bound to it.

I have no idea what is what on yours...

but that is the logic of it. I did not create this system, don't even use that.

just trying to help

OK FINE -- you talked me into it, now let me see if I can figure this out for you on the fly ...

/run/media/michael/K/Documents /home/michael/Documents ntfs-3g rbind,user,umask=0775,defaults 0 0

I don't have the exact same set up as you but, I just created a directory then mounted a directory into it between two seperate HDD's using bind, rebooted and no problems. it is the mount points that are relevant, not the hard drives.

therefore your format is messed up, it is something else that is messing up your formated statment in fstab.

This is my fstab... (in part)


this is yours..
your other mount is ntfs, no need for umask permissons its ntfs. Linux does not recognize permission settings on ntfs format. Linux does not use them, try doing it like this instead.

First mount your whole partition first in fstab, then off of that mount, do like I did.

First go command line commando and type this:

blkid first to get your /dev/sdxx, now open fstab then add it. mounting it to whatever point you chooise to. Not your Documents Dir. that's next, Preferably mount it off of a directory on /

Either:
/media
/tmp
or what ever you create. then create a subDir within it.in case you ever want to use it to mount something else. it will already be there, Then add it to your Fstab.

when you have your entire hdd mount entry in fstab, and saved.Then issue this command . Then open up a filemanager or command line to find it. Get the Absloute path off your mount point like I did. Now add that to your fstab, mounting it to your home/Docs directory.

example:
Now hit your up arrow and issue sudo mount -a again. then check it, then reboot, and re--check it ..

if that does not work then put that "none" back in there and remove the ntfs-3g and see if it works. if not then add the ntfs-3g again. I think that the none will surfice, as it is already mounted as ntfs-3g in the prior mount statment, all you're doing is making a relitive connection between the two mount points. like using a soft link.

It look like you are letting the system mount your ntfs, by your path statment. when your system does this it changes the id's to it everytime you reboot. that's why you're getting a new/different one each time because it seems to be defaulting to creating a new mount/dir/structrue to over come the mount you put in fstab. as it is not completely valid, because the windows part has not been offically mounted in run yet.

doing it this way it is hard copied into the system, taking full charge of the situation. it will stay that way.

see if that works.

and do not forget to

sudo chmod 755 -R /media/data # or what ever mount point you picked to use.

the directory that you created in root has to have permissions changed to 755. if you want user permissions on it.

if it works then you're now offically "the cats ass"

that's an oxymoron metaphor

1 members found this post helpful.

"First mount your whole partition first in fstab, then off of that mount,"

Thanks, that did it.

Happy to hear it...

you are now offically "the cats ass"