Understand your recommendation. My aim is to know if we can go this way technically
For the current status, there is no need to add new disk to that VG, we just need to create new VG and that's all. The scalable VG with PP size 1 GB is created
I have 1 more point, can you explain to me the in-band and calculation of the percentage? In the docs it says this is used to calculate the usage percentage of disk, but somehow I can see 0%, 100% but the disk has data already on it and still has free PPs.
Code:
[root@xxx] / > lslv -l fslv03
fslv03:/export/images
PV COPIES IN BAND DISTRIBUTION
hdisk19 1599:000:000 20% 320:320:319:320:320
hdisk20 1599:000:000 20% 320:320:319:320:320
hdisk21 1599:000:000 20% 320:320:319:320:320
hdisk22 1599:000:000 20% 320:320:319:320:320
hdisk23 1599:000:000 20% 320:320:319:320:320
hdisk24 1599:000:000 20% 320:320:319:320:320
hdisk25 1599:000:000 20% 320:320:319:320:320
hdisk26 1599:000:000 20% 320:320:319:320:320
hdisk17 968:000:000 18% 320:178:319:151:000
[root@xxx] / > lspv -l hdisk21
hdisk21:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
fslv03 1599 1599 320..320..319..320..320 /export/images
[root@xxx] / > lspv hdisk21
PHYSICAL VOLUME: hdisk21 VOLUME GROUP: vg_3
PV IDENTIFIER: 00fa6d12ed215e81 VG IDENTIFIER 00c1cc1400004c0000000128174b7c57
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 64 megabyte(s) LOGICAL VOLUMES: 1
TOTAL PPs: 1599 (102336 megabytes) VG DESCRIPTORS: 1
FREE PPs: 0 (0 megabytes) HOT SPARE: no
USED PPs: 1599 (102336 megabytes) MAX REQUEST: 256 kilobytes
FREE DISTRIBUTION: 00..00..00..00..00
USED DISTRIBUTION: 320..320..319..320..320
MIRROR POOL: None
Hi!
How to extend /usr partition in rootvg on AIX 4.3.3-09?
I guess first I'll have to decrease the size of other partition(s) in rootvg?
Thank you! (2 Replies)
on the disk array (EMC Clariion cx300):
we added 3 disk and extended the LUN corresponding to HP-9000 (rp7410)
on HP-UX 11.11:
diskinfo /dev/rdsk/c10t0d0, show more disk space, but
vgdisplay vg13 does not show more space
So the problem is the disk had increased, but vgdisplay does not... (6 Replies)
I am running solaris 10 with Veritas. I want to extend a filesystem. It's an oracle partition (/ora12). How can I find out if there is space available to expand the filesystem and then how does one extend it.
I'm from the HPUX world and so LVM was always how I did things.
Thanks
jackie (5 Replies)
OK I'm sure this question has been posed far too many times.
I have solaris 10 x86 with NO Veritas or Disksuite filesystems. Below is the output of df -k
# df -k
Filesystem kbytes used avail capacity Mounted on
/ 10485760 547513 9317128 6% /
/dev... (1 Reply)
Hi all,
currently , my root filesystem already reach 90 ++%
I already add more cylinder in the root partition as below
Part Tag Flag Cylinders Size Blocks
0 root wm 67 - 5086 38.46GB (5020/0/0) 80646300
1 swap wu 1 - ... (11 Replies)
Hi,
I have recently increased the size of my pv and I am now attempting to increase the lv but I get the following error:
# vgdisplay
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata... (7 Replies)
Hi all,
I need to extend a lv, but unfortunately I do not have enough space on my mirrored Volume group.
I've planned to add 2 more disks to this vg (for mirroring)
But ... what's the next steps to extend my lv using these 2 disks with a valid mirroring ?
1. extendvg myvg disk1 disk2... (3 Replies)
Hi all.
I have a Logical volume that I can't extend, with this error message:
server171:root:/root# lvextend -L +1024M -v /dev/aplic_vg/siteminderwa_lv
Finding volume group aplic_vg
Archiving volume group "aplic_vg" metadata (seqno 75).
Extending logical volume siteminderwa_lv to... (0 Replies)
Hello,
I have redhat and centos systems that I've only been able to grow the VG by adding more disks. I've been searching the web for a way to extend a volume group by growing the physical disk only and not having to add a second disk. Is it possible?
I can do this with AIX, by just... (0 Replies)
Discussion started by: bbbngowc
0 Replies
LEARN ABOUT NETBSD
amr
AMR(4) BSD Kernel Interfaces Manual AMR(4)NAME
amr -- AMI MegaRAID PCI-SCSI RAID driver
SYNOPSIS
amr* at pci? dev ? function ?
scsibus* at amr?
DESCRIPTION
The amr driver provides support for LSI (formerly American Megatrends) MegaRAID Express, Elite and Enterprise family RAID controllers for
SCSI and SATA, including models relabeled and sold by Dell, Hewlett-Packard, and Intel. Supported controllers include:
o MegaRAID 320-1
o MegaRAID 320-2
o MegaRAID Series 418
o MegaRAID Enterprise 1200 (Series 428)
o MegaRAID Enterprise 1300 (Series 434)
o MegaRAID Enterprise 1400 (Series 438)
o MegaRAID Enterprise 1500 (Series 467)
o MegaRAID Enterprise 1600 (Series 471)
o MegaRAID Elite 1500 (Series 467)
o MegaRAID Elite 1600 (Series 493)
o MegaRAID Express 100 (Series 466WS)
o MegaRAID Express 200 (Series 466)
o MegaRAID Express 300 (Series 490)
o LSI MegaRAID SCSI 320-0X, 320-2X, 320-4X
o LSI MegaRAID SCSI 320-1E, 320-2E
o LSI MegaRAID SATA 300-6x, 300-8x
o Dell PERC
o Dell PERC 2/SC
o Dell PERC 2/DC
o Dell PERC 4/Di
o Dell PERC 4/SC
o Dell PERC 4e/Si
o HP NetRAID-1/Si
o HP NetRAID-3/Si
o HP Embedded NetRAID
o Intel SRCU42X
o Intel SRCU42E
o Intel SRMOBU42E
o Intel SRCS28X
DIAGNOSTICS
Driver initialisation/shutdown phase
amr%d: memory window not available
amr%d: I/O window not available
The PCI BIOS did not allocate resources necessary for the correct operation of the controller. The driver cannot attach to this controller.
amr%d: busmaster bit not set, enabling
The PCI BIOS did not enable busmaster DMA, which is required for the correct operation of the controller. The driver has enabled this bit
and initialisation will proceed.
amr%d: can't allocate register window
amr%d: can't allocate interrupt
amr%d: can't set up interrupt
amr%d: can't allocate parent DMA tag
amr%d: can't allocate buffer DMA tag
amr%d: can't allocate scatter/gather DMA tag
amr%d: can't allocate s/g table
amr%d: can't allocate mailbox tag
amr%d: can't allocate mailbox memory
A resource allocation error occurred while initialising the driver; initialisation has failed and the driver will not attach to this con-
troller.
amr%d: can't obtain configuration data from controller
amr%d: can't obtain product data from controller
The driver was unable to obtain vital configuration data from the controller. Initialisation has failed and the driver will not attach to
this controller.
amr%d: can't establish configuration hook
amr%d: can't scan controller for drives
The scan for logical drives managed by the controller failed. No drives will be attached.
amr%d: device_add_child failed
amr%d: bus_generic_attach returned %d
Creation of the logical drive instances failed; attachment of one or more logical drives may have been aborted.
amr%d: flushing cache...
The controller cache is being flushed prior to shutdown or detach.
Operational diagnostics
amr%d: I/O beyond end of unit (%u,%d > %u)
A partitioning error or disk corruption has caused an I/O request beyond the end of the logical drive. This may also occur if FlexRAID Vir-
tual Sizing is enabled and an I/O operation is attempted on a portion of the virtual drive beyond the actual capacity available.
amr%d: polled command timeout
An initialisation command timed out. The initialisation process may fail as a result.
amr%d: bad slot %d completed
The controller reported completion of a command that the driver did not issue. This may result in data corruption, and suggests a hardware
or firmware problem with the system or controller.
amr%d: I/O error - %x
An I/O error has occurred.
SEE ALSO cd(4), ch(4), intro(4), pci(4), scsi(4), sd(4), st(4), amrctl(8)BSD July 23, 2006 BSD
04-12-2019
