Author: Emerson .

CA eTrust – Users cannot set their own password via selang

I logged in the server with my user and I became root using su

emerson@solaris:~ $ su –
Password:

I was trying to reset my password but it was giving the error message “Users cannot set their own password via selang”

root@solaris:/ # /usr/seos/bin/selang -c “cu emerson pwasown(changeme) unix”
CA Access Control selang v12.0.1.1262 – CA Access Control command line interpreter
Copyright (c) 2008 CA. All rights reserved.

(localhost)
ERROR: Operation not allowed
ERROR: Users cannot set their own password via selang
(localhost)
Unix :
======
ERROR: Operation not allowed
ERROR: Users cannot set their own password via selang

If you login with the user and try to replace the user’s password it will give this error. You need to login with another user to run the command above.

Running fsck and automatically fix any errors encountered

Tried to mount a filesystem but the OS requested to run fsck

root@solaris:/ # mount /1a
mount: the state of /dev/md/dsk/d7 is not okay
and it was attempted to be mounted read/write
mount: Please run fsck and try again

To run fsck and try to automatically fix any errors encountered, pass the flag -y

root@solaris:/ # fsck -y /dev/md/dsk/d7
** /dev/md/rdsk/d7
** Last Mounted on /1a
** Phase 1 – Check Blocks and Sizes
** Phase 2 – Check Pathnames
** Phase 3a – Check Connectivity
** Phase 3b – Verify Shadows/ACLs
** Phase 4 – Check Reference Counts
UNREF FILE I=1762708 OWNER=patrol MODE=100644
SIZE=263127 MTIME=Jan 25 15:40 2009
RECONNECT? yes

LINK COUNT FILE I=1762708 OWNER=patrol MODE=100644
SIZE=263127 MTIME=Jan 25 15:40 2009 COUNT 0 SHOULD BE 1
ADJUST? yes

UNREF FILE I=2376356 OWNER=patrol MODE=10700
SIZE=0 MTIME=Jan 25 15:37 2009
CLEAR? yes

UNREF FILE I=2977939 OWNER=spectrum MODE=100600
SIZE=0 MTIME=Jan 25 15:37 2009
CLEAR? yes

UNREF FILE I=2977940 OWNER=spectrum MODE=100600
SIZE=0 MTIME=Jan 25 15:37 2009
CLEAR? yes

UNREF FILE I=2977941 OWNER=spectrum MODE=100600
SIZE=0 MTIME=Jan 25 15:37 2009
CLEAR? yes

** Phase 5 – Check Cylinder Groups

CORRECT BAD CG SUMMARIES FOR CG 34? yes

CORRECTED SUPERBLOCK SUMMARIES FOR CG 34
CORRECTED SUMMARIES FOR CG 34
FILE BITMAP WRONG
FIX? yes

FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 69
CORRECTED SUMMARIES FOR CG 69
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 146
CORRECTED SUMMARIES FOR CG 146
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 147
CORRECTED SUMMARIES FOR CG 147
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 165
CORRECTED SUMMARIES FOR CG 165
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 168
CORRECTED SUMMARIES FOR CG 168
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 175
CORRECTED SUMMARIES FOR CG 175
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 202
CORRECTED SUMMARIES FOR CG 202
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 224
CORRECTED SUMMARIES FOR CG 224
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 233
CORRECTED SUMMARIES FOR CG 233
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 264
CORRECTED SUMMARIES FOR CG 264
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 269
CORRECTED SUMMARIES FOR CG 269
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 275
CORRECTED SUMMARIES FOR CG 275
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 286
CORRECTED SUMMARIES FOR CG 286
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 311
CORRECTED SUMMARIES FOR CG 311
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 316
CORRECTED SUMMARIES FOR CG 316
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 380
CORRECTED SUMMARIES FOR CG 380
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 386
CORRECTED SUMMARIES FOR CG 386
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 388
CORRECTED SUMMARIES FOR CG 388
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 395
CORRECTED SUPERBLOCK SUMMARIES FOR CG 495
CORRECTED SUPERBLOCK SUMMARIES FOR CG 516
CORRECTED SUMMARIES FOR CG 516
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 519
CORRECTED SUMMARIES FOR CG 519
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 539
CORRECTED SUMMARIES FOR CG 539
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 546
CORRECTED SUMMARIES FOR CG 546
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 576
CORRECTED SUMMARIES FOR CG 576
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 578
CORRECTED SUMMARIES FOR CG 578
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 579
CORRECTED SUMMARIES FOR CG 579
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 588
CORRECTED SUMMARIES FOR CG 588
FRAG BITMAP WRONG (CORRECTED)
CORRECTED SUPERBLOCK SUMMARIES FOR CG 631
CORRECTED SUMMARIES FOR CG 631
FRAG BITMAP WRONG (CORRECTED)
CORRECT GLOBAL SUMMARY
SALVAGE? yes

90655 files, 5690552 used, 50760198 free (12494 frags, 6343463 blocks, 0.0% fragmentation)

***** FILE SYSTEM WAS MODIFIED *****

Since fsck encountered errors, we pass once again and see if more errors are encountered

root@solaris:/ # fsck -y /dev/md/dsk/d7
** /dev/md/rdsk/d7
** Last Mounted on /1a
** Phase 1 – Check Blocks and Sizes
** Phase 2 – Check Pathnames
** Phase 3a – Check Connectivity
** Phase 3b – Verify Shadows/ACLs
** Phase 4 – Check Reference Counts
** Phase 5 – Check Cylinder Groups
90655 files, 5690552 used, 50760198 free (12494 frags, 6343463 blocks, 0.0% fragmentation)

Since no more errors were encountered, we try to mount the filesystem once again

root@solaris:/ # mount /1a
root@solaris:/ # df -k /1a
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d7 56450750 5690552 50195691 11% /1a

Solaris SVM error when attaching a new disk – metattach I/O Error

I was trying to increase a metadevice with another disk but I was getting an I/O error

root@solaris:~ # metattach d200 /dev/rdsk/emcpower46c
metattach: solaris: /dev/dsk/emcpower46c: I/O error

Nothing strange was appearing in the emcpower disk

root@solaris:~ # powermt display dev=emcpower46
Pseudo name=emcpower46a
Symmetrix ID=000287752010
Logical device ID=01A1
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
—————- Host ————— – Stor – — I/O Path – — Stats —
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
3072 pci@8,600000/SUNW,emlxs@1/fp@0,0 c1t5006048449AFD288d18s0 FA 9aA active alive 0 0
3073 pci@8,600000/SUNW,emlxs@2/fp@0,0 c2t5006048449AFD287d18s0 FA 8aA active alive 0 0

A friend here at work asked if the disk has a label. It didn’t have one.

selecting emcpower46e
[disk formatted]
Disk not labeled. Label it now? yes

After that I was able to increase the metadevice.

root@solaris:~ # metattach d200 /dev/rdsk/emcpower46c
d200: component is attached

UnixWare – Unable to invoke login scheme when logging in

If you’re having problems after you’re certain that you are inputting the correct username and password in an UnixWare like in this case below

emerson@shellcore:~ $ telnet 192.168.45.54
Trying 192.168.45.54…
Connected to 192.168.45.54.
Escape character is ‘^]’.

UnixWare 2.1.3 (SCO) (pts/0)

login: emerson
Password:
UX:in.login: ERROR: Login incorrect
telnetd: Unable to invoke login scheme.
Connection to 192.168.45.54 closed by foreign host.

You need to clear the file /var/adm/lastlog

root@SCO:/ # > /var/adm/lastlog

After that, you’ll no longer see the message that is preventing you from logging in

emerson@shellcore:~ $ telnet 192.168.45.54
Trying 192.168.45.54…
Connected to 192.168.45.54.
Escape character is ‘^]’.

UnixWare 2.1.3 (SCO) (pts/0)

login: emerson
Password:
UX:in.login: ERROR: Your password has expired.
UX:in.login: TO FIX: Choose a new one
Old password:

Playstation 3 version of the Street Fighter IV FightStick Tournament Edition works on a PC

I recently bought the Street Fighter IV FightStick Tournament Edition for the PS3. My friend asked if I tried to use in the PC because he can use his PS3 controller on the PC. I tried and the FightStick works on the PC.

Here is the official page on MadCatz FAQ that says the PC is not officially supported but won’t work on a computer that has an NVidia chipset.

Update: Does my Mad Catz Tournament Edition Arcade Stick for PS3 works on PC / PS4 / Street Fighter 5?

Solaris SVM – Metadevice in needs maintenance state. Invoke metareplace

On your Solaris server, a disk that is part of a mirror goes bad and needs replacement.

root@solaris:~ # metastat d50
d50: Mirror
Submirror 0: d51
State: Needs maintenance
Submirror 1: d52
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 32776896 blocks (15 GB)

