Moderator: Forum moderators
I could not take a screenshot, and the pinboard could not update for the same reason. Using fossapup now.
It didn't tell me which device. It looks to me like there is plenty of space. And the internet connection stopped working as well (but only in bookworm). Pretty sure it is the same problem.
Any suggestions?
Thanks!
Don't take life too seriously, you will never get out alive.
Hi Governor
I have had stuff fill up my ram (root) and sneak up on me with a similar error.
Vektor
I think we need more information. Right now, without enough information, the only thing I can think of is you are using a savefile. Not a folder. If my hunch is right you're using a savefile, default size of a savefile is, if I remember it correctly, only 512MB.
The Art of Magic and The Magic of Art
Had a 'disk full' issue last week with BKWP64 v1007 where it would NOT download a file from the web.
I found that my session-save folder had filled the partition. In review, my browser cache was the culprit and after cleaning, needed to restart the desktop.
This phenom may be different from what OP started this thread.
Governor wrote: ↑Sun Jul 28, 2024 6:27 pmI could not take a screenshot, and the pinboard could not update for the same reason. Using fossapup now.
It didn't tell me which device. It looks to me like there is plenty of space. And the internet connection stopped working as well (but only in bookworm). Pretty sure it is the same problem.
Any suggestions?
Thanks!
same problem as what? and which device "looks like" there is plenty of space?
williwaw wrote: ↑Mon Jul 29, 2024 5:24 amGovernor wrote: ↑Sun Jul 28, 2024 6:27 pmI could not take a screenshot, and the pinboard could not update for the same reason. Using fossapup now.
It didn't tell me which device. It looks to me like there is plenty of space. And the internet connection stopped working as well (but only in bookworm). Pretty sure it is the same problem.
Any suggestions?
Thanks!same problem as what? and which device "looks like" there is plenty of space?
IDK, but I wonder if the missing internet connection may be due to the "device full" message.
This is the screenshot of pmount in bookworm:
Here is the screenshot of pmount in fossapup after re-booting:
Here is the output of the 'free' command on the first 3 partitions:
Don't take life too seriously, you will never get out alive.
Clarity wrote: ↑Mon Jul 29, 2024 5:12 amHad a 'disk full' issue last week with BKWP64 v1007 where it would NOT download a file from the web.
I found that my session-save folder had filled the partition. In review, my browser cache was the culprit and after cleaning, needed to restart the desktop.
This phenom may be different from what OP started this thread.
That is interesting because I recently increased my browser disk cache capacity. I can lower it again. Is it possible to tell Firefox where to store the disk cache?
Don't take life too seriously, you will never get out alive.
vektor_alian wrote: ↑Sun Jul 28, 2024 6:54 pmHi Governor
I have had stuff fill up my ram (root) and sneak up on me with a similar error.
Vektor
Wait a minute, are files written to RAM going to the root folder on disk?
Don't take life too seriously, you will never get out alive.
jp734 wrote: ↑Mon Jul 29, 2024 1:57 amI think we need more information. Right now, without enough information, the only thing I can think of is you are using a savefile. Not a folder. If my hunch is right you're using a savefile, default size of a savefile is, if I remember it correctly, only 512MB.
I am using save folders. I posted more info with screenshots.
Don't take life too seriously, you will never get out alive.
you report a "device full" error and clarity reports a "disk full" error. I suppose that needs to be clarified if one is to assume the same thing is happening
anyways
the "device" seems to working again after a reboot? maybe the "device" is the partition you were using earlier when the problem happened. Can you save something to that partition now and rule out whether the disk partition is full?
Run free when the problems occur. Im not sure if running it after a reboot will tell you much about a prior session.
try running df to ascertain disk usage the outputs from pmount do not look consistent.
williwaw wrote: ↑Mon Jul 29, 2024 7:30 amyou report a "device full" error and clarity reports a "disk full" error. I suppose that needs to be clarified if one is to assume the same thing is happening
anyways
the "device" seems to working again after a reboot? maybe the "device" is the partition you were using earlier when the problem happened. Can you save something to that partition now and rule out whether the disk partition is full?Run
freewhen the problems occur. Im not sure if running it after a reboot will tell you much about a prior session.
try runningdfto ascertain disk usage the outputs from pmount do not look consistent.
I posted details here:
https://www.forum.puppylinux.com/viewto ... 83#p127383
I will try the df command later, I am on fossapup now.
Don't take life too seriously, you will never get out alive.
"Round and round the mulberry bush...."
Here we go AGAIN. Oh, boy.....
I can't believe it's possible for anyone to have so many "issues" in such a relatively short space of time.
Mike. 
It is hard to believe for me too! IMO, it certainly and absolutely indicates that there are many issues with the OS.... so please don't blame the user.
Food for thought:
Perhaps the reason why you can't believe a user can have so many issues, is that those who experience many issues are not reporting them in this forum.
And also because users who have many issues simply drop the OS and try something else, and are not informing anyone. 
I doubt many users would be as dedicated and determined as I am, considering the issues I encounter. Perhaps people ought to shake my hand and congratulate me for my commitment and perseverance. 
Don't take life too seriously, you will never get out alive.
williwaw wrote: ↑Mon Jul 29, 2024 7:30 amyou report a "device full" error and clarity reports a "disk full" error. I suppose that needs to be clarified if one is to assume the same thing is happening
anyways
the "device" seems to working again after a reboot? maybe the "device" is the partition you were using earlier when the problem happened. Can you save something to that partition now and rule out whether the disk partition is full?Run
freewhen the problems occur. Im not sure if running it after a reboot will tell you much about a prior session.
try runningdfto ascertain disk usage the outputs from pmount do not look consistent.
Bookworm:
Code: Select all
df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nvme0n1p2 20466388 4649032 14768780 24% /initrd/mnt/dev_save
tmpfs 7533128 321664 7211464 5% /initrd/mnt/tmpfs
/dev/loop0 452864 452864 0 100% /initrd/pup_ro2
/dev/loop1 15616 15616 0 100% /initrd/pup_k
/dev/loop2 112128 112128 0 100% /initrd/pup_f
/dev/loop3 73472 73472 0 100% /initrd/pup_z
/dev/loop4 8448 8448 0 100% /initrd/pup_b
/dev/loop5 76800 76800 0 100% /initrd/pup_a
unionfs 7533128 321664 7211464 5% /
devtmpfs 5017356 4 5017352 1% /dev
shmfs 2469128 0 2469128 0% /dev/shm
/dev/nvme0n1p4 108875068 56978508 46319856 56% /mnt/nvme0n1p4
/dev/nvme0n1p6 192516316 88789772 93890924 49% /mnt/nvme0n1p6
/dev/nvme0n1p5 152555140 134811128 9921832 94% /mnt/nvme0n1p5
#
Don't take life too seriously, you will never get out alive.
williwaw wrote: ↑Mon Jul 29, 2024 7:30 amyou report a "device full" error and clarity reports a "disk full" error. I suppose that needs to be clarified if one is to assume the same thing is happening
anyways
the "device" seems to working again after a reboot? maybe the "device" is the partition you were using earlier when the problem happened. Can you save something to that partition now and rule out whether the disk partition is full?Run
freewhen the problems occur. Im not sure if running it after a reboot will tell you much about a prior session.
try runningdfto ascertain disk usage the outputs from pmount do not look consistent.
Bookworm did it again. I tried to shut bookworm down normally by using the menu exit, but it refuses to quit and I can't take a screenshot. I took this photo with my camera:
I had to press the power button to quit.
Don't take life too seriously, you will never get out alive.
Your savefile's full. Delete some stuff out of it, or move stuff out of it, or increase the size of it.
If you're using Firefox, move the ~/.mozilla folder outside of the save file, and then create a symlink back to it. Saves heaps of lost space in a save file.
Error saving pinboard /root/...
no space left on device...
Hmmm
Vektor
@Governor
You say it is using a save folder.
What is the exact name of the save used in BookwormPup64?
All of these issues are classic, the save file is full.
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
Here is the menu item I am booting from:
/mnt/nvme0n1p2/Bookworm64_10.0.6/dpupbw64save-2024-06-25-basic-02
Don't take life too seriously, you will never get out alive.
Here is my boot menu.
I am on bookworm now, is there anything specific I should do?
Don't take life too seriously, you will never get out alive.
Governor wrote: ↑Mon Jul 29, 2024 11:01 amIt is hard to believe for me too! IMO, it certainly and absolutely indicates that there are many issues with the OS.... so please don't blame the user.
Food for thought:
Perhaps the reason why you can't believe a user can have so many issues, is that those who experience many issues are not reporting them in this forum.
And also because users who have many issues simply drop the OS and try something else, and are not informing anyone.
I doubt many users would be as dedicated and determined as I am, considering the issues I encounter. Perhaps people ought to shake my hand and congratulate me for my commitment and perseverance.
Yes, I'll shake your hand and congratulate you for your persistently testing of very, very complicated usage 
, who knows ? some bug found that nobody else had discovered earlier ?
Indeed, very often people don't report issues, and just quit.
EDIT: dpupbw64save-2024-06-25-basic-02, which this is about, I think, as I see from your screenshot here: viewtopic.php?p=127413#p127413,
it has the same time 'stamp' as dpupbw64save-2024-06-25-basic . (don't know if that has anything to do with the problem though)
@Governor
If you look at the output of du posted above you will see that your nvme0n1p5 partition is 94% used. That doesn't give you much space to save. That maybe the source of the device full error if that's the one with bookworm on it. Try moving some stuff to another partition.
@Governor :-
Getting back to the serious stuff now, let me ask you a question (you may have stated this elsewhere in other posts/threads, but I've not been following the saga right from the beginning and in all honesty I'm completely lost in the sea of problems you've been reporting).
Picking up on p310don's comment above:-
p310don wrote: ↑Mon Jul 29, 2024 12:20 pmYour savefile's full. Delete some stuff out of it, or move stuff out of it, or increase the size of it.
If you're using Firefox, move the ~/.mozilla folder outside of the save file, and then create a symlink back to it. Saves heaps of lost space in a save file.
.....do you only have the one internal drive in your system? In other words, is absolutely everything on it.....OS, applications, software, personal data (downloaded items, music, images, videos, whatever).....the LOT?
You surely must be as aware as anyone that drives have a finite mount of space on them. Save-files, too, utilise a fixed amount of space (you can easily make 'em bigger; making them smaller is way more problematic). Save-FOLDERS will expand/contract automatically depending on content.....but even these can only expand as far as the available space on the drive will permit.
It's standard practice these days across platforms (doesn't matter if it's Windows, MacOS, Linux, BSD.....whatever; everybody agrees on this point) to keep as much of your personal data as possible on some form of connected external drive. Doesn't matter what; HDD, SSD, large-capacity flash drive (I use a 512 GB USB 3.2-gen SanDisk flash-drive as an 'external' on the old D630 Latitude; works a treat!) Even if the OS goes into meltdown, your personal stuff remains safe.
Your personal data is the product of your own efforts; it makes sense to 'safeguard' this where possible.....and multimedia - videos in particular - can quickly gobble up heaps of space. The other item that rapidly balloons is browser 'cache'.....which is where the 'portable' browsers are an advantage (but I think you're aware of this point by now).
Mike.
According to df
/ (the "root" of the file system)
is a tmpfs file system mounted on /initrd/mnt/tmpfs
and you seem to have a save folder in /initrd/mnt/dev_save/
so you can copy the files in your writable layer (in ram)
by clicking the save icon and
optionally when Puppy shuts down.
So the working writable area seems to be in ram
and seems to be 7.5G of ram
it says about 5% is used.
Puppy usually allows the tmpfs to use up to 50% of ram,
so you probably have 16G of ram in your machine.
That seems like enough ram for most purposes.
It's possible that the tmpfs is being remounted read-only.
That would cause the same symptoms as a full FS
The tmpfs may be getting full, and/or
the system and apps may be using too much space in ram,
posssible even with 16G.
I am not sure that writing the ram layer to the save folder
flushes the ram layer.
I suspect it copies the ram layer to the save folder
but does not free up any space in the ram tmpfs layer.
in which case, all you can do is reboot,
which can result in loss of data.
This should tell you what is taking up space in the tmpfs:
du -h /initrd/mnt/tmpfs/ | sort -hk1
fredx181 wrote: ↑Mon Jul 29, 2024 2:41 pmGovernor wrote: ↑Mon Jul 29, 2024 11:01 amIt is hard to believe for me too! IMO, it certainly and absolutely indicates that there are many issues with the OS.... so please don't blame the user.
Food for thought:
Perhaps the reason why you can't believe a user can have so many issues, is that those who experience many issues are not reporting them in this forum.
And also because users who have many issues simply drop the OS and try something else, and are not informing anyone.
I doubt many users would be as dedicated and determined as I am, considering the issues I encounter. Perhaps people ought to shake my hand and congratulate me for my commitment and perseverance.Yes, I'll shake your hand and congratulate you for your persistently testing of very, very complicated usage
Indeed, very often people don't report issues, and just quit.
EDIT: dpupbw64save-2024-06-25-basic-02, which this is about, I think, as I see from your screenshot here: viewtopic.php?p=127413#p127413,
it has the same time 'stamp' as dpupbw64save-2024-06-25-basic . (don't know if that has anything to do with the problem though)
The basic-02 is a duplicate copy of basic, and I have been using the 02 to boot with. I also wondered why they have the same timestamp, because I save the 02 I boot from regularly. The folder names are listed separately in the boot menu, so if that is somehow a problem, I don't know, but it does not seem like it should be.
Don't take life too seriously, you will never get out alive.
williams2 wrote: ↑Mon Jul 29, 2024 5:32 pmAccording to df
/ (the "root" of the file system)
is a tmpfs file system mounted on /initrd/mnt/tmpfsand you seem to have a save folder in /initrd/mnt/dev_save/
so you can copy the files in your writable layer (in ram)
by clicking the save icon and
optionally when Puppy shuts down.So the working writable area seems to be in ram
and seems to be 7.5G of ram
it says about 5% is used.
Puppy usually allows the tmpfs to use up to 50% of ram,
so you probably have 16G of ram in your machine.That seems like enough ram for most purposes.
It's possible that the tmpfs is being remounted read-only.
That would cause the same symptoms as a full FSThe tmpfs may be getting full, and/or
the system and apps may be using too much space in ram,
posssible even with 16G.I am not sure that writing the ram layer to the save folder
flushes the ram layer.
I suspect it copies the ram layer to the save folder
but does not free up any space in the ram tmpfs layer.
in which case, all you can do is reboot,
which can result in loss of data.This should tell you what is taking up space in the tmpfs:
du -h /initrd/mnt/tmpfs/ | sort -hk1
Wow, this looks suspicious. I see Firefox in the output, but Firefox is not running and not listed in Task Manager.
Code: Select all
# du -h /initrd/mnt/tmpfs/ | sort -hk1
0 /initrd/mnt/tmpfs/pup_rw/dev
0 /initrd/mnt/tmpfs/pup_rw/home/spot/Downloads
0 /initrd/mnt/tmpfs/pup_rw/initrd/mnt
0 /initrd/mnt/tmpfs/pup_rw/initrd/mnt/dev_save
0 /initrd/mnt/tmpfs/pup_rw/initrd/mnt/tmpfs
0 /initrd/mnt/tmpfs/pup_rw/initrd/pup_a
0 /initrd/mnt/tmpfs/pup_rw/initrd/pup_b
0 /initrd/mnt/tmpfs/pup_rw/initrd/pup_f
0 /initrd/mnt/tmpfs/pup_rw/initrd/pup_k
0 /initrd/mnt/tmpfs/pup_rw/initrd/pup_ro2
0 /initrd/mnt/tmpfs/pup_rw/initrd/pup_z
0 /initrd/mnt/tmpfs/pup_rw/mnt
0 /initrd/mnt/tmpfs/pup_rw/mnt/nvme0n1p4
0 /initrd/mnt/tmpfs/pup_rw/mnt/nvme0n1p5
0 /initrd/mnt/tmpfs/pup_rw/mnt/nvme0n1p6
0 /initrd/mnt/tmpfs/pup_rw/mnt/sda1
0 /initrd/mnt/tmpfs/pup_rw/mnt/sdd1
0 /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/updates
0 /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/updates/downloading
0 /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updates/downloading
0 /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/cache2/doomed
0 /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting/glean/tmp
0 /initrd/mnt/tmpfs/pup_rw/run/dhcpcd/hook-state/timesyncd
0 /initrd/mnt/tmpfs/pup_rw/run/pipewire
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f10
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f11
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f12
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f13
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f14
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f15
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f16
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f17
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f18
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f19
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f20
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f21
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f22
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f23
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f24
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f25
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f26
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f28
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f7
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f8
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-diskseq\x2f9
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fata-ST1000LM024_HN-M101MBB_S2SMJ9GD603839
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fata-ST1000LM024_HN-M101MBB_S2SMJ9GD603839-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-eui.044a50111199ad51
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-eui.044a50111199ad51-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-eui.044a50111199ad51-part2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-eui.044a50111199ad51-part3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-eui.044a50111199ad51-part4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-eui.044a50111199ad51-part5
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-eui.044a50111199ad51-part6
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4_1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4_1-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4_1-part2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4_1-part3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4_1-part4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4_1-part5
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4_1-part6
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4-part2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4-part3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4-part4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4-part5
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fnvme-UMIS_RPJTJ512MEE1OWX_SS0W76184Z1CH11L0TB4-part6
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fusb-ASMT_2105_3170000000000000412B-0:0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fusb-ASMT_2105_3170000000000000412B-0:0-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fusb-Samsung_PSSD_T7_S6WZNS0W708027E-0:0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fusb-Samsung_PSSD_T7_S6WZNS0W708027E-0:0-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fusb-TOSHIBA_External_USB_3.0_20180114010812F-0:0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fusb-TOSHIBA_External_USB_3.0_20180114010812F-0:0-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fusb-TOSHIBA_External_USB_3.0_20180114010812F-0:0-part2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fwwn-0x50004cf20a8a0d26
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-id\x2fwwn-0x50004cf20a8a0d26-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fc-drv+I-bak
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fMAIN_USB
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fNVME1_FAT32
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fnvme2_ext3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fnvme3_ext3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fnvme4_ext4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fnvme5_ext4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fnvme6_ext3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fT7
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-label\x2fWin+Linux_bak
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partlabel\x2fnvme1_fat32
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partlabel\x2fnvme2_ext3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partlabel\x2fnvme3_ext3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partlabel\x2fnvme4_ext4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partlabel\x2fnvme5_ext4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partlabel\x2fnvme6_ext3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2f0325422a-00fd-4c7e-a04c-6d8762622dd2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2f385429a0-db55-4ce2-a8b9-88650005821f
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2f8a791e82-a418-40ed-8e44-bddbb957a440
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2fb4871312-01
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2fb4871312-02
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2fb6d29dd8-b4e8-494d-9c93-67f6b7c99557
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2fe64ee91d-a089-4142-ac88-f24dc8e105b2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2fe9b97f54-0ba4-4ff9-9e06-730900b8f08b
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2fea6d421c-01
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-partuuid\x2fed86c620-01
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:01:00.0-nvme-1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:01:00.0-nvme-1-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:01:00.0-nvme-1-part2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:01:00.0-nvme-1-part3
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:01:00.0-nvme-1-part4
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:01:00.0-nvme-1-part5
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:01:00.0-nvme-1-part6
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.2:1.0-scsi-0:0:0:0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.2:1.0-scsi-0:0:0:0-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.3:1.0-scsi-0:0:0:0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.3:1.0-scsi-0:0:0:0-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.4.1:1.0-scsi-0:0:0:0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.4.1:1.0-scsi-0:0:0:0-part1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.4.1:1.0-scsi-0:0:0:0-part2
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2f0444-3DB8
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2f0840718640717B70
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2f18E1-1E2B
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2f52d8efaf-bdf6-4281-aeea-871217161d5c
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2f774e807b-c247-4c3f-8181-164459de7173
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2f96415f7e-7b92-43fd-9f57-fcf09523fb6e
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2fb242c9da-fe12-440c-9ba8-10b581c2fe61
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2fb4db67d6-077d-422e-8cac-99b8f8008ead
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2fF00F-1D48
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/disk\x2fby-uuid\x2fF67A373A7A36F6C9
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/dri\x2fby-path\x2fpci-0000:02:00.0-card
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/dri\x2fby-path\x2fpci-0000:02:00.0-render
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-id\x2fusb-275d_USB_OPTICAL_MOUSE-event-mouse
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-id\x2fusb-275d_USB_OPTICAL_MOUSE-mouse
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-id\x2fusb-Chicony_Electronics_Co._Ltd._Integrated_Camera_0x0001-event-if00
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-id\x2fusb-SEMICO_Gaming_Keyboard-event-if01
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-id\x2fusb-SEMICO_Gaming_Keyboard-event-kbd
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-id\x2fusb-SEMICO_Gaming_Keyboard-if01-event-kbd
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fpci-0000:00:14.3-platform-VPC2004:00-event
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fpci-0000:02:00.3-usb-0:2:1.0-event-mouse
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fpci-0000:02:00.3-usb-0:2:1.0-mouse
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.4.3.1:1.0-event-kbd
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.4.3.1:1.1-event
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fpci-0000:02:00.3-usb-0:3.4.3.1:1.1-event-kbd
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fpci-0000:02:00.4-usb-0:1.1:1.0-event
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fplatform-AMDI0010:00-event-mouse
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fplatform-AMDI0010:00-mouse
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fplatform-i8042-serio-0-event-kbd
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/input\x2fby-path\x2fplatform-pcspkr-event-spkr
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/rtc
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/snd\x2fby-path\x2fpci-0000:02:00.1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/snd\x2fby-path\x2fpci-0000:02:00.6
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/v4l\x2fby-id\x2fusb-Chicony_Electronics_Co._Ltd._Integrated_Camera_0x0001-video-index0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/v4l\x2fby-id\x2fusb-Chicony_Electronics_Co._Ltd._Integrated_Camera_0x0001-video-index1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/v4l\x2fby-path\x2fpci-0000:02:00.4-usb-0:1.1:1.0-video-index0
0 /initrd/mnt/tmpfs/pup_rw/run/udev/links/v4l\x2fby-path\x2fpci-0000:02:00.4-usb-0:1.1:1.0-video-index1
0 /initrd/mnt/tmpfs/pup_rw/run/udev/tags
0 /initrd/mnt/tmpfs/pup_rw/run/udev/tags/power-switch
0 /initrd/mnt/tmpfs/pup_rw/run/udev/watch
0 /initrd/mnt/tmpfs/pup_rw/sys
0 /initrd/mnt/tmpfs/pup_rw/var/lib/xkb
0 /initrd/mnt/tmpfs/pup_rw/var/local
0 /initrd/mnt/tmpfs/pup_rw/var/local/shared
0 /initrd/mnt/tmpfs/pup_rw/var/run/cups
0 /initrd/mnt/tmpfs/pup_rw/var/tmp
0 /initrd/mnt/tmpfs/pup_work
0 /initrd/mnt/tmpfs/pup_work/work
0 /initrd/mnt/tmpfs/tmp/.ICE-unix
0 /initrd/mnt/tmpfs/tmp/palemoon_root
0 /initrd/mnt/tmpfs/tmp/pup_event_backend
0 /initrd/mnt/tmpfs/tmp/runtime-root/dbus-1
0 /initrd/mnt/tmpfs/tmp/runtime-root/dbus-1/services
0 /initrd/mnt/tmpfs/tmp/runtime-root/doc
0 /initrd/mnt/tmpfs/tmp/runtime-root/doc/by-app
0 /initrd/mnt/tmpfs/tmp/runtime-root/geany
0 /initrd/mnt/tmpfs/tmp/runtime-spot/dbus-1
0 /initrd/mnt/tmpfs/tmp/runtime-spot/dbus-1/services
0 /initrd/mnt/tmpfs/tmp/.X11-unix
4.0K /initrd/mnt/tmpfs/pup_rw/etc/modprobe.d
4.0K /initrd/mnt/tmpfs/pup_rw/home/spot/.config/pulse
4.0K /initrd/mnt/tmpfs/pup_rw/home/spot/.config/vlc
4.0K /initrd/mnt/tmpfs/pup_rw/home/spot/.dbus
4.0K /initrd/mnt/tmpfs/pup_rw/home/spot/.dbus/session-bus
4.0K /initrd/mnt/tmpfs/pup_rw/home/spot/.local/share
4.0K /initrd/mnt/tmpfs/pup_rw/home/spot/.local/share/vlc
4.0K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/defaults
4.0K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/defaults/pref
4.0K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/icons
4.0K /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache/13
4.0K /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache/51
4.0K /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache/95
4.0K /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache/a2
4.0K /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache/c4
4.0K /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache/d4
4.0K /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache/dc
4.0K /initrd/mnt/tmpfs/pup_rw/root/Choices
4.0K /initrd/mnt/tmpfs/pup_rw/root/Choices/ROX-Filer
4.0K /initrd/mnt/tmpfs/pup_rw/root/.config/gtk-2.0
4.0K /initrd/mnt/tmpfs/pup_rw/root/.config/smplayer/file_settings/3
4.0K /initrd/mnt/tmpfs/pup_rw/root/.config/smplayer/file_settings/4
4.0K /initrd/mnt/tmpfs/pup_rw/root/.config/smplayer/file_settings/d
4.0K /initrd/mnt/tmpfs/pup_rw/root/.dbus
4.0K /initrd/mnt/tmpfs/pup_rw/root/.dbus/session-bus
4.0K /initrd/mnt/tmpfs/pup_rw/root/.local/share/parcellite
4.0K /initrd/mnt/tmpfs/pup_rw/run/cups/certs
4.0K /initrd/mnt/tmpfs/pup_rw/run/systemd
4.0K /initrd/mnt/tmpfs/pup_rw/run/systemd/timesyncd.conf.d
4.0K /initrd/mnt/tmpfs/pup_rw/usr/lib/x86_64-linux-gnu
4.0K /initrd/mnt/tmpfs/pup_rw/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0
4.0K /initrd/mnt/tmpfs/pup_rw/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0
4.0K /initrd/mnt/tmpfs/pup_rw/var/lib/dbus
4.0K /initrd/mnt/tmpfs/pup_rw/var/run/dbus
4.0K /initrd/mnt/tmpfs/pup_rw/var/run/nscd
4.0K /initrd/mnt/tmpfs/tmp/runtime-root
4.0K /initrd/mnt/tmpfs/tmp/runtime-root/dconf
4.0K /initrd/mnt/tmpfs/tmp/runtime-spot/pulse
4.0K /initrd/mnt/tmpfs/tmp/simple_network_setup/udevmodulelist
8.0K /initrd/mnt/tmpfs/pup_rw/etc/rc.d
8.0K /initrd/mnt/tmpfs/pup_rw/home/spot/.config
8.0K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting/glean/events
8.0K /initrd/mnt/tmpfs/pup_rw/root/.config/rox.sourceforge.net
8.0K /initrd/mnt/tmpfs/pup_rw/root/.config/rox.sourceforge.net/ROX-Filer
8.0K /initrd/mnt/tmpfs/pup_rw/root/.config/smplayer/file_settings/6
8.0K /initrd/mnt/tmpfs/pup_rw/root/.config/viewnior
8.0K /initrd/mnt/tmpfs/pup_rw/run/cups
8.0K /initrd/mnt/tmpfs/pup_rw/var/lib/dhcpcd
8.0K /initrd/mnt/tmpfs/pup_rw/var/run
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_nvme0n1
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_nvme0n1p1
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_nvme0n1p2
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_nvme0n1p3
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_nvme0n1p4
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_nvme0n1p5
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_nvme0n1p6
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_sda
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_sda1
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_sdb
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_sdb1
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_sdc
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_sdc1
8.0K /initrd/mnt/tmpfs/tmp/pup_event_frontend/drive_sdc2
8.0K /initrd/mnt/tmpfs/tmp/runtime-spot
8.0K /initrd/mnt/tmpfs/tmp/simple_network_setup
12K /initrd/mnt/tmpfs/pup_rw/home/spot/.local/state
12K /initrd/mnt/tmpfs/pup_rw/home/spot/.local/state/wireplumber
12K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/cache2/trash2079721747
12K /initrd/mnt/tmpfs/pup_rw/root/.config/geany
12K /initrd/mnt/tmpfs/pup_rw/run/dhcpcd/hook-state
12K /initrd/mnt/tmpfs/pup_rw/run/dhcpcd/hook-state/resolv.conf
12K /initrd/mnt/tmpfs/pup_rw/var/lock
12K /initrd/mnt/tmpfs/tmp/services
16K /initrd/mnt/tmpfs/pup_rw/home/spot/.local
16K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting/glean/db
16K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/sessionstore-backups
16K /initrd/mnt/tmpfs/pup_rw/run/dhcpcd
20K /initrd/mnt/tmpfs/pup_rw/root/.config/smplayer/file_settings
20K /initrd/mnt/tmpfs/pup_rw/usr/lib/consolefonts
24K /initrd/mnt/tmpfs/pup_rw/usr/lib
28K /initrd/mnt/tmpfs/pup_rw/home
28K /initrd/mnt/tmpfs/pup_rw/home/spot
32K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting/archived
32K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting/archived/2024-07
32K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting/glean/pending_pings
36K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/browser/chrome
36K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/browser/chrome/icons
36K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/browser/chrome/icons/default
36K /initrd/mnt/tmpfs/pup_rw/usr/bin
40K /initrd/mnt/tmpfs/pup_rw/etc
56K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting/glean
60K /initrd/mnt/tmpfs/pup_rw/usr
64K /initrd/mnt/tmpfs/pup_rw/initrd/sbin
68K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/saved-telemetry-pings
92K /initrd/mnt/tmpfs/pup_rw/initrd/tmp
92K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/datareporting
96K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/cache2/entries
104K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/gmp-clearkey
104K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/gmp-clearkey/0.1
104K /initrd/mnt/tmpfs/pup_rw/root/.local
104K /initrd/mnt/tmpfs/pup_rw/root/.local/share
104K /initrd/mnt/tmpfs/pup_rw/var/log/cups
108K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/cache2
112K /initrd/mnt/tmpfs/tmp/pup_event_frontend
116K /initrd/mnt/tmpfs/pup_rw/root/.config/smplayer
148K /initrd/mnt/tmpfs/pup_rw/root/.config
192K /initrd/mnt/tmpfs/tmp/apps
192K /initrd/mnt/tmpfs/tmp/apps/pmount
232K /initrd/mnt/tmpfs/pup_rw/initrd
380K /initrd/mnt/tmpfs/pup_rw/var/log
500K /initrd/mnt/tmpfs/tmp
812K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/browser/features
920K /initrd/mnt/tmpfs/pup_rw/run/udev
920K /initrd/mnt/tmpfs/pup_rw/run/udev/data
948K /initrd/mnt/tmpfs/pup_rw/run
1000K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/storage/permanent
1000K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/storage/permanent/chrome
1000K /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/storage/permanent/chrome/idb
1.2M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/storage
1.3M /initrd/mnt/tmpfs/pup_rw/root/.cache
1.3M /initrd/mnt/tmpfs/pup_rw/root/.cache/mesa_shader_cache
1.5M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/fonts
9.8M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updates/0
9.9M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updates
12M /initrd/mnt/tmpfs/pup_rw/var
12M /initrd/mnt/tmpfs/pup_rw/var/lib
12M /initrd/mnt/tmpfs/pup_rw/var/lib/plocate
24M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile/startupCache
36M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/profile
42M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated/browser
56M /initrd/mnt/tmpfs/pup_rw/root/.thumbnails
56M /initrd/mnt/tmpfs/pup_rw/root/.thumbnails/normal
58M /initrd/mnt/tmpfs/pup_rw/root
238M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64/updated
248M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64/firefox64
283M /initrd/mnt/tmpfs/pup_rw/opt
283M /initrd/mnt/tmpfs/pup_rw/opt/FirefoxESR-portable64
353M /initrd/mnt/tmpfs/pup_rw
354M /initrd/mnt/tmpfs/
#
Code: Select all
# free
total used free shared buff/cache available
Mem: 10044184 2191032 3231360 386660 5321528 7853152
Swap: 9808772 512 9808260
#
Don't take life too seriously, you will never get out alive.
In my case I have a dedicated system drive partition with a dedicated sessions folder. During boot similar to @Governor I get it's list of save folders where I select one.
While using the system, over time, the cache expanded to fill the 30GB partition. AND ultimately the save expanded to fill the partition.
My PMEDIA=atahd at boot.
I assume responsibility as I have NOT moved the browser cache out of save session pathing. (several weeks of running on this test PC without rebooting)
After cache cleaning, the folder in use reduced back down to approx 600MB. 1st time lon this distro on this PC.
This is the example experience I have had.
Curious... I wonder if any distro has "cache collector" where all cache files are identified such that a user can concentrate them out of the session save and merely have links in the running system.
If so,it would reduce 'the cache hunt'.
The writable save layer is definitely the ram tmpfs.
The error message is "out of space"
not "read only FS"
The tmpfs is using 354M, which is quite reasonable.
Firefox Portable is unzipped in ram,
whether it's running or not.
Firefox is taking about 283M, most of what is in tmpfs.
I don't know where Bookworm puts the sfs files.
They are not in tmpfs, unless you booted nocopy.
This is similar to viewtopic.php?t=11819
who also uses the same mode (pupmode 13 ?)
I'm not sure pupmode 13 is always stable.
The data shows it running normally.
Until no space left.
If a file is deleted while it is in use,
the file name will be deleted,
but the file will still be taking up space,
it will just be invisible.
Such an orphaned inode is usually fixed by rebooting and doing a fsck.
After reading the thread you linked to above, I see you mentioned earlyoom.
If I recall. earlyoom cured a situation I had a few years back by closing the browser before things slowed down too much.
I was wondering if earlyoom could could be utilized in the situation described by the OP in order to prevent the need for a hard shutdown?
(I have not utilized earlyoom recently as my browser cache is cleared regularly and I do not experience slowdowns as I did earlier)