On Sun, 13 Dec 2009 19:57:51 -0800
Robert Miesen <[email protected]> dijo:

>According to the GNOME Nautilus user manual (
>http://library.gnome.org/users/user-guide/stable/gosnautilus-550.html.en), a
>red x by a file means that the user that owns the nautilus process doesn't
>have read permissions to the file.
>
>So having said that, this could indicate either a bug in GNOME Nautilus or
>an unclean filesystem. Have you run fsck.ext3 on the affected filesystem (be
>sure to specify the force check option...I think it is "-f")?

It's not a red X, it's a white X. Also, I told Nautilus to use List View
always. (I know how to read; icons are not necessary.) There is a small
icon next to the text entry, and that icon is what has the white X on it.

I can't find anything in the documentation to explain a white X, but if you
right-click on the file, and then on Properties > Emblems, a white X appears to
mean unreadable.

"Unreadable" suggests you may be right - a file system corruption. Heaven
knows, the Jaunty disk has been popped in and out of the Ultrabay a lot in the
past couple of weeks. So I unmounted it and ran fsck -f -v on it.
(Un)fortunately, there were no errors:

[r...@devil8 jjj]# umount /dev/sdb2
[r...@devil8 jjj]# fsck -f -v /dev/sdb2
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

  402595 inodes used (2.42%)
   14478 non-contiguous files (3.6%)
     636 non-contiguous directories (0.2%)
         # of inodes with ind/dind/tind blocks: 28966/1937/3
21751411 blocks used (65.51%)
       0 bad blocks
       5 large files

  325119 regular files
   41578 directories
     132 character device files
      26 block device files
      27 fifos
     502 links
   35689 symbolic links (32311 fast symbolic links)
      15 sockets
--------
  403088 files
[r...@devil8 jjj]# 

A corrupted filesystem would certainly explain the random invisible files. I
wonder if there is something stronger than fsck -f. But having said that,
Thunar had no problem with the "invisible" files. I wonder if I can install a
different terminal.

I'd go off to see if I can find a Gnome/Nautilus bugtracker, except that I get
the same strange results from the command line (gnome-terminal).

The more I investigate this the more haywire it seems.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to