Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #274108

Re: Trouble with lvreduce and / read-only

Show all headers | View raw

On Sun, Oct 27, 2024 at 06:46:44PM +0000, Jonathan Wiebe wrote:
> On Sunday, October 27th, 2024 at 11:29, Geert Stappers wrote:
> > On Sun, Oct 27, 2024 at 06:11:45PM +0000, Jonathan Wiebe wrote:
> > > On Sunday, October 27th, 2024 at 02:28, Geert Stappers wrote:
> > > > On Sun, Oct 27, 2024 at 05:04:19AM +0000, Jonathan Wiebe wrote:
> > > > 
> > > > > I ran into an issue with my root partition being too small. My plan
> > > > > was to reduce the size of my home partition and increase the size of
> > > > > my root partition. Here is what I have done:
> > > > >   .... 
> > > > > Logical volume debian--vg/home successfully resized.
> > > > 
> > > > Acknowledge
> > > > NOTE: Only the logical volume was resized. [1]
> > > > 
> > > > > This is where I am stalled. The prompt has not come back and I have
> > > > 
> > > > Even on slow hardware is ten hour response time an indicator for
> > > > "something is wrong".
> > > > 
> > > > Input for follow-up:
> > > > * Powercycle the system.
> > > > * Continue with reaching the intended goal
> > > > * complete resizing of /home [1]
> > > > * resize / [1]
> > > > 
> > > > 
> > > > [1] Be aware of the command `resize2fs` and the flag `--resizefs` for
> > > > the command `lvresize`.
> > > 
> > > After a power cycle the system came back up normally
> > 
> > OK, nice.
> > 
> > > and I was able to continue.
> > 
> > And which notes will be shared with this mailinglist?
> > 
> 
> After the reboot I continued with:
> # resize2fs /dev/mapper/debian--vg-home
>  
> # lvextend -L +20G /dev/mapper/debian--vg-root
> (Saving some free space for future use.)
> At this point I rebooted and forced a fsck on the root partition by
> appending fsck.mode=force to the grub boot line starting with linux...
> After a successful fsck:
> # resize2fs /dev/mapper/debian--vg-root
> And finally rebooted the system and checked that all partitions were the expected sizes.
> Thanks all for your help!

Thanks for reporting back.

For those who read this for their resize adventure:

These days can LV resize / LV reduce be done on the fly.
No need for unmount and `fsck`. Just add  --resizefs to
the LV commands.


Groeten
Geert Stappers
-- 
Silence is hard to parse

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Trouble with lvreduce on Debian 12 Jonathan Wiebe <jonathan.b.wiebe@proton.me> - 2024-10-27 06:10 +0100
  Re: Trouble with lvreduce  and / read-only Geert Stappers <stappers@stappers.nl> - 2024-10-27 10:30 +0100
    Re: Trouble with lvreduce  and / read-only Dan Ritter <dsr@randomstring.org> - 2024-10-27 15:10 +0100
      Re: Trouble with lvreduce and / read-only gene heskett <gheskett@shentel.net> - 2024-10-27 15:30 +0100
        Re: Trouble with lvreduce and / read-only Dan Ritter <dsr@randomstring.org> - 2024-10-27 16:50 +0100
    Re: Trouble with lvreduce  and / read-only Jonathan Wiebe <jonathan.b.wiebe@proton.me> - 2024-10-27 19:20 +0100
      Re: Trouble with lvreduce  and / read-only Geert Stappers <stappers@stappers.nl> - 2024-10-27 19:30 +0100
        Re: Trouble with lvreduce  and / read-only Jonathan Wiebe <jonathan.b.wiebe@proton.me> - 2024-10-27 19:50 +0100
          Re: Trouble with lvreduce  and / read-only Geert Stappers <stappers@stappers.nl> - 2024-10-27 22:30 +0100
          Re: Trouble with lvreduce  and / read-only Andy Smith <andy@strugglers.net> - 2024-10-28 02:50 +0100
  Re: Trouble with lvreduce on Debian 12 Anders Andersson <pipatron@gmail.com> - 2024-10-28 13:40 +0100

csiph-web