Re: [PLUG] Rsync user confusion: Who is user 1026?

[Larry Brigman]

You cannot change ownership of mounted filesystems.  That must be done from
the remote end.  Only the contents can be modified when you have
permissions.
You will probably need to figure out what the expected options are on the
NFS mount command.  We mount our NAS at work as remote home directories.
We have this
long line of options.  I suspect some (but not all) of these will apply.

Output of mount with no options (and only my remote home directory being
shown):
bilbo.arrs.arrisi.com:/vol/users/users/lbrigman/private on /users/lbrigman
type nfs
(rw,nosuid,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.109.0.189,mountvers=3,mountport=4046,mountproto=udp,local_lock=none,addr=10.109.0.189)

showmount only shows the exported mount points not the permissions of the
mount.
sudo showmount -e 10.109.0.189
Export list for 10.109.0.189:
/vol/departments (everyone)
/vol/cifs_01 (everyone)
/vol/isos(everyone)
/vol/vm_align01  10.109.80.0/23,10.109.86.0/24
/vol/cvinstall   (everyone)
/vol/vol0/home   (everyone)
/vol/vol0austria.arrisi.com,highlands.arrisi.com
/vol/export2 (everyone)
/vol/data_arwen  (everyone)
/vol/vm_isos 10.109.80.0/23,10.109.86.0/24
/vol/maupin2 (everyone)
/vol/users   (everyone)

Notice that the actual mount point is not the exported mount point but a
directory further in the tree.

Here is my actual mount command:
 mount -t nfs -o
rw,nosuid,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.109.0.189,mountvers=3,mountport=4046,mountproto=udp,local_lock=none,addr=10.109.0.189
bilbo.arrs.arrisi.com:/vol/users/users/lbrigman/private /users/lbrigman

Note the above command is a single long line.



On Mon, Jul 11, 2016 at 7:44 PM, John Jason Jordan 
wrote:

> On Mon, 11 Jul 2016 19:05:46 -0700
> Don Buchholz  dijo:
>
> >
> >I think you're really close ...
> >
> >(1)
> > sudo mount -t nfs
> > 192.168.0.101:*/*volume1/Synology /media/jjj/Synology
> >
> >... that little "/" in front of 'volume1' could be important.
>
> You may be onto something here. First, I thought the : was the proper
> divider, and when I replaced it with the / I got something interesting
> (see below). Then I added both, i.e., :/ and the command executed
> without error. It's finally mounted!!
>
> But all is not completely well, because I can't
> access /media/jjj/Synology. Here is what I did:
>
> sudo mount 192.168.0.101/volume1/Synology /media/jjj/Synology
> mount: special device 192.168.0.101/volume1/Synology does not exist
>
> sudo mount 192.168.0.101:/volume1/Synology /media/jjj/Synology
> 
> But all is not well:
> cd /media/jjj/Synology/
> bash: cd: /media/jjj/Synology/: Permission denied
>
> ls -la
> d-26 root root  81920 Jul 10 18:38 Synology
>
> Aargh! Now the /media/jjj/Synology folder is owned by root again, the
> same as happened when I mounted the share with SMB. Except this time
> note all the missing permissions, which didn't happen when I mounted it
> with SMB.
>
> I was able to change ownership to jjj with 'sudo chown,' which is
> also different from the SMB experience. Mounted with SMB the folder was
> owned by root and I was not able to take ownership, even after sudo su.
> On the other hand I could see all the files and act on them, it's
> just that they were all owned by the mysterious user 1026, thus rsync
> was not able to transfer ownerships from the source files.
>
> I suppose I could also change the permissions here with chmod. But the
> greater question is why is this even happening?
>
> In any event, thanks for the breakthrough insight! Finally a shred of
> progress!
> ___
> PLUG mailing list
> PLUG@lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Mon, 11 Jul 2016 19:05:46 -0700
Don Buchholz  dijo:

>
>I think you're really close ...
>
>(1)
> sudo mount -t nfs
> 192.168.0.101:*/*volume1/Synology /media/jjj/Synology
>
>... that little "/" in front of 'volume1' could be important.

You may be onto something here. First, I thought the : was the proper
divider, and when I replaced it with the / I got something interesting
(see below). Then I added both, i.e., :/ and the command executed
without error. It's finally mounted!!

But all is not completely well, because I can't
access /media/jjj/Synology. Here is what I did:

sudo mount 192.168.0.101/volume1/Synology /media/jjj/Synology 
mount: special device 192.168.0.101/volume1/Synology does not exist

sudo mount 192.168.0.101:/volume1/Synology /media/jjj/Synology

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Tomas Kuchta]

I forgot to add - you must run (as root):
  mount nfsClientMountDir
- if you want to mount the NFS share without reboot.


T

