[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[linux-lvm] lvextend NEVER works but screws up



Hi, i was a big fan of lvm and used to advocate it's use at my workplace but each time i try to use lvreduce or lvextend on production it has ALWAYS been a major let down and messed up our production data and caused major outages and not to forget the big stick up *** . 

please look at the sequence and this is what I did

 vgs
  VG   #PV #LV #SN Attr   VSize   VFree 
  vg0    1   2   0 wz--n- 492.72G      42.72G

df -kh
/dev/mapper/vg0-logs   99G   43G   52G  46% /bin-logs

I wanted to use the free 42.7 G and allocate it to /bin-logs so this is what I ran in order to extended

# lvextend -L +42.7G -n /dev/vg0/logs
  Rounding up size to full physical extent 42.70 GB
  Extending logical volume logs to 142.70 GB
  Logical volume logs successfully resized

#resize2fs /dev/vg0/logs    ( and it gets screwed up here )
resize2fs 1.39 (29-May-2006)
resize2fs: Filesystem has unsupported feature(s) while trying to open /dev/vg0/logs
Couldn't find valid filesystem superblock.

and the free space of 42.7G is also gone , 

 # vgs
  VG   #PV #LV #SN Attr   VSize   VFree 
  vg0    1   2   0 wz--n- 492.72G   20.00M

lvm version
  LVM version:     2.02.88(2)-RHEL5 (2012-01-20)
  Library version: 1.02.67-RHEL5 (2011-10-14)
  Driver version:  4.11.6


It' so annoying to see this happen , from what I know that's the cmd sequence to extend an existing LVM online , now I am not sure what this did to my filesystem and  hoping it hasn't ****ED my data yet .

your insights would greatly be appreciated .


 




--
Tariq Wali.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]