Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 Running Out of Disk Space Using Persistence With Mint
#7
(05-08-2026, 07:39 AM)longpanda Wrote: 1. Please also run the cmd:

Code:
sudo dmsetup ls

If the persistence take affect, there should be a vtoy_persistent like in the picture.


Then take the number after the colon (in this picture, it is  254:3, so the number after colon is 3)
Run the cmds:
Code:
sudo  mount /dev/dm-3  /mnt
sudo  df -h /mnt

PS:  You should use the correct /dev/dm-X according to your environment (e.g.  /dev/dm-1   /dev/dm-4 ...)



2. Which Mint ISO file did you test?
3. Which persistence file did you boot with? The file name and size.


As before, thanks for the continued help.

For #1, I was able to mount the persistence directory after re-reading your "Linux Remount Feature" article. See the output below.
For #2, I use Linux Mint Cinnamon 22.2. See the output below.
For #3, I use the generic "casper" file. It is "persistence_ext4_4GB_casper-rw.dat" Again, see the output below. I must admit I cannot find where I originally got this file from. I have been learning (and promptly forentoy USB device. I have gotten side-tracked by this disk space issue.

After your last reply, and the difference between your output and my output, it seemed to me my problem was how I was extending the persistence file. So, I tried again and extended my persistence file another 16G. While that was running, I realized I made a mistake in how I was invoking the command. I did not use the "bash" keyword in my previous try's. So, the last attempt at using the ExtendPersistentImg.sh script, correctly has the "bash" keyword. I do not know if this error has completely screwed-up my persistence file. I do not want to start over, as my current persistence file has information (mostly email messages) I do not want to lose. I have been exporting my email messages, so I should be able to recover that if I have to...

You may want to read the terminal output from the end to the beginning. PLEASE READ WHAT'S AFTER THE OUTPUT.
BEGIN TERMINAL OUTPUT
======================
mint@mint:/mnt$ lsf
'System Volume Information'/  iso/  persistence/  ventoy/
mint@mint:/mnt$ cd persistence/
mint@mint:/mnt/persistence$ lsf
persistence_ext4_4GB_casper-rw.dat*
mint@mint:/mnt/persistence$ sudo /home/mint/Downloads/Ventoy-1.1.12/ventoy-1.1.12/ExtendPersistentImg.sh persistence_ext4_4GB_casper-rw.dat 16192
Extend dat file... (current is 12192MB, append 16192MB, total 28384MB)
Extend ext filesystem by resize2fs ...
resize2fs /dev/loop1 28384M
e2fsck 1.47.0 (5-Feb-2023)
casper-rw: recovering journal
Clearing orphaned inode 139063 (uid=1000, gid=1000, mode=0100664, size=32768)
Clearing orphaned inode 138894 (uid=1000, gid=1000, mode=0100600, size=39132)
Clearing orphaned inode 138891 (uid=1000, gid=1000, mode=0100664, size=32768)
Clearing orphaned inode 137776 (uid=1000, gid=1000, mode=0100600, size=3796)
Clearing orphaned inode 137586 (uid=1000, gid=1000, mode=0100664, size=32768)
Clearing orphaned inode 133599 (uid=1000, gid=1000, mode=0100600, size=64)
Clearing orphaned inode 142920 (uid=1000, gid=1000, mode=0100664, size=32768)
Clearing orphaned inode 142855 (uid=1000, gid=1000, mode=0100600, size=38592)
Clearing orphaned inode 137721 (uid=1000, gid=1000, mode=0100664, size=19969)
Clearing orphaned inode 132566 (uid=1000, gid=1000, mode=0100664, size=19969)
Resize inode not valid.  Recreate<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Inode 155073 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
Free blocks count wrong for group #0 (784, counted=785).
Fix<y>? yes
Free blocks count wrong (58335, counted=58327).
Fix<y>? yes
Free inodes count wrong (238003, counted=238130).
Fix<y>? yes

casper-rw: ***** FILE SYSTEM WAS MODIFIED *****
casper-rw: 24014/262144 files (4.7% non-contiguous), 990249/1048576 blocks
resize2fs 1.47.0 (5-Feb-2023)
Resizing the filesystem on /dev/loop1 to 7266304 (4k) blocks.
The filesystem on /dev/loop1 is now 7266304 (4k) blocks long.


======= SUCCESS =========

mint@mint:/mnt/persistence$ sudo bash /home/mint/Downloads/Ventoy-1.1.12/ventoy-1.1.12/ExtendPersistentImg.sh persistence_ext4_4GB_casper-rw.dat 2048
Extend dat file... (current is 28384MB, append 2048MB, total 30432MB)
Extend ext filesystem by resize2fs ...
resize2fs /dev/loop1 30432M
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes
Inode 133599 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 136447
Connect to /lost+found<y>? yes
Inode 136447 ref count is 2, should be 1.  Fix<y>? yes
Pass 5: Checking group summary information
Block bitmap differences:  -557636 -(559035--559039) -560967 -561576 -(563616--563623) -(565091--565095) -(574576--574583) -(575496--575505) -(575520--575527) -(576768--576775) -(576994--577003)
Fix<y>? yes
Free blocks count wrong for group #17 (946, counted=944).
Fix<y>? yes
Free blocks count wrong (6176856, counted=6176854).
Fix<y>? yes
Inode bitmap differences:  -132566 -133599 -137586 -137721 -137776 -138891 -138894 -139063
Fix<y>? yes
Free inodes count wrong for group #16 (129, counted=128).
Fix<y>? yes
Free inodes count wrong (1794610, counted=1794609).
Fix<y>? yes

casper-rw: ***** FILE SYSTEM WAS MODIFIED *****
casper-rw: 24015/1818624 files (4.7% non-contiguous), 1089450/7266304 blocks
resize2fs 1.47.0 (5-Feb-2023)
Resizing the filesystem on /dev/loop1 to 7790592 (4k) blocks.
The filesystem on /dev/loop1 is now 7790592 (4k) blocks long.


======= SUCCESS =========

mint@mint:/mnt/persistence$ pwd
/mnt/persistence
mint@mint:/mnt/persistence$ ll
total 31162624
drwxr-xr-x 2 root root      131072 Dec 26 21:49 ./
drwxr-xr-x 6 root root      131072 May  8 20:20 ../
-rwxr-xr-x 1 root root 31910264832 May  8 20:50 persistence_ext4_4GB_casper-rw.dat*
mint@mint:/mnt/persistence$ cd ..
mint@mint:/mnt$ lsf
'System Volume Information'/  iso/  persistence/  ventoy/
mint@mint:/mnt$ lsf iso
linuxmint-22.2-cinnamon-64bit.iso*
mint@mint:/mnt$ lsf ventoy/
ventoy.json*
mint@mint:/mnt$ df -h
Filesystem          Size  Used Avail Use% Mounted on
tmpfs              1.6G  2.1M  1.6G  1% /run
efivarfs            438K  225K  209K  52% /sys/firmware/efi/efivars
/dev/mapper/ventoy  2.9G  2.9G    0 100% /cdrom
/cow                3.8G  3.6G  6.7M 100% /
tmpfs              7.7G  4.0K  7.7G  1% /dev/shm
tmpfs              5.0M  8.0K  5.0M  1% /run/lock
tmpfs              7.7G  4.0K  7.7G  1% /tmp
tmpfs              1.6G  2.6M  1.6G  1% /run/user/1000
/dev/mapper/sda1    233G  33G  201G  14% /mnt
mint@mint:/mnt$ sudo dmsetup ls
sda1 (252:2)
ventoy (252:0)
vtoy_persistent (252:1)
mint@mint:/mnt$ sudo df -h /mnt
Filesystem        Size  Used Avail Use% Mounted on
/dev/mapper/sda1  233G  33G  201G  14% /mnt
mint@mint:/mnt$ du /home|grep -i Mail
18764 /home/mint/.thunderbird/1b2ron07.default-esr/Mail/Local Folders
677432 /home/mint/.thunderbird/1b2ron07.default-esr/Mail/mail.comcast.net
696200 /home/mint/.thunderbird/1b2ron07.default-esr/Mail
4 /home/mint/.cache/evolution/mail/trash
8 /home/mint/.cache/evolution/mail
4 /home/mint/.local/share/evolution/mail/trash
8 /home/mint/.local/share/evolution/mail
mint@mint:/mnt$
END TERMINAL OUTPUT
====================

It occurs to me my problem is not about extending the persistence file. It's about not having a link between my home directory and the persistence file. My home directory is mounted on "/" (on filesystem /cow), and the persistence is mounted on "/mnt" (on filesystem /dev/mapper/sda1). I somehow need to link /mnt and /cow, or move the /cow filesystem to /mnt.
Reply


Messages In This Thread
RE: Running Out of Disk Space Using Persistence With Mint - by jakolodziej - 05-09-2026, 04:33 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)