Hey All, I have a serious and weird problem with my harddrive and ext3. About a week ago I re-arranged my entire directory structure. I moved, deleted, renamed files and dirs. I did some reboots and shutdowns in the mean time. And all was fine, up until now. At the moment I'm looking at the filesystem (onto which I made those changed last week) , but it seems I'm looking at the filesystem from a month ago ( june 20th). Now I have a couple of questions: - How could this have happened? - Is this a journaling problem? If so, how can I fix this and get the filesystem back from july 12th instead of looking at the filesystem how it was on june 20th. I did a fsck/e2fsck on the umounted devs and they can't get any cleaner. Regards, Iskandar -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20080713/5266d042/attachment.htm>
Iskandar Prins wrote:> Hey All, > > I have a serious and weird problem with my harddrive and ext3. About a > week ago I re-arranged my entire directory structure. I moved, deleted, > renamed files and dirs. I did some reboots and shutdowns in the mean > time. And all was fine, up until now. > > At the moment I'm looking at the filesystem (onto which I made those > changed last week) , but it seems I'm looking at the filesystem from a > month ago ( june 20th). > > Now I have a couple of questions: > > - How could this have happened?No idea.> - Is this a journaling problem?It is, but...> If so, how can I fix this and get the > filesystem back from july 12th instead of looking at the filesystem how > it was on june 20th.... that's not what journaling does I'm afraid.> I did a fsck/e2fsck on the umounted devs and they can't get any cleaner.I don't suppose you changed hard drives and you're looking at the old one? :) -Eric
On Sun, Jul 13, 2008 at 01:01:27AM +0200, Iskandar Prins wrote:> At the moment I'm looking at the filesystem (onto which I made those changed > last week) , but it seems I'm looking at the filesystem from a month ago ( > june 20th).is underlying block device a single hard disk, or maybe a RAID1 or similar ? I had a similar problem once, which turned out to be RAID1 which was out of sync (but wrongly thining it is OK!), so sometimes it read "right" data from one disk, and some times "bad" data from other disk. Solution was to break the RAID, force fsck it, and recreate the raid afterwards.> I did a fsck/e2fsck on the umounted devs and they can't get any cleaner.you did specify -f to force it, I assume ? -- Opinions above are GNU-copylefted.