Sponsored Content
Top Forums Shell Programming and Scripting Formatting problem with sizes from /proc/partitions Post 302437771 by pinga123 on Friday 16th of July 2010 05:33:54 AM
Old 07-16-2010
Quote:
Originally Posted by pludi
The dm-? devices are probably LVM volumes.
Is this because while creating virtual disk rather than allocating fixed sized disk i have set it to dynamically extend volume of disk?
 

10 More Discussions You Might Find Interesting

1. Programming

Proc problem

Hello all , We have a c program , it is running well on AIX 4.3.3.0 .But when we run it on AIX 4.2.1.0 version the program exit when it begin to do this command : Exec sql connect . N.B: The version of C compiler is :4.2 Database :Oracle8 thanks in advance . Elie . (2 Replies)
Discussion started by: eyounes
2 Replies

2. Shell Programming and Scripting

Problem in Formatting File

I am facing a very challenging task here but can't finish it.I request all of you to help me please. I have one file which contain some data i need to format it. data file contain data like 54321|item-68|owner|yes||||$ 00-10|invoice|3221|||# 00-11|invoice|3221|||#... (1 Reply)
Discussion started by: Dhruva
1 Replies

3. Filesystems, Disks and Memory

Problem setting up raw partitions on SUSE v8.0 using LVM on Oracle 8.1.7.URGENT!!!!!!

Hi all! Working on Oracle v8.1.7.0.0 with OS  as Suse v8.0 Linux. I had created LVM,linked raw devices to LVM as below: # for binding raw devices raw /dev/raw/raw1 /dev/oracle/sam_raw_system_251m raw /dev/raw/raw2 /dev/oracle/sam_raw_users_26m raw /dev/raw/raw3... (2 Replies)
Discussion started by: Amitstora
2 Replies

4. Shell Programming and Scripting

Formatting Problem

Hi Suppose we have a file consisting of nos in following format 123 - 789 123 - 828 345 - 989 345 - 792 I require the following output 123, 789,828 345, 989,792 Means Unique nos in 1st Column and Corresponding two nos in comma separated 2nd Column Please help me out... (6 Replies)
Discussion started by: PradeepRed
6 Replies

5. AIX

ProC and other C file compilation problem on AIX

I am linking my compiled proC file with other C files and getting following error. ld: 0711-711 ERROR: Input file /opt/orabase/oracle/product/10.2.0/db_1/lib/libirc.a is empty. The file is being ignored. I used following command to compile my proC code. proc iname=dbConnect.pc code=ANSI_C... (0 Replies)
Discussion started by: amit.singhal
0 Replies

6. Shell Programming and Scripting

output formatting problem

I would like to keep the complete lines in the output, but my script adds carriage returns for each space (e.g. keep BRITISH AIRWAYS on one line in the output): File1= BAW BRITISH AIRWAYS RYR RYAN AIR for i in $(cat File1) do echo $i done Output: BAW BRITISH AIRWAYS RYR... (4 Replies)
Discussion started by: barny
4 Replies

7. Shell Programming and Scripting

Problem with array sizes

If I do :- set -A classifications atype btype ctype dtype etype for i in ${classifications} do echo $i print $i >> /tmp/class.txt done print "${#classifications}" The array prints as I would expect and the size of the array is 5 (as expected). If I use an alternative... (2 Replies)
Discussion started by: sniper57
2 Replies

8. UNIX for Dummies Questions & Answers

_/proc/stat vs /proc/uptime

Hi, I am trying to calculate the CPU Usage by getting the difference between the idle time reported by /proc/stat at 2 different intervals. Now the 4th entry in the first line of /proc/stat will give me the 'idle time'. But I also came across /proc/uptime that gives me 2 entries : 1st one as the... (0 Replies)
Discussion started by: coderd
0 Replies

9. UNIX for Dummies Questions & Answers

Query regarding /proc/partitions.

hi whenever i fire cat /proc/partition i get following output. I can make sense out of first 4 lines but what does dm-* suggests. Please help. # cat /proc/partitions major minor #blocks name 8 0 142577664 sda 8 1 104391 sda1 8 2 41945715 sda2 8 3 ... (1 Reply)
Discussion started by: pinga123
1 Replies

10. UNIX for Advanced & Expert Users

Dos2UNIX formatting problem

Hi, I was trying to dos2unix a file that has some special characters but dos2unix converted those into different format. I am working on sun server. I guess the default for dos2unix on sun server is ISO format . Can i change the format so that it does the conversion in UTF format? Because I... (3 Replies)
Discussion started by: abhi1988sri
3 Replies
bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME
bootconf - boot device configuration table DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the file manually. There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown: disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following: Indicates that the root disk is in LVM or VERITAS Volume Manager (VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file. Indicates that the root disk is in the "whole disk" format with no partitions, but boot and swap space are reserved outside the file system. device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file that references the entire disk. Blank lines are permitted. Any line beginning with a is considered to be a comment. DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self- explanatory; a few warrant additional explanation: If there are no other messages about the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem is. The specified device file does not point to a disk where there is a lif which contains the file Some character other than or is in the first field of a line. As of release 10.0, the boot areas in must all be on the same type of disk layout. There are characters after the device file specification. EXAMPLES
The boot area is on an LVM root disk: l /dev/disk/disk7_p2 The boot area is on a whole disk layout: w /dev/disk/disk7 WARNINGS
All of the boot devices in the file must have the same disk layout. AUTHOR
was developed by the Hewlett-Packard Company. FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). documentation. bootconf(4)
All times are GMT -4. The time now is 10:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy