12-04-2006
Error on HACMP5.3 volume group on raw devices after exporting vg
Hello, johnf
No, in both cases, lsvg or lsvg -o VG is not visible and if we run lsvg -l vg01 we have 0516-306 error "Unable to find volume group vg01 in the Device Configuration Database"
Cristi
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
I'm new here, so this information may exist elsewhere on this forum. If so, please point me in the right direction.
Here's the problem.
I'm trying to migrate Oracle data from an HP system to a Sun system using a raw device as a 'bridge' between the two systems. Both machines... (4 Replies)
Discussion started by: Neville
4 Replies
2. UNIX for Advanced & Expert Users
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
3. AIX
Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies
4. AIX
Hello,
I am a french computer technician, and i speak English just a little.
On Aix 5.3, I encounter a name conflict logical volume on two volume group.
The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM
root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies
5. Programming
Hi guys.
what is the benefits of using raw devices in programming?
which applications mostly use raw devices?
how can i use raw devices in C programs? is there any system calls or library functions? (1 Reply)
Discussion started by: majid.merkava
1 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
7. UNIX for Dummies Questions & Answers
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies
8. Red Hat
Can you please modify my script. This script is not working
for i in /dev/sdf
do
/bin/raw /dev/raw/`/bin/basename ${i}` ${i}
/bin/sleep 2
/bin/chown orasm:ordba /dev/raw/`/bin/basename ${i}`
/bin/chmod 660... (9 Replies)
Discussion started by: karthik9358
9 Replies
9. Red Hat
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
10. Solaris
Generally, this is what we do:-
On primary, export 2 LUNs (add-vdsdev).
On primary, assign these disks to the ldom in question (add-vdisk).
On ldom, created mirrored zpool from these two disks.
On one server (which is older) we have:-
On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
RAW(8) System Manager's Manual RAW(8)
NAME
raw - bind a Linux raw character device
SYNOPSIS
raw /dev/raw/raw<N> <major> <minor>
raw /dev/raw/raw<N> /dev/<blockdev>
raw -q /dev/raw/raw<N>
raw -qa
DESCRIPTION
raw is used to bind a Linux raw character device to a block device. Any block device may be used: at the time of binding, the device
driver does not even have to be accessible (it may be loaded on demand as a kernel module later).
raw is used in two modes: it either sets raw device bindings, or it queries existing bindings. When setting a raw device, /dev/raw/raw<N>
is the device name of an existing raw device node in the filesystem. The block device to which it is to be bound can be specified either
in terms of its major and minor device numbers, or as a path name /dev/<blockdev> to an existing block device file.
The bindings already in existence can be queried with the -q option, with is used either with a raw device filename to query that one
device, or with the -a option to query all bound raw devices.
Once bound to a block device, a raw device can be opened, read and written, just like the block device it is bound to. However, the raw
device does not behave exactly like the block device. In particular, access to the raw device bypasses the kernel's block buffer cache
entirely: all I/O is done directly to and from the address space of the process performing the I/O. If the underlying block device driver
can support DMA, then no data copying at all is required to complete the I/O.
Because raw I/O involves direct hardware access to a process's memory, a few extra restrictions must be observed. All I/Os must be cor-
rectly aligned in memory and on disk: they must start at a sector offset on disk, they must be an exact number of sectors long, and the
data buffer in virtual memory must also be aligned to a multiple of the sector size. The sector size is 512 bytes for most devices.
Use the /etc/sysconfig/rawdevices file to define the set of raw device mappings automatically created during the system startup sequence.
The format of the file is the same used in the command line with the exception that the "raw" command itself is omitted.
OPTIONS
-q Set query mode. raw will query an existing binding instead of setting a new one.
-a With -q , specifies that all bound raw devices should be queried.
-h provides a usage summary.
BUGS
The Linux dd (1) command does not currently align its buffers correctly, and so cannot be used on raw devices.
Raw I/O devices do not maintain cache coherency with the Linux block device buffer cache. If you use raw I/O to overwrite data already in
the buffer cache, the buffer cache will no longer correspond to the contents of the actual storage device underneath. This is deliberate,
but is regarded either a bug or a feature depending on who you ask!
AUTHOR
Stephen Tweedie (sct@redhat.com)
Version 0.1 Aug 1999 RAW(8)