Error mounting DFS on CentOS 6.4

Hi,
I'm having a few issues mounting a windows DFS share on a centos 6.4 server. Initially I followed the instructions on this blog but I'm still getting the error below.
http://mikemstech.blogspot.co.uk/201...-in-linux.html
I've installed/updated cifs-utils and keyutils and added the lines to request-key.conf.
We're now getting the error below.
/]sudo mount -t cifs //domain.dev.com/share/content /mnt/testdfs -o username=domain/user
Password:
mount error(40): Too many levels of symbolic links
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Thanks!

Hi,
Sorry I do not have enough knowledge about Linux commands. I searched for the error and some people mentioned to use absolute path in command line. It is recommended to post the question to a Linux forum for further information.
If you have any feedback on our support, please send to [email protected]

Similar Messages

Unable to mount dfs volume from Windows Server 2008 R2

I am trying to use Finder|Go|Connect to Server to connect to a DFS volume shared by a Windows Server 2008 R2 machine. I get the following errors:
A dialog box that says, "There was a problem connecting to the server "server name". Contact your system administrator for more information"
Messages in the log:
PM kernel: smb_ntstatus_error_to_errno: Couldn't map ntstatus (0xc0000225) to errno returning EIO
PM NetAuthSysAgent: checkForDfsReferral: mounting dfs url failed , syserr = Input/output error
PM NetAuthSysAgent: smb_mount: mount failed to <server name>, syserr = Input/output error
I've seen a reference to this article (https://discussions.apple.com/thread/3258472) to fix similar problems but that seems only to apply to Mac-based servers not Windows servers.
I called AppleCare but they said they are unable to troubleshoot a problem originating on a Windows Server.
The Mac is running 10.7.4 but the problem happens on 10.7.3 as well.
I can connect to non-DFS volumes from other Windows Servers with no issue.

After some more digging around I found out that it works when using the cifs: prefix instead of the smb: prefix in Finder|Go|Connect to Server.
So instead of using the name smb://servername.company.com I use the name cifs://servername.company.com.

[SOLVED] Error mounting an ISO file located in an EncFS folder

I have some multimedia files inside an EncFS folder (decrypted via cryptkeeper).
When trying to loop mount the ISO files I get:
mount: foo.iso: failed to setup loop device: Permission denied
There's no error mounting the same ISO from a «regular» FS.
Is there a way around this?
Last edited by JoaoVidal (2014-02-24 06:36:42)

unSpawn at linuxquestions.org answered:
See 'man encfs': the warning at "--public" and 'man fuse': "allow_other"
Without setting the option 'public' in encfs or 'allow_other' is fuse, not even root can access the encfs mount and therefore mounting fails (sudo mount...).
Also, cryptkeeper now has the preference "Allow other users to access mounted folders" which gives exactly this kind of permission.

[solved] docker: Error mounting: invalid argument

