07-27-2012
Done that
The syslog says
Jul 27 18:29:12 Topher-LI mount.ecryptfs: Failed to perform eCryptfs mount: [Not a directory]
Jul 27 18:29:12 Topher-LI kernel: [ 6847.640069] Reading sb failed; rc = [-20]
And the kern.log says
Jul 27 18:29:12 Topher-LI kernel: [ 6847.609883] ecryptfs_mount: kern_path() failed
Jul 27 18:29:12 Topher-LI kernel: [ 6847.640069] Reading sb failed; rc = [-20]
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi...
question is this:
How do I mount an LVD hotswap scsi drive in bay #2 on a netra using the mount command? volmgt doesn't seem to mount it and/or I don't know how to view the drives data if it's formatted which it may not be. This drive is not new out of the box so I'm not sure.
... (4 Replies)
Discussion started by: soulshaker
4 Replies
2. UNIX for Dummies Questions & Answers
Hi
I am accessing a file on nfs mounted device, after completing using of the file, i am tring to restore the access time and modification times of the file.
So i got the previous modified time of the file using stat() function and trying to set the date and time for the file, To set these... (6 Replies)
Discussion started by: deepthi.s
6 Replies
3. UNIX for Advanced & Expert Users
I am having trouble mounting with cifs, but mounting the exact same command with smbfs works fine. The share is on another samba server and is set to full public guest access. # mount -t cifs //servername/sharename /mnt/temp -o password=""
mount error 13 = Permission denied Refer to the... (3 Replies)
Discussion started by: humbletech99
3 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
I am very new to Linux. I have just started preparation for RHCE.
Can anybody pls tell me the meaning of mount a file or directory.
When we mount particular file at that time what exactly we do with the file. (2 Replies)
Discussion started by: kunalpatil09
2 Replies
5. IP Networking
Hello,
I have a few Ubuntu 9.10 laptops I'm trying to learn NFS sharing with. I am just experimenting on this right now, so no harsh words about the security of what I'm playing with, please ;)
Below are the configs
/etc/exports on host
/home/woodnt/Homeschool... (2 Replies)
Discussion started by: Narnie
2 Replies
6. Shell Programming and Scripting
Hi,
I would like to ask if someone know how to test a files if exist the file is a nfs mount ufsdump archive file..
i used the test operator -f -a h almost all test operator but i failed
file1=ufs_root_image.dump
|| echo "files doesn't exist && exit 1
the false file1 is working but... (0 Replies)
Discussion started by: jao_madn
0 Replies
7. AIX
Please can anybody help me with this weird behaviour.
There are 2 x-servers running Fedora 16 work as a cluster with DRBD, corosync & pacemaker. The cluster exports a filesystem using the following statement in /etc/exports
/drbd/home 10.49.17.0/255.255.255.0... (0 Replies)
Discussion started by: spitzie
0 Replies
8. AIX
Hi ,
We i try to mount aix filesystem i am getting the following error
mount: 0506-324 Cannot mount /dev/fslv11 on /testdir: A system call received a parameter that is not valid.
Please help me out (2 Replies)
Discussion started by: chidori
2 Replies
9. Shell Programming and Scripting
Heyas
At home i have 1 nas with 3 shares, of which i used to mount 2 of them using a script with hardcoded password and username in it.
EDIT: Turns out, its not the script, but 'how i access' the nas share.. (-o user=XY,password=... VS. -o credentials=...).
Figured about credential files,... (0 Replies)
Discussion started by: sea
0 Replies
usoc(7D) Devices usoc(7D)
NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver
DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre
Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/usoc
32-bit ELF kernel module
/kernel/drv/sparcv9/usoc
64-bit ELF kernel module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
|Interface stability |Unknown |
+-----------------------------+-----------------------------+
|Availability |SUNWusoc |
+-----------------------------+-----------------------------+
SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998
DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by:
usoc%d:
where
usoc%d:
is the per-port instance number of the usoc controller.
Fibre Channel is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is OFFLINE
The Fibre Channel loop is now offline.
attach failed: device in slave-only slot.
Move soc+ card to another slot.
attach failed: alloc soft state.
Driver did not attach, devices will be inaccessible.
attach failed: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to map eeprom
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map XRAM
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map registers
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access status register
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to install interrupt handler
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access host adapter XRAM
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to write host adapter XRAM
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: read/write mismatch in XRAM
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
SunOS 5.10 20 Jul 1999 usoc(7D)