08-13-2002
Hereby some information
The informatiion you get after you type the mount command is just informational and not a error message.
For more information about the mount options, SEE:
http://docs.sun.com/?p=/doc/816-3319/6m9k06r84&a=view
onerror=action
This option specifies the action that UFS should take to recover from an internal inconsistency on a file system. Specify action as panic, lock, or umount. These values cause a forced system shutdown, a file system lock to be applied to the file system, or the file system to be forcibly unmounted, respectively. The default is panic
10 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. Solaris
When ever i change my hard disk position from primary master to secondary slave, the solaris os gives a panic messge. how could i solve it. (2 Replies)
Discussion started by: ajay234
2 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. Red Hat
I was following this tutorial on How install the rpmfusion nvidia drivers in Fedora 13:
F13, F12 & F11 Nvidia driver guides - FedoraForum.org
Here's the tutorial:
And this is what I did:
First I executed the following commands:
su
rpm -Uvh ... (0 Replies)
Discussion started by: skyxn3t
0 Replies
5. Solaris
A server that I am working on (SUN FIRE V240 , SOLARIS 10) doesn't boot because of a corrupted files system.
I tried to repair de file system, I also tried to to restore all the files systems with a backup of the server that I have but the message bellow appear
panic/thread=30002fc2060:... (8 Replies)
Discussion started by: feg
8 Replies
6. BSD
I see the following warning message during the boot sequence of any FreeBSD machine on stock hardware:
acd0: FAILURE: READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00
Trying to mount root from ufs:/dev/ad6s1
What does this mean and is it really a warning or something that should be fixed?
... (2 Replies)
Discussion started by: figaro
2 Replies
7. Hardware
Hi Guys,
I just tried to reboot my server, but it seems to be panicing and unable to mount the root disk.
The filesystem is supposed to be ufs, so im not sure why its talking about vfs.
At the moment it's just stuck in a loop of Reboot-panic-reboot.
Any ideas?
A.
SunOS Release 5.10... (1 Reply)
Discussion started by: A-Train
1 Replies
8. 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
9. AIX
Dear all
First of all, my English not so good.
We have p52a (production server) and p52a (test server). Tape drives are VXA2.
When both servers were AIX 5.3, mksysb on production server and restoring to test server was OK.
The production server was AIX 5.3 and recently upgraded to... (3 Replies)
Discussion started by: fifa15pc
3 Replies
10. AIX
Dear all
i have two aix system
-Model : P770
-OS version: AIX 6.1
-patch level : 6100-07-04-1216
-ha version : HACMP v 6.1.0.8
-host : A, B
last Wednesday, my B system suddenly went down with crash dump. after 1 minute, A system went down with crash dump. I checked the dump of A-system... (6 Replies)
Discussion started by: tomato00
6 Replies
UMOUNT(8) System Manager's Manual UMOUNT(8)
NAME
umount - unmount file systems
SYNOPSIS
umount [ -fv ] special | node
umount -a [ -fv ] [ -t ufs | external_type ]
DESCRIPTION
The umount command calls the umount(2) system call to remove a special device from the file system tree at the point node. If either spe-
cial or node are not provided, the appropriate information is taken from the fstab(5) file.
The options are as follows:
-a All of the file systems described in fstab(5) are unmounted.
-f The file system is forcibly unmounted. Active special devices continue to work, but all other files return errors if further
accesses are attempted. The root file system cannot be forcibly unmounted. This is not currently implemented in 2.11BSD.
-t ufs | external type
Is used to indicate the actions should only be taken on filesystems of the specified type. More than one type may be specified
in a comma separated list. The list of filesystem types can be prefixed with no to specify the filesystem types for which action
should not be taken. For example, the umount command:
umount -a -t nfs,mfs
umounts all filesystems of the type NFS and MFS.
NOTE: Only UFS is supported by 2.11BSD. The example is for illustrative purposes only.
-v Verbose, additional information is printed out as each file system is unmounted.
FILES
/etc/fstab file system table
SEE ALSO
umount(2), fstab(5), mount(8)
HISTORY
A umount command appeared in Version 6 AT&T UNIX.
4.4 Berkeley Distribution January 16, 1996 UMOUNT(8)