Sponsored Content
Full Discussion: LDOMS and memory (PA/RA)
Operating Systems Solaris LDOMS and memory (PA/RA) Post 303004475 by psychocandy on Tuesday 3rd of October 2017 06:10:46 AM
Old 10-03-2017
LDOMS and memory (PA/RA)

If I do ldm ls l ldom1 the memory block is as follows:-

Code:
MEMORY
    RA               PA               SIZE
    0x20000000       0x20000000       64G
    0x1420000000     0x1020000000     16G
    0x1c20000000     0x1420000000     16G
    0x2420000000     0x1820000000     16G
    0x2c20000000     0x1c20000000     6G

What are RA/PA? What is total memory allocated? Why split like this?

Last edited by rbatte1; 10-03-2017 at 07:33 AM.. Reason: Added ICODE tags
 

9 More Discussions You Might Find Interesting

1. Solaris

RAID1 and LDoms

I have a Netra T5220 Solaris 10 server with LDoms installed and enabled. RAID1 is enabled in the control domain with the following slices: d50 -m d51 d52 1 d51 1 1 c1t0d0s5 d52 1 1 c1t1d0s5 d10 -m d11 d12 1 d11 1 1 c1t0d0s0 d12 1 1 c1t1d0s0 d20 -m d21 d22 1 d21 1 1 c1t0d0s1 d22 1 1... (14 Replies)
Discussion started by: StarSol
14 Replies

2. Solaris

LDOMs on T5220

We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid? I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies

3. Solaris

Dynamically remove CPUs and memory from Ldoms

I 'm tryin to create a new ldom removing 4 vcpus from the existing ldom2 and 4 gb of memory but i get following error bash-3.00# ldm rm-vcpu 8 ldom2 VCPU DR disabled because LDom ldom2 has crypto units bound bash-3.00# ldm rm-mau 7 ldom2 LDom ldom2 is unable to dynamically reconfigure... (2 Replies)
Discussion started by: fugitive
2 Replies

4. Solaris

LDoms can't ping each other

I've got Sun Fire T2000 with two LDoms - primary and ldom1, both being Solaris 10 u8. Both can be accessed over the network (ssh, ping), both can access the network, but they can't ping or ssh to each other. I only use e1000g0 interface on T2000, the primary ldom has an address on it, ldm has a... (1 Reply)
Discussion started by: mludvig
1 Replies

5. Solaris

LDOMS command

What command would i type to get a list of LDOMS running on a blade? (3 Replies)
Discussion started by: soupbone38
3 Replies

6. Solaris

Ldoms not booting from vdisk

I have a T5220 with following configuration of hypervisor and OS # ldm -V Logical Domains Manager (v 2.1) Hypervisor control protocol v 1.7 Using Hypervisor MD v 1.3 System PROM: Hypervisor v. 1.10.4 @(#)Hypervisor 1.10.4 2011/11/17 15:00\015 ... (1 Reply)
Discussion started by: fugitive
1 Replies

7. Solaris

Can not use zone in LDoms on T4-1

I have a T4-1 with Solaris 11.1, LDom ver 3.0.0.1 and I'm encountering two problems with zones. I'd greatly appreciate help on these, especially the first one. I have created multiple guest LDoms, all Solaris 11.1, and they all work fine. The first problem is that I can not boot any... (9 Replies)
Discussion started by: ad101
9 Replies

8. Solaris

LDoms disappeared

System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. I have been experimenting on the above system, using ldmp2v to create "clones" of my physical systems as LDoms on the server when there was an unscheduled power outage. After the system came back up I had lost my LDoms, although... (7 Replies)
Discussion started by: apmcd47
7 Replies

9. UNIX for Advanced & Expert Users

Creating filesystem in LDOMs

Hi, I have a task of creating a UFS filesystem in an LDOM. It is located in a hypervisor (CDOM). The storage has been provisioned to the CDOM. How do I make it reflect to the LDOM, and then from there configure/set up the filesystem in the LDOM? Please help. (1 Reply)
Discussion started by: anaigini45
1 Replies
fsck.ocfs2(8)							OCFS2 Manual Pages						     fsck.ocfs2(8)

NAME
fsck.ocfs2 - Check an OCFS2 file system. SYNOPSIS
fsck.ocfs2 [ -fFGnuvVy ] [ -b superblock block ] [ -B block size ] device DESCRIPTION
fsck.ocfs2 is used to check an OCFS2 file system. device is the file where the file system is stored (e.g. /dev/sda1). It will almost always be a device file but a regular file will work as well. OPTIONS
-b superblock block Normally, fsck.ocfs2 will read the superblock from the first block of the device. This option specifies an alternate block that the superblock should be read from. (Use -r instead of this option.) -B blocksize The block size, specified in bytes, can range from 512 to 4096. A value of 0, the default, is used to indicate that the blocksize should be automatically detected. -D Optimize directories in filesystem. This option causes fsck.ocfs2 to coalesce the directory entries in order to improve the filesys- tem performance. -f Force checking even if the file system is clean. -F By default fsck.ocfs2 will check with the cluster services to ensure that the volume is not in-use (mounted) on any node in the cluster before proceeding. -F skips this check and should only be used when it can be guaranteed that the volume is not mounted on any node in the cluster. WARNING: If the cluster check is disabled and the volume is mounted on one or more nodes, file system cor- ruption is very likely. If unsure, do not use this option. -G Usually fsck.ocfs2 will silently assume inodes whose generation number does not match the generation number of the super block are unused inodes. This option causes fsck.ocfs2 to ask the user if these inodes should in fact be marked unused. -n Give the 'no' answer to all questions that fsck will ask. This guarantees that the file system will not be modified and the device will be opened read-only. The output of fsck.ocfs2 with this option can be redirected to produce a record of a file system's faults. -r backup-number mkfs.ocfs2 makes upto 6 backup copies of the superblock at offsets 1G, 4G, 16G, 64G, 256G and 1T depending on the size of the vol- ume. Use this option to specify the backup, 1 thru 6, to use to recover the superblock. -y Give the 'yes' answer to all questions that fsck will ask. This will repair all faults that fsck.ocfs2 finds but will not give the operator a chance to intervene if fsck.ocfs2 decides that it wants to drastically repair the file system. -v This option causes fsck.ocfs2 to produce a very large amount of debugging output. -V Print version information and exit. EXIT CODE
The exit code returned by fsck.ocfs2 is the sum of the following conditions: 0 - No errors 1 - File system errors corrected 2 - File system errors corrected, system should be rebooted 4 - File system errors left uncorrected 8 - Operational error 16 - Usage or syntax error 32 - fsck.ocfs2 canceled by user request 128 - Shared library error SEE ALSO
mkfs.ocfs2(8) debugfs.ocfs2(8) tunefs.ocfs2(8) mounted.ocfs2(8) ocfs2console(8) o2cb(7) AUTHORS
Oracle Corporation. This man page entry derives some text, especially the exit code summary, from e2fsck(8) by Theodore Y. Ts'o <tytso@mit.edu>. COPYRIGHT
Copyright (C) 2004, 2010 Oracle. All rights reserved. Version 1.4.3 February 2010 fsck.ocfs2(8)
All times are GMT -4. The time now is 03:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy