> 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
-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...
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."
regards
marcel
//----------------------------
fsck output:
defiant:~# fsck.jfs /dev/sda1
fsck.jfs version 1.1.6, 28-Apr-2004
processing started: 9/23/2004 20.30.36
Using default parameter: -p
The current device is: /dev/sda1
Block size in bytes: 4096
Filesystem size in blocks: 49783419
**Phase 0 - Replay Journal Log
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
The root directory has an invalid format. Will correct.
The root directory has an invalid data format. Will correct.
**Phase 2 - Count links
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
Directory entries for unallocated files have been detected. Will remove.
**Phase 4 - Report Problems
Fileset object DF4096: No paths found.
cannot repair the data format error(s) in this directory.
cannot repair DF4096. Will release.
File system object FF4099 is linked as: Underworld
The path(s) refer to an unallocated file. Will remove.
Fileset object DF4160: No paths found.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
10 directories reconnected to /lost+found/.
74 files reconnected to /lost+found/.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
199133676 kilobytes total disk space.
153765 kilobytes in 38890 directories.
121904513 kilobytes in 484851 user files.
37368 kilobytes in extended attributes
376352 kilobytes reserved for system use.
76969208 kilobytes are available for use.
Filesystem is clean.
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
