03-23-2004
I thought I explainend it here
"basically if the root disk(physical disk) goes bad, I can bring up an alternate physical disk with the same filesystems as the root disk that went bad" on solaris the process is to
go to OK prompt, then type boot altboot.
this reads vstab.broot which contains the physical device information used to boot to the secondary disk
am I still not making sense?
5 More Discussions You Might Find Interesting
1. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
2. Linux
Hi,
Am doing an enhancements related to monitoring a Linux disk I/O statistics.
The /proc/diskstats file is used to get the each disk I/O statistics. But, It returns the raw value.
How to calculate the Disk Queue Length and Disk Busy time from the raw values.
Guide me. (1 Reply)
Discussion started by: maruthu
1 Replies
3. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
4. Filesystems, Disks and Memory
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Discussion started by: terrya
1 Replies
5. AIX
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (3 Replies)
Discussion started by: terrya
3 Replies
LEARN ABOUT OSF1
svatophys
svatophys(9r) svatophys(9r)
NAME
svatophys - General: Converts a system virtual address to a physical address
SYNOPSIS
kern_return_t svatophys(
vm_offset_t kern_addr,
vm_offset_t *phys_addr );
ARGUMENTS
Specifies the kernel virtual address. Specifies a pointer to the physical address to be filled in.
DESCRIPTION
The svatophys routine converts a system virtual address to the corresponding physical address. All address and data structure manipulation
done within the kernel is performed using system virtual addresses. Typically, system virtual addresses are a means of mapping physical
memory and I/O space, which often consists of device registers and DMA buffers. In contrast to this, devices are usually unaware of any
virtual addressing and for this reason use physical addresses. You use the svatophys routine to perform this address translation.
As an example of where you can use this address translation, a disk device driver can use DMA buffers to transfer blocks of data to the
disk (for the case of a write operation). The data to be written to disk is present in system memory at a system virtual address known to
the driver. To initiate the DMA operation, the disk driver can set up a command packet to specify a write operation to the underlying disk
controller hardware. This write command packet contains (among other things) the location of the DMA buffer as a physical address and the
length of the buffer. Here, the driver calls the svatophys routine to translate the system virtual address of the DMA buffer to a physical
address in the command packet issued to the disk driver.
RETURN VALUES
The svatophys routine returns the following: The address translation has been completed successfully. Unable to perform address transla-
tion. This value indicates that the address specified by the kern_addr argument is not a valid kernel or system virtual address.
svatophys(9r)