The point is that the device nodes for the root filesystem and the /usr filesystem might be different on the new hardware.
If you enter the command:
Code:
# mount
on the original system you will be able to see the devices mounted for root (/) and /usr. Make a note of them. This is device node list #1.
Now, on the clone, when booted from DVD into single user (with nothing mounted) and using the 'format' command you can see the devices on the clone plus you know what slice YOU are using to configure, format, and ufsrestore different filesystems on. Make a note of these. This is device node list #2. Are they the same devices (eg, c0t0d0s0) on both machines??? Also, if you now mount the root filesystem of the clone on /a and look in /a/dev/dsk, do the required devices (from list #2) exist in this directory?? If not, we need to create them before the system will boot and find its root filesystem.
Hi guys,
I am a new member here. This is my first post.
I try to purchase some new Blade 2500 for the
company. However, the vendor suggests me to get Blade 2000 instead. The vendor said he has many problems
with new Silver Blade 2500's. Has anyone here had
simlar experience with blade 2500?... (4 Replies)
Hi, Sir,
I have a customer who use a SB2000 as server and just upgraded three client machine with SB2500.
The system is used for planning and all boxes likely share the same source on server, so pretty slow when all machines are in operation.
The customer wish to do a server-to-client and... (0 Replies)
Hi everyone this is my first post
I have used linux a couple of times and was impressed, so i bought an old sunblade 1000, just to learn something new.
I cannot get the thing to work! I have tried to install solaris 10 and several types of linux. I am beginning to wonder if i was sold a... (3 Replies)
Progress! 25% there on our way 10,000 FB fans on the new timeline:
https://www.unix.com/members/neo-albums-forum-pics-picture503-facebook-timeline-now-over-2-500-fans.png (0 Replies)
Hi,
I recently got StoragaTek 2500 and I would like to connect it to my solaris machine, since I don't have much experience with storages, could someone point me how to do so, how can i present disks from storage on my solaris os? (everything is already connected)
thanks in advance (1 Reply)
Hello All,
I am new to the forum so forgive me for any mistakes. I have a question. I have been doing alot of reading about how to get a supportable operating system on my sunblade 2500. I also want to use it for Xorg. I have been having trouble getting the sun XVR drivers working... (2 Replies)
hello everyone,
I am new to linux and got this deliverable to write a script that should check for error in multiple log file (count is approx 2500 log files on single server) and once error is found, it should mail that error
My logic says:
we can put all log files path/location in one... (2 Replies)
Good Morning,
I took a mirror drive from one Solaris 9 machine and used it to set up another. After syncing another mirror on the second machine I restarted but I don't get a login screen.
I see a message:The X-server cannot be started on display :0
Also during startup I see:... (8 Replies)
Discussion started by: Stellaman1977
8 Replies
LEARN ABOUT DEBIAN
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)