10-20-2011
It will not allow you to unmount /pay_serv since ukb_pool/temp_ps is mounted on /pay_serv/ps.
The data resides in ukb_pool but it is mounted under pay_serv.
You can change the mount point and then unmount and destroy pay_serv.
You may take below steps.
- Shutdown the zone pay_serv
- Change the mountpoint for ukb_pool/temp_ps from /pay_serv/ps to /ukb_pool/ps
- Change the zone configuration to take the new mount point when booting through zonecfg since the old mount point is not there
- Boot the zone and check the data in ukb_pool/temp_ps is accessible
- Once you are sure and no errors encountered you can unmount and dstroy pay_serv otherwise you have an option to revert back to old configuration
If possible you can create the scenario in a test server and test it.
Regards,
Vishal
10 More Discussions You Might Find Interesting
1. Solaris
Hi community,
I've a hard question for you.
1)What are the differences between ZFS and Veritas Volume Manager on Solaris10?
2) what is the difference to manage the internal disks (Mirror)?
3) what is the difference to manage the external disks?
4) What is the difference to manage... (5 Replies)
Discussion started by: Sunb3
5 Replies
2. Solaris
I have a oracle instance running in NGZ which is on zfs dataset. Is there any possibility if i can take a zfs snapshot without shutting down the zone and then restore the zfs on other server and start oracle .. will the data be fine or not ? (2 Replies)
Discussion started by: fugitive
2 Replies
3. Solaris
zfs-zeta bye filesystem
or
zope filesystem
which is correct (2 Replies)
Discussion started by: kishanreddy
2 Replies
4. Solaris
With Solaris 11 coming out with a requirement of ZFS on the root disk, I was curious to know who is using the Zeta File System now?
I have been using ZFS for the past year and don't plan to go back to UFS since ZFS is much more reliable and easier to maintain. (13 Replies)
Discussion started by: bluescreen
13 Replies
5. Solaris
Hi, I am nowusing ZFS since some weeks and now I have 2 questions:
1) in zpool I saw some disk added with the *s2 at the end, I have in mind that should not be ? is this right and if so can I get the *s2 disk out of the zpool ?
2) Zpool has still 2 spare disk but when I try to create a new... (6 Replies)
Discussion started by: manni2
6 Replies
6. Solaris
what are all the advantages of ZFS comparing to UFS SVM
what is the use of creating file system in a file system in ZFS (15 Replies)
Discussion started by: dinu
15 Replies
7. Solaris
I have installed Solaris 11 Express on my server and want to set up automatic backuping using zfs snapshots. In the backup script I need to find out the name of the last snapshot of the given filesystem (in order to refer to it as the startpoint of an incremental backup). What is the best way to do... (4 Replies)
Discussion started by: RychnD
4 Replies
8. Solaris
I am building a new server on sol10_X86.
I am new to ZFS, this will be one of the first systems to use it.
I would like to have /opt /usr and a /u01 as separate file systems from the main ZFS pool. I know that this goes against the basic idea of ZFS, but this is so I can restrict the size/usage... (1 Reply)
Discussion started by: robsonde
1 Replies
9. Emergency UNIX and Linux Support
Hi all,
A customer has a very active ZFS partitionon their production system, I need to get a copy of the data under one directory at a specific point in time.
Is it possible to do this with the ZFS snapshot/clone tools, (and what commands should be used to capture the info I require for... (6 Replies)
Discussion started by: Skrynesaver
6 Replies
10. Solaris
Hi guys! I am student from poland and I am preparing my assignment about Solaris 11 cloud computing capabilities. :p
I am writing about ZFS now, and as I am quite new to this stuff I have several question (I prefere to have deep understanding of what I am doing, instead of just rewriting the... (1 Reply)
Discussion started by: mlody94
1 Replies
BIND(1) General Commands Manual BIND(1)
NAME
bind, mount, unmount - change name space
SYNOPSIS
bind [ option ... ] new old
mount [ option ... ] servename old [ spec ]
unmount [ new ] old
DESCRIPTION
Bind and mount modify the file name space of the current process and other processes in the same name space group (see fork(2)). For both
calls, old is the name of an existing file or directory in the current name space where the modification is to be made.
For bind, new is the name of another (or possibly the same) existing file or directory in the current name space. After a successful bind,
the file name old is an alias for the object originally named by new; if the modification doesn't hide it, new will also still refer to its
original file. The evaluation of new (see intro(2)) happens at the time of the bind, not when the binding is later used.
The servename argument to mount is the name of a file that, when opened, yields an existing connection to a file server. Almost always,
servename will be a file in /srv (see srv(3)). In the discussion below, new refers to the file named by the new argument to bind or the
root directory of the service available in servename after a mount. Either both old and new files must be directories, or both must not be
directories.
Options control aspects of the modification to the name space:
(none) Replace the old file by the new one. Henceforth, an evaluation of old will be translated to the new file. If they are directo-
ries (for mount, this condition is true by definition), old becomes a union directory consisting of one directory (the new file).
-b Both files must be directories. Add the new directory to the beginning of the union directory represented by the old file.
-a Both files must be directories. Add the new directory to the end of the union directory represented by the old file.
-c This can be used in addition to any of the above to permit creation in a union directory. When a new file is created in a union
directory, it is placed in the first element of the union that permits creation.
The spec argument to mount is passed in the attach(5) message to the server, and selects among different file trees served by the server.
The srv(3) service registry device, normally bound to /srv, is a convenient rendezvous point for services that can be mounted. After boot-
strap, the file /srv/boot contains the communications port to the file system from which the system was loaded.
The effects of bind and mount can be undone with the unmount command. If two arguments are given to unmount, the effect is to undo a bind
or mount with the same arguments. If only one argument is given, everything bound to or mounted upon old is unmounted.
EXAMPLES
To compile a program with the C library from July 16, 1992:
mount /srv/boot /n/dump dump
bind /n/dump/1992/0716/mips/lib/libc.a /mips/lib/libc.a
mk
SOURCE
/sys/src/cmd/bind.c
/sys/src/cmd/mount.c
/sys/src/cmd/unmount.c
SEE ALSO
bind(2), open(2), srv(3), srv(4)
BIND(1)