Re: Trouble with lvreduce and / read-only

From	Dan Ritter <dsr@randomstring.org>
Newsgroups	linux.debian.user
Subject	Re: Trouble with lvreduce and / read-only
Date	2024-10-27 16:50 +0100
Message-ID	<JCdGF-4BJh-3@gated-at.bofh.it> (permalink)
References	<JC3Hj-4v1x-1@gated-at.bofh.it> <JC7KV-4y2R-9@gated-at.bofh.it> <JCc7T-4AYx-13@gated-at.bofh.it> <JCcrf-4B4F-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

gene heskett wrote: 
> On 10/27/24 10:03, Dan Ritter wrote:
> > 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:
> > > > 
> > > > First, I rebooted in single user mode.
> > > > Then I did the following:
> > > > # mount / -rw -o remount
> > > 
> > > I understand the '-o remount', not the '-rw'.
> > > And I think "that command might be the culprit"
> > 
> > 
> > It should be
> > 
> > mount / -o remount,rw
> No, that is an endless loop Dan. The idea is to remount a file system with
> errors as read-only in order to prevent further damage from rw operations.
> From there, you can copy to a new location, like a new drive, rescueing the
> data that does survive. That drive made a mistake and that is sad. But limit
> the losses by putting in a new, bigger drive and remake the system to use it
> in place of the drive that upchucked.

Then you want

mount / -o remount,ro

Neither one of these causes an endless loop. Specifying ro or rw
without remount won't work on an already mounted filesystem.

-dsr-

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