playlist lost when disk is full after game is started
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
when the disk which contains the retroarch home dir and it's lpl database files is full, loading any game will result in a deleted playlist.
Expected behavior
after loading a game from a playlist, the playlist should stay available even when the disk is currently full.
Actual behavior
after selecting a game, retroarch seems to want to update the playlist file with "number of times played" or a similar information, and when the disk is full writing the file back fails, leaving it empty.
Steps to reproduce the bug
- put full mame rom set (zip in zip!) on the slow SD card in your raspberry pi
- scan the directory containing it
- come back to the pi 24 hours laters when retroarch has hopefully finished writing the MAME playlist.
- in a terminal, type:
dd if=/dev/zero of=$HOME/.config/retroarch/filler.dat bs=1M - start retroarch
- wait until dd task finishes when disk/SD card is full
- select a game in your mame playlist, run it
- quit the game and go back to your mame playlist - it is now empty!
alternative smaller steps to reproduce
- create a manual playlist with 1 game
- continue with point 4 above
Version/Commit
You can find this information under Information/System Information
- RetroArch: 1.19.1
Environment information
- OS: Linux/X11
- Compiler: not relevant
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure using the RetroArch playlist under ~/.config/retroarch and a full disk, then trace the playlist update performed after launching a game. Verify that a failed write does not leave the .lpl file empty, and repeat the reproduction steps to confirm the playlist remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- content
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100