For ten years regularly backed up the data partition of my work machine to a backup machine. Then the backup machine had to be mothballed prior to a downsizing move.

Two years later I want to deploy the same script.

First it mounts the remote shares and then runs a series of rsync commands. Except that it now no longer works. It fails at the mpint stage.

After reading man pages and searching the www I cannot fathom why.

This is the first mount line.:

sudo mount -t cifs -o rw,noperm,credentials=/home/alan/.smbcredentials,vers=1.0 //192.168.1.66/alan/ /spare/churchill/alan/

When I try to run it, it returns:

mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

dmesg returns:

[34663.775002] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
[34663.775010] CIFS: Attempting to mount \\192.168.1.66\alan
[34674.119607] CIFS: VFS: Error connecting to socket. Aborting operation.
[34674.119626] CIFS: VFS: cifs_mount failed w/return code = -115

TIA

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

On 7/27/2023 4:54 PM, pinnerite wrote:
> For ten years regularly backed up the data partition of my work machine to a backup machine. Then the backup machine had to be mothballed prior to a downsizing move.
>
> Two years later I want to deploy the same script.
>
> First it mounts the remote shares and then runs a series of rsync commands. Except that it now no longer works. It fails at the mpint stage.
>
> After reading man pages and searching the www I cannot fathom why.
>
> This is the first mount line.:
>
> sudo mount -t cifs -o rw,noperm,credentials=/home/alan/.smbcredentials,vers=1.0 //192.168.1.66/alan/ /spare/churchill/alan/
>
> When I try to run it, it returns:
>
> mount error(115): Operation now in progress
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
>
> dmesg returns:
>
> [34663.775002] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
> [34663.775010] CIFS: Attempting to mount \\192.168.1.66\alan
> [34674.119607] CIFS: VFS: Error connecting to socket. Aborting operation.
> [34674.119626] CIFS: VFS: cifs_mount failed w/return code = -115
>
> TIA

sudo mount -t cifs -o rw,noperm,credentials=/credentials,vers=3 //192.168.2.102/shared /smurf

You're connecting to Windows 10, so vers=3 might be a start.

Paul

On 2023-07-27, pinnerite wrote:
> [...]
> First it mounts the remote shares and then runs a series of rsync
> commands. Except that it now no longer works. It fails at the mpint
> stage.
>
> This is the first mount line.:
>
> sudo mount -t cifs -o
> rw,noperm,credentials=/home/alan/.smbcredentials,vers=1.0
> //192.168.1.66/alan/ /spare/churchill/alan/
> [...]
> dmesg returns:
>
> [34663.775002] CIFS: VFS: Use of the less secure dialect vers=1.0 is
> not recommended unless required for access to very old servers
> [34663.775010] CIFS: Attempting to mount \\192.168.1.66\alan
> [34674.119607] CIFS: VFS: Error connecting to socket. Aborting operation.
> [34674.119626] CIFS: VFS: cifs_mount failed w/return code = -115
>

Looks like an incompatibility in SMB/CIFS versions.

That being said -- why bother? Is the backup target (*66) not capable
of accepting SSH connections?

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860

On Fri, 28 Jul 2023 06:41:37 -0400
Paul <nospam@needed.invalid> wrote:

> On 7/27/2023 4:54 PM, pinnerite wrote:
> > For ten years regularly backed up the data partition of my work machine to a backup machine. Then the backup machine had to be mothballed prior to a downsizing move.
> >
> > Two years later I want to deploy the same script.
> >
> > First it mounts the remote shares and then runs a series of rsync commands. Except that it now no longer works. It fails at the mpint stage.
> >
> > After reading man pages and searching the www I cannot fathom why.
> >
> > This is the first mount line.:
> >
> > sudo mount -t cifs -o rw,noperm,credentials=/home/alan/.smbcredentials,vers=1.0 //192.168.1.66/alan/ /spare/churchill/alan/
> >
> > When I try to run it, it returns:
> >
> > mount error(115): Operation now in progress
> > Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
> >
> > dmesg returns:
> >
> > [34663.775002] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
> > [34663.775010] CIFS: Attempting to mount \\192.168.1.66\alan
> > [34674.119607] CIFS: VFS: Error connecting to socket. Aborting operation.
> > [34674.119626] CIFS: VFS: cifs_mount failed w/return code = -115
> >
> > TIA
>
> sudo mount -t cifs -o rw,noperm,credentials=/credentials,vers=3 //192.168.2.102/shared /smurf
>
> You're connecting to Windows 10, so vers=3 might be a start.
>
> Paul
>
>

