So I don’t understand where the issue is with mount /export which is preventing the system from booting into multi-user mode.
Just read again this thread fom the beginning.
Creating snapshots cannot have any adverse effects.
Importing a root pool without taking specific precautions will create trouble, which is what you are experiencing.
In post 9 I wrote:
Quote:
There are also specific options you need to use to import a root pool as otherwise, some of the properties, especially mount points, will collide with your current root pool.
In post #13 I wrote:
Quote:
This is dubious, as I already wrote, you need specific options to import a root pool, at least a different root mountpoint.
Hi Folks,
I'm a serious UNIX newbie... I'm using a bash shell on Mac OS X.
Basically I took up unix in order to use a specific image processing software package... I've learned enough to write a script to batch process all of my images, but I have so many that I would like to use an... (1 Reply)
Hi ,
We are using Veritas Net Backup , I want to create a new policy for backing up the (Solaris Operating System & the file systems) only the OS. not Full backup because we have an other policy for Oracle Apps and it takes full backup for all Partitions.
I need the OS backup to be in... (2 Replies)
I have a Solaris 10 container that is running on ZFS filesystems being presented from the Global Zone.
I have a filesystem presented to the Local zone and my user wants me to remove it.
It there any way I can remove this while the zone is running?
I tried unmounting it from the local zone... (0 Replies)
how would a make a complete backup of all files spanning all file systems on my SCO box to tape?
i read somewhere:
find . -print | cpio -ocv > /dev/rStp0
from / ... will this do it??
(yes /dev/rStp0 is my tape drive) (11 Replies)
Hi,
I want to take backup of files older than 20 days from a directory onto a tape drive on remote machine on Solaris.
The files are of format abc-20100301000000.gz on my local machine.
I know the below commands for searching files older than x days and command for backup procedure.
solar1 #... (7 Replies)
Hi Guys
I have one Global Zone and 2 non-global zones.
root@solar109
# zoneadm list -icv
ID NAME STATUS PATH BRAND IP
0 global running / native shared
20 solar109b running ... (1 Reply)
I have noticed that when I copy files to flash disk and in UI I see message copy completed in notification area on task bar, usually copy is not completed. So, if I eject the media I loose data.
It is very serious problem because may cause loss of valuable and even critical data.
Moreover, when... (2 Replies)
Hi Guys,
I want to take backup of a ZFS file system on tape drive.
Can anybody help me with this?
Thanks,
Pras (0 Replies)
Discussion started by: prashant2507198
0 Replies
LEARN ABOUT REDHAT
pivot_root
PIVOT_ROOT(2) System Calls PIVOT_ROOT(2)NAME
pivot_root - change the root file system
SYNOPSIS
#include <linux/unistd.h>
_syscall2(int,pivot_root,const char *,new_root,const char *,put_old)
int pivot_root(const char *new_root, const char *put_old);
DESCRIPTION
pivot_root moves the root file system of the current process to the directory put_old and makes new_root the new root file system of the
current process.
The typical use of pivot_root is during system startup, when the system mounts a temporary root file system (e.g. an initrd), then mounts
the real root file system, and eventually turns the latter into the current root of all relevant processes or threads.
pivot_root may or may not change the current root and the current working directory (cwd) of any processes or threads which use the old
root directory. The caller of pivot_root must ensure that processes with root or cwd at the old root operate correctly in either case. An
easy way to ensure this is to change their root and cwd to new_root before invoking pivot_root.
The paragraph above is intentionally vague because the implementation of pivot_root may change in the future. At the time of writing,
pivot_root changes root and cwd of each process or thread to new_root if they point to the old root directory. This is necessary in order
to prevent kernel threads from keeping the old root directory busy with their root and cwd, even if they never access the file system in
any way. In the future, there may be a mechanism for kernel threads to explicitly relinquish any access to the file system, such that this
fairly intrusive mechanism can be removed from pivot_root.
Note that this also applies to the current process: pivot_root may or may not affect its cwd. It is therefore recommended to call
chdir("/") immediately after pivot_root.
The following restrictions apply to new_root and put_old:
- They must be directories.
- new_root and put_old must not be on the same file system as the current root.
- put_old must be underneath new_root, i.e. adding a non-zero number of /.. to the string pointed to by put_old must yield the same direc-
tory as new_root.
- No other file system may be mounted on put_old.
See also pivot_root(8) for additional usage examples.
If the current root is not a mount point (e.g. after chroot(2) or pivot_root, see also below), not the old root directory, but the mount
point of that file system is mounted on put_old.
NOTES
new_root does not have to be a mount point. In this case, /proc/mounts will show the mount point of the file system containing new_root as
root (/).
RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
ERRORS
pivot_root may return (in errno) any of the errors returned by stat(2). Additionally, it may return:
EBUSY new_root or put_old are on the current root file system, or a file system is already mounted on put_old.
EINVAL put_old is not underneath new_root.
ENOTDIR
new_root or put_old is not a directory.
EPERM The current process does not have the administrator capability.
BUGS
pivot_root should not have to change root and cwd of all other processes in the system.
Some of the more obscure uses of pivot_root may quickly lead to insanity.
CONFORMING TO
pivot_root is Linux-specific and hence is not portable.
HISTORY
pivot_root was introduced in Linux 2.3.41.
SEE ALSO chdir(2), chroot(2), initrd(4), pivot_root(8), stat(2)Linux 2000-02-23 PIVOT_ROOT(2)