Thanks for both of your responses.
Sorry for the non-threaded post, but I'm e-mailing from somewhere else.
@ Mogens Kjaer
I have tried this already
@ William L. Maltby
I have looked everywhere on the drive using programs such as 'find'. I have ran:
$ find / -iname "*.jpg" -or "*.JPG"
and the missing files are now listed.
I know enough to be able to find files. This is whats got me because I've never know an ext3 fs to do this; unless it's a bug with fuse-encfs.
On Sun, 2008-09-28 at 15:54 +0100, Stewart Williams wrote:
Thanks for both of your responses.
Sorry for the non-threaded post, but I'm e-mailing from somewhere else.
<snip>
@ William L. Maltby
I have looked everywhere on the drive using programs such as 'find'. I have ran:
$ find / -iname "*.jpg" -or "*.JPG"
Minor points that probably have no effect unless there's a *.jpg file in the current directory: use single, not double quotes, to avoid shell expansion. You want the asterisk to get passed into the find command as a parameter. Also, the "iname" says ignore case, so only one iteration is needed.
and the missing files are now listed.
Now or not?
I know enough to be able to find files. This is whats got me because I've never know an ext3 fs to do this; unless it's a bug with fuse-encfs.
This makes me think they are still *not* listed?
Last stab in the dark: any "undelete" capability on that file system? If the files are not found, I am guessing they have been deleted. Barring that facility, I hope you have a recent backup.
Good luck.
<snip sig stuff>
On Sun, Sep 28, 2008 at 1:50 PM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Sun, 2008-09-28 at 15:54 +0100, Stewart Williams wrote:
$ find / -iname "*.jpg" -or "*.JPG"
Minor points that probably have no effect unless there's a *.jpg file in the current directory: use single, not double quotes, to avoid shell expansion.
Not directly relevant to the subject of the thread, but double quotes are fine here. The only difference between single and double quotes is that shell variable references are expanded in the double quotes but not the single quotes. Glob patterns, whitespace, command separators, etc. are quoted in both cases.
On the original topic ... have you checked in /var/log for log file entries that might provide a clue to what happened?
It might be possible to recover the lost files from the ext3 journal:
William L. Maltby wrote:
...
and the missing files are now listed.
Now or not?
Not. Typo sorry.
...
Last stab in the dark: any "undelete" capability on that file system? If the files are not found, I am guessing they have been deleted. Barring that facility, I hope you have a recent backup.
Not as I am aware.
Hi,
On Sun, Sep 28, 2008 at 10:54, Stewart Williams lists@pinkyboots.co.uk wrote:
$ find / -iname "*.jpg" -or "*.JPG"
This syntax is invalid, this is what I get under CentOS 5:
# find / -iname "*.jpg" -or "*.JPG" find: paths must precede expression Usage: find [-H] [-L] [-P] [path...] [expression]
What you probably meant is find / -iname "*.jpg" -or -iname "*.JPG", but as it was already pointed out, -iname is case-insensitive, so all you need is: # find / -iname "*.jpg"
If you used the wrong command, maybe run it again?
unless it's a bug with fuse-encfs.
If you are using ext3 over fuse-encfs, if there is a problem with fuse-encfs it would bork your ext3 filesystem, but probably the end result would be a corrupted and unusable filesystem, not one with files missing. In any case, you might try to unmount it and run fsck over it to see if there is something wrong with it. If the filesystem got corrupted, by running fsck it might be able to find the missing files and save them under lost+found, it's a long shot, but if you tried everything else it might be worth trying.
HTH, Filipe
On Mon, Sep 29, 2008 at 12:12, Stephen Harris lists@spuddy.org wrote:
On Mon, Sep 29, 2008 at 11:54:23AM -0400, Filipe Brandenburger wrote:
# find / -iname "*.jpg"
Use '*.jpg' because otherwise shell expansion could happen and break things.
No it can't. Have you tried it?
Thank you for all of the suggestions. So far I have tried them all but still cannot fathom it out. The files have just disappeared and I don't know how or why.
I think all I can conclude is that they are gone for good.
On Tue, 2008-09-30 at 21:54 +0100, Stewart Williams wrote:
Thank you for all of the suggestions. So far I have tried them all but still cannot fathom it out. The files have just disappeared and I don't know how or why.
I think all I can conclude is that they are gone for good.
Last gasp: any chance of FS corruption? Maybe an fsck run will show some errors, corrections and put some goodies in lost+found?
<snip sig stuff>
HTH
William L. Maltby wrote:
On Tue, 2008-09-30 at 21:54 +0100, Stewart Williams wrote:
Thank you for all of the suggestions. So far I have tried them all but still cannot fathom it out. The files have just disappeared and I don't know how or why.
I think all I can conclude is that they are gone for good.
Last gasp: any chance of FS corruption? Maybe an fsck run will show some errors, corrections and put some goodies in lost+found?
<snip sig stuff>
HTH
Hi Williams
I have already tried this and gave no errors (even with fsck -f) and nothing appeared in lost+found.
Strange one.
Also that is odd, is when I drag anything to the Trash icon, and open it, there are no files. However when I use a terminal and look in ~/.Trash all deleted files are show.
Coincidence?
On Tue, Sep 30, 2008 at 2:15 PM, Stewart Williams lists@pinkyboots.co.uk wrote:
Also that is odd, is when I drag anything to the Trash icon, and open it, there are no files. However when I use a terminal and look in ~/.Trash all deleted files are show.
This could be a synchronization issue, but I have another thought about your missing files.
What file systems do you have mounted? Is there any chance that your files got moved to a mount point that is now hiding any files that are actually located under it? Try unmounting any file system you don't need and see what's there underneath.
It's probably not the case, but it doesn't hurt to look.
mhr
MHR wrote:
On Tue, Sep 30, 2008 at 2:15 PM, Stewart Williams lists@pinkyboots.co.uk wrote:
Also that is odd, is when I drag anything to the Trash icon, and open it, there are no files. However when I use a terminal and look in ~/.Trash all deleted files are show.
This could be a synchronization issue, but I have another thought about your missing files.
What file systems do you have mounted? Is there any chance that your files got moved to a mount point that is now hiding any files that are actually located under it? Try unmounting any file system you don't need and see what's there underneath.
It's probably not the case, but it doesn't hurt to look.
mhr
Thanks, but I have tried already. The partition is an LVM volume, formatted and mounted as ext3. Then I have fuse-encfs mounted over that.
Stewart Williams wrote:
Also that is odd, is when I drag anything to the Trash icon, and open it, there are no files. However when I use a terminal and look in ~/.Trash all deleted files are show.
Coincidence?
Update: I've Found the problem with this, it's a bug[1] in gnome-vfs. The Trash doesn't work with FUSE file systems.
The version I have installed is:
gnome-vfs2-2.16.2-4.el5
I cannot find any updates, so I don't know if it's been fixed with this Gnome version.
-
Bart Schaefer -
Filipe Brandenburger -
MHR -
Stephen Harris -
Stewart Williams -
William L. Maltby