No, I am not connecting to Windows on the target machine, just use the settings on my work machine's smb.conf that provides access to both Win-XP and Win-10.
This is what smb.conf on both machines includes:

client min protocol = NT1
client max protocol = SMB3

server min protocol = NT1
server max protocol = smb3

It works fine on the work machine.

And Dan, I can ping and ssh to the backuo machine. I just want use a script that until two years ago, ran virtually unchanged for nigh on 15 - 20 years.
I am a bit long in the tooth so never change for change sake.

ATB Alan

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

On Fri, 28 Jul 2023 20:20:57 +0100
pinnerite <pinnerite@gmail.com> wrote:

> On Fri, 28 Jul 2023 06:41:37 -0400
> Paul <nospam@needed.invalid> wrote:
>
> > On 7/27/2023 4:54 PM, pinnerite wrote:
> > > For ten years regularly backed up the data partition of my work machine to a backup machine. Then the backup machine had to be mothballed prior to a downsizing move.
> > >
> > > Two years later I want to deploy the same script.
> > >
> > > First it mounts the remote shares and then runs a series of rsync commands. Except that it now no longer works. It fails at the mpint stage.
> > >
> > > After reading man pages and searching the www I cannot fathom why.
> > >
> > > This is the first mount line.:
> > >
> > > sudo mount -t cifs -o rw,noperm,credentials=/home/alan/.smbcredentials,vers=1.0 //192.168.1.66/alan/ /spare/churchill/alan/
> > >
> > > When I try to run it, it returns:
> > >
> > > mount error(115): Operation now in progress
> > > Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
> > >
> > > dmesg returns:
> > >
> > > [34663.775002] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
> > > [34663.775010] CIFS: Attempting to mount \\192.168.1.66\alan
> > > [34674.119607] CIFS: VFS: Error connecting to socket. Aborting operation.
> > > [34674.119626] CIFS: VFS: cifs_mount failed w/return code = -115
> > >
> > > TIA
> >
> > sudo mount -t cifs -o rw,noperm,credentials=/credentials,vers=3 //192.168.2.102/shared /smurf
> >
> > You're connecting to Windows 10, so vers=3 might be a start.
> >
> > Paul
> >
> >
>
> No, I am not connecting to Windows on the target machine, just use the settings on my work machine's smb.conf that provides access to both Win-XP and Win-10.
> This is what smb.conf on both machines includes:
>
> client min protocol = NT1
> client max protocol = SMB3
>
> server min protocol = NT1
> server max protocol = smb3
>
> It works fine on the work machine.
>
> And Dan, I can ping and ssh to the backuo machine. I just want use a script that until two years ago, ran virtually unchanged for nigh on 15 - 20 years.
> I am a bit long in the tooth so never change for change sake.
>
> ATB Alan
>

I can now mount samba shares but cannot see why my backup command is sending the data to the mount point rather than to the share mounted there.

The mount statement is:

sudo mount -vvv -t cifs //192.168.1.66/alan/ /spare/churchill/alan/ -o rw,noperm,username=alan,password=<my_password>,vers=1.0,uid=alan

The test backup command is:

rsync -rlptD /home/alan/Scripts /spare/churchill/alan/

I can't get my head round it.

--
Linux Mint 21.1 kernel version 5.15.0-78-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

