Files and directories showing in CLI but not in GUI

On 5/13/12, Camaleón wrote:

On Sat, 12 May 2012 23:43:43 +0000, Marc Shapiro wrote:

(...)

Document file 'xxxxx.xxx' is locked for editing by: xxx
( 06.05.2012 15:49)
Open the document read-only or open a copy of the document for editing.

The x's above were the file name that I was trying to open and my login
on the old system. If I select Open Read-Only the file opens right up.
Other files open without the warning. I probably had that particular
file open when the system went wonky (it is almost always open) and that
is the reason for the warning dialog.

Run "mount" and put here the output.

$ mount
aufs on / type aufs (rw)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode55)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode55)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,modeb0)
/dev/sr0 on /live/image type iso9660 (ro,noatime)
tmpfs on /live/cow type tmpfs (rw,noatime,modeu5)
tmpfs on /live type tmpfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
(rw,noexec,nosuid,nodev)
/dev/mapper/vg1-home on /mnt type ext3 (rw)

So my question is: Why do some of my files and directories show in GUI
apps, but not all of them, while all of them seem to show up just fine
from the command line?

By defaul, Nautilus does not show hidden directories (.my_dir) nor files
(.my_file), but I suppose this is not the problem here, right?

No. I wouldn't expect hidden files and directories to show. I don't
see a permissions problem, either. Here is a listing of the directory
showing only the non-hiddden sub-directories. I have also left in any
error lines that were generated. (Remember that this was an LVM
volume that was in a VG spread over three partitions, two of which
were on a dying disk and I did a pvmove to migrate all of the data to
the new drive. I believe that fsck does show errors on this
filesystem. Could that cause the GUI to not find files and
directories that the CLI can find?) I have marked the directories
that DO show up in Nautilus with an asterisk:

$ ls -all
ls: cannot access html: Input/output error
ls: cannot access .pdf: Input/output error
ls: cannot access The Lone Ranger Theme - William Tell Overture.mp3:
Input/output error
total 9528
drwxr-xr-x 112 user user 8192 May 7 05:28 .
drwxr-xr-x 7 root root 4096 Dec 4 19:06 ..
drwxr-xr-x 3 user user 4096 Oct 7 2010 accordion-menus_files
drwxr-xr-x 10 user user 4096 Jun 11 2009 bf
drwxr-xr-x 2 user user 4096 May 3 04:13 bin
drwxr-xr-x 8 user user 4096 Dec 2 2009 blackfin
drwxr-xr-x 3 user user 4096 Dec 20 2008 citrix.ICAClient *
drwxr-xr-x 3 user user 4096 May 30 2011 Desktop
drwxr-xr-x 2 user user 4096 Jun 13 2011 dwhelper *
drwxr-xr-x 2 user user 4096 Aug 16 2007 gotmail *
d????????? ? ? ? ? ? html
drwxr-xr-x 8 user user 4096 Sep 26 2011 images
drwx 2 user user 4096 Sep 25 2011 mail *
drwxr-xr-x 3 user user 4096 Jan 27 2010 mc
drwxr-xr-x 4 user user 4096 May 7 2011 music
drwxr-xr-x 17 user user 8192 May 12 16:35 MyDocs
drwxr-xr-x 5 user user 4096 Feb 8 2010 nls
drwxr-xr-x 2 user user 4096 Dec 5 2006 omer
-????????? ? ? ? ? ? .pdf
drwxr-xr-x 9 user user 4096 Jun 21 2010 Projects *
drwxr-xr-x 3 user user 4096 May 22 2011 public_html
-????????? ? ? ? ? ? The Lone Ranger Theme -
William Tell Overture.mp3
drwxr-xr-x 2 user user 4096 May 7 2011 tmp *
drwxr-xr-x 2 user user 4096 Dec 16 06:22 VirtualBoxDisks
drwxr-xr-x 2 user user 4096 Dec 16 06:49 VirtualBox VMs
lrwxrwxrwx 1 user user 8 Oct 8 2006 .Xsession -> .xinitrc

I count 14 directories that DO NOT show up in Nautilus and 6 that DO.

I have not yet checked if there are any FILES that are not showing up,
but I am hoping that whatever gets the directories to show would work
on files, as well.

1/ Copy the whole disk content data into another device/volume/hard disk
2/ Check the copied data is okay and all the files opens fine from
different systems
3/ Then run the disk manufacturer's verification utilities to ensure the
hard disk is still in good shape and thus, usuable
4/ Format the disk and create the required partitions
5/ Copy back the data
6/ Have a cup of coffee/tea while remember yourself for the needing of
doing regular backups :-)

I will start copying and testing as soon as I actually get enough free time.

Thanks.


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Archive: http://lists.debian.org/

On 05/13/2012 12:43 PM, Marc Shapiro wrote:

d????????? ? ? ? ? ? html

That kind of line is a pretty good sign that your filesystem has errors.
I don't know why it would prevent other directories from appearing in a
GUI, but I wouldn't bother right now. Umount the filesystem, make a copy
of it if you have space (or copy what you can, but mount it readonly),
and fsck it.



There's nothing in the middle of the road but yellow stripes and dead
armadillos.

Eduardo M KALINOWSKI



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Archive: http://lists.debian.org/

On Sun, 13 May 2012 15:43:50 +0000, Marc Shapiro wrote:

On 5/13/12, Camaleón wrote:

Run "mount" and put here the output.

$ mount
aufs on / type aufs (rw)

(...)

Are you still running from a LiveCD media? If yes, why? :-?

/dev/mapper/vg1-home on /mnt type ext3 (rw)

That has to be the damaged volume. Was it added automatically by the
system or is that you manually mounted?

By defaul, Nautilus does not show hidden directories (.my_dir) nor
files (.my_file), but I suppose this is not the problem here, right?

No. I wouldn't expect hidden files and directories to show. I don't
see a permissions problem, either.

Yes, I also think so, I mean, that permissions have no direct relation
with the problem.

Here is a listing of the directory showing only the non-hiddden sub
-directories. I have also left in any error lines that were
generated. (Remember that this was an LVM volume that was in a VG
spread over three partitions, two of which were on a dying disk and I
did a pvmove to migrate all of the data to the new drive. I believe
that fsck does show errors on this filesystem. Could that cause the
GUI to not find files and directories that the CLI can find?)

(...)

Yes, that can be the cause. A corrupted or severe damaged filesystem can
fool nautilus and prevent from files and folders to be displayed (and
even more if it was a part of spread LVM volume). Look, even "ls" is
having problems ("I/O errors") to show them.

You can, however, try with another file browser, just to compare with the
Nautilus output, but I think that would be irrelevant for the main
problem.

I count 14 directories that DO NOT show up in Nautilus and 6 that DO.

I have not yet checked if there are any FILES that are not showing up,
but I am hoping that whatever gets the directories to show would work on
files, as well.

(...)

I wouldn't bother about that now (given the status and history of the
data) and start from scratch should the hard disk present no hardware
problems.

Greetings,

Camaleón


To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Archive: http://lists.debian.org/joomvd$dun$