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
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary 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.
Comment by Allan McRae (Allan) - Saturday, 26 March 2016, 09:03 GMT
Turn off CheckSpace.
Comment by Marty Plummer (ntzrmtthihu777) - Saturday, 26 March 2016, 09:21 GMT
Oh yeah, that should work, but is there not a way to check the space on a ramdisk?
Meaning, one mounted with `mount -t ramfs none -o size=2G /mnt' or the like?
Comment by Allan McRae (Allan) - Saturday, 26 March 2016, 09:24 GMT
Not that I know of. If you have a ramfs in /mnt and run "df /mnt" you get no information.
Comment by Marty Plummer (ntzrmtthihu777) - Saturday, 26 March 2016, 11:34 GMT
Ah. Either way, I've figured a better way of going about it, so I'll explain here for anyone else looking at this and close
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.

Loading...