I'm relatively new to using docker. When I had initially set it up (weeks ago) I was able to pull and manipulate containers. Today I came back to my docker project and now I can't even successfully pull an image.
$ docker pull ubuntu:14.04
ubuntu:14.04: The image you are pulling has been verified
511136ea3c5a: Download complete
511136ea3c5a: Error downloading dependent layers
d497ad3926c8: Downloading [============================> ] 115.7 MB/201.6 MB 7s
e791be0477f2: Download complete
3680052c0f5c: Download complete
22093c35d77b: Download complete
5506de2b643b: Download complete
5506de2b643b: Error pulling image (14.04) from ubuntu, endpoint: https://registry-1.docker.io/v1/, Error mounting '/dev/mapper/dock5506de2b643b: Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d26982014/11/14 20:14:12 Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
This is the log:
$ journalctl -e
Nov 14 20:24:47 example.com docker[18225]: 2014/11/14 20:24:47 docker daemon: 1.3.1 4e9bbfa; execdriver: native; graphdriver:
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job serveapi(fd://)
Nov 14 20:24:47 example.com docker[18225]: [info] Listening for HTTP on fd ()
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job init_networkdriver()
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] -job init_networkdriver() = OK (0)
Nov 14 20:24:47 example.com docker[18225]: 2014/11/14 20:24:47 WARNING: Your kernel does not support cgroup swap limit.
Nov 14 20:24:47 example.com docker[18225]: [info] Loading containers:
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 07b2a034632f0ddb8f01ebdcf1c0cc4ba0ade7a6d927b544754b44aa3b58f877: open /var/lib/docker/containers/07b2a034632f0ddb8f01ebdcf1c0cc4ba0ade7a6d927b544754b44aa3b58f877/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 0bb0b50393dd951caeaa8386eb8ec8be1cc60e0822167ebed4dfdce9724b618c: open /var/lib/docker/containers/0bb0b50393dd951caeaa8386eb8ec8be1cc60e0822167ebed4dfdce9724b618c/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 15732a4b2a97b91a2c590cab260f91dde7708b50059942221d349a778f94c892: open /var/lib/docker/containers/15732a4b2a97b91a2c590cab260f91dde7708b50059942221d349a778f94c892/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 17b4471d4b031cd24feba6a2dc46e1524bcd9a6bb3b03342a642a5968caff3fa: open /var/lib/docker/containers/17b4471d4b031cd24feba6a2dc46e1524bcd9a6bb3b03342a642a5968caff3fa/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 20686bda195d61f2c76c3e3c809f8b07df9b830d8bc650e10593e1863c82b7f3: open /var/lib/docker/containers/20686bda195d61f2c76c3e3c809f8b07df9b830d8bc650e10593e1863c82b7f3/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 2fe7db68f38445c8ac0124be87174f66ccd1729880c5fa94b93d77ac0aa547fe: open /var/lib/docker/containers/2fe7db68f38445c8ac0124be87174f66ccd1729880c5fa94b93d77ac0aa547fe/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 31b34a085e90849bcffd50c5f7b41d93849d494913448a92849c5d621555251d: open /var/lib/docker/containers/31b34a085e90849bcffd50c5f7b41d93849d494913448a92849c5d621555251d/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 3484c3c05947051eea53865c973100d493e7ec495b3d7a5d4fbc1e5096196733: open /var/lib/docker/containers/3484c3c05947051eea53865c973100d493e7ec495b3d7a5d4fbc1e5096196733/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 3ed275efb25789d6c9e18bf36e46f437fbdb21f3ffd7a93cb4525610737441f0: open /var/lib/docker/containers/3ed275efb25789d6c9e18bf36e46f437fbdb21f3ffd7a93cb4525610737441f0/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 4503890c72d2f728e315b6ecae05fbabba85a3f959898a52df800f6fa22ca094: open /var/lib/docker/containers/4503890c72d2f728e315b6ecae05fbabba85a3f959898a52df800f6fa22ca094/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 4db4ed2fbac1b442d770bcd325937508d2b190caa766f4ddef4f21628a953ea2: open /var/lib/docker/containers/4db4ed2fbac1b442d770bcd325937508d2b190caa766f4ddef4f21628a953ea2/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 56f36a11482d6b9c513cbb819d6c67a768bd47dc4c02bd0de62c61365b6ba363: open /var/lib/docker/containers/56f36a11482d6b9c513cbb819d6c67a768bd47dc4c02bd0de62c61365b6ba363/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 5b254c1c2344f61ab6bf6b338b22150cccd6ebd04407f3d00d6b5b3e37810d4f: open /var/lib/docker/containers/5b254c1c2344f61ab6bf6b338b22150cccd6ebd04407f3d00d6b5b3e37810d4f/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 73fd6f0edadcf67fcdad7a397784275db013df085e648230b5818f0e68e3f48c: open /var/lib/docker/containers/73fd6f0edadcf67fcdad7a397784275db013df085e648230b5818f0e68e3f48c/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 7ad8ad079db979b156af858cd36b908434157efd43e8cbc13677fa287bdf4da0: open /var/lib/docker/containers/7ad8ad079db979b156af858cd36b908434157efd43e8cbc13677fa287bdf4da0/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 82a2e14c00dd73e2df1d78c45a0e576d52637c5dc422c32182ded365d6893167: open /var/lib/docker/containers/82a2e14c00dd73e2df1d78c45a0e576d52637c5dc422c32182ded365d6893167/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 86572f605d7990f173875853bcfbdfe3f909c9b26f439378ab73d561e0e735eb: open /var/lib/docker/containers/86572f605d7990f173875853bcfbdfe3f909c9b26f439378ab73d561e0e735eb/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container 9eecdb0bf364f80cc88532832221da9de86c10a31b24660fdce8b68c79504a88: open /var/lib/docker/containers/9eecdb0bf364f80cc88532832221da9de86c10a31b24660fdce8b68c79504a88/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container a0920424bc83bffbc980f39f6dad17c865f84de1c3508a01d3c1298870f608c1: open /var/lib/docker/containers/a0920424bc83bffbc980f39f6dad17c865f84de1c3508a01d3c1298870f608c1/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container be228e991ffba0d423bb8bdca22fda9e318b7084bae53d765212bed6612e6b01: open /var/lib/docker/containers/be228e991ffba0d423bb8bdca22fda9e318b7084bae53d765212bed6612e6b01/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container e01b5a18f7c252f9c06e6d2dc9720baa184bc803e52aa68e9253372854382213: open /var/lib/docker/containers/e01b5a18f7c252f9c06e6d2dc9720baa184bc803e52aa68e9253372854382213/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container f00aff0df390b90f0a739430b4896cd67afc256a1c657271caf989fd3791ac91: open /var/lib/docker/containers/f00aff0df390b90f0a739430b4896cd67afc256a1c657271caf989fd3791ac91/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .[error] daemon.go:321 Failed to load container f271529997f7479b5b6f65ccdd21d6b91445bbb31a3b253e95b1cf6ad6468c37: open /var/lib/docker/containers/f271529997f7479b5b6f65ccdd21d6b91445bbb31a3b253e95b1cf6ad6468c37/config.json: no such file or directory
Nov 14 20:24:47 example.com docker[18225]: .......................[info] : done.
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job acceptconnections()
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] -job acceptconnections() = OK (0)
Nov 14 20:24:47 example.com docker[18225]: [info] POST /v1.15/images/create?fromImage=ubuntu%3A14.04
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job pull(ubuntu, 14.04)
Nov 14 20:24:47 example.com docker[18225]: [0687b0f9] +job trust_update_base()
Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] -job trust_update_base() = OK (0)
Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] +job trust_key_check(/library/ubuntu)
Nov 14 20:24:48 example.com docker[18225]: [0687b0f9] -job trust_key_check(/library/ubuntu) = OK (0)
Nov 14 20:24:48 example.com kernel: device-mapper: thin: Creation of new snapshot 0 of device 0 failed.
Nov 14 20:24:48 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:48 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:24:48 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:48 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:24:52 example.com systemd-udevd[298]: error: /dev/dm-1: No such device or address
Nov 14 20:24:53 example.com docker[18225]: [error] pull.go:151 Error from V2 registry: Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
Nov 14 20:24:57 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:57 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:24:57 example.com kernel: JBD2: no valid journal superblock found
Nov 14 20:24:57 example.com kernel: EXT4-fs (dm-1): error loading journal
Nov 14 20:25:02 example.com systemd-udevd[298]: error: /dev/dm-1: No such device or address
Nov 14 20:25:03 example.com docker[18225]: Error pulling image (14.04) from ubuntu, Error mounting '/dev/mapper/docker-8:98-380441-511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158' on '/var/lib/docker/devicemapper/mnt/511136ea3c5a64f264b78b5433614aec563103b4d4702f3ba7d4d2698e22c158': invalid argument
Nov 14 20:25:03 example.com docker[18225]: [0687b0f9] -job pull(ubuntu, 14.04) = ERR (1)
Nov 14 20:25:03 example.com docker[18225]: panic: runtime error: invalid memory address or nil pointer dereference
Nov 14 20:25:03 example.com docker[18225]: [signal 0xb code=0x1 addr=0x20 pc=0x6bb9ac]
Nov 14 20:25:03 example.com docker[18225]: goroutine 58 [running]:
Nov 14 20:25:03 example.com docker[18225]: runtime.panic(0xa6bc20, 0x1087c93)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/runtime/panic.c:279 +0xf5
Nov 14 20:25:03 example.com docker[18225]: bufio.(*Writer).flush(0xc2082228c0, 0x0, 0x0)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/bufio/bufio.go:530 +0xdc
Nov 14 20:25:03 example.com docker[18225]: bufio.(*Writer).Flush(0xc2082228c0, 0x0, 0x0)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/bufio/bufio.go:519 +0x39
Nov 14 20:25:03 example.com docker[18225]: net/http.(*response).Flush(0xc20816fa40)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:885 +0x38f
Nov 14 20:25:03 example.com docker[18225]: created by net/http.(*Transport).dialConn
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:601 +0x957
Nov 14 20:25:03 example.com docker[18225]: goroutine 118 [runnable]:
Nov 14 20:25:03 example.com docker[18225]: net/http.(*persistConn).readLoop(0xc2080d7130)
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:868 +0x829
Nov 14 20:25:03 example.com docker[18225]: created by net/http.(*Transport).dialConn
Nov 14 20:25:03 example.com docker[18225]: /usr/lib/go/src/pkg/net/http/transport.go:600 +0x93f
(snipping several dozen lines of stack trace in the middle there)
The search results for various permutations of "docker error mount invalid argument dm" are badly washed out so I wasn't able to find any helpful leads; nor was I able to find anything relevant in the docker issue list. I tried re-installing docker (by running pacman -Rns docker and then pacman -S docker hoping that it was a config setting I could nuke & pave but this had no effect. I then ran the following:
$ dmsetup ls
docker-8:98-380441-pool (254:0)
followed by dmsetup remove docker-8:98-380441-pool and attempted the pull again. No difference.
I'm convinced this is not a docker bug but a misconfiguration of my system, but the error provided ("error mounting .... invalid argument") is rather opaque and I'm stuck with what to try next.
Any suggestions would be appreciated.
Last edited by cmtonkinson (2014-11-15 11:41:47)

