01-04-2018
Most likely cause is......you cannot mount or umount any volume if you are actually on the volume.
So, if you were actually in the /mnt directory, you could not mount something on that mountpoint until you move away from it. As soon as you see 'busy' when mounting or dismounting a volume, that's the first thing you should think of. If you're not on the volume/mountpoint then probably some other user is.
Anyway, very well done!!! You are getting there.
Last edited by hicksd8; 01-04-2018 at 12:43 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi there,
I have a problem at the moment trying to restore a directory from a Super DLT tape with about 3 weeks worth of backups on it. I need to be able to get the last backup performed on this tape but using ufsrestore -i it only restores the first backup which is no good to me. There is... (4 Replies)
Discussion started by: gerwhelan
4 Replies
2. Solaris
on sparc solaris 2.8 hosts, HOSTB, after changing to /dir1 need to:
connect to tape drive on HostA. change directory to /dir0/dir1 on tape and
restore everything under that path to /dir1 directory.
could i get help?. (1 Reply)
Discussion started by: S26+
1 Replies
3. Solaris
I'm trying to restore a server from a backup tape. I've partitioned my drive, and I've run into a problem; After extracting everything from the tape, It seems as if only the directory structure is intact. Here are my steps:
1. booted from cdrom to single user mode boot cdrom -s
2. used... (3 Replies)
Discussion started by: ECBROWN
3 Replies
4. Solaris
HI Gurus,
I have a sunfire V445 server running SAP ECC 6.0 with an Oracle database on Solaris 9 (SunOS 5.9). I recently completed a ufsdump to tape of the following files:-
/,
/usr,
/oracle,
/export,
/sapr3,
I want to restore these files from tape onto a different server of the same... (5 Replies)
Discussion started by: charleywasharo
5 Replies
5. Solaris
Hi , I accidentally deleted crontab entries and I need to restore back urgently ! we use a ufsdump with 0cfu option. I like to know how to restrore / retrieve to different location for crontab file only from the backup. Thanks. (4 Replies)
Discussion started by: skully
4 Replies
6. Solaris
Hi Gurus,
Can you guys please explain what is volume in ufsrestore?
Thanks (2 Replies)
Discussion started by: kumarmani
2 Replies
7. Solaris
hey all,
i did a ufsdump/restore from a mirrored system and i'm not able to get the new system to boot off of the dump.
system 1 is a v245 mirrored with disk suite. metadb's are in place
d3 -m d23 d13 d33 1
d23 1 1 c1t1d0s3
d13 1 1 c1t0d0s3
d33 1 1 c1t2d0s3
d0 -m d20 d10 d30 1
d20 1... (3 Replies)
Discussion started by: em23
3 Replies
8. Solaris
hi, on my sol9 box i create my backup using the below command:
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u1
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u2
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u3
/usr/sbin/ufsdump 0uf /dev/rmt/0n /u4
now on the new sol10 box, to restore i use this commands:
cd /u1... (3 Replies)
Discussion started by: pinoy43v3r
3 Replies
9. Solaris
Hi Friends
we have sun T5240 server, we have taken ufsdump of this server remotely with scsi tapedrive, If we need to do ufsrestore means what we have to do, since T5240 has not having scsi port, any procedure is there?
Regards
Rajasekar (5 Replies)
Discussion started by: rajasekg
5 Replies
10. UNIX for Beginners Questions & Answers
Good Morning,
I'm running through a Solaris 9 ufsrestore process on a Sunblade 2500 that folks here helped me write a year ago. Here: https://www.unix.com/303011447-post11.html
Hicksd8 tells me to # rm restoresymtable. I see this file in the other slices as well. Do I remove it from... (8 Replies)
Discussion started by: Stellaman1977
8 Replies
LEARN ABOUT DEBIAN
mount.crypto_luks
mount.crypt(8) pam_mount mount.crypt(8)
Name
mount.crypt - mount a dm-crypt encrypted volume
Syntax
mount.crypt [-nrv] [-o options] device directory
Options
-o options
Set further mount options. mount.crypt will take out its own options it recognizes and passes any remaining options on to the under-
lying mount program. See below for possible options.
-n Do not update /etc/mtab. Note that this makes it impossible to unmount the volume by naming the container - you will have to pass
the mountpoint to umount.crypt.
-r Set up the loop device (if necessary) and crypto device in read-only mode. (The mount itself will necessarily also be read-only.)
Note that doing a remount using `mount /mnt -o remount,rw` will not make the mount readwrite. The crypto and loop devices will have
to be disassociated first.
-v Turn on debugging and be a bit more verbose.
Mount options
cipher The cryptsetup cipher used for the encrypted volume. This option is mandatory for PLAIN (non-LUKS) volumes. pmt-ehd(8) defaults to
creating volumes with "aes-cbc-essiv:sha256" as a cipher.
crypto_name
Select the name for the crypto device (optional). This option is currently only usable with dm-crypt systems.
fsck Run fsck on the container before mounting it.
fsk_cipher
The OpenSSL cipher used for the filesystem key. The special keyword "none" can be used to bypass decryption and pass the file con-
tents directly to libcryptsetup.
fsk_hash
The OpenSSL hash used for producing key and IV.
fstype The exact type of filesystem in the encrypted container. The default is to let the kernel autodetect.
hash The cryptsetup hash used for the encrypted volume. This defaults to no hashing, because pam_mount assumes EHD volumes with strong
and simple fskey generation.
keyfile
The path to the key file. This option is mandatory for "normal" crypto volumes and should not be used for LUKS volumes.
remount
Causes the filesystem to be remounted with new options. Note that mount.crypt cannot switch the underlying loop device (if applies)
or the crypto device between read-only and read-write once it is created; only the actual filesystem mount can be changed, with lim-
its. If the loop device is read-only, the crypto device will be read-only, and changing the mount to read-write is impossible. Sim-
ilarly, going from rw to ro will only mark the mount read-only, but not the crypto or loop device, thus making it impossible to set
the filesystem the crypto container is located on to read-only.
ro Same as the -r option.
verbose
Same as the -v option.
Obsolete mount options
This section is provided for reference.
loop This option used to set up a loop device, because cryptsetup(8) expects a block device. The option is ignored because mount.crypt
can figure this out on its own.
pam_mount 2011-12-15 mount.crypt(8)