Bug#489917: jed: Opening a file fails with 'File XXX not readable.' on a large filesystem

Alter Ego alter at napiform.org
Thu Feb 5 09:58:46 UTC 2009


On Wed, Feb 04, 2009 at 02:22:43PM +0100, Jörg Sommer wrote:
> Hi Alter,
> 
> Alter Ego schrieb am Tue 08. Jul, 20:27 (+0300):
> > Package: jed
> > Version: 1:0.99.18+dfsg.1-10+b1
> > Severity: normal
> > 
> > 
> > Opening a file fails with 'File XXX not readable.' on a large filesystem
> > (tested on 16TB XFS filesystems using inode64).
> > 
> > unix.c/sys_chmod() returns -3 to file.c/file_status() with error "Value
> > too large for defined data type".
> > Compiling sys_chmod() with -D_FILE_OFFSET_BITS=64 stops it from happening.
> 
> Can you try if the same problem is present in the S‐Lang library? Can you
> install the package slsh and execute slsh. Then run
> 
> slsh> chmod("/file", 0644); errno_string(errno);
> 
> What's the output?
---
slsh version 0.8.2-0; S-Lang version: 2.1.3
Copyright (C) 2005-2007 John E. Davis <jed at jedsoft.org>
This is free software with ABSOLUTELY NO WARRANTY.

slsh> chmod("/opt/queue/run", 0644); errno_string(errno);
0
No such file or directory
---
Seems to work (chmod modifes the file and exits with success with errno
containing an old value).

What I don't think the bug report mentioned is that this is on a system
with a 64-bit kernel and 32-bit libraries. I haven't noticed the problem
on a couple of other systems with both 64-bit kernels and libraries, so
it might just be a case of an unsupported combination and PEBCAK ;)

> Thank's for your help.
> 
> Bye, Jörg.
> -- 
> Das Recht, seine Meinung zu wechseln, ist eines der wichtigsten
> menschlichen Privilegien.
> 	     		 			(Robert Peel)







More information about the Pkg-jed-devel mailing list