d51: Submirror of d50
State: Needs maintenance
Invoke: metareplace d50 c0t0d0s5
Size: 32776896 blocks (15 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t0d0s5 0 No Maintenance Yes

d52: Submirror of d50
State: Okay
Size: 32776896 blocks (15 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t1d0s5 0 No Okay Yes

Device Relocation Information:
Device Reloc Device ID
c0t0d0 Yes id1,sd@n500000e013633ce0
c0t1d0 Yes id1,sd@n500000e013633810

After you physically replace the bad disk, the submirror will still show as needing maintenance. You need to invoke metareplace to sync the submirror

root@solaris:~ # metareplace -e d50 /dev/dsk/c0t0d0s5
d50: device c0t0d0s5 is enabled

root@solaris:~ # metastat d50
d50: Mirror
Submirror 0: d51
State: Resyncing
Submirror 1: d52
State: Okay
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 32776896 blocks (15 GB)

d51: Submirror of d50
State: Resyncing
Size: 32776896 blocks (15 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t0d0s5 0 No Resyncing Yes

d52: Submirror of d50
State: Okay
Size: 32776896 blocks (15 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c0t1d0s5 0 No Okay Yes

Device Relocation Information:
Device Reloc Device ID
c0t0d0 Yes id1,sd@n500000e013633ce0
c0t1d0 Yes id1,sd@n500000e013633810

Repeat the process to all the remaining submirrors that were on that disk

Linux denying user access after reseting password

Depending of how you configured your Linux server, the Pluggable Authentication Module (PAM) won’t let you login.

To check the login attempts to see if it needs to be reset type faillog -u <username>

root@linux:~ # faillog -u username
Username Failures Maximum Latest
<username>       15        0

Reset the counter with the -r flag

root@linux:~ # /usr/bin/faillog -r username
Username Failures Maximum Latest
<username>        0        0

If you’re root but is not managing to become a user with su, you also need to reset the login counter

root@linuxserver ~ # su – username
su: incorrect password

root@linux:~ # /sbin/pam_tally —-user username —-reset
User <username> (685) had 36

root@linux:~ # su – username
username@linux:~ $

For RHEL 6, it uses pam_tally2

root@rhel64:~ # /sbin/pam_tally2 —-user username —-reset
Login Failures Latest failure From
username 9 02/13/14 09:22:10 /dev/pts/1

root@rhel64:~ # /sbin/pam_tally2 —-user username —-reset
Login Failures Latest failure From
username 0

CA Access Control sepass error message: Password was changed recently, cannot be changed again at this time

When you try to change the password of a user that recently changed its password and the server has the CA Access Control, the change will be denied.

root@solaris:/ # passwd username
CA Access Control sepass v12.0.1.1262 – Password replacement
Copyright (c) 2008 CA. All rights reserved.
Password was changed recently, cannot be changed again at this time.

To force the password change, type the command and change <username> and <password>to the values appropriate to your case

root@solaris:/ # /usr/seos/bin/selang -c “cu <username> pwasown (<password>)”
CA Access Control selang v12.0.1.1262 – CA Access Control command line interpreter
Copyright (c) 2008 CA. All rights reserved.

(localhost)
Successfully updated USER <username>
(localhost)
Native:
===
Successfully updated USER <username>

Removing dead paths on EMC PowerPath

Check the HBA paths with powermt display and check if there are any failed path.

root@solaris:~ # powermt display
Symmetrix logical device count=12
CLARiiON logical device count=24
Hitachi logical device count=0
Invista logical device count=0
HP xp logical device count=0
Ess logical device count=0
HP HSx logical device count=0
==============================================================================
—– Host Bus Adapters ——— —— I/O Paths —– —— Stats ——
### HW Path Summary Total Dead IO/Sec Q-IOs Errors
==============================================================================
2304 ssm@0,0/pci@1c,700000/pci@3/lpfc@4 failed 12 12 – 0 12
2305 ssm@0,0/pci@1c,700000/pci@3/lpfc@5 optimal 12 0 – 0 0
2306 ssm@0,0/pci@1c,600000/lpfc@1 failed 24 24 – 0 24
2307 ssm@0,0/pci@1d,700000/pci@1/lpfc@4 failed 12 12 – 0 12
2308 ssm@0,0/pci@1d,700000/pci@1/lpfc@5 optimal 12 0 – 0 0
2309 ssm@0,0/pci@1d,600000/lpfc@1 optimal 24 0 – 1 0

To remove the failed paths, run powermt check

root@solaris:~ # powermt check
Warning: Symmetrix device path c5t18d10s0 is currently dead.
Do you want to remove it (y/n/a/q)? a
Warning: Symmetrix device path c5t18d11s0 is currently dead.
Warning: Symmetrix device path c5t18d12s0 is currently dead.
Warning: Symmetrix device path c5t18d1s0 is currently dead.
Warning: Symmetrix device path c5t18d2s0 is currently dead.
Warning: Symmetrix device path c5t18d3s0 is currently dead.
Warning: Symmetrix device path c5t18d4s0 is currently dead.
Warning: Symmetrix device path c5t18d5s0 is currently dead.
Warning: Symmetrix device path c5t18d6s0 is currently dead.
Warning: Symmetrix device path c5t18d7s0 is currently dead.
Warning: Symmetrix device path c5t18d8s0 is currently dead.
Warning: Symmetrix device path c5t18d9s0 is currently dead.
Warning: Symmetrix device path c7t19d10s0 is currently dead.
Warning: Symmetrix device path c7t19d11s0 is currently dead.
Warning: Symmetrix device path c7t19d12s0 is currently dead.
Warning: Symmetrix device path c7t19d1s0 is currently dead.
Warning: Symmetrix device path c7t19d2s0 is currently dead.
Warning: Symmetrix device path c7t19d3s0 is currently dead.
Warning: Symmetrix device path c7t19d4s0 is currently dead.
Warning: Symmetrix device path c7t19d5s0 is currently dead.
Warning: Symmetrix device path c7t19d6s0 is currently dead.
Warning: Symmetrix device path c7t19d7s0 is currently dead.
Warning: Symmetrix device path c7t19d8s0 is currently dead.
Warning: Symmetrix device path c7t19d9s0 is currently dead.
Warning: CLARiiON device path c1t16d0s0 is currently dead.
Warning: CLARiiON device path c1t16d10s0 is currently dead.
Warning: CLARiiON device path c1t16d11s0 is currently dead.
Warning: CLARiiON device path c1t16d12s0 is currently dead.
Warning: CLARiiON device path c1t16d13s0 is currently dead.
Warning: CLARiiON device path c1t16d14s0 is currently dead.
Warning: CLARiiON device path c1t16d15s0 is currently dead.
Warning: CLARiiON device path c1t16d16s0 is currently dead.
Warning: CLARiiON device path c1t16d17s0 is currently dead.
Warning: CLARiiON device path c1t16d18s0 is currently dead.
Warning: CLARiiON device path c1t16d19s0 is currently dead.
Warning: CLARiiON device path c1t16d1s0 is currently dead.
Warning: CLARiiON device path c1t16d20s0 is currently dead.
Warning: CLARiiON device path c1t16d21s0 is currently dead.
Warning: CLARiiON device path c1t16d22s0 is currently dead.
Warning: CLARiiON device path c1t16d23s0 is currently dead.
Warning: CLARiiON device path c1t16d2s0 is currently dead.
Warning: CLARiiON device path c1t16d3s0 is currently dead.
Warning: CLARiiON device path c1t16d4s0 is currently dead.
Warning: CLARiiON device path c1t16d5s0 is currently dead.
Warning: CLARiiON device path c1t16d6s0 is currently dead.
Warning: CLARiiON device path c1t16d7s0 is currently dead.
Warning: CLARiiON device path c1t16d8s0 is currently dead.
Warning: CLARiiON device path c1t16d9s0 is currently dead.
Warning: CLARiiON device path c2t17d0s0 is currently dead.
Warning: CLARiiON device path c2t17d10s0 is currently dead.
Warning: CLARiiON device path c2t17d11s0 is currently dead.
Warning: CLARiiON device path c2t17d12s0 is currently dead.
Warning: CLARiiON device path c2t17d13s0 is currently dead.
Warning: CLARiiON device path c2t17d14s0 is currently dead.
Warning: CLARiiON device path c2t17d15s0 is currently dead.
Warning: CLARiiON device path c2t17d16s0 is currently dead.
Warning: CLARiiON device path c2t17d17s0 is currently dead.
Warning: CLARiiON device path c2t17d18s0 is currently dead.
Warning: CLARiiON device path c2t17d19s0 is currently dead.
Warning: CLARiiON device path c2t17d1s0 is currently dead.
Warning: CLARiiON device path c2t17d20s0 is currently dead.
Warning: CLARiiON device path c2t17d21s0 is currently dead.
Warning: CLARiiON device path c2t17d22s0 is currently dead.
Warning: CLARiiON device path c2t17d23s0 is currently dead.
Warning: CLARiiON device path c2t17d2s0 is currently dead.
Warning: CLARiiON device path c2t17d3s0 is currently dead.
Warning: CLARiiON device path c2t17d4s0 is currently dead.
Warning: CLARiiON device path c2t17d5s0 is currently dead.
Warning: CLARiiON device path c2t17d6s0 is currently dead.
Warning: CLARiiON device path c2t17d7s0 is currently dead.
Warning: CLARiiON device path c2t17d8s0 is currently dead.
Warning: CLARiiON device path c2t17d9s0 is currently dead.

After clearing the dead paths it will show only the active paths

root@solaris:~ # powermt display
Symmetrix logical device count=12
CLARiiON logical device count=0
Hitachi logical device count=0
Invista logical device count=0
HP xp logical device count=0
Ess logical device count=0
HP HSx logical device count=0
==============================================================================
—– Host Bus Adapters ——— —— I/O Paths —– —— Stats ——
### HW Path Summary Total Dead IO/Sec Q-IOs Errors
==============================================================================
2305 ssm@0,0/pci@1c,700000/pci@3/lpfc@5 optimal 12 0 – 0 0
2308 ssm@0,0/pci@1d,700000/pci@1/lpfc@5 optimal 12 0 – 0 0

Resizing an ext3 filesystem mounted on a logical volume in a Linux

My home directory got full

root@linux:~ # df -h /home
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/rootvg-homevol
101M 96M 94K 100% /home

Checking if the logical volume permits online resizing and if it was created with an older e2fsprogs version. Volumes created prior to SUSE Linux 10 SP2 are using an older e2fsprogs version and needs to be recreated

root@linux:~ # dumpe2fs -h /dev/mapper/rootvg-homevol | grep features
dumpe2fs 1.35 (28-Feb-2004)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file

We checked that the volume has the resize_inode property so to extend the filesystem, first we extend the logical volume

root@linux:~ # lvextend -L 200M /dev/rootvg/homevol
Extending logical volume homevol to 200.00 MB
Logical volume homevol successfully resized

You can see that the filesystem is not yet showing the new size

root@linux:~ # df -h /home
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/rootvg-homevol
101M 96M 95K 100% /home

Now we increase the filesystem with resize2fs

root@linux:~ # resize2fs /dev/rootvg/homevol
resize2fs 1.41.9 (22-Aug-2009)
Filesystem at /dev/rootvg/homevol is mounted on /home; on-line resizing required
old desc_blocks = 1, new_desc_blocks = 1
Performing an on-line resize of /dev/rootvg/homevol to 204800 (1k) blocks.
The filesystem on /dev/rootvg/homevol is now 204800 blocks long.

Checking the new size

root@linux:~ # df -h /home
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/rootvg-homevol
194M 94M 90M 52% /home

If you receive a message saying that you can’t resize a mounted filesystem, use ext2online

root@suselinux10:~ # resize2fs /dev/localVG/sys.opt
resize2fs 1.38 (30-Jun-2005)
/dev/localVG/sys.opt is mounted; can’t resize a mounted filesystem!

root@suselinux10:~ # ext2online /dev/localVG/sys.opt
ext2online v1.1.18 – 2001/03/18 for EXT2FS 0.5b

You can also pass the flag -r to resize the filesystem without using resize2fs and use lvresize instead of lvextend

root@linux:~ # lvresize -L +2g -r /dev/vgHQ0ascs/lv_sapmnt_exe
Size of logical volume vgHQ0ascs/lv_sapmnt_exe changed from 5.00 GiB (1280 extents) to 7.00 GiB (1792 extents).
Logical volume lv_sapmnt_exe successfully resized
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/mapper/vgHQ0ascs-lv_sapmnt_exe is mounted on /export/sapmnt/HQ0/exe; on-line resizing required
old desc_blocks = 20, new_desc_blocks = 28
Performing an on-line resize of /dev/mapper/vgHQ0ascs-lv_sapmnt_exe to 7340032 (1k) blocks.
The filesystem on /dev/mapper/vgHQ0ascs-lv_sapmnt_exe is now 7340032 blocks long.