VMware Cloud Community
bug007
Contributor
Contributor

failed to expand file system

hello,

my problem is, i have extend my SAN Lun and then i have extend the volume in virtual center

now i have a problem with this volume

in vmkernel log i have the message

sx21 vmkernel: Invalid lock address 0[lockAddr 0] Invalid lock type 0x0[lockAddr 536603065344] Invalid lock addr 00:21:18:18.473 cpu2:4106)WARNING: FS3: 556: Volume 4abb1d12-e2da5ed8-da5b-0015171da1e6 ("LH_VM3") may be damaged on disk. Corrupt lock detected at offset

May 4 08:40:57 vm-esx21 vmkernel: 7cf008fc00: [type 0 offset 0 v 0, hb offset 0

May 4 08:40:57 vm-esx21 vmkernel: gen 0, mode 0, owner 00000000-00000000-0000-00

May 4 08:40:57 vm-esx21 vmkernel: 0:21:18:18.474 cpu2:4106)Vol3: 365: Failed to expand file system LH_VM3 (Invalid metadata), but logical volume was successfully extended. Will try to expand file system nexttime(s) volume is opened.

Reply
0 Kudos
1 Reply
VMmatty
Virtuoso
Virtuoso

I had a problem similar to this a little while back. I was able to expand the volume successfully in the vSphere Client after a host reboot. If you're behind on any patches use this as an opportunity to get them installed, reboot, and then see if you can extend the volume.

Matt | http://www.thelowercasew.com | @mattliebowitz
Reply
0 Kudos