hello,
if i have a logical sector/block "x" on a lvm logical volume , is there
a way to easily calculate/determine (optimally by script/cli) the
corresponding physical sector of the physical device it belongs to and
the extent number of the appropiate pv/vg where it resides ?
rega
thanks!
any chance to get retrieve this information for automated/script based
processing ?
roland
Am 03.01.22 um 00:12 schrieb Andy Smith:
Hi Roland,
On Sun, Jan 02, 2022 at 08:00:30PM +0100, Roland wrote:
if i have a logical sector/block "x" on a lvm logical volume , is t
o build an
appropriate output field command option from the default output. i
remember i had such issue with other tools...
think this is a missing feature ?
roland
# pvs --segments -olv_name,seg_start_pe,seg_size_pe,pvseg_start -S
lv_name=usedblocks -O seg_start
LV Start
Hi,
> Hi Roland, is `lvs --reportformat json` or `lvs --nameprefixes` good
enough?
good when using scripting / automated processing - but not good, when we
need it human readable.
i'd even would call it a bug, when using same strings for "translated"
names.
would anybody accept s
0 1
0S 2097152S 1 1
0S 0S 5309 0
0S 0S 5587 0
0S 0S 5588 0
roland
___
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read t
have too much coffee and had overseen that in the manpage)
the question regarding native column headers/description remains
roland
Am 19.08.23 um 17:20 schrieb Roland:
hello,
does somebody know how we can have native (i.e. non translated) column
field names in first line of output of pvs ?
Am 21.08.23 um 18:17 schrieb David Teigland:
On Sat, Aug 19, 2023 at 06:05:58PM +0200, Roland wrote:
furthermore, it's a little bit weird that some columns being printed by
default when using -o, is there an easier way to remove those besides
explictly removing them one by one with several -o
0
VGloop0 blocks_good 200 1 1020
VGloop0 blocks_good 4 1 1021
VGloop0 blocks_bad 0 1 1022
blocks_good is LV with healty PE's, blocks_bad is LV with bad PE's and
blocks_spare is LV
where you take healthy PE's from as a replacement for bad PE's found in
blocks_good LV
0 4 11
blocks_allocated 3 1 15
0 476922 16
how can i remove extent number 10 ?
is this a bug ?
regards
roland
___
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo
just like "dismiss the problematic
extents and replace with healthy extents".
i'd better like remapping instead of removing a PE, as removing will invalidate
the whole LV
roland
Am 09.04.23 um 19:32 schrieb Roger Heflin:
On Sun, Apr 9, 2023 at 10:18 AM Roland wrote:
hi,
we
thank you, very valuable!
Am 09.04.23 um 20:53 schrieb Roger Heflin:
On Sun, Apr 9, 2023 at 1:21 PM Roland wrote:
Well, if the LV is being used for anything real, then I don't know of
anything where you could remove a block in the middle and still have a
working fs. You can only reduce
ven if it's dumb to do or if it's something which will not succeed
, it's at least worth a try to show if it works or show why it can't
work - and if it doesn't work - there is at least something to learn
about lvm or dead disks.
roland
Am 09.04.23 um 22:18 schrieb matthew patton:
> my pla
, or could this
utility get integrated into the lvm2 tools suite ?
regards
roland
___
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
quot;broken" disks being used with zfs in a redundant setup,
they could probable still serve a purpose. maybe not
for production data, but probably good enough for "not so important"
application.
it's a little bit academic project. for my own fun. i like to fiddle
with disks, lvm,
14 matches
Mail list logo
