Pádraig Brady wrote: > bs=0 > ws=4095: printf: write error > ws=4096: printf: write error > ws=4097: printf: write error > bs=4096 > ws=4095: printf: write error: No space left on device > ws=4096: printf: write error > ws=4097: printf: write error > bs=8192 > ws=4095: printf: write error: No space left on device > ws=4096: printf: write error: No space left on device > ws=4097: printf: write error: No space left on device
Yep. There are cases where the errno value gets lost (due to the ISO C standard, and even in glibc the errno value gets lost in such cases). For the user, both messages are nearly equivalent, since a full disk is the most likely reason for a write error. > It might be appropriate instead to just not look for the specific ENOSPC > error. +1 Bruno
