04-24-2015
p2v is having a problem creating files on your designated zone path.
Try setting the zone mount point access to 777 whilst migrating data.
What hardware is this? This may be a stupid thing to say but you know that you cannot migrate a Sparc system to a zone on a x86 system?
Typically, zones are created on their own disk slice (of suitable size to take the migrating data) which is mounted on a mount point on the root filesystem. I think here you are using an area on your /export filesystem. yes?
9 More Discussions You Might Find Interesting
1. Solaris
Hello,
I am attempting to install a newly configured Solaris 9 zone using the flash archive image provided on the sun website. Each time I run the install I get a failure during the Postprocess: Creating mount points. Following is the log:
Log File: /var/tmp/s9-zone.install.25457.log... (0 Replies)
Discussion started by: brialt1
0 Replies
2. Solaris
1. i read that VxFS (3.x) installed on a solaris 8 will not work on a branded zone. fair enough, but what is the impact of having the packages installed when the flarcreate is done? will the container fail to boot with those packages installed?
2. NTP client and server doesnt work on branded... (11 Replies)
Discussion started by: frustin
11 Replies
3. Solaris
Dear all,
we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message:
***The image patch level is downrev for running in a solaris10 branded zone***
The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed.
Does the... (0 Replies)
Discussion started by: xunil321
0 Replies
4. Solaris
I have a T5220 running Solaris 10. I have a application that can only run on Solaris 9. I want to build a branded Solaris 9 zone for this application on the Solaris 10 Server.
What steps would I need to accomplish this? (2 Replies)
Discussion started by: soupbone38
2 Replies
5. Solaris
I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate.
#zonecfg -z <device>
>create -b
>set brand=solaris10
>set zonepath=/zonez/<device>
>set ip-type=exclusive
>add net... (1 Reply)
Discussion started by: aeroforce
1 Replies
6. Solaris
I am trying to get a NFS share on a Solaris 10 branded zone. I have read that this is not possible...but I was hoping someone here could tell me different.
share -F nfs -o ro,anon=0 /dir
This would really surprise me that you cannot do this.
Thanks (2 Replies)
Discussion started by: aeroforce
2 Replies
7. Solaris
All.
I am trying to create a 10 branded zone on a Sol 11.1 T5. The Global is using IPMP...so aggregating is out of the question. Has anyone successfully created a branded zone with IPMP? If they have can you please show me the steps you took to get this to run.
Thanks (4 Replies)
Discussion started by: aeroforce
4 Replies
8. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
9. Solaris
So I started with following the example on the omnios page for bhyve (sorry, I can't provide the link because I'm a post shy of the 5 to give a URL):
And found that in the end I was able to create a running bhyve zone, but accessing it via zlogin results in a blank console. I've tried Debian 9... (14 Replies)
Discussion started by: stratacast1
14 Replies
LEARN ABOUT MOJAVE
xfs_freeze
xfs_freeze(8) System Manager's Manual xfs_freeze(8)
NAME
xfs_freeze - suspend access to an XFS filesystem
SYNOPSIS
xfs_freeze -f | -u mount-point
DESCRIPTION
xfs_freeze suspends and resumes access to an XFS filesystem (see xfs(5)).
xfs_freeze halts new access to the filesystem and creates a stable image on disk. xfs_freeze is intended to be used with volume managers
and hardware RAID devices that support the creation of snapshots.
The mount-point argument is the pathname of the directory where the filesystem is mounted. The filesystem must be mounted to be frozen
(see mount(8)).
The -f flag requests the specified XFS filesystem to be frozen from new modifications. When this is selected, all ongoing transactions in
the filesystem are allowed to complete, new write system calls are halted, other calls which modify the filesystem are halted, and all
dirty data, metadata, and log information are written to disk. Any process attempting to write to the frozen filesystem will block waiting
for the filesystem to be unfrozen.
Note that even after freezing, the on-disk filesystem can contain information on files that are still in the process of unlinking. These
files will not be unlinked until the filesystem is unfrozen or a clean mount of the snapshot is complete.
The -u flag is used to un-freeze the filesystem and allow operations to continue. Any filesystem modifications that were blocked by the
freeze are unblocked and allowed to complete.
One of -f or -u must be supplied to xfs_freeze.
NOTES
A copy of a frozen XFS filesystem will usually have the same universally unique identifier (UUID) as the original, and thus may be pre-
vented from being mounted. The XFS nouuid mount option can be used to circumvent this issue.
In Linux kernel version 2.6.29, the interface which XFS uses to freeze and unfreeze was elevated to the VFS, so that this tool can now be
used on many other Linux filesystems.
SEE ALSO
xfs(5), lvm(8), mount(8).
xfs_freeze(8)