This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ---------------------d125c26a3b05fe765e9aa16cc6a896ff Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8

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 # amount /homeumount: /home: not mounted.# fsck -f /dev/mapper/debian --vg-homefsck from util-linux 2.38.1e2fsck 1.47.0 (5-Feb-2023)Pass 1: Checking inodes, blocks, and sizes Inode 8803015 extent tree (at level 1) could be
shorter. Optimize<y>? yesInode 8919578 extent tree (at level 1) could be shorter. Optimize<y>? yesInode 9328852 extent tree (at level 1) could be shorter. Optimize<y>? yesInode 11273442 extent tree (at level 1) could be shorter. Optimize<y>? yesPass
1E: Optimizing extent treesPass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference countsPass 5: Checking group summary information /dev/mapper/debian--vg-home: ***** FILE SYSTEM WAS MODIFIED *****/
dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks # fsck -f /dev/mapper/debian--vg-home fsck from util-linux 2.38.1e2fsck 1.47.0 (5-Feb-2023)Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking
directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks # resize2fs /
dev/mapper/debian--vg-home 400Gresize2fs 1.47.0 (5-Feb-2023)Resizing the filesystem on /dev/mapper/debian--vg-home to 104857600 (4k) blocks.The filesystem on /dev/mapper/debian--vg-home is now 104857600 (4k) blocks long.# lvreduce -L -39G /dev/mapper/
debian--vg-home WARNING: Reducing active logical volume to 408.07 GiB.THIS MAY DESTROY YOUR DATA (filesystem etc.)Do you really want to reduce debian--vg/home? [y/n]: ySize of logical volume debian--vg/home changed from 447.07 GiB (114450 extents) to
408.07 GiB (104466 extents).Logical volume debian--vg/home successfully resized.This is where I am stalled. The prompt has not come back and I have been waiting about 10.5 hours. Is it normal for this to take this long? Should I just be patient? Or
has something gone wrong? I am not sure what to do at this point.Thanks in advance for your assistance.Jonathan -- Jonathan WiebeOur passions are there to drive us to act, not to be the seasoning of our emotional stew.Sent from Proton Mail
Android
---------------------d125c26a3b05fe765e9aa16cc6a896ff Content-Transfer-Encoding: base64
Content-Type: application/pgp-keys; filename="=?UTF-8?B?cHVibGlja2V5IC0gam9
uYXRoYW4uYi53aWViZUBwcm90b24ubWUgLSAweDgzNUEwQ0UwLmFzYw==?="; name="=?UTF-
8?B?cHVibGlja2V5IC0gam9uYXRoYW4uYi53aWViZUBwcm90b24ubWUgLSAweDgzNUEwQ0UwLm
FzYw==?="
Content-Disposition: attachment; filename="=?UTF-8?B?cHVibGlja2V5IC0gam9uYX
RoYW4uYi53aWViZUBwcm90b24ubWUgLSAweDgzNUEwQ0UwLmFzYw==?="; name="=?UTF-8?B
?cHVibGlja2V5IC0gam9uYXRoYW4uYi53aWViZUBwcm90b24ubWUgLSAweDgzNUEwQ0UwLmFzY
w==?="

LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tClZlcnNpb246IEdvcGVuUEdQIDI
uOC4wCkNvbW1lbnQ6IGh0dHBzOi8vZ29wZW5wZ3Aub3JnCgp4ak1FWWt4TlloWUpLd1lCQkFIY
VJ3OEJBUWRBYWhxVWFqblpuUkgvb0RYWkRqVVFqNDJ6M1hkKzk1am9CNmJ1CklVV1U2M3ZOTjJ
wdmJtRjBhR0Z1TG1JdWQybGxZbVZBY0hKdmRHOXVMbTFsSUR4cWIyNWhkR2hoYmk1aUxuZHAKW
ldKbFFIQnliM1J2Ymk1dFpUN0Nqd1FRRmdvQUlBVUNZa3hOWWdZTENRY0lBd0lFRlFnS0FnUVd
BZ0VBQWhrQgpBaHNEQWg0QkFDRUpFSlV0czNoTFlvUk5GaUVFZzFvTTRIazc2OEY1dFhzaWxTM
nplRXRpaEUxT2FBRDlHS0RZClo2MElGM0lqQ2dHbjJzL1R2QkdDR1RwN3RLYUdBVldiQ25tb09
sd0JBSi9sdVBvbEZtSjREM2xlQ0Y5eVJiV1AKbk9HVExXaUIzNHBQRForMmJXOEl6amdFWWt4T
lloSUtLd1lCQkFHWFZRRUZBUUVIUUwwanJaaDlMWWJmbHlhYgpEajBEVVdHS28zMm5Sdnd3MTl
mQ25QckdFeFV4QXdFSUI4SjRCQmdXQ0FBSkJRSmlURTFpQWhzTUFDRUpFSlV0CnMzaExZb1JOR
mlFRWcxb000SGs3NjhGNXRYc2lsUzJ6ZUV0aWhFM2NmQUQvWFdldWZtNlpPRE9FYkcxSVZqalk
KS0J0c2ZreFdGZzFYL0Z2SWdWNXcwTklCQU9hNXg1Ynd4YTFSeHVOTWhHcXRJSUx6V2UreUs0W
WFuWW15enU4ZwpQZ2tHCj1JWWcyCi0tLS0tRU5EIFBHUCBQVUJMSUMgS0VZIEJMT0NLLS0tLS0
=
---------------------d125c26a3b05fe765e9aa16cc6a896ff--
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYIACcFAmcdydIJEJUts3hLYoRNFiEEg1oM4Hk768F5tXsilS2zeEti hE0AAGQMAP4+ODwG0Lk064vKrZsYZC3FOnyHc7C6+8ljtmTAkbhXlQD9EXVq MFMVKTknH384R7qXow0jCAEG/zh2igHNDCgw/AU=
=sg9G
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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"

# amount /home

Assuming an ugly typo.

umount: /home: not mounted.

I think: That is strange.
And wonder: Why was /home not mounted?

# fsck -f /dev/mapper/debian --vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 8803015 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 8919578 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 9328852 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 11273442 extent tree (at level 1) could be shorter. Optimize<y>? yes Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/mapper/debian--vg-home: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "/home had some burses"

# fsck -f /dev/mapper/debian--vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "fsck is happy"

# resize2fs /dev/mapper/debian--vg-home 400G
resize2fs 1.47.0 (5-Feb-2023)
Resizing the filesystem on /dev/mapper/debian--vg-home to 104857600 (4k) blocks.
The filesystem on /dev/mapper/debian--vg-home is now 104857600 (4k) blocks long.

Assuming something as "home was and is 400G"

# lvreduce -L -39G /dev/mapper/debian--vg-home
WARNING: Reducing active logical volume to 408.07 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce debian--vg/home? [y/n]: y
Size of logical volume debian--vg/home changed from 447.07 GiB (114450 extents) to 408.07 GiB (104466 extents).
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
been waiting about 10.5 hours. Is it normal for this to take this
long? Should I just be patient? Or has something gone wrong? I am not
sure what to do at this point.

Think "have shot my self in the foot", "learnt much today".

Even on slow hardware is ten hour response time an indicator for
"something is wrong".

My guess is root filesystem mounted readonly being the culprit.

Thanks in advance for your assistance.

Oh, that is cheap. I do read it as:


You must spend time on my problem and report back to me!
Do not expect any follow-up from me, I have already said "Thanks"!!!


Input for follow-up:
* Powercycle the system.
* Continue with reaching the intended goal
* complete resizing of /home [1]
* resize / [1]

Jonathan

Groeten
Geert Stappers

[1] Be aware of the command `resize2fs` and the flag `--resizefs` for
the command `lvresize`.
--
Silence is hard to parse

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

-dsr-

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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.

-dsr-

.

Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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-

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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:

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"

# amount /home

Assuming an ugly typo.

umount: /home: not mounted.

I think: That is strange.
And wonder: Why was /home not mounted?

# fsck -f /dev/mapper/debian --vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 8803015 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 8919578 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 9328852 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 11273442 extent tree (at level 1) could be shorter. Optimize<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/mapper/debian--vg-home: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "/home had some burses"

# fsck -f /dev/mapper/debian--vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "fsck is happy"

# resize2fs /dev/mapper/debian--vg-home 400G
resize2fs 1.47.0 (5-Feb-2023)
Resizing the filesystem on /dev/mapper/debian--vg-home to 104857600 (4k) blocks.
The filesystem on /dev/mapper/debian--vg-home is now 104857600 (4k) blocks long.

Assuming something as "home was and is 400G"

