1752649 Members
5639 Online
108788 Solutions
New Discussion юеВ

Error during resizing FS

 
marvik
Regular Advisor

Error during resizing FS

Hello,

Can anybody help with that error please with ext2online

root@pdmgbl2:~# lvextend -L 15G /dev/vg00/lvcrash
Extending logical volume lvcrash to 15.00 GB
Logical volume lvcrash successfully resized

root@pdmgbl2:~# ext2online /dev/vg00/lvcrash
ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
found 0 not 50 at 257[48]
5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: Error during resizing FS

Shalom,

What is the version of Red Hat.

cat /etc/redhat-release

after ext2online command:
echo $?

Need an error code.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
marvik
Regular Advisor

Re: Error during resizing FS

Hi SEP,

here its

root@server:~# ext2online /dev/vg00/lvcrash
ext2online v1.1.18 - 2001/03/18 for EXT2FS 0.5b
found 0 not 50 at 257[48]

ext2online: unable to resize /dev/mapper/vg00-lvcrash
root@server:~# exho $?
-bash: exho: command not found
root@server:~# echo $?
127
root@server:~# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 3)
Ivan Ferreira
Honored Contributor

Re: Error during resizing FS

I would try umounting the file system, and doing e2reize. Sominthing is not good with e2online.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Fabio Ettore
Honored Contributor

Re: Error during resizing FS

Hi,

the echo command suggested by Steven should be issued after the ext2online and not after exho $?. The exit code 127 refers to exho infact.
Issue ext2online command and after echo $?.

If it's not equal to zero then try to umount the filesystem, I would suggest resizefs.

Good luck...

Best regards,
Fabio
WISH? IMPROVEMENT!
marvik
Regular Advisor

Re: Error during resizing FS

:-( that was a miss with "exho "
Many thanks for all your suggestion.

It looks to be an issue with teh version.We have a schedule for updation once that is over we will try that again.


Cheers
Marvik