On Monday, July 11, 2016 07:17:18 PM you wrote:
> Here is simple example of NFS NAS and client (PC) configuration:
> 
> Names and abreviations:
>   * data - NFS server dir to be exported
>   * nfsServerIp - IP of NFS Server
>   * nfsClientIp - IP of NFS client (example: 192.168.1.100)
>   * networkIp - IP of your network (example: 192.168.1.1)
>   * nfsClientMountDir - mount directory for NFS share (not to be used for
> anything else. Example: /nfs/filer)
>   * CP - Control Panel
> 
> NFS v4 background:
>   * NFS server must recognize your client users by user names (UIDs may be
> different). The easiest way to achieve that is to create all not-root users
> owning stored files on the NFS server.
>   * If you are mounting multiple NFS server directories into multiple mount
> points on client - you must keep the servers directory tree structure in
> the clients mount directory. Bullet proof simple rule is to create data dir
> on the NFS server and mount that on client, keeping all data directories
> will be inside that data dir.
> 
> Synology NAS:
>   * Create users (not root) owning the data to be stored: CP -> User ->
> Create make users members of users group
>   * Create Shared Folder data: CP -> Shared Folder -> Create -> data
> NFS Permissions (tab) -> Create -> Hostname or IP: nfsClientIp
>Priviledge: Read/Write
>Squash: No mapping
>Enable asynchronnous: Yes
>   If you have other NFS clients which do not need root access you can
> chose for them: Squash: Map root to guest
>   If you have a lot of nfs client on the same network you can use:
>Hostname or IP: networkIp/24
>   * Enable NFS: CP -> File Services -> Enable NFS: Yes
>Enable NFSv4 Support: Yes
> 
> Client Setup mounting NFS folder data to nfsClientMountDir
>   * install nfs-client nfsidmap packages
>   * create nfsClientMountDir: mkdir nfsClientMountDir (become root if
> needed) * create /etc/fstab entry:
> nfsServerIp:/volume1/data nfsClientMountDir nfs4 defaults,suid 0 0
> If you do not want to auto mount NFS share at boot time, and allow users
> to mount/umount on demand - change the line to:
> nfsServerIp:/volume1/data nfsClientMountDir nfs4
> defaults,suid,noauto,users 0 0
> 
> I hope that I did not forget anything, Tomas
> 
> On Monday, July 11, 2016 05:37:46 PM John Jason Jordan wrote:
> > On Mon, 11 Jul 2016 18:04:41 -0500
> > 
> > David Fleck  dijo:
> > >Forgive me if somebody has already posted this link:
> > >https://www.synology.com/en-us/knowledgebase/DSM/tutorial/File_Sharing/Ho
> > >w_
> > >to_access_files_on_Synology_NAS_within_the_local_network_NFS
> > >
> > >Perhaps there is something in there that will clear up what the
> > >configuration issue is.
> > 
> > Thank you, I had not yet found that.
> > 
> > I read through the whole thing and followed the instructions to the
> > letter, but I still get 'access denied by server.'
> > 
> > I should add that their instructions say the mount command should be
> > 
> > (copied and pasted):
> > mount [Synology NAS IP address] : [mount path of shared
> > folder] / [mount point on NFS client]
> > 
> > Thus my command should be
> > 
> > mount 192.168.0.101:Synology / /media/jjj/Synology
> > 
> > Note the extra / between the source and the destination. If I add it
> > the mount command fails completely and displays help information. The
> > extra / can't be right.
> > 
> > And when I try it without the extra / it generates 'only root can do
> > that.' If I preface it with sudo or do sudo su to root, then I get
> > 'access denied by server.'
> > 
> > At the very end of the instructions it says "Can't mount the shared
> > folder? The user account you enter here must have access privileges for
> > the shared folder that you wish to map." I'm not sure where 'here' is,
> > the NAS or my command line? In any event, when I initially set up the
> > NAS with the Synology DiskStation Manager it came with an admin and a
> > guest account and I added an account 'jjj.' I gave all of them every
> > permission I could find.
> > 
> > I recently discovered a user forum on Synology's website. My next
> > effort wll be to post my tale of woe there.
> > ___
> > PLUG mailing list
> > PLUG@lists.pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug

___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Tomas Kuchta]

Here is simple example of NFS NAS and client (PC) configuration:

Names and abreviations:
  * data - NFS server dir to be exported
  * nfsServerIp - IP of NFS Server
  * nfsClientIp - IP of NFS client (example: 192.168.1.100)
  * networkIp - IP of your network (example: 192.168.1.1)
  * nfsClientMountDir - mount directory for NFS share (not to be used for 
anything else. 
Example: /nfs/filer)
  * CP - Control Panel

NFS v4 background:
  * NFS server must recognize your client users by user names (UIDs may be 
different). 
The easiest way to achieve that is to create all not-root users owning stored 
files on the 
NFS server.
  * If you are mounting multiple NFS server directories into multiple mount 
