[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#189011: libc6: Change ENOSPC 28 to /* No space or inodes left on device */



On Mon:16:09, Ben Collins wrote:
> Kingsley wrote:
> > glibc currently returns errno 28, which is
> > defined as 
> > 
> > 	"No space left on device"
> > 
> > and is misleading. It should mention inodes.
> 
> Inodes are a specific term that does not apply
> to all cases where ENOSPC is used. What happens
> if ENOSPC starts to be returned when an A/V
> filesystem runs out of "media blocks", should we
> then change it to "No space, inodes or media
> blocks left on device"? Not likely. ENOSPC is
> not specific to filesystems either.

Good point.

Thanks.

In light of your considerable experience in these
matters, do you happen to have any thoughts on how
more helpful error messages could be provided to
newbie users? 

For example, is there a way that glibc could
report specifically whether it's disk space,
inodes or media blocks that have been exhausted?

Unique errnos???

Thanks,
Kingsley

> 
> At most, this is a FAQ.
> 
> -- Debian     - http://www.debian.org/ Linux
> 1394 - http://www.linux1394.org/ Subversion -
> http://subversion.tigris.org/ Deqo       -
> http://www.deqo.com/
> 
> This mail is probably spam.  The original
> message has been attached along with this
> report, so you can recognize or block similar
> unwanted mail in future.  See
> http://spamassassin.org/tag/ for more details.
> 
> Content preview:  > glibc currently returns
> errno 28, which is defined as
>   > > "No space left on device" > > and is
>   > > misleading. It should mention
>   inodes. Inodes are a specific term that does
>   not apply to all cases where ENOSPC is used.
>   What happens if ENOSPC starts to be returned
>   when an A/V filesystem runs out of "media
>   blocks", should we then change it to "No
>   space, inodes or media blocks left on device"?
>   Not likely.  ENOSPC is not specific to
>   filesystems either. [...] 
> 
> Content analysis details:   (-22.60 points, 5
> required) IN_REP_TO          (-3.2 points) Has a
> In-Reply-To header REFERENCES         (-6.5
> points) Has a valid-looking References header
> BAYES_01           (-6.6 points) BODY: Bayesian
> classifier says spam probability is 1 to 10%
> [score: 0.0181] USER_AGENT_MUTT    (-6.3 points)
> User-Agent header indicates a non-spam MUA
> (Mutt)

-- 




Reply to: