| View previous topic :: View next topic |
| Author |
Message |
devsk
Advocate
Joined: 24 Oct 2003
Posts: 3003
Location: Bay Area, CA
|
 Posted: Mon May 26, 2008 12:25 am Post subject: Can someone explain this? Is this a filesystem corruptioN? |
 |
|
I seem to be able to "see" some files but not quite vi them. The timestamp is same as the file with bz2 extension but the name is different. I have unmounted the portage directory and fsck'ed the partition (ext3) and it still shows like this. Any idea what's up?
| Code: | 17:14:30 root@localhost /usr/portage/local/log
# /bin/ls -al *log|tail -5
-rw-r--r-- 1 root portage 84 May 21 23:00 x11-misc:xdg-utils-1.0.2-r2:20080522-060027.log
-rw-r--r-- 1 root portage 215 Apr 18 21:23 x11-themes:gnome-icon-theme-2.22.0:20080419-042304.log
-rw-r--r-- 1 root portage 215 Apr 18 21:22 x11-themes:gnome-themes-2.22.0:20080419-042247.log
-rw-r--r-- 1 root portage 215 Apr 18 21:02 x11-themes:gtk-engines-2.14.1:20080419-040201.log
-rw-r--r-- 1 root portage 215 Apr 18 21:31 x11-wm:metacity-2.22.0:20080419-043110.log
17:14:48 root@localhost /usr/portage/local/log
# ls -al x11-wm:metacity-2.22.0:20080419-043110.log
/bin/ls: cannot access x11-wm:metacity-2.22.0:20080419-043110.log: No such file or directory
17:14:58 root@localhost /usr/portage/local/log
# ls -al x11-wm\:metacity-2.22.0\:20080419-043110.log
/bin/ls: cannot access x11-wm:metacity-2.22.0:20080419-043110.log: No such file or directory
17:15:04 root@localhost /usr/portage/local/log
# ls -al x11-wm:metacity-2.22.0:20080419-043110.log*
/bin/ls: cannot access x11-wm:metacity-2.22.0:20080419-043110.log*: No such file or directory
17:15:11 root@localhost /usr/portage/local/log
# ls -al x11-wm:metacity-2.22.0:200*
-rw-rw---- 1 portage portage 13293 Apr 18 21:31 x11-wm:metacity-2.22.0:20080419-042925.log.bz2
-rw-rw---- 1 portage portage 13047 May 10 14:31 x11-wm:metacity-2.22.0:20080510-212932.log.bz2
17:15:17 root@localhost /usr/portage/local/log
# file x11-wm:metacity-2.22.0:20080419-043110.log
x11-wm:metacity-2.22.0:20080419-043110.log: cannot open `x11-wm:metacity-2.22.0:20080419-043110.log' (No such file or directory)
17:16:22 root@localhost /usr/portage/local/log
# file x11-wm:metacity-2.22.0:20080510-212932.log.bz2
x11-wm:metacity-2.22.0:20080510-212932.log.bz2: bzip2 compressed data, block size = 900k
|
amd64 with 2.6.25.4, root partition is ext3 and portage is ext3 as well.
No errors in dmesg. |
|
| Back to top |
|
 |
Wormo
Retired Dev
Joined: 29 Nov 2004
Posts: 526
Location: SB County California
|
| Posted: Mon May 26, 2008 1:39 am Post subject: |
|
|
The weird thing is that 'ls' seems able to find these files in the first instance where you use wildcard but not otherwise...
What happens if you try something like this
| Code: |
cp /usr/portage/local/log/x11-wm*log /tmp
|
P.S. how is your courageous pet hamster Boo doing? |
|
| Back to top |
|
|
SeaTiger
l33t
Joined: 22 Nov 2007
Posts: 603
Location: Toronto, Ontario, Canada
|
| Posted: Mon May 26, 2008 4:53 am Post subject: |
|
|
Try following: | Code: | | vi /usr/portage/local/log/x11-misc{TAB} |
{TAB} <--- Press [TAB] on your keyboard. |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 3003
Location: Bay Area, CA
|
| Posted: Mon May 26, 2008 8:24 am Post subject: Solved... :( |
|
|
| I kinda feel stupid now. There is a directory elog in /usr/portage/local/log. When I say '/bin/ls -al *log', the files in that dir also get listed. elog files are much smaller in size and with a different pid. |
|
| Back to top |
|
|
|
Kernel & Hardware
