[linux-lvm] lvm snapshot cannot be removed with the error "Failed to refresh without snapshot"

[linux-lvm] lvm snapshot cannot be removed with the error "Failed to refresh without snapshot"

[Gang He]

Hello List,

Our user is using lvm2-2.02.180, he attempted to remove a snapshot LV, but failed with the below error,
lvremove /dev/evg00/snap_var
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Do you really want to remove active logical volume evg00/snap_var? [y/n]: y
  device-mapper: reload ioctl on  (254:36) failed: Invalid argument
  Failed to refresh var without snapshot.

But I can not reproduce in local, how do I find the root cause behind this problem?
I also can see one related error message in /var/log/messages
Jun 12 09:00:22 gtunxlnb04864 sudo:   buss18 : TTY=pts/0 ; PWD=/PZIR/users/buss18 ; USER=root ; COMMAND=/sbin/lvremove /dev/evg00/snap_opt
Jun 12 09:00:22 gtunxlnb04864 sudo[25821]: pam_unix(sudo:session): session opened for user root by buss18(uid=0)
Jun 12 09:00:22 gtunxlnb04864 kernel: [1492631.077551] device-mapper: ioctl: can't change device type after initial table load.  <<== here
Jun 12 09:00:22 gtunxlnb04864 sudo[25821]: pam_unix(sudo:session): session closed for user root
Jun 12 09:01:01 gtunxlnb04864 cron[25932]: pam_unix(crond:session): session opened for user ggmonux1 by (uid=0)

Thanks
Gang

Re: [linux-lvm] lvm snapshot cannot be removed with the error "Failed to refresh without snapshot"

[Gang He]

Hello Guys,

Any ideas? or what information do I need to provide to help this problem?

Thanks a lot.
Gang

>>> On 2019/6/19 at 17:26, in message
<5D09FFC9020000F90006D3D6@prv1-mh.provo.novell.com>, "Gang He" <ghe@suse.com>
wrote:
> Hello List,
> 
> Our user is using lvm2-2.02.180, he attempted to remove a snapshot LV, but 
> failed with the below error,
> lvremove /dev/evg00/snap_var
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> Do you really want to remove active logical volume evg00/snap_var? [y/n]: y
>   device-mapper: reload ioctl on  (254:36) failed: Invalid argument
>   Failed to refresh var without snapshot.
> 
> But I can not reproduce in local, how do I find the root cause behind this 
> problem?
> I also can see one related error message in /var/log/messages
> Jun 12 09:00:22 gtunxlnb04864 sudo:   buss18 : TTY=pts/0 ; 
> PWD=/PZIR/users/buss18 ; USER=root ; COMMAND=/sbin/lvremove 
> /dev/evg00/snap_opt
> Jun 12 09:00:22 gtunxlnb04864 sudo[25821]: pam_unix(sudo:session): session 
> opened for user root by buss18(uid=0)
> Jun 12 09:00:22 gtunxlnb04864 kernel: [1492631.077551] device-mapper: ioctl: 
> can't change device type after initial table load.  <<== here
> Jun 12 09:00:22 gtunxlnb04864 sudo[25821]: pam_unix(sudo:session): session 
> closed for user root
> Jun 12 09:01:01 gtunxlnb04864 cron[25932]: pam_unix(crond:session): session 
> opened for user ggmonux1 by (uid=0)
> 
> Thanks
> Gang
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com 
> https://www.redhat.com/mailman/listinfo/linux-lvm 
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

Re: [linux-lvm] lvm snapshot cannot be removed with the error "Failed to refresh without snapshot"

[Zdenek Kabelac]

Dne 20. 06. 19 v 7:41 Gang He napsal(a):
> Hello Guys,
> 
> Any ideas? or what information do I need to provide to help this problem?
> 


Hi

It does look like  dmtable had different type of device in place and lvm2
was not able to remove device type.

So was this state a result of some 'regular' workflow you can reproduce?

Or is this some state after some 'vgcfgrestore' usage while some live
LVs were present in table?

Or maybe some incorrectly working error path in code after some failure?

You would probably need to tar /etc/lvm/archive - eventually
open upstream lvm2 community bugzilla:

https://bugzilla.redhat.com/enter_bug.cgi?product=LVM%20and%20device-mapper

and provide steps for reproduction and 'lvmdump -a -m'

Final note - if this bug is happening with some old version of lvm2 - check
first if the newer version isn't already fixed.

Regards

Zdenek