Sponsored Content
Operating Systems HP-UX Pid X killed due to text modification or page I/O error Post 302320180 by vbe on Wednesday 27th of May 2009 09:10:44 AM
Old 05-27-2009
VxFS or VxVM ?
All our servers use LVM but the filesystems are VxFS (OnlineJFS)...
In other words 2 totally diferent products...but that not the todays topic I agree...

2 things come to my mind:
text modification -> Any NFS around?
or
I/O error -> That may not be good news...

I would test the (yet?) primary swap:
Code:
fsck -F vxfs -y -o full /dev/vg00/lvol2

But I dont know what it would look like when not in LVM... (the case above)
You could also try:
Code:
dd if=/dev/rdsk/<yourbootdisk -eg c0t1d0>  of=/dev/null bs=256k

and see if it generates errors
 

10 More Discussions You Might Find Interesting

1. Programming

Text Modification and page I/O error

Hi!, while launching my C application on HP-UX 10.2 workstation, I get the following error message sometime: Pid 9951 killed due to text modification or page I/O error Could someone tell me what does this error means?? and how is this caused? Thanx in Advance, JP (4 Replies)
Discussion started by: jyotipg
4 Replies

2. Filesystems, Disks and Memory

finding out the pid for a busy text file

Can some one please tell me how to find out the proccess ID that is holding up a file. I am attempting to remove a file and I am getting a message stating that it is busy. i.e rm filename filename: 777 mode ? (y/n) y rm: filename not removed. Text file busy Thanks in advance. (1 Reply)
Discussion started by: jxh461
1 Replies

3. Shell Programming and Scripting

SED for text file modification

Hi all, i have a text file something like that FLAG DATE(YYYYMMDD) TIME(HHMMSS) FLAG1 DATE20060101 141216 FLAG1 DATE20070101 141216 FLAG2 DATE20060102 140010 FLAG2 DATE20060103 101212 FLAG1 ... (6 Replies)
Discussion started by: gfhgfnhhn
6 Replies

4. HP-UX

Pid killed due to trashed stack

Hi when im running an application in load im getting pid 2433 killed due to trashed stack Pid 2433 was killed due to failure in writing the signal context. when we ll get this type of problem.any solnnnn plz give reply this is my system config: HP-UX devusp2 B.11.11 U 9000/800... (1 Reply)
Discussion started by: pramod123
1 Replies

5. UNIX for Advanced & Expert Users

Problem due to Fork Error

