lvextend error on XFS
Quoted 9 lines · Frank J. Buchholz
Hello,
I recently attempted to extend my logical volume. First I added an additional physical volume to an existing volume group. This worked fine.
vgextend Volume00
/dev/sba
lvextend -L+100G/dev/Volume00/LogVol00
Quoted 7 lines
However when it came time to run the lvextend command I received a number of device-mapper errors. While I was trying to determine what the errors were I noticed that the filesystem that sits on the logical volume being extended was no longer available. I attempted to umount the filesystem however the command froze. I then rebooted the system without mounting the filesystem in question and manually mounted the filesystem. XFS reported back that it could not locate the superblock.
I have done lvextend followed by xfs_growfs many times without any problems. Have you checked for hardware errors?
Signature · 21 lines
M�ns Rullg�rd mru inprovide com M�ns - Unfortunately the timing is far too coincidental to be a hardware error. Just after typing the following command and recieving the following error lvm> lvextend -L+1G /dev/Volume00/LogVol00 Extending logical volume LogVol00 to 2.93 TB device-mapper ioctl cmd 9 failed: Invalid argument Couldn't load device 'Volume00-LogVol00'. Problem reactivating LogVol00 I then noticed that the filesystem on LogVol00 was no longer available and when I ran xfs_repair it stated the following: # xfs_repair /dev/Volume00/LogVol00 Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval 0 fatal error -- Invalid argument
Quoted 19 lines · Frank J. Buchholz
Quoted 19 lines
Quoted 16 lines · Frank J. Buchholz
Hello,
I recently attempted to extend my logical volume. First I added an additional physical volume to an existing volume group. This worked fine.
vgextend Volume00
/dev/sba
lvextend -L+100G/dev/Volume00/LogVol00However when it came time to run the lvextend command I received a number of device-mapper errors. While I was trying to determine what the errors were I noticed that the filesystem that sits on the logical volume being extended was no longer available. I attempted to umount the filesystem however the command froze. I then rebooted the system without mounting the filesystem in question and manually mounted the filesystem. XFS reported back that it could not locate the superblock.
Quoted 4 lines
Quoted 2 lines
I have done lvextend followed by
xfs_growfsmany times without any problems. Have you checked for hardware errors?Unfortunately the timing is far too coincidental to be a hardware error.
Since you had just added another disk, it may not be so coincidental after all.
Quoted 6 lines
Just after typing the following command and recieving the following error lvm> lvextend -L+1G
/dev/Volume00/LogVol00
Extending logical volume LogVol00 to 2.93 TB
device-mapper ioctl cmd 9 failed: Invalid argument
Couldn't load device 'Volume00-LogVol00'.
Problem reactivating LogVol00
The last line would explain why the filesystem went offline. Something went wrong just after the LV had been extended, and was about to be reactivated.
Quoted 7 lines
I then noticed that the filesystem on LogVol00 was no longer available and when I ran
xfs_repairit stated the following:# xfs_repair /dev/Volume00/LogVol00 Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval 0fatal error -- Invalid argument
What does "dmesg" have to say about this?
I had a problem once with some strange errors from a disk. It turned out the cable wasn't plugged in properly.
Signature · 2 lines
M�ns Rullg�rd [email protected]