Well i'm not sure if I really understand. But after jfs_debug and xt 1 I got
[1] flag 0x03 BT_ROOT BT_LEAF
[2] nextindex 2 [5] self.addr1 0x00
[3] maxentry 18 [6] self.addr2 0x00000000
[4] self.len 0x000000 self.addr 0
xtree: [m]odify, or e[x]it:
So I modify 1, then run jfs_fsck -fv
many many error, aFile inode 12 has been reconnected to /lost+found/.
File inode 11 has been reconnected to /lost+found/.
File inode 10 has been reconnected to /lost+found/.
File inode 9 has been reconnected to /lost+found/.
File inode 8 has been reconnected to /lost+found/.
Directory inode 4 has been reconnected to /lost+found/.
763 directories reconnected to /lost+found/.
5844 files reconnected to /lost+found/.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
Filesystem Summary:
Blocks in use for inodes: 7508
Inode count: 60064
File count: 43914
Directory count: 3638
Block count: 29304560
Free block count: 5075020
117218240 kilobytes total disk space.
14511 kilobytes in 3638 directories.
96841917 kilobytes in 43914 user files.
0 kilobytes in extended attributes
0 kilobytes in access control lists
90754 kilobytes reserved for system use.
20300080 kilobytes are available for use.
Filesystem is clean.
All observed inconsistencies have been repaired.
Filesystem has been marked clean.
**** Filesystem was modified. ****
processing terminated: 9/20/2004 21:17:40 with return code: 0 exit code: 1.nd on
the end:
Ater this I can mount filesystem and I see data in lost+found. That really wonderful,
but i lost original directory tree. Maybe I want impossible, but can I safe this data
better?
But how I say, This result is really great and, I'm very grateful. If I can't get
better result, after all I'm glad for this.
Thank you very much
Petr Humlicek
>Forget what I told you do to fix this. I was confused on which inode
>fsck is complaining about. It is fileset inode 1, not aggregate inode 1
>that is the problem. You should be able to fix this with jfs_debugfs as
>follows. Please ignore my previous instructions.
>
>Run "jfs_debugfs /dev/hdg6". From the command prompt, type "xt 1". On
>a good filesystem it should look like this:
>
> xt 1
>Root X-Tree Node of inode 1
>
>[1] flag 0x83 BT_ROOT BT_LEAF
>[2] nextindex 2 [5] self.addr1 0x00
>[3] maxentry 18 [6] self.addr2 0x00000000
>[4] self.len 0x000000 self.addr 0
>xtree: [m]odify, or e[x]it:
>
>From here, you can use the "m" sub-command to change any incorrect field
>to the right value. i.e. "m 1 0x83", "m 2 2", "m 3 18", etc.
>
>On Fri, 2004-09-17 at 16:44, David Kleikamp wrote:
>> But now, to try to fix your filesystem...
>>
>> Running "jfs_debugfs /dev/hdg6" should give you a command prompt. From
>> here, type "in 1 a". On a good file system, you should see something
>> like this:
>>
>> <Bad advise deleted>
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
