Bug#542451: More info about the problematic directory

[Svante R Signell]

severity 542809 important

I would claim that severity is important, not normal. Nevertheless, it
can remain normal as long as anybody attends this problem. The directory
listing should not be empty in Nautilus (via gvfs). ls behaves as
expected, listing all entries except OldFiles/OldFiles, se below.

The problematic directory is part of our backup system: Oldfiles
contains the backup data (in addition to the whole home directory tree).
Of course the OldFiles/OldFiles directory cannot contain any data. This
would create a recursive dependency. 

Looking at exit codes ls and gvfs-ls give different results. Even if
gvfs-ls exit code is 0, an error is flagged, see last two entries. Seem
like it just exits instead of reporting the other directory entries.

Using ls:
ls -l .|grep OldFiles
drwxr-xr-x 89 srs imit     8192 2009-08-21 17:19 OldFiles
echo $?
0

ls -l OldFiles/|grep OldFiles
ls: cannot access OldFiles/OldFiles: No such device
??????????  ? ?   ?           ?                ? OldFiles
echo $?
1

ls -ld ./OldFiles/OldFiles
ls: cannot access ./OldFiles/OldFiles: No such device
echo $?
2

ls -l ./OldFiles/OldFiles 
ls: cannot access ./OldFiles/OldFiles: No such device
echo $?
2

Using gvfs-ls:
gvfs-ls -l .|grep OldFiles
OldFiles	8192	(directory)
echo $?
0

gvfs-ls -l ./OldFiles/
Error: Error stating file '/afs/.../srs/OldFiles/OldFiles': No such
device
echo $?
0

gvfs-ls -l ./OldFiles/OldFiles
Error: No such device
srs at s1499:~/afs_srs$ echo $?
0

For completeness exit codes for ls are given below (unknown for gvfs-ls,
since no manual page is available ...):
Exit status:
0      if OK,
1      if minor problems (e.g., cannot access subdirectory),
2      if serious trouble (e.g., cannot access command-line argument).