Well, rm -rf /var/lib/docker did it!
I was unable to remove /var/lib/docker/devicemapper ("device or resource busy") but that doesn't seem to matter - as you suggest docker reconfigured itself. Thanks for the tip!
For the record (should have posted this previously):
$ docker info
Containers: 1
Images: 7
Storage Driver: devicemapper
Pool Name: docker-8:98-380441-pool
Pool Blocksize: 65.54 kB
Data file: /var/lib/docker/devicemapper/devicemapper/data
Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
Data Space Used: 598.3 MB
Data Space Total: 107.4 GB
Metadata Space Used: 1.18 MB
Metadata Space Total: 2.147 GB
Library Version: 1.02.90 (2014-09-01)
Execution Driver: native-0.2
Kernel Version: 3.17.2-1-ARCH
Operating System: Arch Linux
WARNING: No swap limit support
$ docker --version
Docker version 1.3.1, build 4e9bbfa

After Effects Alert when opening (Error: Mount Point list is empty)

I am so confused right now. I have searched everywhere for a solution to no avail. I have a brand new Mac Pro 2.7 Ghz 12-core intel Xeon e5 with 32 gigs of ram. I installed Reelsmart's Motion blur and when I tried to re-open After Effects I got an After Efects Alert that reads.
Last log message was: <140735179719440> <EAMountPoints> <0> Error: mount point list is empty
Generating crash log, which may take a few minutes.
Can anyone help please! I'm on a tight deadline and I'm grounded.
Thank you, thank you!!