On 8/3/2023 3:55 PM, pinnerite wrote:
> On Fri, 28 Jul 2023 20:20:57 +0100
> pinnerite <pinnerite@gmail.com> wrote:
>
>> On Fri, 28 Jul 2023 06:41:37 -0400
>> Paul <nospam@needed.invalid> wrote:
>>
>>> On 7/27/2023 4:54 PM, pinnerite wrote:
>>>> For ten years regularly backed up the data partition of my work machine to a backup machine. Then the backup machine had to be mothballed prior to a downsizing move.
>>>>
>>>> Two years later I want to deploy the same script.
>>>>
>>>> First it mounts the remote shares and then runs a series of rsync commands. Except that it now no longer works. It fails at the mpint stage.
>>>>
>>>> After reading man pages and searching the www I cannot fathom why.
>>>>
>>>> This is the first mount line.:
>>>>
>>>> sudo mount -t cifs -o rw,noperm,credentials=/home/alan/.smbcredentials,vers=1.0 //192.168.1.66/alan/ /spare/churchill/alan/
>>>>
>>>> When I try to run it, it returns:
>>>>
>>>> mount error(115): Operation now in progress
>>>> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
>>>>
>>>> dmesg returns:
>>>>
>>>> [34663.775002] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
>>>> [34663.775010] CIFS: Attempting to mount \\192.168.1.66\alan
>>>> [34674.119607] CIFS: VFS: Error connecting to socket. Aborting operation.
>>>> [34674.119626] CIFS: VFS: cifs_mount failed w/return code = -115
>>>>
>>>> TIA
>>>
>>> sudo mount -t cifs -o rw,noperm,credentials=/credentials,vers=3 //192.168.2.102/shared /smurf
>>>
>>> You're connecting to Windows 10, so vers=3 might be a start.
>>>
>>> Paul
>>>
>>>
>>
>> No, I am not connecting to Windows on the target machine, just use the settings on my work machine's smb.conf that provides access to both Win-XP and Win-10.
>> This is what smb.conf on both machines includes:
>>
>> client min protocol = NT1
>> client max protocol = SMB3
>>
>> server min protocol = NT1
>> server max protocol = smb3
>>
>> It works fine on the work machine.
>>
>> And Dan, I can ping and ssh to the backuo machine. I just want use a script that until two years ago, ran virtually unchanged for nigh on 15 - 20 years.
>> I am a bit long in the tooth so never change for change sake.
>>
>> ATB Alan
>>
>
> I can now mount samba shares but cannot see why my backup command is sending the data to the mount point rather than to the share mounted there.
>
> The mount statement is:
>
> sudo mount -vvv -t cifs //192.168.1.66/alan/ /spare/churchill/alan/ -o rw,noperm,username=alan,password=<my_password>,vers=1.0,uid=alan
>
> The test backup command is:
>
> rsync -rlptD /home/alan/Scripts /spare/churchill/alan/
>
> I can't get my head round it.

On my mount command, I didn't use trailing slashes.

I suspect some amount of "slash testing" might be needed.

You know how picky syntax can be for stuff like this.

Paul

On Thu, 3 Aug 2023 18:02:19 -0400
Paul <nospam@needed.invalid> wrote:

