Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#48698 - pacman -S package fails when arch linux is booted on ramfs
Attached to Project:
Pacman
Opened by Marty Plummer (ntzrmtthihu777) - Saturday, 26 March 2016, 08:36 GMT
Last edited by Allan McRae (Allan) - Monday, 28 March 2016, 06:30 GMT
Opened by Marty Plummer (ntzrmtthihu777) - Saturday, 26 March 2016, 08:36 GMT
Last edited by Allan McRae (Allan) - Monday, 28 March 2016, 06:30 GMT
|
DetailsSummary and Info:
So, I've been playing with the idea of running arch linux in ram, syncing to disk on shutdown, and I've encountered a problem error: Partition / too full: x blocks needed, 0 blocks free error: failed to commit transaction (not enough free disk space) Errors occurred, no packages were upgraded Steps to Reproduce: Install arch linux in such a manner as to boot into a ramdisk as /, attempt to install package |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 28 March 2016, 06:30 GMT
Reason for closing: Not a bug
Additional comments about closing: ramfs do not have blocks needed to judge space usage unless generated with brd module.
Monday, 28 March 2016, 06:30 GMT
Reason for closing: Not a bug
Additional comments about closing: ramfs do not have blocks needed to judge space usage unless generated with brd module.
Meaning, one mounted with `mount -t ramfs none -o size=2G /mnt' or the like?
Protip: use the brd kernel module to create a /dev/ram0 block device with the size you want, this avoids the issue I had here.