Mount error 255 - Исправление ошибок и поиск оптимальных решений проблем

Setup: 3 node swarm cluster
Steps:

Try to start container using shared volume on master
Mount fails with Failed to mount vFile volume. Error: exit status 255

root@u-1:~# docker run --rm -it -v doesitwork2:/x busybox
docker: Error response from daemon: error while mounting volume '/mnt/vfile/doesitwork2/': VolumeDriver.Mount: Failed to mount vFile volume. Error: exit status 255.
root@u-1:~# vi /var/log/vfile.log 
root@u-1:~# docker volume inspect doesitwork2
[
    {
        "Driver": "vfile:latest",
        "Labels": {},
        "Mountpoint": "/mnt/vfile/doesitwork2/",
        "Name": "doesitwork2",
        "Options": {},
        "Scope": "global",
        "Status": {
            "Clients": null,
            "File server Port": 0,
            "Global Refcount": 0,
            "Service name": "",
            "Volume Status": "Ready"
        }
    }
]
root@u-1:~# ip addr
...
    inet 172.16.111.131/24 brd 172.16.111.255 scope global ens160

From vfile.log

2017-08-25 21:11:25.936768801 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 21:11:25.942214739 +0000 UTC [WARNING] No service returned with name doesitwork2.
2017-08-25 21:11:25.972762754 +0000 UTC [INFO] Updating port and file service name for doesitwork2
2017-08-25 21:12:21.717058057 +0000 UTC [INFO] VolumeDriver Get: doesitwork2
2017-08-25 21:12:21.95763916 +0000 UTC [INFO] Mounting volume name=doesitwork2
2017-08-25 21:12:22.012096338 +0000 UTC [INFO] Before AtomicIncr
2017-08-25 21:12:23.060467684 +0000 UTC [INFO] Watcher on global refcount returns event type=PUT
2017-08-25 21:12:24.076707491 +0000 UTC [INFO] Attempting to change volume state to Mounting
2017-08-25 21:12:29.126624469 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 21:12:29.155411432 +0000 UTC [INFO] Updating port and file service name for doesitwork2
2017-08-25 21:12:30.094439552 +0000 UTC [INFO] Volume state mounted, prepare to mounting locally
2017-08-25 21:12:30.095608168 +0000 UTC [INFO] Get info for mounting name=doesitwork2 Port=30000 ServiceName=vFileServerdoesitwork2
2017-08-25 21:12:30.116197187 +0000 UTC [INFO] Mounting volume with options volume name=doesitwork2 arguments=[-t cifs -o username=root,password=badpass,port=30000,vers=3.0 //172.16.111.131/share1 /mnt/vfile/doesitwork2/]
2017-08-25 21:12:33.417475677 +0000 UTC [ERROR] Mount failed: output="mount: mounting //172.16.111.131/share1 on /mnt/vfile/doesitwork2/ failed: Host is unreachablen" error="exit status 255" volume name=doesitwork2
2017-08-25 21:12:34.473825803 +0000 UTC [INFO] Watcher on global refcount returns event type=PUT
2017-08-25 21:12:34.474049185 +0000 UTC [ERROR] error="Failed to mount vFile volume. Error: exit status 255." name=doesitwork2
2017-08-25 21:12:34.474067351 +0000 UTC [ERROR] Failed to mount name=doesitwork2 error="Failed to mount vFile volume. Error: exit status 255."
2017-08-25 21:12:34.474080549 +0000 UTC [INFO] Detaching doesitwork2 - it is not used anymore
2017-08-25 21:12:35.474755108 +0000 UTC [INFO] Attempting to change volume state to Unmounting
2017-08-25 21:12:40.518041793 +0000 UTC [INFO] Checking status of file server container...
2017-08-25 21:12:40.523266418 +0000 UTC [WARNING] No service returned with name doesitwork2.
2017-08-25 21:12:40.54726316 +0000 UTC [INFO] Updating port and file service name for doesitwork2
2017-08-25 21:13:53.522887647 +0000 UTC [INFO] VolumeDriver Get: doesitwork2

CC / @luomiao @shivanshu21

Источник

View Full Version : [lubuntu] Can’t share mounted ntfs disk on network

VanillaMozilla

August 29th, 2010, 02:08 PM

I have samba installed. I also have a Windows NTFS disk mounted on Ubuntu. To share the file, I migrate to the folder with the file manager, right click on it and select «Sharing Options». I get the message

The disk is mounted by the system with the line

/dev/sda2 /mnt/Windisk ntfs-3g defaults 0 0
in fstab.

Here’s what I’ve tried:
=========================
Adding the line to fstab and rebooting does not solve the problem. I still get error 255, but without the advice.

Changing ownership does not help. I tried
sudo chown -v root:sambashare /mnt/Windisk/<path>
and
sudo chown -v mylogin:sambashare /mnt/Windisk/<path>
changed ownership of `/mnt/Windisk/<path>’ to mylogin:sambashare

Chown confirms the change, but right clicking on file, Properties tab still shows root owns file, and I still get an error 255.

Morbius1

August 29th, 2010, 02:30 PM

‘net usershare’ returned error 255: net usershare add:
cannot share path /mnt/Windisk/<path> as we are restricted to only sharing directories we own. Ask the administrator to add the line «usershare owner only = false» to the [global] section of the smb.conf to allow this.There’s two ways to fix this, one of which is offered in what is probably the best written error message in all of computing

When you added:

usershare owner only = falseDid you do it without quotes?
And did you save smb.conf and restart the samba daemon:

sudo service smbd restart

VanillaMozilla

August 30th, 2010, 03:43 AM

Yes, I added it without quotes, and I ran testparm to make sure the line worked. I rebooted the computer, so there is no question that samba restarted. I still got error 255, but this time I got it without the advice to add that line to the file.

EDIT: It turns out that it doesn’t work unless the share name is the same as the directory name.

But there’s another problem. I can’t view it on the Ubuntu client. It’s asking for a password AND a domain name. There should be no password and there is no domain — it’s workgroup WORKGROUP. The form keeps filling in domain «MSHOME». I have all the passwords and it doesn’t work with any of them.

Checking the box «Allow others to create and delete files in this folder» makes no difference.

Morbius1

August 30th, 2010, 04:21 PM

Post the output of these 3 commands please:

net usershare info
sudo net usershare info
testparm -s

VanillaMozilla

August 30th, 2010, 05:11 PM

Interesting. Something is going on here, for sure. By way of explanation, I tried to name the share «thunderprof», but I had to mount it as «profiles». ls -Fal shows I am the owner of «profiles», but root is the owner of «thunderprof».

:~$ net usershare info
[profiles]
path=/mnt/Windisk/DocumentsAndSettings/Common/ApplicationData/Thunderbird/Profiles
comment=
usershare_acl=Everyone:R,
guest_ok=n

:~$ sudo net usershare info
info_fn: file /var/lib/samba/usershares/thunderprof is not a well formed usershare file.
info_fn: Error was Path is not a directory.

:~$ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section «[printers]»
Processing section «[print$]»
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
server string = %h server (Samba, Ubuntu)
map to guest = Bad User
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
unix password sync = Yes
syslog = 0
log file = /var/log/samba/log.%m
max log size = 1000
dns proxy = No
usershare allow guests = Yes
usershare owner only = No
panic action = /usr/share/samba/panic-action %d

Morbius1

August 30th, 2010, 05:24 PM

:~$ net usershare info
[profiles]
path=/mnt/Windisk/DocumentsAndSettings/Common/ApplicationData/Thunderbird/Profiles
comment=
usershare_acl=Everyone:R,
guest_ok=n

:~$ sudo net usershare info
info_fn: file /var/lib/samba/usershares/thunderprof is not a well formed usershare file.
info_fn: Error was Path is not a directory.

I tried to name the share «thunderprof», but I had to mount it as «profiles»(1) You did a «gksu nautilus» somewhere along the line and creates a Nautilus-share for «thunderprof». Then you created another one under your own username.

I would go back in as gksu nautilus and remove the thunderprof share to clear this up.

(2) The reason the client is asking for authentication is because you have the share set to not allow guests. Go back into nautilus and check the «allow guests» option.

VanillaMozilla

August 30th, 2010, 06:23 PM

(1) You did a «gksu nautilus» somewhere along the line and creates a Nautilus-share for «thunderprof». Then you created another one under your own username.

I would go back in as gksu nautilus and remove the thunderprof share to clear this up.
Yikes! Nonorthogonal tools and paths to be undone.

Yes, that’s correct, I did run gksudo nautilus. But now I can’t find the share. The mount point doesn’t show any sharing, and I can’t get to the actual ntfs disk (only the mount point). Also, Nautilus won’t show me the path in text form when I start it from gksudo! gksudo shares-admin shows no shares (I do have «profiles» turned off). Is there a file I can edit?

(2) The reason the client is asking for authentication is because you have the share set to not allow guests. Go back into nautilus and check the «allow guests» option.
OK, that seems to work.

But how am I going to clean up thunderprof?

VanillaMozilla

August 30th, 2010, 06:35 PM

Oh, wait, I see the problem. thunderprof refers to a mount point that has been changed. It was on /media, now it’s on /mnt.

Stand by….

VanillaMozilla

August 30th, 2010, 06:54 PM

Note to self (and anyone else who enjoys masochism)

OK, this is defying a fix for now, and I’m out of time. I tried just renaming thunderprof and the system just used the renamed file!

I’m afraid to delete it outright, for fear of breaking something else. It’s write protected.

And just changing the mount point and rebooting failed (user error?). I don’t know. I’ll try later.

Morbius1

August 30th, 2010, 09:00 PM

Your making this too complicated. Let’s try a different path.

Nautilus-shares creates share definitions at the following location:

/var/lib/samba/usersharesOpen nautilus as root:

gksu nautilusAnd go to /var/lib/samba/usershares

Once you’re there you should see 2 files:

profiles
thunderprofIf you doulble click on thunerprof you will see something like this:

#VERSION 2
path=/media/Windisk/DocumentsAndSettings/Common/ApplicationData/Thunderbird/Profiles
comment=
usershare_acl=S-1-1-0:F
guest_ok=yIt’s just a config file that tells samba what to do with the folder. Just delete the file — it’s not deleting the source.

VanillaMozilla

August 31st, 2010, 12:13 AM

OK, that worked. (Actually, I wasn’t making it so complicated. I just needed to move it out of the directory or delete it instead of renaming it.)

Thanks very much for all your accurate diagnosis.

*************************
EDIT: Darn. There’s yet another problem. The client doesn’t recognize the share from a command line. This is going in circles. I’ll work on it maybe tomorrow evening and see if I can either solve it or define the problem better.

VanillaMozilla

September 1st, 2010, 03:59 AM

OK, here’s the big problem.

thunderprof is shared, but I can’t read it from the mount point on the client computer.
ls /mnt/thunderprof shows no files.
Nautilus shows no files in /mnt/thunderprof , but shows the files in smb://computername/thunderprof

mount -a gives error message:
mount error: could not resolve address for <computername>: No address associated with host name
No ip address specified and hostname not found.

Any ideas? I thought I had this solved once. I need command-line access for the Thunderbird configuration file «profiles.ini».

/etc/fstab has the line
//computername/thunderprof /mnt/thunderprof cifs guest,uid=1000,iocharset=utf8, codepage=cp850 0 0

Источник

yes, i did it before , no clue what is wrong

Kueche:~/.config/system.d # systemctl enable storage-recordings.mount

Kueche:~/.config/system.d # systemctl start storage-recordings.mount

Job for storage-recordings.mount failed.

See «systemctl status storage-recordings.mount» and «journalctl -xe» for details.

● storage-recordings.mount — cifs mount script

Loaded: loaded (/storage/.config/system.d/storage-recordings.mount; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Sun 2017-08-27 14:28:19 CEST; 11s ago

Where: /storage/recordings

What: //192.168.178.3/TVrecordings

Process: 1114 ExecMount=/usr/bin/mount //192.168.178.3/TVrecordings /storage/recordings -t cifs -o username=xxx,password=xxx,rw

(code=exited, status=255)

Aug 27 14:28:19 Kueche systemd[1]: Mounting cifs mount script…

Aug 27 14:28:19 Kueche systemd[1]: storage-recordings.mount: Mount process exited, code=exited status=255

Aug 27 14:28:19 Kueche systemd[1]: Failed to mount cifs mount script.

Aug 27 14:28:19 Kueche systemd[1]: storage-recordings.mount: Unit entered failed state.

JOURNALCTL :

Aug 27 14:29:10 Kueche kernel: rtc-pcf8563 1-0051: pcf8563_get_datetime: read error

Aug 27 14:29:11 Kueche kernel: i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)