On Thu, 2004-09-23 at 13:52, Marcel Lanz wrote:
> > fsck against it, and remounting it.  Rebooting should also fix it,
> > assuming a valid entry in /etc/fstab.
> see below.
> 
> > I'm not aware of any known bugs that would have caused the corruption. 
> > You haven't seen any i/o errors from the disk, have you?
> no. i haven't.
> 
> well after the fsck i have the following (trunc) in lost+found and the directory 
> tree is blown away:
> 
> defiant:/mounts/wormhole# l lost+found/ | head  -n 20 
> total 36801744
> drwx------  12 root  root         4096 Sep 23 20:35 .
> drwxr-xr-x   3 lanzm users           8 Sep  6 16:13 ..
> drwxr-xr-x   2 lanzm lanzm           1 Jun 28 20:40 D004128.RCN
> drwxr-xr-x  11 lanzm lanzm          80 Aug  7 14:24 D004160.RCN
> drwxr-xr-x   3 lanzm lanzm           8 Jul  9 13:04 D020480.RCN
> drwxr-xr-x   2 lanzm lanzm           1 Sep 17 11:18 D028090.RCN
> drwxr-xr-x   2 lanzm lanzm          72 Jul 29 11:20 D098336.RCN
> drwxr-xr-x   2 lanzm lanzm          64 Jul 12 06:24 D122880.RCN
> drwxr-xr-x   2 lanzm lanzm           1 Sep 17 11:15 D135168.RCN
> drwxr-xr-x   2 lanzm lanzm          72 Aug 23 07:55 D143392.RCN
> drwxr-xr-x   2 root  root           16 Sep  6 14:00 D147488.RCN
> drwxr-xr-x   6 root  root           56 Sep 23 11:34 D151584.RCN

You may be able to determine from doing an ls in these directories, what
they originally were and mv them back to the proper path.  From the fsck
output, it looks like the contents of lost+found came from the root of
the file system, and one other directory.

> -rw-r--r--   1 lanzm lanzm           1 Jul  9 20:04 I004104.RCN
> -rw-r--r--   1 lanzm lanzm   507445248 Aug  7 14:35 I004105.RCN
> -rw-r--r--   1 root  root  36748583424 Aug  4 11:38 I004106.RCN
> -rw-r--r--   1 lanzm lanzm           0 Jul  9 20:00 I049152.RCN
> -rw-r--r--   1 lanzm lanzm   137598377 Jul  9 20:01 I053248.RCN
> -rw-r--r--   1 lanzm lanzm           0 Jul  9 20:00 I057344.RCN
> -rw-r--r--   1 lanzm lanzm           0 Jul  9 20:00 I057345.RCN
> 
> it seems the files are there, but well...

It's tedious to go through 74 files to determine what they are, but if
any of these files are vital, you can probably identify them and mv them
back to the proper path after fixing the directories.  Again they should
all have come from the root and one other directory.  The other
directories should be intact under /lost+found/Dxxxxxx.RCN/

>     I know that one can say that I should backup my stuff. 
>     well this is my backup drive and I have those things redundant, but
>     hey. I used ext2 for years and never had something like this. (i
>     know I should say that)
> 
>     I'm interested if someone can tell me what this could be. its 
>     enough if I hear something like: 
>     "well something with you Y went wrongs while the fs commited X during
>      the Z transaction and sync up."

I wish I knew what caused this, but I don't.  :^(

Can you send me the output of "jfs_fscklog -d -e /dev/sda1"?  It
probably won't be enough to figure out the cause of the problem, but it
might help me to know where to look.


Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center

_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion

Reply via email to