Sure
cat /tmp/file
A4ABCdd
a654321
a987463
1122322
I am trying to get the following output
a654321
a987463
I want to get first character be [a-z] and the last 6 characters be numbers [0-9]
Trying something like this
awk '{ if ($1==/^[a-z][0-9]{6}$/) print $1 }' /tmp/file
TIA
How can I test for the following:
A4ABCdd
a654321
a987463
1122322
I want to get first character be [a-z] and the last 6 characters be numbers [0-9]
So, this would print out
Desired output:
a654321
a987463
Sorry, forgot to put restore directions.
In case your TL gives you issues, here is how you revert
change bootlist to hdisk0 (bootlist -m normal hdisk0)
reboot
alt_diskinstall -X (this will clean up the hdisk1 image, and clean up ODM entries)
HTH
Okay guys, here is what I tried, and works perfectly!
Unmirror my rootvg
Reduce my rootvg (remove hdisk1 from rootvg)
alt_diskinstall -C hdisk1 (this takes a mksysb of hdisk0, and restores it to hdisk1, and change the bootlist to hdisk1, and sets bootimage on hdisk1)
Reboot (will automatically...
Anyone here practice, unmirroring rootvg before applying ML/TL?
I have a NFS share with my ML8, I usually do a mount and an smit update_all
Is this a good practice or overkill?
Hey Ken:
Just that I understand this, you tried to go from ML1 to TL8, and Java SDK was giving you problems while doing the 'smitty update_all' ?
The taylored version is, when you select '01' and you would like to goto '08'?
So your upgrade went well?
p5wizard:
thanks for the good explanation. (more important, thanks for putting it into plain english!)
Seems I may need to disable diagele for the inactive paths...
still awating for my SAN team's response.
p5wizard:
To answer your questions, yes I am able to get to my disks (hdiskpowerXX). All the errors on my errpt show hdiskXX not hdiskpowerXX (if that was the case, I don't think I can access data).
My question is what is hdiskXX in my server, is it a virtual path?
Also, I will be speaking...
DukeSSD & P5wizard:
Unfortunately, there are other hdisks that show the same exact error.
I do have a backup but this is a large production box. Each LUN is about 256Gig, and I don't think I have the option to remove and restore. I wish I did :-)
I will ask the SAN guys to see if there is a...
Hi All,
I have a system hooked up to the SAN, and I keep getting "Disk Operation Errors"
LABEL: SC_DISK_ERR2
IDENTIFIER: 79B0DF89
Type: PERM
Resource Type: CLAR_FC_LUNZ
Description
DISK OPERATION ERROR
Any idea whats going on with this?
TIA
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.