Hi all,
I have run a file server (mdk 9.2) as a test. It has used samba to share a public directory with XPee and other linux clients and worked flawlessly with ext3. Then a "power failure" "occured" , the public subdirectory structure was not damaged, but all the files _in_ each directory were gone. (as far as I can tell, nothing happened to the system itself which was running on the very same hard disk) This is strange, isn't it? Is there something I should have done to prevent that? I thought ext3 doesn't "mind" a power failure ... or did samba cause this problem...?

Someone got an idea?

Regards
Blaumieser

Well, ext3 "minds" powerfailures a bit. The journal makes it possible to avoid filesystem corruption most of the time. But the only files that would be affected, if any, would be files that were being written to at the time of the powerfailure. Losing ALL your files is incredibly unlikely, though not impossible. Try running fsck with the option for journal recovery?

you might want to check the 'lost+found' directory in the root of that particular mount point

Hi again,
thanks for the hints. There wasn't even a lost+found directory. I performed a fsck and got a "no problems" answer. So I tried e2fsck -f /dev/hda1 and a lost+found directory was created but nothing was put into it. Furthermore, e2fsck didn't find anything suspicious. I'm not sure about your hint

"Try running fsck with the option for journal recovery"

When I "man fsck.ext3" I only find an option for using an external journal. Did I miss something there?

Greets
BM