# lvreduce -L -39G /dev/mapper/debian--vg-home
WARNING: Reducing active logical volume to 408.07 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce debian--vg/home? [y/n]: y
Size of logical volume debian--vg/home changed from 447.07 GiB (114450 extents) to 408.07 GiB (104466 extents).
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
been waiting about 10.5 hours. Is it normal for this to take this
long? Should I just be patient? Or has something gone wrong? I am not sure what to do at this point.

Think "have shot my self in the foot", "learnt much today".

Even on slow hardware is ten hour response time an indicator for
"something is wrong".

My guess is root filesystem mounted readonly being the culprit.

Thanks in advance for your assistance.

Oh, that is cheap. I do read it as:

You must spend time on my problem and report back to me!
Do not expect any follow-up from me, I have already said "Thanks"!!!

Input for follow-up:
* Powercycle the system.
* Continue with reaching the intended goal
* complete resizing of /home [1]
* resize / [1]

Jonathan

Groeten
Geert Stappers

[1] Be aware of the command `resize2fs` and the flag `--resizefs` for
the command `lvresize`.

Thank-you for your help Geert.

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?




Groeten
Geert Stappers

As to your last comment, I am sorry that you took it that way. :)

I think we have a cultural translation issue. Here in Canada we often
thank people in advance without any expectations.

Then we follow up.

Just do it


--
Silence is hard to parse

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) -----------------------38c40fd02a08af83a30396bb0022c532 Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8





--
Jonathan Wiebe

Our passions are there to drive us to act, not to be the seasoning of our emotional stew.

Sent with Proton Mail secure email.

On Sunday, October 27th, 2024 at 02:28, Geert Stappers <[email protected]> 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"

# amount /home

Assuming an ugly typo.

umount: /home: not mounted.

I think: That is strange.
And wonder: Why was /home not mounted?

# fsck -f /dev/mapper/debian --vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 8803015 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 8919578 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 9328852 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 11273442 extent tree (at level 1) could be shorter. Optimize<y>? yes Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/mapper/debian--vg-home: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "/home had some burses"

# fsck -f /dev/mapper/debian--vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "fsck is happy"

# resize2fs /dev/mapper/debian--vg-home 400G
resize2fs 1.47.0 (5-Feb-2023)
Resizing the filesystem on /dev/mapper/debian--vg-home to 104857600 (4k) blocks.
The filesystem on /dev/mapper/debian--vg-home is now 104857600 (4k) blocks long.

Assuming something as "home was and is 400G"

# lvreduce -L -39G /dev/mapper/debian--vg-home
WARNING: Reducing active logical volume to 408.07 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce debian--vg/home? [y/n]: y
Size of logical volume debian--vg/home changed from 447.07 GiB (114450 extents) to 408.07 GiB (104466 extents).
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
been waiting about 10.5 hours. Is it normal for this to take this
long? Should I just be patient? Or has something gone wrong? I am not
sure what to do at this point.

Think "have shot my self in the foot", "learnt much today".

Even on slow hardware is ten hour response time an indicator for
"something is wrong".

My guess is root filesystem mounted readonly being the culprit.

Thanks in advance for your assistance.

Oh, that is cheap. I do read it as:

You must spend time on my problem and report back to me!
Do not expect any follow-up from me, I have already said "Thanks"!!!

Input for follow-up:
* Powercycle the system.
* Continue with reaching the intended goal
* complete resizing of /home [1]
* resize / [1]

Jonathan

Groeten
Geert Stappers

[1] Be aware of the command `resize2fs` and the flag `--resizefs` for
the command `lvresize`.
--
Silence is hard to parse

Thank-you for your help Geert.

After a power cycle the system came back up normally and I was able to continue.

As to your last comment, I am sorry that you took it that way. :)

I think we have a cultural translation issue. Here in Canada we often thank people in advance without any expectations.

Then we follow up.

And finally we say that we are sorry if we have caused any offense. :)

Thank-you!
-----------------------38c40fd02a08af83a30396bb0022c532
Content-Type: application/pgp-keys; filename="publickey - [email protected] - 0x835A0CE0.asc"; name="publickey - [email protected] - 0x835A0CE0.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="publickey - [email protected] - 0x835A0CE0.asc"; name="publickey - [email protected] - 0x835A0CE0.asc"

LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgp4ak1FWWt4TlloWUpLd1lCQkFI YVJ3OEJBUWRBYWhxVWFqblpuUkgvb0RYWkRqVVFqNDJ6M1hkKzk1am8KQjZidUlVV1U2M3ZOTjJw dmJtRjBhR0Z1TG1JdWQybGxZbVZBY0hKdmRHOXVMbTFsSUR4cWIyNWhkR2hoCmJpNWlMbmRwWldK bFFIQnliM1J2Ymk1dFpUN0Nqd1FRRmdvQUlBVUNZa3hOWWdZTENRY0lBd0lFRlFnSwpBZ1FXQWdF QUFoa0JBaHNEQWg0QkFDRUpFSlV0czNoTFlvUk5GaUVFZzFvTTRIazc2OEY1dFhzaWxTMnoKZUV0 aWhFMU9hQUQ5R0tEWVo2MElGM0lqQ2dHbjJzL1R2QkdDR1RwN3RLYUdBVldiQ25tb09sd0JBSi9s CnVQb2xGbUo0RDNsZUNGOXlSYldQbk9HVExXaUIzNHBQRForMmJXOEl6amdFWWt4TlloSUtLd1lC QkFHWApWUUVGQVFFSFFMMGpyWmg5TFliZmx5YWJEajBEVVdHS28zMm5Sdnd3MTlmQ25QckdFeFV4 QXdFSUI4SjQKQkJnV0NBQUpCUUppVEUxaUFoc01BQ0VKRUpVdHMzaExZb1JORmlFRWcxb000SGs3 NjhGNXRYc2lsUzJ6CmVFdGloRTNjZkFEL1hXZXVmbTZaT0RPRWJHMUlWampZS0J0c2ZreFdGZzFY L0Z2SWdWNXcwTklCQU9hNQp4NWJ3eGExUnh1Tk1oR3F0SUlMeldlK3lLNFlhbllteXp1OGdQZ2tH Cj1JWWcyCi0tLS0tRU5EIFBHUCBQVUJMSUMgS0VZIEJMT0NLLS0tLS0K -----------------------38c40fd02a08af83a30396bb0022c532--

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmceglAJkJUts3hLYoRNFiEEg1oM4Hk768F5tXsilS2zeEti hE0AAL2+AQDstkwK+MISiSiFZ6ry8Kf/mMjkpz5yxiFBixatxdM4xwEA1sPK ZDqefRcoFVfyeKFZSpV33MuWM1MLqjNZIsu5kAM=
=xeXG
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) -----------------------380bbca5a442aa275c3578375bcc06fb Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8





--
Jonathan Wiebe

Our passions are there to drive us to act, not to be the seasoning of our emotional stew.

Sent with Proton Mail secure email.

On Sunday, October 27th, 2024 at 11:29, Geert Stappers <[email protected]> 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:

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"

# amount /home

Assuming an ugly typo.

umount: /home: not mounted.

I think: That is strange.
And wonder: Why was /home not mounted?

# fsck -f /dev/mapper/debian --vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 8803015 extent tree (at level 1) could be shorter. Optimize<y>? yes
Inode 8919578 extent tree (at level 1) could be shorter. Optimize<y>? yes
Inode 9328852 extent tree (at level 1) could be shorter. Optimize<y>? yes
Inode 11273442 extent tree (at level 1) could be shorter. Optimize<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/mapper/debian--vg-home: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "/home had some burses"

# fsck -f /dev/mapper/debian--vg-home
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/debian--vg-home: 329100/29302784 files (1.8% non-contiguous), 12560416/117196800 blocks

Acknowledge on "fsck is happy"

# resize2fs /dev/mapper/debian--vg-home 400G
resize2fs 1.47.0 (5-Feb-2023)
Resizing the filesystem on /dev/mapper/debian--vg-home to 104857600 (4k) blocks.
The filesystem on /dev/mapper/debian--vg-home is now 104857600 (4k) blocks long.

Assuming something as "home was and is 400G"

# lvreduce -L -39G /dev/mapper/debian--vg-home
WARNING: Reducing active logical volume to 408.07 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce debian--vg/home? [y/n]: y
Size of logical volume debian--vg/home changed from 447.07 GiB (114450 extents) to 408.07 GiB (104466 extents).
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 been waiting about 10.5 hours. Is it normal for this to take this
long? Should I just be patient? Or has something gone wrong? I am not sure what to do at this point.

