[SERVER-34258] Error from mount_drives.sh on Windows Created: 02/Apr/18  Updated: 29/Oct/23  Resolved: 31/May/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.7, 4.0.2, 4.1.1

Type: Bug Priority: Minor - P4
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-33695 Include the loop name in the before a... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0, v3.6
Sprint: TIG 2018-06-04
Participants:
Story Points: 5

 Description   

The setfacl: No such file or directory error is observed when running mount_drives.sh on a windows remote instance:

[2018/04/02 12:27:48.862] Return code: 0 for command ['buildscripts/remote_operations.py', '--verbose', '--userHost', 'Administrator@10.122.9.230', '--sshConnectionOptions', '-i /cygdrive/c/data/mci/d50ca8d39e058ec1000e48604476e076/powercycle.pem -o GSSAPIAuthentication=no -o CheckHostIP=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectTimeout=20 -o ConnectionAttempts=20', '--retries', '10', '--commands', " bash mount_drives.sh -d 'd' -t ntfs -l 'e' -u Administrator:None; ls -ld /data/db /log; df; mount"]
[2018/04/02 12:27:48.862] Warning: Permanently added '10.122.9.230' (ECDSA) to the list of known hosts.
[2018/04/02 12:27:48.862] Looking for drive 'd' to mount data
[2018/04/02 12:27:48.862] Looking for drive 'd' to mount data
[2018/04/02 12:27:48.862] Looking for drive 'd' to mount data
[2018/04/02 12:27:48.862] Looking for drive 'd' to mount data
[2018/04/02 12:27:48.862] Found drive
[2018/04/02 12:27:48.862] Junction created for c:\data <<===>> d:\data
[2018/04/02 12:27:48.862] setfacl: No such file or directory
[2018/04/02 12:27:48.862] ls: cannot access '/data/db': No such file or directory
[2018/04/02 12:27:48.862] ls: cannot access '/log': No such file or directory
[2018/04/02 12:27:48.862] Filesystem     1K-blocks     Used Available Use% Mounted on
[2018/04/02 12:27:48.862] C:/cygwin       67106812 49203748  17903064  74% /
[2018/04/02 12:27:48.862] D:             104855548    95076 104760472   1% /cygdrive/d
[2018/04/02 12:27:48.862] C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
[2018/04/02 12:27:48.862] C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
[2018/04/02 12:27:48.862] C:/cygwin on / type ntfs (binary,auto)
[2018/04/02 12:27:48.862] C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
[2018/04/02 12:27:48.862] D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto)



 Comments   
Comment by Githook User [ 10/Aug/18 ]

Author:

{'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}

Message: SERVER-34258 Fix error in mount_drives.sh on Windows

(cherry picked from commit 1bbdb461b5ee44886e25dc0b44df2859471e6ed3)
Branch: v3.6
https://github.com/mongodb/mongo/commit/4e88e120caa555333ad7e611fea543fdfe3c82fa

Comment by Githook User [ 10/Aug/18 ]

Author:

{'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}

Message: SERVER-34258 Fix error in mount_drives.sh on Windows

(cherry picked from commit 1bbdb461b5ee44886e25dc0b44df2859471e6ed3)
Branch: v4.0
https://github.com/mongodb/mongo/commit/073e9af2911b55850157b6a0d6be3543814c2bc7

Comment by Githook User [ 31/May/18 ]

Author:

{'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}

Message: SERVER-34258 Fix error in mount_drives.sh on Windows
Branch: master
https://github.com/mongodb/mongo/commit/1bbdb461b5ee44886e25dc0b44df2859471e6ed3

Comment by Jonathan Abrahams [ 19/Apr/18 ]

Surprisingly the tests seem to work, but I need to look further into it to see how that's possible.

Comment by Max Hirschhorn [ 19/Apr/18 ]

jonathan.abrahams, what is the impact of this issue? Does the powercycle task fail if it cannot mount the drives?

Generated at Thu Feb 08 04:36:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.