We will need to see all the script I think, to me it should read more like;
But you might want to put some error checking in place, I think - reading your additional post that you need a more fundamental understanding of things. The second script is failing because the files donot exist.
I'm trying to figure out how to simply create a 500Gb ufs file system named
/rec using DiskSuite 4.2.1 on a Solaris 8 platform via command line using two
250Gb partitions on two different disks. Does anyone know what the proper
command string and options are to perform this task? Would I use the... (2 Replies)
dear sir/madam
presently i am in a process of creating a multithread pool using
clone() system call in unix with c programming.
i am facing some problem ie., i am able create multithread pool and
able to keep all the threads in wait state,but when i call kill
(afunction revoke a... (6 Replies)
Hi All,
I am planning to do a LVM replicate to another server.
Example :
server1.foo.com has / , /boot , swap and few LVM partitions. All are in /dev/sda disk of size 80GB. /dev/sda5 is a LVM partition which has only one vg00 and it has 2 LV's (/var and /usr) and a SAN storage connected to... (0 Replies)
Hi All,
I am planning to do a LVM replicate to another server.
Example :
server1.foo.com has / , /boot , swap and few LVM partitions. All are in /dev/sda disk of size 80GB. /dev/sda5 is a LVM partition which has only one vg00 and it has 2 LV's (/var and /usr) and a SAN storage connected to... (0 Replies)
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Hi all;
I have a quick question about LVM.
2.6.18-92.1.18.el5
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 5.3 (Tikanga)
Release: 5.3
Codename: Tikanga
I was going through /etc/lvm.conf and I am not clear with lvm meta... (0 Replies)
Hey everyone.
I am working on designing a logging solution for a deployment we have going out in a few months. Right now we have a single storage head end, connected via fibre to a SAN. Basically the plan is to create a number of smaller LUNs on the SAN, and then use LVM2 to handle concatenating... (5 Replies)
I've three partitions on /dev/sda: sda1, sda2 sda3. There is FREE space between sda2 and sda3 and sda3 ends on the last sector. sda2 and sda3 have the same number of sectors allocated and so are the exact same size.
/dev/sda2 is already part of the VG VolGroup. However, what puzzles me is that... (0 Replies)
I apologize is this isn't an appropriate post for the 'advanced' UNIX, so please let me know if I should post this under UNIX for dummies, but here's my problem in a nutshell: I having problems creating a mirrored logical volume.
I have created two new physical volumes
... (2 Replies)
Discussion started by: simonrodan
2 Replies
LEARN ABOUT V7
rp
RP(4) Kernel Interfaces Manual RP(4)NAME
rp - RP-11/RP03 moving-head disk
DESCRIPTION
The files rp0 ... rp7 refer to sections of RP disk drive 0. The files rp8 ... rp15 refer to drive 1 etc. This allows a large disk to be
broken up into more manageable pieces.
The origin and size of the pseudo-disks on each drive are as follows:
disk start length
0 0 81000
1 0 5000
2 5000 2000
3 7000 74000
4-7 unassigned
Thus rp0 covers the whole drive, while rp1, rp2, rp3 can serve usefully as a root, swap, and mounted user file system respectively.
The rp files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records. There is also a `raw' interface which provides for direct transmission between the disk and the user's read or write buffer. A
single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are
transmitted. The names of the raw RP files begin with rrp and end with a number which selects the same disk section as the corresponding
rp file.
In raw I/O the buffer must begin on a word boundary.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO hp(4)BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
RP(4)