points on 
client - you must keep the servers directory tree structure in the clients 
mount directory. 
Bullet proof simple rule is to create data dir on the NFS server and mount that 
on client, 
keeping all data directories will be inside that data dir.

Synology NAS:
  * Create users (not root) owning the data to be stored: CP -> User -> Create
make users members of users group 
  * Create Shared Folder data: CP -> Shared Folder -> Create -> data
NFS Permissions (tab) -> Create -> Hostname or IP: nfsClientIp
   Priviledge: Read/Write
   Squash: No mapping
   Enable asynchronnous: Yes
  If you have other NFS clients which do not need root access you can chose 
for them:
   Squash: Map root to guest
  If you have a lot of nfs client on the same network you can use:
   Hostname or IP: networkIp/24
  * Enable NFS: CP -> File Services -> Enable NFS: Yes
   Enable NFSv4 Support: Yes

Client Setup mounting NFS folder data to nfsClientMountDir
  * install nfs-client nfsidmap packages
  * create nfsClientMountDir: mkdir nfsClientMountDir (become root if needed)
  * create /etc/fstab entry:
nfsServerIp:/volume1/data nfsClientMountDir nfs4 defaults,suid 0 0
If you do not want to auto mount NFS share at boot time, and allow users to 
mount/umount on demand - change the line to:
nfsServerIp:/volume1/data nfsClientMountDir nfs4 defaults,suid,noauto,users 
0 0

I hope that I did not forget anything, Tomas

On Monday, July 11, 2016 05:37:46 PM John Jason Jordan wrote:
> On Mon, 11 Jul 2016 18:04:41 -0500
> 
> David Fleck  dijo:
> >Forgive me if somebody has already posted this link:
> >https://www.synology.com/en-us/knowledgebase/DSM/tutorial/File_Sharing/How_
> >to_access_files_on_Synology_NAS_within_the_local_network_NFS
> >
> >Perhaps there is something in there that will clear up what the
> >configuration issue is.
> 
> Thank you, I had not yet found that.
> 
> I read through the whole thing and followed the instructions to the
> letter, but I still get 'access denied by server.'
> 
> I should add that their instructions say the mount command should be
> (copied and pasted):
> 
>   mount [Synology NAS IP address] : [mount path of shared
>   folder] / [mount point on NFS client]
> 
> Thus my command should be
> 
>   mount 192.168.0.101:Synology / /media/jjj/Synology
> 
> Note the extra / between the source and the destination. If I add it
> the mount command fails completely and displays help information. The
> extra / can't be right.
> 
> And when I try it without the extra / it generates 'only root can do
> that.' If I preface it with sudo or do sudo su to root, then I get
> 'access denied by server.'
> 
> At the very end of the instructions it says "Can't mount the shared
> folder? The user account you enter here must have access privileges for
> the shared folder that you wish to map." I'm not sure where 'here' is,
> the NAS or my command line? In any event, when I initially set up the
> NAS with the Synology DiskStation Manager it came with an admin and a
> guest account and I added an account 'jjj.' I gave all of them every
> permission I could find.
> 
> I recently discovered a user forum on Synology's website. My next
> effort wll be to post my tale of woe there.
> ___
> PLUG mailing list
> PLUG@lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Don Buchholz]

I think you're really close ...