Think "have shot my self in the foot", "learnt much today".

Even on slow hardware is ten hour response time an indicator for "something is wrong".

My guess is root filesystem mounted readonly being the culprit.

Thanks in advance for your assistance.

Oh, that is cheap. I do read it as:

You must spend time on my problem and report back to me!
Do not expect any follow-up from me, I have already said "Thanks"!!!

Input for follow-up:
* Powercycle the system.
* Continue with reaching the intended goal
* complete resizing of /home [1]
* resize / [1]

Jonathan

Groeten
Geert Stappers

[1] Be aware of the command `resize2fs` and the flag `--resizefs` for
the command `lvresize`.

Thank-you for your help Geert.

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?

Groeten
Geert Stappers

As to your last comment, I am sorry that you took it that way. :)

I think we have a cultural translation issue. Here in Canada we often
thank people in advance without any expectations.

Then we follow up.

Just do it

--
Silence is hard to parse

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! -----------------------380bbca5a442aa275c3578375bcc06fb
Content-Type: application/pgp-keys; filename="publickey - [email protected] - 0x835A0CE0.asc"; name="publickey - [email protected] - 0x835A0CE0.asc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="publickey - [email protected] - 0x835A0CE0.asc"; name="publickey - [email protected] - 0x835A0CE0.asc"

LS0tLS1CRUdJTiBQR1AgUFVCTElDIEtFWSBCTE9DSy0tLS0tCgp4ak1FWWt4TlloWUpLd1lCQkFI YVJ3OEJBUWRBYWhxVWFqblpuUkgvb0RYWkRqVVFqNDJ6M1hkKzk1am8KQjZidUlVV1U2M3ZOTjJw dmJtRjBhR0Z1TG1JdWQybGxZbVZBY0hKdmRHOXVMbTFsSUR4cWIyNWhkR2hoCmJpNWlMbmRwWldK bFFIQnliM1J2Ymk1dFpUN0Nqd1FRRmdvQUlBVUNZa3hOWWdZTENRY0lBd0lFRlFnSwpBZ1FXQWdF QUFoa0JBaHNEQWg0QkFDRUpFSlV0czNoTFlvUk5GaUVFZzFvTTRIazc2OEY1dFhzaWxTMnoKZUV0 aWhFMU9hQUQ5R0tEWVo2MElGM0lqQ2dHbjJzL1R2QkdDR1RwN3RLYUdBVldiQ25tb09sd0JBSi9s CnVQb2xGbUo0RDNsZUNGOXlSYldQbk9HVExXaUIzNHBQRForMmJXOEl6amdFWWt4TlloSUtLd1lC QkFHWApWUUVGQVFFSFFMMGpyWmg5TFliZmx5YWJEajBEVVdHS28zMm5Sdnd3MTlmQ25QckdFeFV4 QXdFSUI4SjQKQkJnV0NBQUpCUUppVEUxaUFoc01BQ0VKRUpVdHMzaExZb1JORmlFRWcxb000SGs3 NjhGNXRYc2lsUzJ6CmVFdGloRTNjZkFEL1hXZXVmbTZaT0RPRWJHMUlWampZS0J0c2ZreFdGZzFY L0Z2SWdWNXcwTklCQU9hNQp4NWJ3eGExUnh1Tk1oR3F0SUlMeldlK3lLNFlhbllteXp1OGdQZ2tH Cj1JWWcyCi0tLS0tRU5EIFBHUCBQVUJMSUMgS0VZIEJMT0NLLS0tLS0K -----------------------380bbca5a442aa275c3578375bcc06fb--

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wnUEARYKACcFgmceioYJkJUts3hLYoRNFiEEg1oM4Hk768F5tXsilS2zeEti hE0AAHtGAQC88XQzAa8s4tSTPov8penfCnN1WYp0NQCHCnOUFJxizgD/ZszM 2N8QKcedxL+gtoeAO7TWIOVEflktQ7dT4EisFAU=
=U45L
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Jonathan,

By the way, for future reference, one can use the -r option to lvextend
/ lvreduce which will call the equivalent of resize2fs for you. For
filesystems like ext* that don't allow online shrink it will ask you if
you want to umount it first.

I find it takes some of the guesswork and stress out of such
operations.

Thanks,
Andy

--
https://bitfolk.com/ -- No-nonsense VPS hosting

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)