> On 8/3/2023 3:55 PM, pinnerite wrote:
> > On Fri, 28 Jul 2023 20:20:57 +0100
> > pinnerite <pinnerite@gmail.com> wrote:
> >
> >> On Fri, 28 Jul 2023 06:41:37 -0400
> >> Paul <nospam@needed.invalid> wrote:
> >>
> >>> On 7/27/2023 4:54 PM, pinnerite wrote:
> >>>> For ten years regularly backed up the data partition of my work machine to a backup machine. Then the backup machine had to be mothballed prior to a downsizing move.
> >>>>
> >>>> Two years later I want to deploy the same script.
> >>>>
> >>>> First it mounts the remote shares and then runs a series of rsync commands. Except that it now no longer works. It fails at the mpint stage.
> >>>>
> >>>> After reading man pages and searching the www I cannot fathom why.
> >>>>
> >>>> This is the first mount line.:
> >>>>
> >>>> sudo mount -t cifs -o rw,noperm,credentials=/home/alan/.smbcredentials,vers=1.0 //192.168.1.66/alan/ /spare/churchill/alan/
> >>>>
> >>>> When I try to run it, it returns:
> >>>>
> >>>> mount error(115): Operation now in progress
> >>>> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
> >>>>
> >>>> dmesg returns:
> >>>>
> >>>> [34663.775002] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
> >>>> [34663.775010] CIFS: Attempting to mount \\192.168.1.66\alan
> >>>> [34674.119607] CIFS: VFS: Error connecting to socket. Aborting operation.
> >>>> [34674.119626] CIFS: VFS: cifs_mount failed w/return code = -115
> >>>>
> >>>> TIA
> >>>
> >>> sudo mount -t cifs -o rw,noperm,credentials=/credentials,vers=3 //192.168.2.102/shared /smurf
> >>>
> >>> You're connecting to Windows 10, so vers=3 might be a start.
> >>>
> >>> Paul
> >>>
> >>>
> >>
> >> No, I am not connecting to Windows on the target machine, just use the settings on my work machine's smb.conf that provides access to both Win-XP and Win-10.
> >> This is what smb.conf on both machines includes:
> >>
> >> client min protocol = NT1
> >> client max protocol = SMB3
> >>
> >> server min protocol = NT1
> >> server max protocol = smb3
> >>
> >> It works fine on the work machine.
> >>
> >> And Dan, I can ping and ssh to the backuo machine. I just want use a script that until two years ago, ran virtually unchanged for nigh on 15 - 20 years.
> >> I am a bit long in the tooth so never change for change sake.
> >>
> >> ATB Alan
> >>
> >
> > I can now mount samba shares but cannot see why my backup command is sending the data to the mount point rather than to the share mounted there.
> >
> > The mount statement is:
> >
> > sudo mount -vvv -t cifs //192.168.1.66/alan/ /spare/churchill/alan/ -o rw,noperm,username=alan,password=<my_password>,vers=1.0,uid=alan
> >
> > The test backup command is:
> >
> > rsync -rlptD /home/alan/Scripts /spare/churchill/alan/
> >
> > I can't get my head round it.
>
> On my mount command, I didn't use trailing slashes.
>
> I suspect some amount of "slash testing" might be needed.
>
> You know how picky syntax can be for stuff like this.
>
> Paul
>
There is an old joke about a drunk looking for a sixpence (remember those) near a lamp post. A kindly policeman joins him. After a fruitless search, the copper asks "Are you sure you lost it over here?"

"No" says the drunk. "I lost it in that dark alley but its lighter over here".

That sums up what I have been doing. Because I could see the contents of the copy at the mount point, I assumed that it wasn't getting to the target but of course it had. Last night I discovered that I could see it apparently in both places and the penny dropped.

Sorry to be such a pain and yes Paul, you are right about the trailing slashes. I kept changing things round but I will test back later today.

Thank you.

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

On 2023-07-28, pinnerite wrote:
> [...]
> And Dan, I can ping and ssh to the backuo machine. I just want use a
> script that until two years ago, ran virtually unchanged for nigh on
> 15 - 20 years.
> I am a bit long in the tooth so never change for change sake.

Well, it's "change for the sake of not needing CIFS mounts" moreso than
"...for the sake of change".

Personally, I've found that just letting rsync use ssh is overall easier
and less error-prone as computers change over time -- have had this
particular one for near on a decade now, with only minor changes,
generally due to learning more about rsync options.

Long story short, instead of the script needing to handle:

(1) mount -t cifs [...] /spare/churchill/user
(2) rsync [opts] /source /spare/churchill/user

it just has to run the one command:

(1) rsync [opts] /source user@host:/path/to/dest

Well, with the following caveats:

- "user" on the remote host has write permissions to "/path/to/dest"
- you're okay with either
(A) inputting the password for "user" when the script runs OR
(B) setup an ssh key (with or without passphrase, at your
discretion)

That being said, since I think I saw a post with '[solved]' in the
title, I guess you figured out whatever oddness SMB/CIFS was
introducing, and you're good to go now.

--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860