http://bugzilla.suse.com/show_bug.cgi?id=1132308 http://bugzilla.suse.com/show_bug.cgi?id=1132308#c3 heming zhao <heming.zhao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #3 from heming zhao <heming.zhao@suse.com> --- from comment #0 info: ``` device-mapper: reload ioctl on (254:4) failed: Input/output error Failed to lock logical volume some_data/some_data_lv. Aborting. Manual intervention required. ``` _lv_create_an_lv +-> lv_update_and_reload | +-> _lv_update_and_reload | +-> suspend_lv => _do_dm_ioctl() => log: | | device-mapper: reload ioctl on (254:4) failed: Input/output error | +-> log: Failed to lock logical volume some_data/some_data_lv. +-> log: "Aborting. Manual intervention required." This is very common error, the lvm log "reload ioctl on ..." responses kernel dm layer: table_load() For the too little info, I closed this bug for noresponse. If the bug reporter still interesting the fix, please provide info which I said in comment #2. and please also provide below commands output: dmsetup ls --tree dmsetup table dmsetup status lsof /dev/some_data/some_data_lv Thank you. -- You are receiving this mail because: You are on the CC list for the bug.