What exact version of AE (down to the last decimal point)?

ASM configuration error, mount failed

When running "oracleasm configure", I am getting the following error:
Mounting ASMlib driver filesystem: mount: block device oracleasmfs is write-protected, mounting read-only
mount: cannot mount block device oracleasmfs read-only
Unable to mount ASMlib driver filesystem
[FAILED]
I am using RedHat 4.0 kernel 2.6.9-22 on x86_64 SMP and have downloaded the relevant ASM rpms.
Any ideas?
Message was edited by:
[email protected]

After reading some more documents, I found out that you actually need to partition the harddrive. I probably will partition it using a software like magic partition. This is different than Redhat Linux 9.0 Personal.
Thank you,
Victor

Virtual Box error: error mounting /dev/sda1 on /mnt

Hello folks,
After getting fed up with Ubuntu's bloated setup, I was trying to switch to Arch linux. But before that I wanted to try it in Virtual Box. I was using Arch Linux Core image for this. But after setting up file system and mountpoint I am getting this error:
error mounting /dev/sda1 on /mnt
The steps I followed:
1. Source: Core local
2. Editor: Nano
3. Clock: As usual
4. Prepare hard drive:
a) Manually Partition (as this is what I will be doing during actual installation)
b) /dev/sda
c) New partition on all space available on virtual machine, making it primary, bootable, Type: Linux Extended (option 85).
d) Write partition and Quit and Done
5. Manually configure block device, filesystems and mountpoints.
a) dev
b) Do not recreate file system.
c) Set ext4 format and mount point, ignoring swap space or seperate /boot partition.
d) Now when I goto next step as Done, It gives an error : Error mounting /dev/sda1 on /mnt/.
Is there any problem with creating the filesystem as I have done? Can anyone shed some light if there is any particular configuration needed for virtual machine. I searched the forum for other options. But none of them seem applicable for me.
Thank you for your time.

What host os and CPU are you using? The message states that you need virtualization hardware support in the CPU (Intel VT-x or AMD-V) in order to run that 64 bit guets OS. Reasons for this error (that I could think of) could be:
- you have a very old cpu
- you have disabled virtualization in your bios
- you are running a 32-bit host os
These links to the docs may also help
https://www.virtualbox.org/manual/ch10.html#hwvirt
https://www.virtualbox.org/manual/ch03.html#intro-64bitguests
cheers
bjoern

[SOLVED]Error mounting: mount exited with exit code 16

hi guys, i have a dual OS. today after i force shutdown my computer, i can't mount one of the ntfs 。it shows the follow errors:
Error mounting: mount exited with exit code 16: Mount is denied because the NTFS volume is already exclusively opened.
The volume may be already mounted, or another software may use it which
could be identified for example by the help of the 'fuser' command.
any idea?
Last edited by wntyygtwxf (2011-12-01 11:09:27)

i resolve it by myself.
first, i mount it at another place, just like sudo mount /dev/sda? ~/home/down
then umount it.
now it work well. but i don't know why this worked.

Lucreate 'ERROR: mount: /export: invalid argument' - Live Upgrade u8 to u9

I'm trying to update several servers running solaris cluster 3.2 from u8 to u9 using live upgrade, first server (quorum server) worked just fine, next one (cluster member) goes down like this:
# lucreate -n solaris-10-u9
ERROR: mount: /export: Invalid argument
ERROR: cannot mount mount point </.alt.tmp.b-pob.mnt/export> device </export>
ERROR: failed to mount file system </export> on </.alt.tmp.b-pob.mnt/export>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to mount ABE <solaris-10-u9>
ERROR: Unable to clone the existing file systems from boot environment <s10x_u8wos_08a> to create boot environment <solaris-10-u9>.
ERROR: Cannot make file systems for boot environment <solaris-10-u9>.I followed all the necessary steps, removed the installed live upgrade packages and installed the ones from the u9 iso...
Any ideas would be greatly appreciated.
Edited by: 801033 on Oct 8, 2010 5:11 AM
Edited by: 801033 on Oct 8, 2010 5:28 AM
Edited by: 801033 on Oct 8, 2010 5:33 AM

The answer, at least in my case:
When I originally installed this cluster, I apparently misread the part of the documentation which lead me to disable lofs. The documentation states that you need to disable lofs if BOTH of two conditions are met,
1) You are running HA for NFS to server a locally available filesystem AND
2) you are running automountd.
In my case, I have no need for automountd, so I disabled the autofs service, reenabled lofs and am proceeding with the upgrade.

[SOLVED] Error mounting Kindle

