hot-add disk in oracle enterprise linux 5.5

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat hot-add disk in oracle enterprise linux 5.5
# 8  
Old 09-26-2011
unfortunately no, my fdisk -l command is not showing the increased allocated space until i reboot. I want to force the kernel to see the extra space allocated on /dev/sda without having any downtime.
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Linux

Oracle Enterprise Linux

Simple question: i need a linux distro wich support Veritas Storage,Veritas said Oracle Enterprise Linux is supported. The question is: where to download Oracle Enterprise Linux? I have tried https://edelivery.oracle.com But i found only Oracle Linux Server aka unbreakable Linux. Where to... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies

2. UNIX for Advanced & Expert Users

Linux fdisk question (Oracle Enterprise Linux)

OS: Oracle Enterprise Linux 6.2 Hypervisor: VMWare workstation 9 I created a VM and attached a 7gb virtual disk to it. Using fdisk , I partioned the disk like below. The filesystems mounted on this is working fine. But I am seeing the message Partition n does not end on cylinder boundary.... (2 Replies)
Discussion started by: kraljic
2 Replies

3. Red Hat

OEL5.5 hot add disk

Hi All, I have an issue when trying to hot-add a SAN disk to an oracle enterprise linux 5.5 server. The storage array we are using is an HP 24000, we have no issues with the disk usage for both ASM and LVM setup, it is just a simple matter of not being able to scan for new disk when it is... (4 Replies)
Discussion started by: Tommyk
4 Replies
Login or Register to Ask a Question
vxunreloc(1M)															     vxunreloc(1M)

NAME
vxunreloc - move a hot-relocated subdisk back to its original disk SYNOPSIS
/etc/vx/bin/vxunreloc [-f] [-g diskgroup] [-n dm_name] [-t tasktag] dm_name DESCRIPTION
The Veritas Volume Manager (VxVM) hot-relocation feature can detect an I/O failure in a subdisk, relocate the subdisk, and recover the plex associated with the subdisk. vxunreloc lets you reverse the process and move the hot-relocated subdisks back onto a disk that was replaced after a disk failure. dm_name specifies the disk where the hot-relocated subdisks originally resided. The -n option moves the subdisks to a different disk from where VxVM originally relocated them. For example, when disk03 fails, all the subdisks residing on it are hot-relocated to other disks. After the disk is repaired, it is added back to the disk group using a different name, for example, disk05. If you wanted to move all the hot-relocated subdisks back to the repaired disk, you would enter: /etc/vx/bin/vxunreloc -n disk05 disk03 When vxunreloc moves the hot-relocated subdisks, it moves them to their original offsets. However, if there was a subdisk that occupied part or all of the area on the destination disk, vxunreloc prints an error message and exits. In this situation, you can use the -f option to unrelocate the subdisks to a specified disk, but not to their original offsets. OPTIONS
-f Unrelocates a subdisk to a different offset if unrelocating to the original offset is not possible. -g diskgroup Unrelocates a subdisk from the specified disk group. If this option is not specified, the default disk group is determined using the rules given in the vxdg(1M) manual page. -n dm_name Specifies a new disk name to relocate to a disk with a different name. -t tasktag Specifies a tag to pass to the underlying utility. SUBDISK RECORD FIELDS
orig_dmname When a subdisk is hot-relocated, its original disk media name is stored in the orig_dmname field. When you run the vxunreloc command to move the subdisk back to the original disk (or to a new disk), this field is cleared. Before you run the vxunreloc command, you can do a search on this field to determine the subdisks that originated from a failed disk. For example, the fol- lowing command lists all the subdisks that were hot-relocated from mydg01 in the disk group mydg. Note that you must prefix the field name with "sd_" for the command to work. vxprint -g mydg -se 'sd_orig_dmname="mydg01"' orig_dmoffset When a subdisk is hot-relocated, its offset into the original disk is stored in the orig_dmoffset field. When you run vxunreloc to move the subdisk to the original disk, or to a new disk, this field is zeroed. The following command lists a hot-relocated subdisk which originally resided at disk10 at offset 1000. Again note that you must prefix the field names with "sd_" for the command to work. vxprint -g dg01 -se 'sd_orig_dmname="disk10" && sd_orig_dmoffset=1000' EXIT CODES
If the operation fails, vxunreloc exits with a non-zero status. A non-zero exit code is not a complete indicator of the problems encoun- tered, but rather denotes the first condition that prevented further execution of the utility. See vxintro(1M) for a list of standard exit codes. SEE ALSO
vxassist(1M), vxintro(1M), vxmake(1M), vxprint(1M), vxrelocd(1M), vxsd(1M), vxsparecheck(1M) VxVM 5.0.31.1 24 Mar 2008 vxunreloc(1M)