Tag Info

Hot answers tagged

4

Turns out there was a LVM snapshot of the root filesystem's LV, but not the other. Appears snapshots block TRIM, because the device-mapper snapshot target doesn't support it.


3

You are seeing the extents that made up the previous PV's. Run pvs --segments to have lvm agree with system-config-lvm. See http://www.redhat.com/magazine/009jul05/features/lvm2/ for more information.


2

You can't fix LVM by growing size back to original size, unless you were very lucky and the LV had no fragmentation whatsoever due to previous resizes. Chances are the new LV will have the first 20G or so of your original filesystem but the remaining 780G (or whatever) are scrambled eggs (wrong data, wrong offset, wrong order). And that's assuming you're ...


2

I don't suppose there's a way I can skip having LVM running in the guest and just lvextend on the host then resize2fs in the guest? There's absolutely no requirement to use LVM inside a guest. You can just use the block device directly. Using LVM inside the guest gets you almost nothing (since you're already using LVM on the host to manage your ...


1

If you hadn't blown away the old ext4, there might have been some hope for fsck to do some repairs and find some intact directory structures. There might actually still be hope for that, by using an alternate superblock that was in the part of the disk you didn't mess up with mkfs. Or if your old FS had a different number of backup superblocks than your ...



Only top voted, non community-wiki answers of a minimum length are eligible