On 3/18/24 11:38, Peter Dyballa wrote:
Am 18.03.2024 um 18:57 schrieb Paul Eggert <egg...@cs.ucla.edu>:
What's up with that "No space left on device" message?
I'd say that this is a misinterpretation. Mac OS X was not able to create a new
subdirectory, so it said "No space left on device".
This sounds unlikely. There are lots of reasons a subdirectory cannot be
created (e.g., permissions problem), and whatever syscall failed, rm
surely used perror or strerror or whatever.
What happens if you run something like these shell commands with the
problematic directory? (You may need to be root.) I am interested in the
system call that occurred just before 'rm' outputs a diagnostic.
export LC_ALL=C
ktrace rm -rf confdir-14B---
kdump
If you can send me a programme that reads from /dev/null into some file until
the disk is full and then tries system calls like unlink() I'd test it at once.
I don't think that would help, as I don't think the file system was
actually full.