Dear all,
whenever I connect my Kindle to the laptop, caja (Mate's fork of Nautilus) shows this error message:
Unable to mount Kindle
Error mounting /dev/sdc1 at /run/media/luca/Kindle: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sdc1" "/run/media/luca/Kindle"' exited with non-zero exit status 32: mount: unknown filesystem type 'vfat'
Any idea how can I fix this issue?
Last edited by lucacerone (2014-05-21 23:22:40)

I should also mention that before rebooting I also installed the packages dosfstools ntfs-3g ntfsprogs (dosfstools contains tools to manage vfat partitions),
I am not sure whether this contributed to fix the issues or not.

Error mounting MDM Server

Hi,
Error mounting MDM Server
We are unable to mount the MDM server, the error message saying
(The specified SAP instance does not exist on server mdm-sr)
mdm-sr : hostname of mdm server
FYI: The mdm server and mdm console running on the same host .
Thanks
Faris

Hi Deep,
restarted both DB and then MDM server, but still not working, giving same error message
(Error mounting MDM Server, The specified SAP instance does not exist on server mdm-srv)
FYI: The mdm server and mdm console running on the same host .
But the DB instance is runing on the diffrent server
Tx,
FSS

Java initialization error on a vps, centos 5

ok, i recently tried to install the newest jdk since my vps provider gave me 1.4.2. i did a rm /var/lib/alternatives/java through the counsel of another forum, but that did nothing. right now, when i try to java --version, this is what shows up. is this because i still have 1.4.2 installed? or is this a memory problem? the version i updated to was jdk6u6linuxi586.rpm i used the java-1.6.0-sun-compat-1.6.0.06-1jpp.i586.rpm as instructed by the java wiki on how to install java in a centos environment
Error occurred during initialization of VM
Could not reserve enough space for object heap
*** glibc detected *** java: free(): invalid pointer: 0xb7e4f290 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7edeaa6]
/lib/libc.so.6(cfree+0x90)[0xb7ee1fc0]
/usr/java/jdk1.6.0_06/jre/lib/i386/server/libjvm.so[0x6603393]
/usr/java/jdk1.6.0_06/jre/lib/i386/server/libjvm.so[0x65b43e0]
/usr/java/jdk1.6.0_06/jre/lib/i386/server/libjvm.so[0x65b601d]
/usr/java/jdk1.6.0_06/jre/lib/i386/server/libjvm.so[0x65b9499]
/usr/java/jdk1.6.0_06/jre/lib/i386/server/libjvm.so(JNI_CreateJavaVM+0x53)[0x639c453]
java[0x804afcc]
java(JavaMain+0x72)[0x8049942]
/lib/libpthread.so.0[0xb7fca45b]
/lib/libc.so.6(clone+0x5e)[0xb7f4624e]
======= Memory map: ========
06000000-0665d000 r-xp 00000000 00:23 148897840 /usr/java/jdk1.6.0_06/jre/lib/i386/server/libjvm.so
0665d000-066a1000 rwxp 0065c000 00:23 148897840 /usr/java/jdk1.6.0_06/jre/lib/i386/server/libjvm.so
066a1000-06ac3000 rwxp 066a1000 00:00 0
08048000-08052000 r-xp 00000000 00:23 148869550 /usr/java/jdk1.6.0_06/jre/bin/java
08052000-08053000 rwxp 00009000 00:23 148869550 /usr/java/jdk1.6.0_06/jre/bin/java
08053000-08074000 rwxp 08053000 00:00 0
70b00000-70b21000 rwxp 70b00000 00:00 0
70b21000-70c00000 ---p 70b21000 00:00 0
70cae000-70cb9000 r-xp 00000000 00:23 136881218 /lib/libgcc_s-4.1.2-20070626.so.1
70cb9000-70cba000 rwxp 0000a000 00:23 136881218 /lib/libgcc_s-4.1.2-20070626.so.1
b4cc2000-b4ccb000 rwxp b4cc2000 00:00 0
b4ccb000-b4d82000 rwxp b4ccb000 00:00 0
b4d82000-b4fc2000 rwxp b4d82000 00:00 0
b4fc2000-b7d82000 rwxp b4fc2000 00:00 0
b7d82000-b7d91000 r-xp 00000000 00:23 148869966 /usr/java/jdk1.6.0_06/jre/lib/i386/libzip.so
b7d91000-b7d93000 rwxp 0000e000 00:23 148869966 /usr/java/jdk1.6.0_06/jre/lib/i386/libzip.so
b7d93000-b7db6000 r-xp 00000000 00:23 148869920 /usr/java/jdk1.6.0_06/jre/lib/i386/libjava.so
b7db6000-b7db8000 rwxp 00023000 00:23 148869920 /usr/java/jdk1.6.0_06/jre/lib/i386/libjava.so
b7db8000-b7dc3000 r-xp 00000000 00:23 148869964 /usr/java/jdk1.6.0_06/jre/lib/i386/libverify.so
b7dc3000-b7dc4000 rwxp 0000b000 00:23 148869964 /usr/java/jdk1.6.0_06/jre/lib/i386/libverify.so
b7dc4000-b7dcd000 r-xp 00000000 00:23 136881142 /lib/libnss_files-2.5.so
b7dcd000-b7dce000 r-xp 00008000 00:23 136881142 /lib/libnss_files-2.5.so
b7dce000-b7dcf000 rwxp 00009000 00:23 136881142 /lib/libnss_files-2.5.so
b7dcf000-b7de2000 r-xp 00000000 00:23 136881148 /lib/libnsl-2.5.so
b7de2000-b7de3000 r-xp 00012000 00:23 136881148 /lib/libnsl-2.5.so
b7de3000-b7de4000 rwxp 00013000 00:23 136881148 /lib/libnsl-2.5.so
b7de4000-b7de6000 rwxp b7de4000 00:00 0
b7de6000-b7dee000 rwxs 00000000 00:23 141338056 (deleted) /tmp/hsperfdata_root/3754
b7dee000-b7df5000 r-xp 00000000 00:23 136881120 /lib/librt-2.5.so
b7df5000-b7df6000 r-xp 00006000 00:23 136881120 /lib/librt-2.5.so
b7df6000-b7df7000 rwxp 00007000 00:23 136881120 /lib/librt-2.5.so
b7df8000-b7dfe000 r-xp 00000000 00:23 148897832 /usr/java/jdk1.6.0_06/jre/lib/i386/native_threads/libhpi.so
b7dfe000-b7dff000 rwxp 00006000 00:23 148897832 /usr/java/jdk1.6.0_06/jre/lib/i386/native_threads/libhpi.so
b7dff000-b7e02000 ---p b7dff000 00:00 0
b7e02000-b7e50000 rwxp b7e02000 00:00 0
b7e50000-b7e75000 r-xp 00000000 00:23 136881118 /lib/libm-2.5.so
b7e75000-b7e76000 r-xp 00024000 00:23 136881118 /lib/libm-2.5.so
b7e76000-b7e77000 rwxp 00025000 00:23 136881118 /lib/libm-2.5.so
b7e77000-b7e78000 rwxp b7e77000 00:00 0
b7e78000-b7fb2000 r-xp 00000000 00:23 136881020 /lib/libc-2.5.so
b7fb2000-b7fb4000 r-xp 0013a000 00:23 136881020 /lib/libc-2.5.so
b7fb4000-b7fb5000 rwxp 0013c000 00:23 136881020 /lib/libc-2.5.so
b7fb5000-b7fb8000 rwxp b7fb5000 00:00 0
b7fb8000-b7fba000 r-xp 00000000 00:23 136880990 /lib/libdl-2.5.so
b7fba000-b7fbb000 r-xp 00001000 00:23 136880990 /lib/libdl-2.5.so
b7fbb000-b7fbc000 rwxp 00002000 00:23 136880990 /lib/libdl-2.5.so
b7fbc000-b7fc3000 r-xp 00000000 00:23 148897824 /usr/java/jdk1.6.0_06/jre/lib/i386/jli/libjli.so
b7fc3000-b7fc5000 rwxp 00006000 00:23 148897824 /usr/java/jdk1.6.0_06/jre/lib/i386/jli/libjli.so
b7fc5000-b7fd8000 r-xp 00000000 00:23 136881172 /lib/libpthread-2.5.so
b7fd8000-b7fd9000 r-xp 00012000 00:23 136881172 /lib/libpthread-2.5.so
b7fd9000-b7fda000 rwxp 00013000 00:23 136881172 /lib/libpthread-2.5.so
b7fda000-b7fdd000 rwxp b7fda000 00:00 0
b7fe3000-b7fe4000 rwxp b7fe3000 00:00 0
b7fe4000-b7fe5000 r-xp b7fe4000 00:00 0
b7fe5000-b7ffe000 r-xp 00000000 00:23 136881106 /lib/ld-2.5.so
b7ffe000-b7fff000 r-xp 00019000 00:23 136881106 /lib/ld-2.5.so
b7fff000-b8000000 rwxp 0001a000 00:23 136881106 /lib/ld-2.5.so
bfff7000-bfffe000 rwxp bfff7000 00:00 0
ffffe000-fffff000 r-xp 00000000 00:00 0
Aborted
Edited by: poolshark181 on May 11, 2008 7:08 PM

classboy wrote:
Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 5
at rekener.getGetal(rekener.java:22)
at venster.main(venster.java:37)The error message is telling you exactly what's wrong. On linke 22 of rekener.java (should be Rekener--class names conventionally start with uppercase), you are trying to access the 6th element, at index 5, of an array that has at more 5 elements, at indices 0..4
the line 22 is this :
getallen[counter]= getal;
So counter is 5. But getallen has only 5 elements at indices 0..4, or fewer.
this makes me think that the function that should fill the array isn't really doing it, It has nothing to do with whether the array is being "filled." Rather, it's just that the size of the array is less than what you're trying to access.
Even if i change the volume of the array to 4 or 6 "even though 5 is the correct ammount since i'm inserting 6 integers", keeps on giving me the same errorNo idea what you're saying here, but the compiler doesn't lie. You're trying to access an array element that doesn't exist.
Put print statements in your code so you can see what's happening at each step of the way, and figure out what you did to tell it to access elements that don't exist.

Check for mounted DFS share with exists in apple script

OS: OSX Mountain lion.
Can any one advise how to detect if a DFS share is mounted or not?
I have been using the following code:
set volumeLabel to "R$"
tell application "Finder"
exists disk volumeLabel
end tell
Which works fine with a normal SMB shares or attached hard drives but I cant get it to work with a DFS Share, it always returns false (see attached screen shot.
Also tried:
if volumeLabel is in (do shell script "/bin/ls Volumes") then
return true
else
return false
end if
Which didnt work with a DFS Share aswell.
Any help appreciated.
Cheers,
Richard

Hi,
Since you're checking to see if a value exists in the Desktop key, you can do something along these lines:
If (Get-ItemProperty -Path 'HKCU:\Control Panel\Desktop' -Name SCRNSAVE.EXE -ErrorAction SilentlyContinue) {
Write-Output 'Value exists'
} Else {
Write-Output 'Value DOES NOT exist'
EDIT: Sam, what version of PowerShell are you running? Your code doesn't seem to work for me on v4:
PS C:\> Push-Location
Set-Location "HKCU:\Control Panel"
$Result = Test-Path -Path ".\desktop\SCRNSAVE.EXE"
Pop-Location
$Result
False
Don't retire TechNet! -
(Don't give up yet - 12,950+ strong and growing)

Error mount database ORA 01995 ORA 27091

Hi, first of all, sorry for my pour english.
Someone can help me with this situation?
Os.: SUSE LINUX
DAtabase: Oracle Enterprise Linux 9.2.0.8
If I try mount db I get this error:
SQL> alter database mount
ERROR at line 1:
ORA-01995: error reading password file '/usr/oracle/9i/v920e/dbs/orapwsca'
ORA-27091: skgfqio: unable to queue I/O
ORA-27072: skgfdisp: I/O error
Linux Error: 22: Invalid argument
Additional information: 1
If I change parameter filesystemio_options to NONE I can mount database with no problem.
How can I use filesystemio_options = SETALL? Can I use this parameter?
Thanks in advice.

Setting filesystemio_options parameter to SETALL enables Direct IO and Async IO (Asynchronous I/O Support on OCFS/OCFS2 and Related Settings: filesystemio_options, disk_asynch_io [ID 432854.1]).
It seems that your file system does not properly support either of those advanced IO options.
You need to go to Metalink and dig the details from there - SuSE/Novell: Linux, Filesystem & I/O Type Supportability [ID 414673.1]
Iordan Iotzov
http://iiotzov.wordpress.com/

Error mounting a USB disk

After last upgrade, I am getting this error when trying to mount an external hard disk.
If I try it using dolphin, it says
"An error occured while accessing 'disk name', the system responded: An unspecified error has occurred.: Not Authorized"
with
udisks --mount
I am getting the same error too.
If I use these with sudo (gksu/kdesu) it works just fine.
My user is part of storage group. Also made changes in
/usr/shre/polkit-1/actions/org.freedesktop.udisks.policy
to allow_inactive.
<allow_inactive>yes</allow_inactive>

I figured it out.
xinit is tasked with two jobs: finding a client to run, and finding a server to run it on.
The default behavior of xinit is to first look for commandline arguments that tell it what to do, e.g.:
xinit /usr/bin/awesome -- /usr/bin/X
This tells it to run awesome wm using the X server located at /usr/bin/X.
Failing commandline arguments, xinit then looks in your home directory for files .xinitrc and .xserverrc. If they exist, xinit will execute these files for the responsibility of the client and server, respectively.
If these do not exist, then xinit uses defaults built-in to the xinit program (launches xterm with /usr/bin/X). This is where startx differs. Under the same circumstance, startx will also search the /etc/X11/xinit directory for system wide xinitrc and xserverrc files. In all other ways startx is the same program, such that if you provide server arguments to startx then it will preference that over the default xserverrc, and thus you'll have the same problem.
All of this boils down to the appropriate X server arguments. The system wide xserverrc located in /etc/X11/xinit/xserverrc checks if the environment variable XDG_VTNR has been set (the current virtual terminal number, set by pam_systemd), and if it is then to use that same terminal number for the next X session by running:
exec /usr/bin/X vt$XDG_VTNR
So, there's three solutions:
Use startx instead of xinit
Make a symlink to the default xserverrc file in your home directory. This works because xinit still checks your home directory for xinitrc and xserverrc, just not the system wide files.
Make your own xserverrc that will do the correct thing, and put it in your home directory.
Last edited by Whef (2012-11-11 04:34:27)

Error mounting DFS on CentOS 6.4

Similar Messages

Maybe you are looking for