(1)
 sudo mount -t nfs 192.168.0.101:*/*volume1/Synology /media/jjj/Synology

... that little "/" in front of 'volume1' could be important.


(2)
 You might want to clean-up the exports list ...
  ... just to get started, put *only* the IP address for
  the client host (the system on which you are running
  the 'mount' command)
  ... if it will allow, you can try "192.168.0/24" or
  "192.168.0.*"  --  I can't speak for Synology's
  implementation specifics.

(3)
 Is there any kind of firewall running on your client host?






On 7/11/2016 6:47 PM, John Jason Jordan wrote:
> On Mon, 11 Jul 2016 18:07:23 -0700
> Don Buchholz  dijo:
>
>> (3) Try this command (as 'root'!) to see what the NAS is making
>>  available to mount with the NFS protocol:
>>
>>  showmount -e 192.168.0.101
> Export list for 192.168.0.101:
> /volume1/Synology *.*.*.*,192.168.0.136,192.168.0.146,192.168.0.126
> /volume1/Synology_NFS 192.168.0.126,192.168.0.146,192.168.0.101
>
> Note that the above lists all kinds of attempts by me - adding IP
> addresses for my laptop (...126), desktop (...146) and even *.*.*.*,
> plus creating a second share Synology_NFS. All to no avail so far.
>
> I should add that I didn't notice that you said 'as root' so I ran it
> as jjj, and later as root. The results were the same.
>
> And seeing the results I amended my mount command to
>
> sudo mount -t nfs 192.168.0.101:volume1/Synology /media/jjj/Synology
> sudo mount -t nfs 192.168.0.101:volume1 /media/jjj/Synology
>
> But I still get 'access denied by server.'
>
>> (2) About your local mount point ...
>>  I'd suggest:
>>  mkdir /synology
>> / ... makes a new mount //point/
> Didn't make any difference, not that I expected it to. I have lots of
> things mounted in /media/jjj - USB drives mostly.
>
> I should add that I get the same results from my desktop computer (also
> Xubuntu 14.04).
>
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Mon, 11 Jul 2016 18:07:23 -0700
Don Buchholz  dijo:

>(3) Try this command (as 'root'!) to see what the NAS is making
> available to mount with the NFS protocol:
>
> showmount -e 192.168.0.101

Export list for 192.168.0.101:
/volume1/Synology *.*.*.*,192.168.0.136,192.168.0.146,192.168.0.126
/volume1/Synology_NFS 192.168.0.126,192.168.0.146,192.168.0.101

Note that the above lists all kinds of attempts by me - adding IP
addresses for my laptop (...126), desktop (...146) and even *.*.*.*,
plus creating a second share Synology_NFS. All to no avail so far. 

I should add that I didn't notice that you said 'as root' so I ran it
as jjj, and later as root. The results were the same.

And seeing the results I amended my mount command to

sudo mount -t nfs 192.168.0.101:volume1/Synology /media/jjj/Synology
sudo mount -t nfs 192.168.0.101:volume1 /media/jjj/Synology

But I still get 'access denied by server.'

>(2) About your local mount point ...
> I'd suggest:
> mkdir /synology
>/ ... makes a new mount //point/

Didn't make any difference, not that I expected it to. I have lots of
things mounted in /media/jjj - USB drives mostly. 

I should add that I get the same results from my desktop computer (also
Xubuntu 14.04).

___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[David Fleck]

On Mon, 2016-07-11 at 18:07 -0700, Don Buchholz wrote:

showmount -e 192.168.0.101

Yes. Running this command (it may be /usr/sbin/showmount on your
machine) and posting the output will be helpful.  

It looks to me as though the NAS isn't configured quite right. You need
to know what it thinks it's configured to do (as compared to what you
think you configured it to do).



___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Don Buchholz]

(1) "only root can do that ..."
 -- um, yes, generally, only 'root' is allowed to perform
mount(8) commands
 -- so, you need to become 'root'
  (a) login to the console as 'root', -OR-
  (b) execute the command "su -" and enter root p/w
  when prompted, -OR-
  (c) prefix everything with "sudo" (as you've done in
  earlier messages to this forum

(2) "the extra '/' ..."
 -- you're right, it shouldn't be there ...


(3) Try this command (as 'root'!) to see what the NAS is making
 available to mount with the NFS protocol:

 showmount -e 192.168.0.101


(4) In it's most simple form, the mount(8) command is parsed as

 mount

 "mount" --> the command

 ""  -->  When mounting a partition
  from a local disks the argument will look something
  like "/dev/sda1"/.  When mounting an NFS filesystem,
  it will look like "server:/path".

  In your case, "server" is '192.168.0.101' and the
  "path" is 'Synology'.

 ""  --> "/media/jjj/Synology".


 So, putting it all together ...

 mount 192.168.0.101:/Synology /media/jjj/Synology



Now -- I see two possible problems ...

(1) The 'path' on the NAS might not by "/Synology".

 This is why I suggest you do the "showmount -e 192.168.0.101".
 It should tell you what path(s) are being exported.


(2) About your local mount point ...

 With all the GUI and hand-holding crap that goes on with
 these modern distros (what in the heck is a 'Thunar' anyway?)
 some areas of the filesystem fall under 'special' management
 [cue Dana Carvey Church Lady voice when you say 'special'].

 "/media" is probably one of those areas ...

 I'd suggest:

 mkdir /synology
/ ... makes a new mount //point/

 mount -t nfs  192.168.0.101:/Synology  /synology
/ ... mounts NAS filesystem onto /synology (assuming
  we've got the correct name for the path begin
  exported -- see the "showmount -e 192.168.0.101"
  results.
/

 df -t nfs
/ ... displays "disk-free" on all mounted filesystems
  of type (-t) "nfs"/



On 7/11/2016 5:37 PM, John Jason Jordan wrote:
> On Mon, 11 Jul 2016 18:04:41 -0500
> David Fleck  dijo:
>
>> Forgive me if somebody has already posted this link:
>> https://www.synology.com/en-us/knowledgebase/DSM/tutorial/File_Sharing/How_to_access_files_on_Synology_NAS_within_the_local_network_NFS
>>
>> Perhaps there is something in there that will clear up what the
>> configuration issue is.
> Thank you, I had not yet found that.
>
> I read through the whole thing and followed the instructions to the
> letter, but I still get 'access denied by server.'
>
> I should add that their instructions say the mount command should be
> (copied and pasted):
>
>   mount [Synology NAS IP address] : [mount path of shared
>   folder] / [mount point on NFS client]
>
> Thus my command should be
>
>   mount 192.168.0.101:Synology / /media/jjj/Synology
>
> Note the extra / between the source and the destination. If I add it
> the mount command fails completely and displays help information. The
> extra / can't be right.
>
> And when I try it without the extra / it generates 'only root can do
> that.' If I preface it with sudo or do sudo su to root, then I get
> 'access denied by server.'
>
> At the very end of the instructions it says "Can't mount the shared
> folder? The user account you enter here must have access privileges for
> the shared folder that you wish to map." I'm not sure where 'here' is,
> the NAS or my command line? In any event, when I initially set up the
> NAS with the Synology DiskStation Manager it came with an admin and a
> guest account and I added an account 'jjj.' I gave all of them every
> permission I could find.
>
> I recently discovered a user forum on Synology's website. My next
> effort wll be to post my tale of woe there.
> ___
> PLUG mailing list
> PLUG@lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug

___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Mon, 11 Jul 2016 18:04:41 -0500
David Fleck  dijo:

>Forgive me if somebody has already posted this link:
>https://www.synology.com/en-us/knowledgebase/DSM/tutorial/File_Sharing/How_to_access_files_on_Synology_NAS_within_the_local_network_NFS
>
>Perhaps there is something in there that will clear up what the
>configuration issue is.

Thank you, I had not yet found that. 

I read through the whole thing and followed the instructions to the
letter, but I still get 'access denied by server.'

I should add that their instructions say the mount command should be
(copied and pasted):

mount [Synology NAS IP address] : [mount path of shared
folder] / [mount point on NFS client]

Thus my command should be

mount 192.168.0.101:Synology / /media/jjj/Synology

Note the extra / between the source and the destination. If I add it
the mount command fails completely and displays help information. The
extra / can't be right.

And when I try it without the extra / it generates 'only root can do
that.' If I preface it with sudo or do sudo su to root, then I get
'access denied by server.'

At the very end of the instructions it says "Can't mount the shared
folder? The user account you enter here must have access privileges for
the shared folder that you wish to map." I'm not sure where 'here' is,
the NAS or my command line? In any event, when I initially set up the
NAS with the Synology DiskStation Manager it came with an admin and a
guest account and I added an account 'jjj.' I gave all of them every
permission I could find.

I recently discovered a user forum on Synology's website. My next
effort wll be to post my tale of woe there.
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[David Fleck]

On Mon, 2016-07-11 at 12:30 -0700, John Jason Jordan wrote:

> jjj@Devil-Bonobo:/media/jjj$ mount -t nfs
>   synology.local:/synology /media/jjj/Synology 
> mount: only root can do   that 
> jjj@Devil-Bonobo:/media/jjj$ sudo su
> root@Devil-Bonobo:/media/jjj# mount -t nfs
>   synology.local:/synology /media/jjj/Synology 
> mount.nfs: access denied by server while mounting
>   synology.local:/synology
> 

Forgive me if somebody has already posted this link:
https://www.synology.com/en-us/knowledgebase/DSM/tutorial/File_Sharing/How_to_access_files_on_Synology_NAS_within_the_local_network_NFS

Perhaps there is something in there that will clear up what the
configuration issue is.


___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Mon, 11 Jul 2016 12:20:26 -0700
Bill Barry  dijo:

>On Jul 11, 2016 11:48 AM, "John Jason Jordan" 
>wrote:
>>
>> On Mon, 11 Jul 2016 17:41:30 +
>> Jason Spohn  dijo:
>>
>> >Check out this page for some info on mounting NFS on Linux. Also
>> >shows how to create the proper 'fstab' to make it persistent.
>> >http://www.tldp.org/LDP/nag2/x-087-2-nfs.mountd.html
>>
>> I read the above page and tried what it said to do, but nothing
>> worked. Mostly I think the problem is that it never addressed
>> mount.cifs. 
>
>You will not be using mount.cifs. That is for the windows cifs
>filesystem. You will be using something else for NFS.

Ah! Thanks for clearing that up. 
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Mon, 11 Jul 2016 10:54:40 -0700
Don Buchholz  dijo:

>> This is the command that mounts it with SMB:
>>
>> sudo mount.cifs //synology.local/synology/ /media/jjj/Synology/
>>  --verbose -o user=jjj
>>
>> I assume I have to change either 'mount.cifs' or
>> '//synology.local/synology/. So far Google hasn't been much help.


>Based on your 'mount.cifs' command ...
>
> sudo mount -t nfs synology.local:/synology /media/jjj/Synology

jjj@Devil-Bonobo:/media/jjj$ mount -t nfs
synology.local:/synology /media/jjj/Synology 
mount: only root can do that 
jjj@Devil-Bonobo:/media/jjj$ sudo su
root@Devil-Bonobo:/media/jjj# mount -t nfs
synology.local:/synology /media/jjj/Synology 
mount.nfs: access denied by server while mounting
synology.local:/synology

I should add that in the Synology DiskStation Manager under NFS I have
set up permissions for 192.168.0.126 (my laptop) and 192.168.0.146 (my
desktop). The permissions are read/write, no mapping, asynchronous,
non-privileged: denied, cross-mount: allowed.

Also, I am very familiar with the 'access denied by server' message.
Some months ago I set up a share on my laptop so my desktop could
connect to it. After days of fussing with NFS and countless posts here I
gave up and went back to sneakernet.

>To auto-magically mount at boot time ... put this In the /etc/fstab
>(see "man fstab").
>
> synology.local:/synology  /media/jjj/Synology nfs 
>auto,defaults  0  0

I changed my fstab entry to the above. However, doesn't 'defaults' mean
'nouser'?
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Bill Barry]

On Jul 11, 2016 11:48 AM, "John Jason Jordan"  wrote:
>
> On Mon, 11 Jul 2016 17:41:30 +
> Jason Spohn  dijo:
>
> >Check out this page for some info on mounting NFS on Linux. Also shows
> >how to create the proper 'fstab' to make it persistent.
> >http://www.tldp.org/LDP/nag2/x-087-2-nfs.mountd.html
>
> I read the above page and tried what it said to do, but nothing worked.
> Mostly I think the problem is that it never addressed mount.cifs.
> 

You will not be using mount.cifs. That is for the windows cifs filesystem.
You will be using something else for NFS.

Bill
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Dale Snell]

On Mon, 11 Jul 2016 11:48:44 -0700, in message
2016074844.0a360442@Devil-Bonobo, John Jason Jordan wrote:

> On Mon, 11 Jul 2016 17:41:30 +
> Jason Spohn  dijo:
> 
> >Check out this page for some info on mounting NFS on Linux. Also
> >shows how to create the proper 'fstab' to make it persistent.
> >http://www.tldp.org/LDP/nag2/x-087-2-nfs.mountd.html
> 
> I read the above page and tried what it said to do, but nothing
> worked. Mostly I think the problem is that it never addressed
> mount.cifs.


Why should it?  That web page is about mounting an NFS share.  It
has nothing to do with mounting SMB/CIFS shares.  Note that there
is an analog to mount.cifs: mount.nfs.  It is meant to be used by
the mount(8) program, but can be used standalone if you really
must.  See the man pages for mount.nfs(8) and mount(8) for
details.

Hope this helps.

--Dale

-- 
"Always do right -- this will gratify some and astonish the rest."
-- Mark Twain (1835-1910) 
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Mon, 11 Jul 2016 17:41:30 +
Jason Spohn  dijo:

>Check out this page for some info on mounting NFS on Linux. Also shows
>how to create the proper 'fstab' to make it persistent.
>http://www.tldp.org/LDP/nag2/x-087-2-nfs.mountd.html

I read the above page and tried what it said to do, but nothing worked.
Mostly I think the problem is that it never addressed mount.cifs.
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Don Buchholz]

On 7/11/2016 10:34 AM, John Jason Jordan wrote:
> On Sun, 10 Jul 2016 23:02:13 -0700
> Bill Barry  dijo:
>
>> On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan
>>  wrote:
>>> I have discovered something that I should have noticed a long time
>>> ago, that is, that the entire drive is owned by root. That would
>>> explain the fact that   the -o --owner and -g --group options are
>>> not working in rsync, leaving the owner of the files the mysterious
>>> user 1026. (I'm betting user 1026 is root on my Xubuntu.) "And why
>>> is the drive owned by root?" you ask. That is because the only way I
>>> could mount it was with sudo.
>> The problem is not quite that the entire drive is owned by root. The
>> underlying problem is that you are trying to rsync to a windows type
>> file system. Or probably more correctly what is presented to you as a
>> windows file system.  This will prevent you from correctly preserving
>> owners and groups and such because windows has a different notion of
>> such things.   If you want to preserve those file attributes, you
>> would be better off mounting the drive as an NFS drive if the Synology
>> allows for that.
> The Synology does provide NFS and, in fact, in my initial setup with
> the DiskStation Manager utility I enabled both SMB and NFS.
>
> Now the question is how to mount it with NFS instead of SMB. I scoured
> the DiskStation Manager Help and didn't find a word about how to mount
> the share with NFS, just lots of stuff about setting permissions. I
> suppose that is because mount commands probably vary from OS to OS.
>
> This is the command that mounts it with SMB:
>
> sudo mount.cifs //synology.local/synology/ /media/jjj/Synology/
>   --verbose -o user=jjj
>
> I assume I have to change either 'mount.cifs' or
> '//synology.local/synology/. So far Google hasn't been much help.
> ___
Based on your 'mount.cifs' command ...

 sudo mount -t nfs synology.local:/synology /media/jjj/Synology

To auto-magically mount at boot time ... put this In the /etc/fstab (see 
"man fstab").

 synology.local:/synology  /media/jjj/Synology nfs 
auto,defaults  0  0

 column#1:  -->  hostname:/path/on/server
 column#2:  -->  local mount point
 column#3:  -->  filesystem type (in this case "nfs")
 column#4:  -->  mount options:
  "auto" -->  mount at system boot time
  "defaults"  --> just use the normal default
  options for thefilesytems type
  being mounted ...
 column#5:  --> used for the dump(8) backup program. Leave
it as "0" ...

 column#6:  --> As the system boots, local filesystems may be 
checked for
consistency/integrity.  This really doesn't 
apply to remote
(CIFS or NFS) filesystems.  Leave it as "0" ...


___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Jason Spohn]

Check out this page for some info on mounting NFS on Linux. Also shows how to 
create the proper 'fstab' to make it persistent.  
http://www.tldp.org/LDP/nag2/x-087-2-nfs.mountd.html

Jason Spohn

This electronic data is provided by Siegfried, as a courtesy. This data is 
distributed "as is" without warranty of any kind, either expressed or implied. 
Siegfried distributes this data for your sole use and may not be sold to 
another entity.
-Original Message-
From: plug-boun...@lists.pdxlinux.org [mailto:plug-boun...@lists.pdxlinux.org] 
On Behalf Of John Jason Jordan
Sent: Monday, July 11, 2016 10:34 AM
To: plug@lists.pdxlinux.org
Subject: Re: [PLUG] Rsync user confusion: Who is user 1026?

On Sun, 10 Jul 2016 23:02:13 -0700
Bill Barry <b...@billbarry.org> dijo:

>On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan 
><joh...@comcast.net> wrote:
>> I have discovered something that I should have noticed a long time 
>> ago, that is, that the entire drive is owned by root. That would
>> explain the fact that   the -o --owner and -g --group options are
>> not working in rsync, leaving the owner of the files the mysterious 
>> user 1026. (I'm betting user 1026 is root on my Xubuntu.) "And why is 
>> the drive owned by root?" you ask. That is because the only way I 
>> could mount it was with sudo.

>The problem is not quite that the entire drive is owned by root. The 
>underlying problem is that you are trying to rsync to a windows type 
>file system. Or probably more correctly what is presented to you as a 
>windows file system.  This will prevent you from correctly preserving 
>owners and groups and such because windows has a different notion of
>such things.   If you want to preserve those file attributes, you
>would be better off mounting the drive as an NFS drive if the Synology 
>allows for that.

The Synology does provide NFS and, in fact, in my initial setup with the 
DiskStation Manager utility I enabled both SMB and NFS. 

Now the question is how to mount it with NFS instead of SMB. I scoured the 
DiskStation Manager Help and didn't find a word about how to mount the share 
with NFS, just lots of stuff about setting permissions. I suppose that is 
because mount commands probably vary from OS to OS. 

This is the command that mounts it with SMB:

sudo mount.cifs //synology.local/synology/ /media/jjj/Synology/
--verbose -o user=jjj

I assume I have to change either 'mount.cifs' or '//synology.local/synology/. 
So far Google hasn't been much help.
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Sun, 10 Jul 2016 23:02:13 -0700
Bill Barry  dijo:

>On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan
> wrote:
>> I have discovered something that I should have noticed a long time
>> ago, that is, that the entire drive is owned by root. That would
>> explain the fact that   the -o --owner and -g --group options are
>> not working in rsync, leaving the owner of the files the mysterious
>> user 1026. (I'm betting user 1026 is root on my Xubuntu.) "And why
>> is the drive owned by root?" you ask. That is because the only way I
>> could mount it was with sudo.

>The problem is not quite that the entire drive is owned by root. The
>underlying problem is that you are trying to rsync to a windows type
>file system. Or probably more correctly what is presented to you as a
>windows file system.  This will prevent you from correctly preserving
>owners and groups and such because windows has a different notion of
>such things.   If you want to preserve those file attributes, you
>would be better off mounting the drive as an NFS drive if the Synology
>allows for that.

The Synology does provide NFS and, in fact, in my initial setup with
the DiskStation Manager utility I enabled both SMB and NFS. 

Now the question is how to mount it with NFS instead of SMB. I scoured
the DiskStation Manager Help and didn't find a word about how to mount
the share with NFS, just lots of stuff about setting permissions. I
suppose that is because mount commands probably vary from OS to OS. 

This is the command that mounts it with SMB:

sudo mount.cifs //synology.local/synology/ /media/jjj/Synology/
--verbose -o user=jjj

I assume I have to change either 'mount.cifs' or
'//synology.local/synology/. So far Google hasn't been much help.
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[Bill Barry]

On Sun, Jul 10, 2016 at 10:42 PM, John Jason Jordan 
wrote:

> On Sat, 9 Jul 2016 22:42:04 -0700
> John Jason Jordan  dijo:
>
> >But to test it I created a 0 byte file 'test' in the source folder, and
>
> I have discovered something that I should have noticed a long time ago,
> that is, that the entire drive is owned by root. That would explain the
> fact that   the -o --owner and -g --group options are not working in
> rsync, leaving the owner of the files the mysterious user 1026.
> (I'm betting user 1026 is root on my Xubuntu.) "And why is the drive
> owned by root?" you ask. That is because the only way I could mount it
> was with sudo.
>
>

The problem is not quite that the entire drive is owned by root. The
underlying problem is that you are trying to rsync to a windows type file
system. Or probably more correctly what is presented to you as a windows
file system.  This will prevent you from correctly preserving owners and
groups and such because windows has a different notion of such things.   If
you want to preserve those file attributes, you would be better off
mounting the drive as an NFS drive if the Synology allows for that.

Bill
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

On Sat, 9 Jul 2016 22:42:04 -0700
John Jason Jordan  dijo:

>But to test it I created a 0 byte file 'test' in the source folder, and
>changed the * to test in the above command. At first the command failed
>with a permissions error (although I thought I had read that rsync does
>not require sudo), so I executed the command with sudo. This
>workedjjj@Devil-Bonobo:/media/jjj/Data1$
>mount.cifs //synology.local/synology/ /media/jjj/Synology/ --verbose
>-o user=jjj
Password for jjj@//synology.local/synology/: 
mount.cifs kernel mount options:
ip=192.168.0.101,unc=\\synology.local\synology,auto,uid=1000,gid=1000,user=jjj,pass=
mount error(22): Invalid argument Refer to the mount.cifs(8) manual 
page (e.g. man mount.cifs)
>without error and the file appeared in the destination. To make sure I
>still owned it I right-clicked on it with Thunar, then Properties >
>Permissions. All the permissions are grayed out and the owner is listed
>as 1026. Checking users and permissions I am user 1000. Yet, in spite
>of the fact that some strange user owns the file, as jjj I can delete
>it, rename it, etc.
>
>So where did user 1026 come from?

I have discovered something that I should have noticed a long time ago,
that is, that the entire drive is owned by root. That would explain the
fact that   the -o --owner and -g --group options are not working in
rsync, leaving the owner of the files the mysterious user 1026.
(I'm betting user 1026 is root on my Xubuntu.) "And why is the drive
owned by root?" you ask. That is because the only way I could mount it
was with sudo.

Fast forward to after several hours of googling and it appears that I
can mount it as jjj only if it is in fstab with 'user' as one of the
options. "No problem," I thought, "I'll just edit up my fstab file."
Here is the line I cooked up:

//synology.local/synology/ /media/jjj/Synology auto auto,user,rw 0 0

My mount command (sans sudo) is:

mount.cifs //synology.local/synology/ /media/jjj/Synology/
--verbose -o user=jjj

Unfortunately, something is wrong:

mount.cifs //synology.local/synology/ /media/jjj/Synology/ --verbose -o
user=jjj 
Password for jjj@//synology.local/synology/: 
mount.cifs kernel mount options:
ip=192.168.0.101,unc=\\synology.local\synology,auto,uid=1000,gid=1000,user=jjj,pass=
mount error(22): Invalid argument 
Refer to the mount.cifs(8) manual   page (e.g. man mount.cifs)

It would have been really helpful if the error message gave me some
clue as to which argument is not valid. I don't even know if it's an
argument in the command or in the fstab line.

So far I have about a dozen hours invested in trying to get this thing
working and I'm close to giving up. Perhaps in the morning my attitude
will be refreshed. In the meantime, if anyone sees anything in the
mount command or the fstab line, please let me know. Any suggestions
are better than what I have now.

I opened the mount.cifs man page and read everything I could
understand. 
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug

[PLUG] Rsync user confusion: Who is user 1026?

[John Jason Jordan]

Having finally (!) mounted my new NAS drive I am working on rsync. I
have a prototype command:

rsync -rpt --delete /media/jjj/Movies/* /media/jjj/Synology

But to test it I created a 0 byte file 'test' in the source folder, and
changed the * to test in the above command. At first the command failed
with a permissions error (although I thought I had read that rsync does
not require sudo), so I executed the command with sudo. This worked
without error and the file appeared in the destination. To make sure I
still owned it I right-clicked on it with Thunar, then Properties >
Permissions. All the permissions are grayed out and the owner is listed
as 1026. Checking users and permissions I am user 1000. Yet, in spite
of the fact that some strange user owns the file, as jjj I can delete
it, rename it, etc.

So where did user 1026 come from?
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug