Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • has done a decent job of clarifying the question and giving some insight into what's going on - enough, surely, for the reward that comes from a green tick, especially in the absense of any other answers. The detailed explanation is evidence of labour and concern for the welfare of one's fellow hacks. But it is not a canonical answer to the questions posed - and that is what the reward was put up for: for the definitive statement on (i) What is "resized" if no size information is stored? and (ii) How does a "resize" get remembered across open / closes of a encrypted volume? Commented Jan 16, 2018 at 18:19
  • @markling I thought it was clear enough, but here you go. Commented Jan 16, 2018 at 21:22
  • Yeah, it's a brilliant answer. I didn't know what I was talking about. I do now, however - now that I have read it again. Ah, I see - you edited it. Well I'm certainly wiser for it now. Thank you. Commented Mar 19, 2019 at 18:12
  • can you add a bit more information ? I did the resize2fs on my partiion, my lvdisplay and pvdisplay shows the shrinked size? How can I make the volume smaller now? as far as I understand here, cryptsetup only reports a size, but does not store or have a size? so I guess next step is to go a level higher. My volume is a VirtualBox .vdi image file. is there an extra layer between VBox and Luks? I don't know. Thanks Commented Apr 27, 2021 at 3:42
  • 1
    some small precision here, --getsize64 gives a size 512 times bigger than what you want to give to cryptsetup resize --size Commented Apr 27, 2021 at 3:54