6:33 p.m.
F31 upgrade to F32.
#dnf system-upgrade download --releasever=32
Error Summary
-------------
Disk Requirements:
At least 5265MB more space needed on the / filesystem.
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 112M 32G 1% /dev/shm
tmpfs 32G 2.0M 32G 1% /run
/dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
tmpfs 32G 28K 32G 1% /tmp
/dev/nvme0n1p2 976M 376M 534M 42% /boot
/dev/mapper/fedora_localhost--live-home 162G 132G 22G 86% /home
/dev/loop0 23M 23M 0 100%
/var/lib/snapd/snap/snapd/5754
/dev/loop1 55M 55M 0 100%
/var/lib/snapd/snap/core18/1668
/dev/loop2 134M 134M 0 100%
/var/lib/snapd/snap/projectlibre/3
tmpfs 6.3G 20K 6.3G 1% /run/user/42
tmpfs 6.3G 64K 6.3G 1%
/run/user/1000
How does one resize --live-root ?
7:02 p.m.
On 5/4/20 4:33 PM, linux guy wrote:
F31 upgrade to F32.
#dnf system-upgrade download --releasever=32
Error Summary
-------------
Disk Requirements:
At least 5265MB more space needed on the / filesystem.
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 112M 32G 1% /dev/shm
tmpfs 32G 2.0M 32G 1% /run
/dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
tmpfs 32G 28K 32G 1% /tmp
/dev/nvme0n1p2 976M 376M 534M 42% /boot
/dev/mapper/fedora_localhost--live-home 162G 132G 22G 86% /home
/dev/loop0 23M 23M 0 100%
/var/lib/snapd/snap/snapd/5754
/dev/loop1 55M 55M 0 100%
/var/lib/snapd/snap/core18/1668
/dev/loop2 134M 134M 0 100%
/var/lib/snapd/snap/projectlibre/3
tmpfs 6.3G 20K 6.3G 1% /run/user/42
tmpfs 6.3G 64K 6.3G 1%
/run/user/1000
How does one resize --live-root ?
lvresize to resize the lv. Useful options are -l +# of extents or -L
+size in M or G, etc. There is also a -r which will also resize the
filesystem which I've never tried. I usually follow the lvresize with
resize2fs which without options will expand the fs to fill the lv. I
think it may require you to e2fsck first.
7:24 p.m.
On 5/4/20 4:33 PM, linux guy wrote:
F31 upgrade to F32.
#dnf system-upgrade download --releasever=32
Error Summary
-------------
Disk Requirements:
At least 5265MB more space needed on the / filesystem.
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 112M 32G 1% /dev/shm
tmpfs 32G 2.0M 32G 1% /run
/dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
tmpfs 32G 28K 32G 1% /tmp
/dev/nvme0n1p2 976M 376M 534M 42% /boot
/dev/mapper/fedora_localhost--live-home 162G 132G 22G 86% /home
/dev/loop0 23M 23M 0 100%
/var/lib/snapd/snap/snapd/5754
/dev/loop1 55M 55M 0 100%
/var/lib/snapd/snap/core18/1668
/dev/loop2 134M 134M 0 100%
/var/lib/snapd/snap/projectlibre/3
tmpfs 6.3G 20K 6.3G 1% /run/user/42
tmpfs 6.3G 64K 6.3G 1%
/run/user/1000
How does one resize --live-root ?
for increase only lvextend will also work. options are similar. there
are man pages for all of these.
7:37 p.m.
On 5/4/20 4:33 PM, linux guy wrote:
F31 upgrade to F32.
#dnf system-upgrade download --releasever=32
Error Summary
-------------
Disk Requirements:
At least 5265MB more space needed on the / filesystem.
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 112M 32G 1% /dev/shm
tmpfs 32G 2.0M 32G 1% /run
/dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
tmpfs 32G 28K 32G 1% /tmp
/dev/nvme0n1p2 976M 376M 534M 42% /boot
/dev/mapper/fedora_localhost--live-home 162G 132G 22G 86% /home
/dev/loop0 23M 23M 0 100%
/var/lib/snapd/snap/snapd/5754
/dev/loop1 55M 55M 0 100%
/var/lib/snapd/snap/core18/1668
/dev/loop2 134M 134M 0 100%
/var/lib/snapd/snap/projectlibre/3
tmpfs 6.3G 20K 6.3G 1% /run/user/42
tmpfs 6.3G 64K 6.3G 1%
/run/user/1000
How does one resize --live-root ?
The alternate solution which I have used on several occasions is to
symlink /var/lib/dnf/system-upgrade to somewhere with enough space for
the rpm files. Since they're already downloaded, you can just move them
so you don't have to download them again. You have enough room on /home
for example. I've even used a USB stick a couple of times, but you have
to add it to the fstab for that to work.
8:16 p.m.
lvextend -L +6G /dev/mapper/fedora_localhost--live-root
Insufficient free space: 1536 extents needed, but only 0 available
???
I kind of miss the old days of /dev/sda1, /dev/sda2, /dev/sda3...
8:21 p.m.
On 5/4/20 6:16 PM, linux guy wrote:
lvextend -L +6G /dev/mapper/fedora_localhost--live-root
Insufficient free space: 1536 extents needed, but only 0 available
Do you have space to expand it into? I assume the PV is fully used.
I kind of miss the old days of /dev/sda1, /dev/sda2, /dev/sda3...
That's what I use. I still haven't found a use for LVM yet. (And I'm
not saying it's not useful for others!)
8:37 p.m.
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 112M 32G 1% /dev/shm
tmpfs 32G 2.0M 32G 1% /run
/dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
tmpfs 32G 28K 32G 1% /tmp
/dev/nvme0n1p2 976M 376M 534M 42% /boot
/dev/mapper/fedora_localhost--live-home 162G 132G 22G 86% /home
/dev/loop0 23M 23M 0 100%
/var/lib/snapd/snap/snapd/5754
/dev/loop1 55M 55M 0 100%
/var/lib/snapd/snap/core18/1668
/dev/loop2 134M 134M 0 100%
/var/lib/snapd/snap/projectlibre/3
tmpfs 6.3G 20K 6.3G 1% /run/user/42
tmpfs 6.3G 64K 6.3G 1%
/run/user/1000
PV = Parent Volume = /boot ? There is lots of room on /home.
8:45 p.m.
On Mon, 4 May 2020 at 22:38, linux guy <linuxguy123(a)gmail.com> wrote:
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 112M 32G 1% /dev/shm
tmpfs 32G 2.0M 32G 1% /run
/dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
tmpfs 32G 28K 32G 1% /tmp
/dev/nvme0n1p2 976M 376M 534M 42% /boot
/dev/mapper/fedora_localhost--live-home 162G 132G 22G 86% /home
/dev/loop0 23M 23M 0 100%
/var/lib/snapd/snap/snapd/5754
/dev/loop1 55M 55M 0 100%
/var/lib/snapd/snap/core18/1668
/dev/loop2 134M 134M 0 100%
/var/lib/snapd/snap/projectlibre/3
tmpfs 6.3G 20K 6.3G 1% /run/user/42
tmpfs 6.3G 64K 6.3G 1%
/run/user/1000
PV = Parent Volume = /boot ? There is lots of room on /home.
PV = physical volume
Use case for LVM is to adjust sizes when your initial choices didn't work
out. You can probably shrink "fedora_localhost--live-home" and then expand
"fedora_localhost--live-root".
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
--
George N. White III
8:45 p.m.
On 2020-05-05 09:37, linux guy wrote:
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
tmpfs 32G 112M 32G 1% /dev/shm
tmpfs 32G 2.0M 32G 1% /run
/dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
tmpfs 32G 28K 32G 1% /tmp
/dev/nvme0n1p2 976M 376M 534M 42% /boot
/dev/mapper/fedora_localhost--live-home 162G 132G 22G 86% /home
/dev/loop0 23M 23M 0 100%
/var/lib/snapd/snap/snapd/5754
/dev/loop1 55M 55M 0 100%
/var/lib/snapd/snap/core18/1668
/dev/loop2 134M 134M 0 100%
/var/lib/snapd/snap/projectlibre/3
tmpfs 6.3G 20K 6.3G 1% /run/user/42
tmpfs 6.3G 64K 6.3G 1% /run/user/1000
PV = Parent Volume = /boot ? There is lots of room on /home.
No PV=Physical Volume
What is the output of
sudo pvdisplay
and
sudo lvdisplay
--
The key to getting good answers is to ask good questions.
8:51 p.m.
# lvdisplay
--- Logical volume ---
LV Path /dev/fedora_localhost-live/swap
LV Name swap
VG Name fedora_localhost-live
LV UUID k4E6Ti-yS97-79Ih-wQng-yEc5-mqRk-Pjq2V5
LV Write Access read/write
LV Creation host, time localhost-live, 2020-01-09 13:30:13 -0700
LV Status available
# open 2
LV Size 16.15 GiB
Current LE 4135
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/fedora_localhost-live/home
LV Name home
VG Name fedora_localhost-live
LV UUID f7qEPQ-d1y2-bUge-xBE7-bjcx-mpBF-Dasa8B
LV Write Access read/write
LV Creation host, time localhost-live, 2020-01-09 13:30:13 -0700
LV Status available
# open 1
LV Size <165.04 GiB
Current LE 42249
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2
--- Logical volume ---
LV Path /dev/fedora_localhost-live/root
LV Name root
VG Name fedora_localhost-live
LV UUID lKuD2i-m5R1-1P70-OeTc-IX2L-mcSh-tEFk8N
LV Write Access read/write
LV Creation host, time localhost-live, 2020-01-09 13:30:36 -0700
LV Status available
# open 1
LV Size <50.11 GiB
Current LE 12828
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
# pvdisplay
--- Physical volume ---
PV Name /dev/nvme0n1p3
VG Name fedora_localhost-live
PV Size <231.30 GiB / not usable 2.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 59212
Free PE 0
Allocated PE 59212
PV UUID 3VH3r7-BOSc-PaRC-Ragt-15Co-Th5g-YX4nVs
9:10 p.m.
# lvreduce -L 6G /dev/mapper/fedora_localhost--live-home
WARNING: Reducing active and open logical volume to 6.00 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce fedora_localhost-live/home? [y/n]:
Is lvreduce smart, ie does it know not to touch existing data ?
Is there a way to do this with parted ?
9:57 p.m.
On 2020-05-05 10:10, linux guy wrote:
# lvreduce -L 6G /dev/mapper/fedora_localhost--live-home
WARNING: Reducing active and open logical volume to 6.00 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce fedora_localhost-live/home? [y/n]:
Is lvreduce smart, ie does it know not to touch existing data ?
FWIW, I generally use lvresize and only on unmounted file-systems.
I'm pretty much sure that is what the warning is trying to tell you.
Having an active filesystem during a resize operation sounds dangerous to me.
(I've not used LV's much recently)
--
The key to getting good answers is to ask good questions.
11:18 p.m.
Gparted won't run on my system. It hangs scanning the hard drive.
On Mon, May 4, 2020 at 8:58 PM Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 2020-05-05 10:10, linux guy wrote:
> # lvreduce -L 6G /dev/mapper/fedora_localhost--live-home
> WARNING: Reducing active and open logical volume to 6.00 GiB.
> THIS MAY DESTROY YOUR DATA (filesystem etc.)
> Do you really want to reduce fedora_localhost-live/home? [y/n]:
> Is lvreduce smart, ie does it know not to touch existing data ?
>
FWIW, I generally use lvresize and only on unmounted file-systems.
I'm pretty much sure that is what the warning is trying to tell you.
Having an active filesystem during a resize operation sounds dangerous to
me.
(I've not used LV's much recently)
--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
11:29 a.m.
On 5 May 2020, at 03:57, Ed Greshko <ed.greshko(a)greshko.com>
wrote:
FWIW, I generally use lvresize and only on unmounted file-systems.
I'm pretty much sure that is what the warning is trying to tell you.
Having an active filesystem during a resize operation sounds dangerous to me.
(I've not used LV's much recently)
I use "lvresize -L+${size}G --resizefs ${name}" often and its very safe to do on
a live file system.
Barry
2:54 p.m.
On 5/16/20 9:29 AM, Barry Scott wrote:
> On 5 May 2020, at 03:57, Ed Greshko <ed.greshko(a)greshko.com
> <mailto:ed.greshko@greshko.com>> wrote:
>
> FWIW, I generally use lvresize and only on unmounted file-systems.
> I'm pretty much sure that is what the warning is trying to tell you.
> Having an active filesystem during a resize operation sounds dangerous
> to me.
>
> (I've not used LV's much recently)
I use "lvresize -L+${size}G --resizefs ${name}" often and its very safe
to do on a live file system.
To shrink or grow? And which filesystem?
3:40 p.m.
On 5/16/20 12:54 PM, Samuel Sieb wrote:
On 5/16/20 9:29 AM, Barry Scott wrote:
>> On 5 May 2020, at 03:57, Ed Greshko <ed.greshko(a)greshko.com
>> <mailto:ed.greshko@greshko.com>> wrote:
>>
>> FWIW, I generally use lvresize and only on unmounted file-systems.
>> I'm pretty much sure that is what the warning is trying to tell you.
>> Having an active filesystem during a resize operation sounds
>> dangerous to me.
>>
>> (I've not used LV's much recently)
>
> I use "lvresize -L+${size}G --resizefs ${name}" often and its very
> safe to do on a live file system.
To shrink or grow? And which filesystem?
-L is the option, the + following says increase. I believe the lvresize
and lvextend commands are filesystem agnostic.
I, too, use these commands on mounted filesystems and have never had a
bad experience ( knock on wood ;)
5:38 p.m.
On 5/17/20 1:40 PM, Mike Wright wrote:
On 5/16/20 12:54 PM, Samuel Sieb wrote:
> On 5/16/20 9:29 AM, Barry Scott wrote:
>>> On 5 May 2020, at 03:57, Ed Greshko <ed.greshko(a)greshko.com
>>> <mailto:ed.greshko@greshko.com>> wrote:
>>>
>>> FWIW, I generally use lvresize and only on unmounted file-systems.
>>> I'm pretty much sure that is what the warning is trying to tell you.
>>> Having an active filesystem during a resize operation sounds
>>> dangerous to me.
>>>
>>> (I've not used LV's much recently)
>>
>> I use "lvresize -L+${size}G --resizefs ${name}" often and its very
>> safe to do on a live file system.
>
> To shrink or grow? And which filesystem?
-L is the option, the + following says increase. I believe the lvresize
and lvextend commands are filesystem agnostic.
I, too, use these commands on mounted filesystems and have never had a
bad experience ( knock on wood ;)
Ok, growing is fine, but the OP needed to shrink one as well which can't
be done live.
6:02 p.m.
On 2020-05-18 06:38, Samuel Sieb wrote:
On 5/17/20 1:40 PM, Mike Wright wrote:
> On 5/16/20 12:54 PM, Samuel Sieb wrote:
>> On 5/16/20 9:29 AM, Barry Scott wrote:
>>>> On 5 May 2020, at 03:57, Ed Greshko <ed.greshko(a)greshko.com
<mailto:ed.greshko@greshko.com>> wrote:
>>>>
>>>> FWIW, I generally use lvresize and only on unmounted file-systems.
>>>> I'm pretty much sure that is what the warning is trying to tell you.
>>>> Having an active filesystem during a resize operation sounds dangerous to
me.
>>>>
>>>> (I've not used LV's much recently)
>>>
>>> I use "lvresize -L+${size}G --resizefs ${name}" often and its very
safe to do on a live file system.
>>
>> To shrink or grow? And which filesystem?
>
> -L is the option, the + following says increase. I believe the lvresize and lvextend
commands are filesystem agnostic.
>
> I, too, use these commands on mounted filesystems and have never had a bad experience
( knock on wood ;)
Ok, growing is fine, but the OP needed to shrink one as well which can't be done
live.
Frankly, I don't know why this tread is being revived. It has already been shown how
the OP can accomplish
what he wants after booting from a LIVE image.
Anyway, if one tries to shrink a mounted filesystem they are presented with this....
[root@f32k2 ~]# lvresize -r -L -1G /dev/fedora_f32k2/home
Do you want to unmount "/home" ? [Y|n] n
fsadm: Cannot proceed with mounted filesystem "/home".
/usr/sbin/fsadm failed: 1
Filesystem resize failed.
And unmouting a filesystem that happens to be in use may result in "problems".
--
The key to getting good answers is to ask good questions.
10:19 p.m.
On 5/4/20 7:10 PM, linux guy wrote:
# lvreduce -L 6G /dev/mapper/fedora_localhost--live-home
WARNING: Reducing active and open logical volume to 6.00 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce fedora_localhost-live/home? [y/n]:
Is lvreduce smart, ie does it know not to touch existing data ?
I expect you need to resize the filesystem first before resizing the
volume. But also, you can't shrink ext4 while it's mounted.
Is there a way to do this with parted ?
No, this is unrelated to partitions.
12:59 a.m.
On 2020-05-05 11:19, Samuel Sieb wrote:
On 5/4/20 7:10 PM, linux guy wrote:
> # lvreduce -L 6G /dev/mapper/fedora_localhost--live-home
> WARNING: Reducing active and open logical volume to 6.00 GiB.
> THIS MAY DESTROY YOUR DATA (filesystem etc.)
> Do you really want to reduce fedora_localhost-live/home? [y/n]:
> Is lvreduce smart, ie does it know not to touch existing data ?
I expect you need to resize the filesystem first before resizing the volume. But also,
you can't shrink ext4 while it's mounted.
Yes, I just did it on a VM to test. I booted from a LIVE image so the nothing was
mounted.
BEFORE
[root@f30g ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root fedora_f30g -wi-ao----
<17.00g
swap fedora_f30g -wi-ao---- 2.00g
ran e2fsck on the file system
ran resize2fs to shrink it
ran lvresize with -L to shrink the root LV
Since this was a VM with no real users I didn't have a separate /home. So, I
ran lvresize with -L to increase the swap LV
ran mkswap to remake the swap partition
AFTER
[root@f30g ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root fedora_f30g -wi-ao---- 16.00g
swap fedora_f30g -wi-ao---- 2.80g
--
The key to getting good answers is to ask good questions.
1:12 a.m.
On 2020-05-05 13:59, Ed Greshko wrote:
On 2020-05-05 11:19, Samuel Sieb wrote:
> On 5/4/20 7:10 PM, linux guy wrote:
>> # lvreduce -L 6G /dev/mapper/fedora_localhost--live-home
>> WARNING: Reducing active and open logical volume to 6.00 GiB.
>> THIS MAY DESTROY YOUR DATA (filesystem etc.)
>> Do you really want to reduce fedora_localhost-live/home? [y/n]:
>> Is lvreduce smart, ie does it know not to touch existing data ?
> I expect you need to resize the filesystem first before resizing the volume. But
also, you can't shrink ext4 while it's mounted.
>
Yes, I just did it on a VM to test. I booted from a LIVE image so the nothing was
mounted.
BEFORE
[root@f30g ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync
Convert
root fedora_f30g -wi-ao----
<17.00g
swap fedora_f30g -wi-ao---- 2.00g
ran e2fsck on the file system
ran resize2fs to shrink it
Oh, forgot that before doing the lvresize I did lvchange to deactivate the LV
ran lvresize with -L to shrink the root LV
Since this was a VM with no real users I didn't have a separate /home. So, I
ran lvresize with -L to increase the swap LV
ran mkswap to remake the swap partition
AFTER
[root@f30g ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root fedora_f30g -wi-ao---- 16.00g
swap fedora_f30g -wi-ao---- 2.80g
--
The key to getting good answers is to ask good questions.
11:38 a.m.
"Oh, forgot that before doing the lvresize I did lvchange to deactivate the
LV"
So what were the exact steps you used ?
1:36 p.m.
On 2020-05-06 00:38, linux guy wrote:
"Oh, forgot that before doing the lvresize I did lvchange to
deactivate the LV"
So what were the exact steps you used ?
Well, it is 02:30 at the moment. So, I'll retrace and post the exact commands later.
--
The key to getting good answers is to ask good questions.
10:22 p.m.
On 5/4/20 7:10 PM, linux guy wrote:
# lvreduce -L 6G /dev/mapper/fedora_localhost--live-home
WARNING: Reducing active and open logical volume to 6.00 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce fedora_localhost-live/home? [y/n]:
Is lvreduce smart, ie does it know not to touch existing data ?
Is there a way to do this with parted ?
Reducing an LV is fraught with risk. You must first reduce the size of
the filesystem. Only then is it safe to reduce the size of the LV. If
you don't shrink the filesystem first when you shrink the LV it will
truncate the filesystem which is full. Now the fs is irreparably hosed.
The error you got is because the VG (volume group) that contains your
LVs has no more extents to allocate.
In your situation the easiest and safest method is to create another PV
(physical volume) then add it the the VG that contains your LVs. Once
you do that there will be more available extents and you can proceed
with the lvextend/lvresize.
10:17 p.m.
On 05/04/2020 07:21 PM, Samuel Sieb wrote:
>
That's what I use. I still haven't found a use for LVM yet. (And I'm
not saying it's not useful for others!)
Neither have I. But then, I'm retired and only using Linux for my
personal computers. I'm sure there are many uses for it in business.
1:16 p.m.
New subject: F32 Upgrade error: more space needed on the / filesystem... --live-root ?
Hi.
On Mon, 04 May 2020 17:37:02 -0700 Samuel Sieb wrote:
On 5/4/20 4:33 PM, linux guy wrote:
> Disk Requirements:
> At least 5265MB more space needed on the / filesystem.
> # df -h
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/fedora_localhost--live-root 49G 48G 0 100% /
> How does one resize --live-root ?
The alternate solution which I have used on several occasions is to
symlink /var/lib/dnf/system-upgrade to somewhere with enough space for
the rpm files.
Right. I do that also for /var/cache/dnf, but before doing that, or
resizing the LV's, I suggest to check if you can suppress
files/directories to make free space in /
49G, even with /var/lib/dnf/system-upgrade seems too big for F31.
Proceed for example as follows;
cd /
du -h -x --max-depth 1 | sort -h | tail
then iterate on the big subdirs shown.
The winners are often:
/var/cache/PackageKit
/var/spool/abrt
/var/cache/abrt-di
/root
/var/lib/docker
--
francis
4:40 p.m.
I've missed those "other instructions". The part I don't understand
is
doing a lvresize/ lvextend / lvreduce on a live system without losing data.
On Tue, May 5, 2020 at 2:56 PM Samuel Sieb <samuel(a)sieb.net> wrote:
On 5/5/20 1:43 PM, linux guy wrote:
>
> I need to resize / regardless of this dnf operation. /home has space
> to spare.
Then follow the other part of this thread where the instructions for
that are. And good luck...
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
4:46 p.m.
On 2020-05-06 05:40, linux guy wrote:
I've missed those "other instructions". The part I
don't understand is doing a lvresize/ lvextend / lvreduce on a live system without
losing data.
I didn't do it on a "live" system. I booted from the "live" image
where those filesystems are not being
used.
Do you still need precise details on what I did? I can do that after a bit.
--
The key to getting good answers is to ask good questions.
5:12 p.m.
I would appreciate them, Ed, just to make sure I'm not missing something.
No rush. Don't get up early.
7:07 p.m.
On 2020-05-06 06:12, linux guy wrote:
I would appreciate them, Ed, just to make sure I'm not missing
something. No rush. Don't get up early.
I do normally get up early. But had some other things to take care of first.
In my case I don't have separate / and /home. So, I am going to decrease / and
increase swap.
Decreasing is more dangerous than Increasing. You'll be decreasing /home and
increasing /.
This is the system normally booted before modification.
[egreshko@f31m ~]$ df -t ext4
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/fedora_localhost--live-root 17410832 7037660 9465704 43% /
/dev/vda1 999320 263436 667072 29% /boot
[egreshko@f31m ~]$ swapon
NAME TYPE SIZE USED PRIO
/dev/dm-1 partition 2G 0B -2
[egreshko@f31m ~]$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log
Cpy%Sync Convert
root fedora_localhost-live -wi-ao----
<17.00g
swap fedora_localhost-live -wi-ao---- 2.00g
My goal is to reduce / by 2 GB and add to swap. So, I then boot from the F31 Mate Spin
image and
do the following.
[root@localhost-live ~]# e2fsck -ff /dev/fedora_localhost-live/root
e2fsck 1.45.3 (14-Jul-2019)
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/fedora_localhost-live/root: 226041/1114112 files (0.2% non-contiguous),
1855851/4455424 blocks
I now resize the filesystem to 15GB. Failure to resize the FS will result in disaster.
[root@localhost-live ~]# resize2fs /dev/fedora_localhost-live/root 15G
resize2fs 1.45.3 (14-Jul-2019)
Resizing the filesystem on /dev/fedora_localhost-live/root to 3932160 (4k) blocks.
The filesystem on /dev/fedora_localhost-live/root is now 3932160 (4k) blocks long.
Make the LV inactive
[root@localhost-live ~]# lvchange -a n /dev/fedora_localhost-live/root
Now, shrink the LV....but not as much as the FS.
I can't recall the reason for this....but that is what I've done in the past. 0.5
difference is probably excessive
but....
[root@localhost-live ~]# lvresize /dev/fedora_localhost-live/root -L 15.5GB
Size of logical volume fedora_localhost-live/root changed from <17.00 GiB (4351
extents) to 15.50 GiB (3968 extents).
Logical volume fedora_localhost-live/root successfully resized.
Activate the LV
[root@localhost-live ~]# lvchange -a y /dev/fedora_localhost-live/root
And run a check on the new size
[root@localhost-live ~]# e2fsck -ff /dev/fedora_localhost-live/root
e2fsck 1.45.3 (14-Jul-2019)
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/fedora_localhost-live/root: 226041/983040 files (0.3% non-contiguous),
1846611/3932160 blocks
Then I want to increase swap. But I intentionally make it too big to find out what is
really available.
This is where you'd increase /.
[root@localhost-live ~]# lvresize /dev/fedora_localhost-live/swap -L 4GB
Insufficient free space: 512 extents needed, but only 383 available
So then I do this. In this case I'm adding extents rather than giving a specific
size.
[root@localhost-live ~]# lvresize /dev/fedora_localhost-live/swap -l +383
Size of logical volume fedora_localhost-live/swap changed from 2.00 GiB (512 extents) to
<3.50 GiB (895 extents).
Logical volume fedora_localhost-live/swap successfully resized.
I then boot normally and see.
[egreshko@f31m ~]$ df -t ext4
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/fedora_localhost--live-root 15350728 7033772 7514144 49% /
/dev/vda1 999320 263436 667072 29% /boot
[egreshko@f31m ~]$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync
Convert
root fedora_localhost-live -wi-ao----
15.50g
swap fedora_localhost-live -wi-ao---- <3.50g
[egreshko@f31m ~]$ sudo swapon
NAME TYPE SIZE USED PRIO
/dev/dm-1 partition 2G 0B -2
So, / is now smaller. But I have to fix swap manually. This wouldn't be needed with
/home
Originally
root@f31m ~]# swapon
NAME TYPE SIZE USED PRIO
/dev/dm-1 partition 2G 0B -2
Turn it off
[root@f31m ~]# swapoff /dev/dm-1
Remake it
[root@f31m ~]# mkswap /dev/dm-1
mkswap: /dev/dm-1: warning: wiping old swap signature.
Setting up swapspace version 1, size = 3.5 GiB (3753897984 bytes)
no label, UUID=bfc61bdb-3252-42e1-9b4c-e72b154c6c30
And now the new size
[root@f31m ~]# swapon /dev/dm-1
[root@f31m ~]# swapon
NAME TYPE SIZE USED PRIO
/dev/dm-1 partition 3.5G 0B -2
--
The key to getting good answers is to ask good questions.
7:19 p.m.
On 2020-05-06 08:07, Ed Greshko wrote:
On 2020-05-06 06:12, linux guy wrote:
> I would appreciate them, Ed, just to make sure I'm not missing something. No
rush. Don't get up early.
I do normally get up early. But had some other things to take care of first.
In my case I don't have separate / and /home. So, I am going to decrease / and
increase swap.
Decreasing is more dangerous than Increasing. You'll be decreasing /home and
increasing /.
This is the system normally booted before modification.
[egreshko@f31m ~]$ df -t ext4
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/fedora_localhost--live-root 17410832 7037660 9465704 43% /
/dev/vda1 999320 263436 667072 29% /boot
[egreshko@f31m ~]$ swapon
NAME TYPE SIZE USED PRIO
/dev/dm-1 partition 2G 0B -2
[egreshko@f31m ~]$ sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log
Cpy%Sync Convert
root fedora_localhost-live -wi-ao----
<17.00g
swap fedora_localhost-live -wi-ao---- 2.00g
My goal is to reduce / by 2 GB and add to swap. So, I then boot from the F31 Mate Spin
image and
do the following.
[root@localhost-live ~]# e2fsck -ff /dev/fedora_localhost-live/root
e2fsck 1.45.3 (14-Jul-2019)
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/fedora_localhost-live/root: 226041/1114112 files (0.2% non-contiguous),
1855851/4455424 blocks
I now resize the filesystem to 15GB. Failure to resize the FS will result in disaster.
[root@localhost-live ~]# resize2fs /dev/fedora_localhost-live/root 15G
resize2fs 1.45.3 (14-Jul-2019)
Resizing the filesystem on /dev/fedora_localhost-live/root to 3932160 (4k) blocks.
The filesystem on /dev/fedora_localhost-live/root is now 3932160 (4k) blocks long.
Make the LV inactive
[root@localhost-live ~]# lvchange -a n /dev/fedora_localhost-live/root
Now, shrink the LV....but not as much as the FS.
I can't recall the reason for this....but that is what I've done in the past. 0.5
difference is probably excessive
but....
[root@localhost-live ~]# lvresize /dev/fedora_localhost-live/root -L 15.5GB
Size of logical volume fedora_localhost-live/root changed from <17.00 GiB (4351
extents) to 15.50 GiB (3968 extents).
Logical volume fedora_localhost-live/root successfully resized.
Activate the LV
[root@localhost-live ~]# lvchange -a y /dev/fedora_localhost-live/root
And run a check on the new size
[root@localhost-live ~]# e2fsck -ff /dev/fedora_localhost-live/root
e2fsck 1.45.3 (14-Jul-2019)
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/fedora_localhost-live/root: 226041/983040 files (0.3% non-contiguous),
1846611/3932160 blocks
Then I want to increase swap. But I intentionally make it too big to find out what is
really available.
This is where you'd increase /.
[root@localhost-live ~]# lvresize /dev/fedora_localhost-live/swap -L 4GB
Insufficient free space: 512 extents needed, but only 383 available
So then I do this. In this case I'm adding extents rather than giving a specific
size.
[root@localhost-live ~]# lvresize /dev/fedora_localhost-live/swap -l +383
Size of logical volume fedora_localhost-live/swap changed from 2.00 GiB (512 extents)
to <3.50 GiB (895 extents).
Logical volume fedora_localhost-live/swap successfully resized.
Oh, forgot to add
Here you'd also have to resize2fs to give more space to /
That's not needed in the case of swap as the mkswap fixes it.
--
The key to getting good answers is to ask good questions.
7:22 p.m.
On 2020-05-06 08:19, Ed Greshko wrote:
Oh, forgot to add
Here you'd also have to resize2fs to give more space to /
That's not needed in the case of swap as the mkswap fixes it.
If you need it....
I could create a VM to more closely match your filesystem layout and run the commands
in much the same way you'd need to.
It would just take me a bit of time.
--
The key to getting good answers is to ask good questions.
5:20 a.m.
On Tue, 5 May 2020 at 21:22, Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 2020-05-06 08:19, Ed Greshko wrote:
> Oh, forgot to add
>
> Here you'd also have to resize2fs to give more space to /
>
> That's not needed in the case of swap as the mkswap fixes it.
If you need it....
I could create a VM to more closely match your filesystem layout and run
the commands
in much the same way you'd need to.
It would just take me a bit of time.
That is really going the extra distance to help. The OP should consider
creating
his own VM. I do this using an external USB3 spinning disk (several TB
for $100,
avoid the slow "archive" disks, and get one that takes power from an AC
plug).
The OP needs one to backup his home anyway, and the ability to work an
example
on a disposable VM will build confidence. As an added bonus, if something
unexpected happens on the target system he will know it wasn't caused by
misunderstanding the procedure.
--
George N. White III
2:13 a.m.
I got my update done by doing a symlink for /var/lib/dnf/system-upgrade to
a directory on /home.
I'll resize / in the future.
7:56 a.m.
To Ed Greshko (and everyone else who helps)
The help/comments you guys provide is great!
As a casual user, can't tell you the number of times I've tried to
deal with problem X and recall something that someone has said about
another issue that's given me that "aha" thought to further
research/sove my issue.
just a hearty thanks!
2:33 a.m.
New subject: (BETTER) F32 Upgrade error: more space needed on the /
filesystem... --live-root ?
On 2020-05-06 06:12, linux guy wrote:
I would appreciate them, Ed, just to make sure I'm not missing
something. No rush. Don't get up early.
Maybe I should have waited. My afternoon freed up. So, I created a new VM.
This is BEFORE.....
[root@f32k2 ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/vda2 fedora_f32k2 lvm2 a-- <31.16g 4.00m
[root@f32k2 ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
home fedora_f32k2 -wi-ao---- 18.00g
root fedora_f32k2 -wi-ao---- 12.00g
swap fedora_f32k2 -wi-ao---- 1.15g
[root@f32k2 ~]# df -h -t ext4
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/fedora_f32k2-root 12G 5.5G 5.8G 49% /
/dev/mapper/fedora_f32k2-home 18G 234M 17G 2% /home
/dev/vda1
I then booted the LIVE image and this time used the -r and -L in the following manner.
[root@localhost-live ~]# lvresize -r -L -4G /dev/fedora_f32k2/home
fsck from util-linux 2.35.1
/dev/mapper/fedora_f32k2-home: 625/1179648 files (6.1% non-contiguous), 166652/4718592
blocks
resize2fs 1.45.5 (07-Jan-2020)
Resizing the filesystem on /dev/mapper/fedora_f32k2-home to 3670016 (4k) blocks.
The filesystem on /dev/mapper/fedora_f32k2-home is now 3670016 (4k) blocks long.
Size of logical volume fedora_f32k2/home changed from 18.00 GiB (4608 extents) to 14.00
GiB (3584 extents).
Logical volume fedora_f32k2/home successfully resized.
[root@localhost-live ~]# lvresize -r -L +4G /dev/fedora_f32k2/root
fsck from util-linux 2.35.1
/dev/mapper/fedora_f32k2-root: 185073/786432 files (0.2% non-contiguous), 1482127/3145728
blocks
Size of logical volume fedora_f32k2/root changed from 12.00 GiB (3072 extents) to 16.00
GiB (4096 extents).
Logical volume fedora_f32k2/root successfully resized.
resize2fs 1.45.5 (07-Jan-2020)
Resizing the filesystem on /dev/mapper/fedora_f32k2-root to 4194304 (4k) blocks.
The filesystem on /dev/mapper/fedora_f32k2-root is now 4194304 (4k) blocks long.
[root@localhost-live ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
home fedora_f32k2 -wi-a----- 14.00g
root fedora_f32k2 -wi-a----- 16.00g
swap fedora_f32k2 -wi-a----- 1.15g
Just to check I ran fsck on both
[root@localhost-live ~]# e2fsck -ff /dev/fedora_f32k2/home
e2fsck 1.45.5 (07-Jan-2020)
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/fedora_f32k2/home: 625/917504 files (6.1% non-contiguous), 149166/3670016 blocks
[root@localhost-live ~]# e2fsck -ff /dev/fedora_f32k2/root
e2fsck 1.45.5 (07-Jan-2020)
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/fedora_f32k2/root: 185073/1048576 files (0.2% non-contiguous), 1499602/4194304
blocks
I then booted normally
AFTER
[root@f32k2 ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/vda2 fedora_f32k2 lvm2 a-- <31.16g 4.00m
[root@f32k2 ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
home fedora_f32k2 -wi-ao---- 14.00g
root fedora_f32k2 -wi-ao---- 16.00g
swap fedora_f32k2 -wi-ao---- 1.15g
[root@f32k2 ~]# df -h -t ext4
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/fedora_f32k2-root 16G 5.5G 9.5G 37% /
/dev/vda1 829M 222M 549M 29% /boot
/dev/mapper/fedora_f32k2-home 14G 230M 13G 2% /home
--
The key to getting good answers is to ask good questions.
1437
days inactive
1450
days old
42 comments
9 participants
participants (9)
-
Barry Scott -
bruce -
Ed Greshko -
Francis.Montagnac＠inria.fr -
George N. White III -
Joe Zeff -
linux guy -
Mike Wright -
Samuel Sieb