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-