Hi, I have developed a datastage job...which has many process running in parallel..but because of Fork Error my job is not working:( Can any body help me out to solve this Fork error problem.:rolleyes: My Os is SUNOS. IS there any setting in Unix through admin where in if i set some paramter... (8 Replies)
Discussion started by: Amey Joshi
8 Replies

6. Shell Programming and Scripting

aborted due to compilation error

I wanted to edit the time for a cron job that cleans out the quarantine in mailscanner. etc/cron.daily/clean.quarantine I edited the file #!/usr/bin/perl # # IMPORTANT NOTE: # # Change the next line to 0 instead of 1 to enable this script. # By default it will be disabled and... (2 Replies)
Discussion started by: mcraul
2 Replies

7. Shell Programming and Scripting

Text string modification

My shell needs to take a 10 digit number and output it in the forum nnn-nnn-nnnn I considered using the fold command but that won't help too much. (11 Replies)
Discussion started by: computethis
11 Replies

8. Shell Programming and Scripting

bc syntax error due to sed

Hi all, before posting this questions i have looked up and found similar cases as the one i have but none of them had the answer i was lookink for. i have the next two commands (with their corresponding output) e1=$(grep KCAL input.OUT | sed 's/ FINAL HEAT OF FORMATION = ... (2 Replies)
Discussion started by: ezitoc
2 Replies

9. Shell Programming and Scripting

Grep text matching problem with script which checks if web page contains text.

I wrote a Bash script which checks to see if a text string exists on a web page and then sends me an email if it does (or does not e.g. "Out of stock"). I run it from my crontab, it's quite handy from time to time and I've been using it for a few years now. The script uses wget to download an... (6 Replies)
Discussion started by: gencon
6 Replies

10. Shell Programming and Scripting

Help with text modification and displaying

I have a file storing some text and another file storing some numbers I want to display characters other than the specified place of strings one.txt xyz abc 233 skfo 4r443 sfs abc abcd sd fsdf sdfd abc 11 abc 33 abc dsaf two.txt Nt_djd_k='5-6,7-9' Nt_hh_l='3-6,7-8' a=`grep... (4 Replies)
Discussion started by: rahulsk
4 Replies
LVM(3pm)						User Contributed Perl Documentation						  LVM(3pm)

NAME
Linux::LVM - Perl extension for accessing Logical Volume Manager(LVM) data structures on Linux. SYNOPSIS
use Linux::LVM; Linux::LVM->units('G'); ABSTRACT
The live data used in the examples is included in the DESCRIPTION area for your convenience and reference. DESCRIPTION
units() Get or set the units used to report sizes of LVs, PVs, etc. legal values: hbskmgtpeHBSKMGTPE see man lvm documentation of --units get_volume_group_list() This routine will return an array that contains the names of the volume groups. @vgs = get_volume_group_list(); print "@vgs "; Would yield the following: vg00 get_volume_group_information($) This routine will return all of the volume group information about the specified volume group. %vg = get_volume_group_information("vg00"); foreach(sort keys %vg) { print "$_ = $vg{$_} "; } Would yield the following: access = read/write act_pv = 2 alloc_pe = 3840 alloc_pe_size = 15 alloc_pe_size_unit = GB cur_lv = 3 cur_pv = 2 free_pe = 864 free_pe_size = 3.38 free_pe_size_unit = GB max_lv = 256 max_lv_size = 255.99 max_lv_size_unit = GB max_pv = 256 open_lv = 0 pe_size = 4 pe_size_unit = MB status = available/resizable total_pe = 4704 uuid = BBq8si-NyRR-9ZNW-3J5e-DoRO-RBHK-ckrszi vg_number = 0 vg_size = 18.38 vg_size_unit = GB vgname = vg00 get_logical_volume_information($) This routine will return all of the logical volume information associated with the specified volume group. %lv = get_logical_volume_information("vg00"); foreach $lvname (sort keys %lv) { foreach(sort keys %{$lv{$lvname}}) { print "$_ = $lv{$lvname}->{$_} "; } print " "; } Would yield the following results: alloc_le = 1024 allocation = next free cur_le = 1024 device = 58:0 lv_number = 1 lv_size = 4 lv_size_unit = GB name = /dev/vg00/lvol1 open_lv = 0 read_ahead = 1024 status = available write_access = read/write alloc_le = 1280 allocation = next free cur_le = 1280 device = 58:1 lv_number = 2 lv_size = 5 lv_size_unit = GB name = /dev/vg00/lvol2 open_lv = 0 read_ahead = 1024 status = available write_access = read/write alloc_le = 1536 allocation = next free cur_le = 1536 device = 58:2 lv_number = 3 lv_size = 6 lv_size_unit = GB name = /dev/vg00/lvol3 open_lv = 0 read_ahead = 1024 status = available write_access = read/write get_physical_volume_information($) This routine will return all of the information information about the physical volumes assigned to the specified volume group. %pv = get_physical_volume_information("vg00"); foreach $pvname (sort keys %pv) { foreach(sort keys %{$pv{$pvname}}) { print "$_ = $pv{$pvname}->{$_} "; } print " "; } Would yield the following results: device = /dev/hda3 free_pe = 0 pv_number = 1 status = available / allocatable total_pe = 2160 device = /dev/hda4 free_pe = 864 pv_number = 2 status = available / allocatable total_pe = 2544 get_lv_info($) This routine will return all of the information about the specified logical volume. The information will be returned in a hash. get_lv_info %lv = get_lv_info("/dev/vg00/lvol1"); foreach (sort keys %lv) { print "$_ = $lv{$_} "; } Would yield the following results: access = read/write alloc_le = 1024 allocation = next free block_device = 58:0 current_le = 1024 lv_name = /dev/vg00/lvol1 lv_number = 1 lv_open = 0 read_ahead = 1024 size = 4 size_unit = GB status = available vg_name = vg00 get_pv_info($) This routine will return all of the information about the specified physical volume. The information will be returned in a hash. %pv = get_pv_info("/dev/hda3"); foreach (sort keys %pv) { print "$_ = $pv{$_} "; } Would yield the following results: alloc_pe = 2160 allocatable = yes (but full) free_pe = 0 num_lvols = 2 pe_size = 4096 pe_size_unit = KByte pv_name = /dev/hda3 pv_number = 1 sectors = 17703630 size = 8.44 size_info = NOT usable 4.19 MB [LVM: 136 KB] size_unit = GB status = available total_pe = 2160 uuid = 2c5ADu-oEdt-ovCe-rqp0-MWpF-I5u1-8XigH4 vg_name = vg00 Command Output Used In The Above Examples: /sbin/vgdisplay -v --- Volume group --- VG Name vg00 VG Access read/write VG Status available/resizable VG # 0 MAX LV 256 Cur LV 3 Open LV 0 MAX LV Size 255.99 GB Max PV 256 Cur PV 2 Act PV 2 VG Size 18.38 GB PE Size 4 MB Total PE 4704 Alloc PE / Size 3840 / 15 GB Free PE / Size 864 / 3.38 GB VG UUID BBq8si-NyRR-9ZNW-3J5e-DoRO-RBHK-ckrszi --- Logical volume --- LV Name /dev/vg00/lvol1 VG Name vg00 LV Write Access read/write LV Status available LV # 1 # open 0 LV Size 4 GB Current LE 1024 Allocated LE 1024 Allocation next free Read ahead sectors 1024 Block device 58:0 --- Logical volume --- LV Name /dev/vg00/lvol2 VG Name vg00 LV Write Access read/write LV Status available LV # 2 # open 0 LV Size 5 GB Current LE 1280 Allocated LE 1280 Allocation next free Read ahead sectors 1024 Block device 58:1 --- Logical volume --- LV Name /dev/vg00/lvol3 VG Name vg00 LV Write Access read/write LV Status available LV # 3 # open 0 LV Size 6 GB Current LE 1536 Allocated LE 1536 Allocation next free Read ahead sectors 1024 Block device 58:2 --- Physical volumes --- PV Name (#) /dev/hda3(1) PV Status available / allocatable Total PE / Free PE 2160 / 0 PV Name (#) /dev/hda4(2) PV Status available / allocatable Total PE / Free PE 2544 / 864 SEE ALSO
vgdisplay(1M) lvdisplay(1M) pvdisplay(1M) AUTHOR
Chad Kerner, <chadkerner@yahoo.com> COPYRIGHT AND LICENSE
Copyright 2003 by Chad Kerner This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2012-02-11 LVM(3pm)
All times are GMT -4. The time now is 07:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy