Displaying 4 results from an estimated 4 matches for "tviewer_vorigin".
2017 Jul 06
2
logical volume is unreadable
...viewer
>> VG Name vg0
>> LV UUID XdgHFs-RHVZ-9BAH-1ZSK-yiBX-qqf0-273CtT
>> LV Write Access read/write
>> LV Creation host, time host1, 2016-02-06 14:58:19 +0100
>> LV snapshot status INACTIVE destination for lv-vm-tviewer_vorigin
>> LV Status available
>> # open 0
>> LV Size 58.59 GiB
>> Current LE 15000
>> COW-table size 5.86 GiB
>> COW-table LE 1500
>> Snapshot chunk size 4.00 KiB
>...
2017 Jul 06
3
logical volume is unreadable
...vg0/lv-vm-tviewer
LV Name lv-vm-tviewer
VG Name vg0
LV UUID XdgHFs-RHVZ-9BAH-1ZSK-yiBX-qqf0-273CtT
LV Write Access read/write
LV Creation host, time host1, 2016-02-06 14:58:19 +0100
LV snapshot status INACTIVE destination for lv-vm-tviewer_vorigin
LV Status available
# open 0
LV Size 58.59 GiB
Current LE 15000
COW-table size 5.86 GiB
COW-table LE 1500
Snapshot chunk size 4.00 KiB
Segments 1
Allocation inherit
Read ahead...
2017 Jul 06
0
logical volume is unreadable
...lv-vm-tviewer
> VG Name vg0
> LV UUID XdgHFs-RHVZ-9BAH-1ZSK-yiBX-qqf0-273CtT
> LV Write Access read/write
> LV Creation host, time host1, 2016-02-06 14:58:19 +0100
> LV snapshot status INACTIVE destination for lv-vm-tviewer_vorigin
> LV Status available
> # open 0
> LV Size 58.59 GiB
> Current LE 15000
> COW-table size 5.86 GiB
> COW-table LE 1500
> Snapshot chunk size 4.00 KiB
> Segments...
2017 Jul 06
0
logical volume is unreadable
..., Robert Nichols wrote:
>> That looks like a snapshot volume that became invalid because it was
>> filled to capacity. Such a snapshot is lost forever. It si your
>> responsibility to monitor snapshot usage to make sure it does not run
>> out of space. The base volume, lv-vm-tviewer_vorigin, should still have
>> its original content.
>>
>
> That's it. Thanks for the information.
>
> How would I remove the only the snapshot but not the base volume? Will
>
> $ lvremove /dev/vg0/lv-vm-tviewer
>
> leave the base volume untouched?
That should do...