* reiser4progs 1.0.4 @ 2005-02-20 10:44 Vitaly Fertman 2005-02-21 13:10 ` Ookhoi 0 siblings, 1 reply; 11+ messages in thread From: Vitaly Fertman @ 2005-02-20 10:44 UTC (permalink / raw) To: reiserfs-list Hello All The new reiser4progs package is available on our ftp site (ftp://ftp.namesys.com/pub/reiser4progs/). It includes: Bugfixes: - in file body/extent item truncate code; - in backup handling & traverse code; - in journal unpack code; - in node repair code; - in not aligned access to on-disk data; - in extent item-by-item insertion code; - in tree balancing code; - in SuperBlock handling code; - in syncing code; - in file body convertion code. Enable libminimal by default. Do not configure/install empty utils(resizer, cpfs). A reiser4 support for grub 0.96 is available in ftp://ftp.namesys.com/pub/reiser4progs/grub -- Thanks, Vitaly Fertman ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-02-20 10:44 reiser4progs 1.0.4 Vitaly Fertman @ 2005-02-21 13:10 ` Ookhoi 2005-02-21 13:59 ` Vitaly Fertman 2005-02-21 14:35 ` Jindrich Makovicka 0 siblings, 2 replies; 11+ messages in thread From: Ookhoi @ 2005-02-21 13:10 UTC (permalink / raw) To: Vitaly Fertman; +Cc: reiserfs-list On Sun, Feb 20, 2005 at 01:44:41PM +0300, Vitaly Fertman wrote: > The new reiser4progs package is available on our ftp > site (ftp://ftp.namesys.com/pub/reiser4progs/). Thank you for this release. It doesn't crash anymore :-) But it does tell me: "NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE." I have a copy of the fs, but I did run verson 1.0.3 on it before I made a copy. (1.0.3 crashes with segfault). Is this fs fixable you think? Thanks in advance and with kind regards, Sander bellyup:~# fsck.reiser4 --version fsck.reiser4 1.0.4 Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by reiser4progs/COPYING. bellyup:~# fsck.reiser4 /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will check the consistency of the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:49:30 2005 Fatal: Wrong magic found in the master super block. Fatal: Failed to open the reiser4 backup. Fatal: Cannot open the FileSystem on (/dev/hda1). 1 fatal corruptions were detected in SuperBlock. Run with --build-sb option to fix them. bellyup:~# fsck.reiser4 --build-sb /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will build the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:49:43 2005 Fatal: Wrong magic found in the master super block. Fatal: Failed to open the reiser4 backup. Fatal: Cannot open the FileSystem on (/dev/hda1). 1 fatal corruptions were detected in SuperBlock. Run with --build-sb option to fix them. bellyup:~# fsck.reiser4 --build-sb /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will build the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:49:43 2005 Fatal: Wrong magic found in the master super block. Master super block cannot be found on (/dev/hda1). Do you want to build a new one? (Yes/No): Yes Which block size do you use? [4096]: Warn : A new master superblock is created on '/dev/hda1'. Fatal: Can't open disk-format format40. Enter the key plugin name [key_large]: Enter the correct block count please [126504]: Warn : The format 'format40' is created on '/dev/hda1'. Error: Wrong magic is found in the filesystem status block. Warn : Creating a new status block. FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be 0x885c0260. FSCK: Checksums will be fixed later. Reiser4 fs was detected on /dev/hda1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0xe78822c blocks: 126504 free blocks: 0 root block: 0 tail policy: 0x2 (smart) next oid: 0x0 file count: 0 tree height: 0 key policy: LARGE CHECKING STORAGE TREE Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Invalid node pointers 1 Time interval: Mon Feb 21 13:49:52 2005 - Mon Feb 21 13:49:52 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:49:52 2005 - Mon Feb 21 13:49:52 2005 Warn : Fatal corruptions were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Mon Feb 21 13:49:52 2005 Closing fs...done 1 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them. bellyup:~# fsck.reiser4 /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will check the consistency of the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:50:02 2005 FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be 0x885c0260. Reiser4 fs was detected on /dev/hda1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0xe78822c blocks: 126504 free blocks: 0 root block: 0 tail policy: 0x2 (smart) next oid: 0x0 file count: 0 tree height: 0 key policy: LARGE CHECKING STORAGE TREE Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Invalid node pointers 1 Time interval: Mon Feb 21 13:50:02 2005 - Mon Feb 21 13:50:02 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:50:02 2005 - Mon Feb 21 13:50:02 2005 Warn : Fatal corruptions were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Mon Feb 21 13:50:02 2005 Closing fs...done 1 fixable corruptions were detected in the SuperBlock. Run with --fix option to fix them. bellyup:~# fsck.reiser4 --fix /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will fix minor corruptions of the Reiser4 SuperBlock. Will fix minor corruptions of the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:50:14 2005 FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be 0x885c0260. FSCK: Checksums will be fixed later. Reiser4 fs was detected on /dev/hda1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0xe78822c blocks: 126504 free blocks: 0 root block: 0 tail policy: 0x2 (smart) next oid: 0x0 file count: 0 tree height: 0 key policy: LARGE CHECKING STORAGE TREE Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Invalid node pointers 1 Time interval: Mon Feb 21 13:50:14 2005 - Mon Feb 21 13:50:14 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:50:14 2005 - Mon Feb 21 13:50:14 2005 Warn : Fatal corruptions were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Mon Feb 21 13:50:14 2005 Closing fs...done 1 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them. bellyup:~# fsck.reiser4 --build-fs /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:50:26 2005 FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be 0x885c0260. Reiser4 fs was detected on /dev/hda1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0xe78822c blocks: 126504 free blocks: 0 root block: 0 tail policy: 0x2 (smart) next oid: 0x0 file count: 0 tree height: 0 key policy: LARGE CHECKING STORAGE TREE Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Zeroed node pointers 1 Time interval: Mon Feb 21 13:50:26 2005 - Mon Feb 21 13:50:26 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:50:26 2005 - Mon Feb 21 13:50:26 2005 LOOKING FOR UNCONNECTED NODES Read nodes 96346 Good nodes 0 Leaves of them 0, Twigs of them 0 Time interval: Mon Feb 21 13:50:26 2005 - Mon Feb 21 13:50:35 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:50:35 2005 - Mon Feb 21 13:50:35 2005 INSERTING UNCONNECTED NODES 1. Twigs: done 2. Twigs by item: done 3. Leaves: done 4. Leaves by item: done Twigs: read 0, inserted 0, by item 0, empty 0 Leaves: read 0, inserted 0, by item 0 Time interval: Mon Feb 21 13:50:35 2005 - Mon Feb 21 13:50:35 2005 Fatal: No reiser4 metadata were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Mon Feb 21 13:50:35 2005 Closing fs...done 1 fixable corruptions were detected in the SuperBlock. Run with --fix option to fix them. NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE. bellyup:~# fsck.reiser4 --fix /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will fix minor corruptions of the Reiser4 SuperBlock. Will fix minor corruptions of the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:51:01 2005 Reiser4 fs was detected on /dev/hda1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0xe78822c blocks: 126504 free blocks: 126476 root block: 18446744073709551615 tail policy: 0x2 (smart) next oid: 0x0 file count: 0 tree height: 0 key policy: LARGE CHECKING STORAGE TREE Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Invalid node pointers 1 Time interval: Mon Feb 21 13:51:02 2005 - Mon Feb 21 13:51:02 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:51:02 2005 - Mon Feb 21 13:51:02 2005 Warn : Fatal corruptions were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Mon Feb 21 13:51:02 2005 Closing fs...done 1 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them. bellyup:~# fsck.reiser4 --build-fs --fix /dev/hda1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hda1 block device. Will fix minor corruptions of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Mon Feb 21 13:52:45 2005 Reiser4 fs was detected on /dev/hda1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0xe78822c blocks: 126504 free blocks: 126476 root block: 18446744073709551615 tail policy: 0x2 (smart) next oid: 0x0 file count: 0 tree height: 0 key policy: LARGE CHECKING STORAGE TREE Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Zeroed node pointers 1 Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 LOOKING FOR UNCONNECTED NODES Read nodes 0 Good nodes 0 Leaves of them 0, Twigs of them 0 Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 INSERTING UNCONNECTED NODES 1. Twigs: done 2. Twigs by item: done 3. Leaves: done 4. Leaves by item: done Twigs: read 0, inserted 0, by item 0, empty 0 Leaves: read 0, inserted 0, by item 0 Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 Fatal: No reiser4 metadata were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Mon Feb 21 13:52:46 2005 Closing fs...done NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-02-21 13:10 ` Ookhoi @ 2005-02-21 13:59 ` Vitaly Fertman 2005-02-21 17:01 ` Ookhoi 2005-02-22 20:08 ` Sander 2005-02-21 14:35 ` Jindrich Makovicka 1 sibling, 2 replies; 11+ messages in thread From: Vitaly Fertman @ 2005-02-21 13:59 UTC (permalink / raw) To: Ookhoi; +Cc: reiserfs-list On Monday 21 February 2005 16:10, Ookhoi wrote: > On Sun, Feb 20, 2005 at 01:44:41PM +0300, Vitaly Fertman wrote: > > The new reiser4progs package is available on our ftp > > site (ftp://ftp.namesys.com/pub/reiser4progs/). > > Thank you for this release. It doesn't crash anymore :-) > > But it does tell me: > "NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE." > > I have a copy of the fs, but I did run verson 1.0.3 on it before > I made a copy. (1.0.3 crashes with segfault). > > Is this fs fixable you think? > > Thanks in advance and with kind regards, Sander > > > bellyup:~# fsck.reiser4 --version > fsck.reiser4 1.0.4 > Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by > reiser4progs/COPYING. > > bellyup:~# fsck.reiser4 /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will check the consistency of the Reiser4 SuperBlock. > Will check the consistency of the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:49:30 2005 > Fatal: Wrong magic found in the master super block. > Fatal: Failed to open the reiser4 backup. > Fatal: Cannot open the FileSystem on (/dev/hda1). > > 1 fatal corruptions were detected in SuperBlock. Run with --build-sb option > to fix them. > > bellyup:~# fsck.reiser4 --build-sb /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will build the Reiser4 SuperBlock. > Will check the consistency of the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:49:43 2005 > Fatal: Wrong magic found in the master super block. > Fatal: Failed to open the reiser4 backup. > Fatal: Cannot open the FileSystem on (/dev/hda1). > > 1 fatal corruptions were detected in SuperBlock. Run with --build-sb option > to fix them. > > bellyup:~# fsck.reiser4 --build-sb /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will build the Reiser4 SuperBlock. > Will check the consistency of the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:49:43 2005 > Fatal: Wrong magic found in the master super block. > Master super block cannot be found on (/dev/hda1). Do you want to build a > new one? (Yes/No): Yes > Which block size do you use? [4096]: > Warn : A new master superblock is created on '/dev/hda1'. > Fatal: Can't open disk-format format40. > Enter the key plugin name [key_large]: > Enter the correct block count please [126504]: > Warn : The format 'format40' is created on '/dev/hda1'. > Error: Wrong magic is found in the filesystem status block. > Warn : Creating a new status block. > FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be > 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is > 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block > 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum > missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be > 0x885c0260. FSCK: Checksums will be fixed later. > Reiser4 fs was detected on /dev/hda1. > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0xe78822c > blocks: 126504 > free blocks: 0 > root block: 0 > tail policy: 0x2 (smart) > next oid: 0x0 > file count: 0 > tree height: 0 > key policy: LARGE > > > CHECKING STORAGE TREE > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > Read nodes 0 > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Invalid node pointers 1 > Time interval: Mon Feb 21 13:49:52 2005 - Mon Feb 21 13:49:52 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:49:52 2005 - Mon Feb 21 13:49:52 2005 > Warn : Fatal corruptions were found. Semantic pass is skipped. > ***** fsck.reiser4 finished at Mon Feb 21 13:49:52 2005 > Closing fs...done > > 1 fatal corruptions were detected in FileSystem. Run with --build-fs option > to fix them. > > bellyup:~# fsck.reiser4 /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will check the consistency of the Reiser4 SuperBlock. > Will check the consistency of the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:50:02 2005 > FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be > 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is > 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block > 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum > missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be > 0x885c0260. Reiser4 fs was detected on /dev/hda1. > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0xe78822c > blocks: 126504 > free blocks: 0 > root block: 0 > tail policy: 0x2 (smart) > next oid: 0x0 > file count: 0 > tree height: 0 > key policy: LARGE > > > CHECKING STORAGE TREE > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > Read nodes 0 > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Invalid node pointers 1 > Time interval: Mon Feb 21 13:50:02 2005 - Mon Feb 21 13:50:02 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:50:02 2005 - Mon Feb 21 13:50:02 2005 > Warn : Fatal corruptions were found. Semantic pass is skipped. > ***** fsck.reiser4 finished at Mon Feb 21 13:50:02 2005 > Closing fs...done > > 1 fixable corruptions were detected in the SuperBlock. Run with --fix > option to fix them. > > bellyup:~# fsck.reiser4 --fix /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will fix minor corruptions of the Reiser4 SuperBlock. > Will fix minor corruptions of the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:50:14 2005 > FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be > 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is > 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block > 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum > missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be > 0x885c0260. FSCK: Checksums will be fixed later. > Reiser4 fs was detected on /dev/hda1. > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0xe78822c > blocks: 126504 > free blocks: 0 > root block: 0 > tail policy: 0x2 (smart) > next oid: 0x0 > file count: 0 > tree height: 0 > key policy: LARGE > > > CHECKING STORAGE TREE > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > Read nodes 0 > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Invalid node pointers 1 > Time interval: Mon Feb 21 13:50:14 2005 - Mon Feb 21 13:50:14 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:50:14 2005 - Mon Feb 21 13:50:14 2005 > Warn : Fatal corruptions were found. Semantic pass is skipped. > ***** fsck.reiser4 finished at Mon Feb 21 13:50:14 2005 > Closing fs...done > > 1 fatal corruptions were detected in FileSystem. Run with --build-fs option > to fix them. > > bellyup:~# fsck.reiser4 --build-fs /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will check the consistency of the Reiser4 SuperBlock. > Will build the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:50:26 2005 > FSCK: Checksum missmatch in bitmap block 18. Checksum is 0x0, should be > 0xffc0001. FSCK: Checksum missmatch in bitmap block 32736. Checksum is > 0xef2d8782, should be 0x955c26fe. FSCK: Checksum missmatch in bitmap block > 65472. Checksum is 0x64c78fa2, should be 0xf55bf507. FSCK: Checksum > missmatch in bitmap block 98208. Checksum is 0xf6d9d7e3, should be > 0x885c0260. Reiser4 fs was detected on /dev/hda1. > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0xe78822c > blocks: 126504 > free blocks: 0 > root block: 0 > tail policy: 0x2 (smart) > next oid: 0x0 > file count: 0 > tree height: 0 > key policy: LARGE > > > CHECKING STORAGE TREE > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > Read nodes 0 > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Zeroed node pointers 1 > Time interval: Mon Feb 21 13:50:26 2005 - Mon Feb 21 13:50:26 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:50:26 2005 - Mon Feb 21 13:50:26 2005 > LOOKING FOR UNCONNECTED NODES > Read nodes 96346 > Good nodes 0 > Leaves of them 0, Twigs of them 0 > Time interval: Mon Feb 21 13:50:26 2005 - Mon Feb 21 13:50:35 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:50:35 2005 - Mon Feb 21 13:50:35 2005 > INSERTING UNCONNECTED NODES > 1. Twigs: done > 2. Twigs by item: done > 3. Leaves: done > 4. Leaves by item: done > Twigs: read 0, inserted 0, by item 0, empty 0 > Leaves: read 0, inserted 0, by item 0 > Time interval: Mon Feb 21 13:50:35 2005 - Mon Feb 21 13:50:35 2005 > Fatal: No reiser4 metadata were found. Semantic pass is skipped. > ***** fsck.reiser4 finished at Mon Feb 21 13:50:35 2005 > Closing fs...done > > 1 fixable corruptions were detected in the SuperBlock. Run with --fix > option to fix them. NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT > POSSIBLE. > > bellyup:~# fsck.reiser4 --fix /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will fix minor corruptions of the Reiser4 SuperBlock. > Will fix minor corruptions of the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:51:01 2005 > Reiser4 fs was detected on /dev/hda1. > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0xe78822c > blocks: 126504 > free blocks: 126476 > root block: 18446744073709551615 > tail policy: 0x2 (smart) > next oid: 0x0 > file count: 0 > tree height: 0 > key policy: LARGE > > > CHECKING STORAGE TREE > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > Read nodes 0 > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Invalid node pointers 1 > Time interval: Mon Feb 21 13:51:02 2005 - Mon Feb 21 13:51:02 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:51:02 2005 - Mon Feb 21 13:51:02 2005 > Warn : Fatal corruptions were found. Semantic pass is skipped. > ***** fsck.reiser4 finished at Mon Feb 21 13:51:02 2005 > Closing fs...done > 1 fatal corruptions were detected in FileSystem. Run with --build-fs option > to fix them. > > bellyup:~# fsck.reiser4 --build-fs --fix /dev/hda1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hda1 block device. > Will fix minor corruptions of the Reiser4 SuperBlock. > Will build the Reiser4 FileSystem. > Continue? > (Yes/No): Yes > ***** fsck.reiser4 started at Mon Feb 21 13:52:45 2005 > Reiser4 fs was detected on /dev/hda1. > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0xe78822c > blocks: 126504 > free blocks: 126476 > root block: 18446744073709551615 > tail policy: 0x2 (smart) > next oid: 0x0 > file count: 0 > tree height: 0 > key policy: LARGE > > > CHECKING STORAGE TREE > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > Read nodes 0 > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Zeroed node pointers 1 > Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 > LOOKING FOR UNCONNECTED NODES > Read nodes 0 > Good nodes 0 > Leaves of them 0, Twigs of them 0 > Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 > CHECKING EXTENT REGIONS. > Read twigs 0 > Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 > INSERTING UNCONNECTED NODES > 1. Twigs: done > 2. Twigs by item: done > 3. Leaves: done > 4. Leaves by item: done > Twigs: read 0, inserted 0, by item 0, empty 0 > Leaves: read 0, inserted 0, by item 0 > Time interval: Mon Feb 21 13:52:46 2005 - Mon Feb 21 13:52:46 2005 > Fatal: No reiser4 metadata were found. Semantic pass is skipped. > ***** fsck.reiser4 finished at Mon Feb 21 13:52:46 2005 > Closing fs...done > > NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE. no master super block, no format-specific super block, no backup blocks, no status block, all bitmap blocks are not valid, no one reiser4 formatted node has been found ... what you are fscking does not look like a reiser4 filesystem at all. -- Thanks, Vitaly Fertman ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-02-21 13:59 ` Vitaly Fertman @ 2005-02-21 17:01 ` Ookhoi 2005-02-22 20:08 ` Sander 1 sibling, 0 replies; 11+ messages in thread From: Ookhoi @ 2005-02-21 17:01 UTC (permalink / raw) To: Vitaly Fertman; +Cc: reiserfs-list On Mon, Feb 21, 2005 at 04:59:53PM +0300, Vitaly Fertman wrote: > On Monday 21 February 2005 16:10, Ookhoi wrote: > > On Sun, Feb 20, 2005 at 01:44:41PM +0300, Vitaly Fertman wrote: > > > The new reiser4progs package is available on our ftp > > > site (ftp://ftp.namesys.com/pub/reiser4progs/). > > > > Thank you for this release. It doesn't crash anymore :-) > > > > But it does tell me: > > "NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE." > no master super block, no format-specific super block, no backup blocks, > no status block, all bitmap blocks are not valid, no one reiser4 formatted > node has been found ... what you are fscking does not look like a reiser4 > filesystem at all. Ugh .. It should be hda2, nog hda1 .. Well, it is checked now. I can't mount it with the current kernel (no support) so I'll reboot and let you all know. Sorry for the noise of that particular message .. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-02-21 13:59 ` Vitaly Fertman 2005-02-21 17:01 ` Ookhoi @ 2005-02-22 20:08 ` Sander 1 sibling, 0 replies; 11+ messages in thread From: Sander @ 2005-02-22 20:08 UTC (permalink / raw) To: Vitaly Fertman; +Cc: Ookhoi, reiserfs-list Vitaly Fertman wrote (ao): > On Monday 21 February 2005 16:59, Vitaly Fertman wrote: > > On Monday 21 February 2005 16:10, Ookhoi wrote: > > > On Sun, Feb 20, 2005 at 01:44:41PM +0300, Vitaly Fertman wrote: > > > > The new reiser4progs package is available on our ftp > > > > site (ftp://ftp.namesys.com/pub/reiser4progs/). > > > > > > Thank you for this release. It doesn't crash anymore :-) > > > > > > But it does tell me: > > > "NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE." > > no master super block, no format-specific super block, no backup > > blocks, no status block, all bitmap blocks are not valid, no one > > reiser4 formatted node has been found ... what you are fscking does > > not look like a reiser4 filesystem at all. As said before I was very much asleep when I ran the fsck command. It should have been hda2, not hda1. Btw, hda1 contained an ext2 filesystem which was not mountable and not recoverable after running all the fsck.reiser4 commands on it. Can't blame it I guess :-) Luckily it was only /boot and thus easy to recover. I managed to reboot the machine and mount the fs. Some files where corrupted, but on the whole the fs seems fine now. So a big thumbs up for this release of fsck.reiser4 :-) Btw, I blame the corruption on the combination kernel and a forced hard-reboot during shutdown (it hung). Again, thumbs up. This all made me much more confident wrt Reiser4. With kind regards, Sander ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-02-21 13:10 ` Ookhoi 2005-02-21 13:59 ` Vitaly Fertman @ 2005-02-21 14:35 ` Jindrich Makovicka 2005-02-21 16:49 ` Vitaly Fertman 1 sibling, 1 reply; 11+ messages in thread From: Jindrich Makovicka @ 2005-02-21 14:35 UTC (permalink / raw) Cc: Vitaly Fertman, reiserfs-list Ookhoi wrote: > Fatal: Failed to open the reiser4 backup. > Fatal: Cannot open the FileSystem on (/dev/hda1). > > 1 fatal corruptions were detected in SuperBlock. Run with --build-sb option to fix them. Anyway, what is the preferred way to convert reiser4 to this new backup layout? I have all reiser4 partitions created with reiserfsprogs 1.0.0, so 1.0.3 & 1.0.4 bail out. Using fsck.reiser4 --build-sb from reiser4progs 1.0.3 rendered the filesystem created under 1.0.0 unusable, I still didn't try fsck 1.0.4. I also found the -C option of debugfs.reiser4, but it didn't help either, and subsequent fsck also botched the filesystem. Were there any fixes in 1.0.4 regarding this? Thanks, -- Jindrich Makovicka ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-02-21 14:35 ` Jindrich Makovicka @ 2005-02-21 16:49 ` Vitaly Fertman 2005-03-18 18:59 ` Jindrich Makovicka 0 siblings, 1 reply; 11+ messages in thread From: Vitaly Fertman @ 2005-02-21 16:49 UTC (permalink / raw) To: Jindrich Makovicka; +Cc: reiserfs-list On Monday 21 February 2005 17:35, Jindrich Makovicka wrote: > Ookhoi wrote: > > Fatal: Failed to open the reiser4 backup. > > Fatal: Cannot open the FileSystem on (/dev/hda1). > > > > 1 fatal corruptions were detected in SuperBlock. Run with --build-sb > > option to fix them. > > > Anyway, what is the preferred way to convert reiser4 to this new backup > layout? I have all reiser4 partitions created with reiserfsprogs 1.0.0, there was no format changes since 1.0.0, just a problem in reiser4progs with writing backups to disk > so 1.0.3 & 1.0.4 bail out. Using fsck.reiser4 --build-sb from > reiser4progs 1.0.3 rendered the filesystem created under 1.0.0 unusable, fsck.reiser4 --build-sb is supposed to fix evth. what goes wrong? > I still didn't try fsck 1.0.4. I also found the -C option of > debugfs.reiser4, but it didn't help either, and subsequent fsck also > botched the filesystem. Were there any fixes in 1.0.4 regarding this? -- Thanks, Vitaly Fertman ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-02-21 16:49 ` Vitaly Fertman @ 2005-03-18 18:59 ` Jindrich Makovicka 2005-03-19 14:23 ` Vitaly Fertman 0 siblings, 1 reply; 11+ messages in thread From: Jindrich Makovicka @ 2005-03-18 18:59 UTC (permalink / raw) To: Vitaly Fertman, reiserfs-list Vitaly Fertman wrote: >>so 1.0.3 & 1.0.4 bail out. Using fsck.reiser4 --build-sb from >>reiser4progs 1.0.3 rendered the filesystem created under 1.0.0 unusable, > > > fsck.reiser4 --build-sb is supposed to fix evth. what goes wrong? sorry I didn't replied earlier, but I didn't have a spare disk available. here it goes. 40GB partition was mkfs'ed with 1.0.0, populated somehow (about 32k files, 400MB), then fsck --build-sb from 1.0.4 was run: 8<--- snip holly:~# fsck.reiser4 --build-sb /dev/hdk1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hdk1 block device. Will build the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Fri Mar 18 19:46:33 2005 FSCK: UUID (0xea4de9160ad898572244086da443359e) found in the master super block does not match the one found in the backup (0xba44099ce147985c3da7d6bf7448b582). Fixed. FSCK: The on-disk format mkfs id (0x19e74713) does not match the backup one (0x75315ca). Fixed. Reiser4 fs was detected on /dev/hdk1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 5c9847e1-9c09-44ba-82b5-4874bfd6a73d label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0x75315ca blocks: 9770662 free blocks: 9676935 root block: 25 tail policy: 0x2 (smart) next oid: 0x17d22 file count: 32034 tree height: 4 key policy: LARGE CHECKING STORAGE TREE FSCK: Node (25): failed to open the root node. The whole filter pass is skipped. Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Invalid node pointers 1 Time interval: Fri Mar 18 19:46:37 2005 - Fri Mar 18 19:46:37 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Fri Mar 18 19:46:37 2005 - Fri Mar 18 19:46:37 2005 Warn : Fatal corruptions were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Fri Mar 18 19:46:37 2005 Closing fs...done 1 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them. holly:~# fsck.reiser4 --build-sb /dev/hdk1 > ~/r4_buildsb.txt ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hdk1 block device. Will build the Reiser4 SuperBlock. Will check the consistency of the Reiser4 FileSystem. Continue? (Yes/No): Yes holly:~# fsck.reiser4 --build-fs /dev/hdk1 ******************************************************************* This is an EXPERIMENTAL version of fsck.reiser4. Read README first. ******************************************************************* Fscking the /dev/hdk1 block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. Continue? (Yes/No): Yes ***** fsck.reiser4 started at Fri Mar 18 19:48:56 2005 Reiser4 fs was detected on /dev/hdk1. Master super block (16): magic: ReIsEr4 blksize: 4096 format: 0x0 (format40) uuid: 5c9847e1-9c09-44ba-82b5-4874bfd6a73d label: <none> Format super block (17): plugin: format40 description: Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes: 0 mkfs id: 0x75315ca blocks: 9770662 free blocks: 9676935 root block: 25 tail policy: 0x2 (smart) next oid: 0x17d22 file count: 32034 tree height: 4 key policy: LARGE CHECKING STORAGE TREE FSCK: Node (25): failed to open the root node. The whole filter pass is skipped. Warn : Reiser4 storage tree does not exist. Filter pass skipped. Read nodes 0 Nodes left in the tree 0 Leaves of them 0, Twigs of them 0 Zeroed node pointers 1 Time interval: Fri Mar 18 19:48:59 2005 - Fri Mar 18 19:48:59 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Fri Mar 18 19:48:59 2005 - Fri Mar 18 19:48:59 2005 LOOKING FOR UNCONNECTED NODES Read nodes 93393 Good nodes 0 Leaves of them 0, Twigs of them 0 Time interval: Fri Mar 18 19:49:00 2005 - Fri Mar 18 19:49:09 2005 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Fri Mar 18 19:49:09 2005 - Fri Mar 18 19:49:09 2005 INSERTING UNCONNECTED NODES 1. Twigs: done 2. Twigs by item: done 3. Leaves: done 4. Leaves by item: done Twigs: read 0, inserted 0, by item 0, empty 0 Leaves: read 0, inserted 0, by item 0 Time interval: Fri Mar 18 19:49:10 2005 - Fri Mar 18 19:49:10 2005 Fatal: No reiser4 metadata were found. Semantic pass is skipped. ***** fsck.reiser4 finished at Fri Mar 18 19:49:10 2005 Closing fs...done NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE. 8<--- snip -- Jindrich Makovicka ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-03-18 18:59 ` Jindrich Makovicka @ 2005-03-19 14:23 ` Vitaly Fertman 2005-03-19 18:03 ` Jindrich Makovicka 0 siblings, 1 reply; 11+ messages in thread From: Vitaly Fertman @ 2005-03-19 14:23 UTC (permalink / raw) To: Jindrich Makovicka; +Cc: reiserfs-list On Friday 18 March 2005 21:59, Jindrich Makovicka wrote: > Vitaly Fertman wrote: > >>so 1.0.3 & 1.0.4 bail out. Using fsck.reiser4 --build-sb from > >>reiser4progs 1.0.3 rendered the filesystem created under 1.0.0 unusable, > > > > > > fsck.reiser4 --build-sb is supposed to fix evth. what goes wrong? > > sorry I didn't replied earlier, but I didn't have a spare disk > available. here it goes. 40GB partition was mkfs'ed with 1.0.0, > populated somehow (about 32k files, 400MB), then fsck --build-sb from > 1.0.4 was run: > > 8<--- snip > > holly:~# fsck.reiser4 --build-sb /dev/hdk1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hdk1 block device. > > Will build the Reiser4 SuperBlock. > > Will check the consistency of the Reiser4 FileSystem. > > Continue? > > (Yes/No): Yes > ***** fsck.reiser4 started at Fri Mar 18 19:46:33 2005 > FSCK: UUID (0xea4de9160ad898572244086da443359e) found in the master > super block does not match the one found in the backup > (0xba44099ce147985c3da7d6bf7448b582). Fixed. > FSCK: The on-disk format mkfs id (0x19e74713) does not match the backup > one (0x75315ca). Fixed. > Reiser4 fs was detected on /dev/hdk1. it seems you forgot to mention that you had already created some reiser4 on this partition with 1.0.4 and after that created fs again with 1.0.0. the result of such experiments is that you have the mix of metadata -- fresh super blocks and old backup blocks. all formatted blocks are created according to the new parameters whereas recovery goes according to the detected backup blocks and as the result no valid reiser4 block is found. if you do not downgrade progs, you should not get such resuls. > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > uuid: 5c9847e1-9c09-44ba-82b5-4874bfd6a73d > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0x75315ca > blocks: 9770662 > free blocks: 9676935 > root block: 25 > tail policy: 0x2 (smart) > next oid: 0x17d22 > file count: 32034 > tree height: 4 > key policy: LARGE > > > CHECKING STORAGE TREE > > FSCK: Node (25): failed to open the root node. The whole filter pass is > skipped. > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > > Read nodes 0 > > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Invalid node pointers 1 > Time interval: Fri Mar 18 19:46:37 2005 - Fri Mar 18 19:46:37 2005 > CHECKING EXTENT REGIONS. > > Read twigs 0 > > Time interval: Fri Mar 18 19:46:37 2005 - Fri Mar 18 19:46:37 2005 > Warn : Fatal corruptions were found. Semantic pass is skipped. > > ***** fsck.reiser4 finished at Fri Mar 18 19:46:37 2005 > Closing fs...done > > 1 fatal corruptions were detected in FileSystem. Run with --build-fs > option to fix them. > > holly:~# fsck.reiser4 --build-sb /dev/hdk1 > ~/r4_buildsb.txt > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hdk1 block device. > > Will build the Reiser4 SuperBlock. > > Will check the consistency of the Reiser4 FileSystem. > > Continue? > > (Yes/No): Yes > > holly:~# fsck.reiser4 --build-fs /dev/hdk1 > ******************************************************************* > This is an EXPERIMENTAL version of fsck.reiser4. Read README first. > ******************************************************************* > > Fscking the /dev/hdk1 block device. > > Will check the consistency of the Reiser4 SuperBlock. > > Will build the Reiser4 FileSystem. > > Continue? > > (Yes/No): Yes > ***** fsck.reiser4 started at Fri Mar 18 19:48:56 2005 > Reiser4 fs was detected on /dev/hdk1. > > Master super block (16): > magic: ReIsEr4 > blksize: 4096 > format: 0x0 (format40) > uuid: 5c9847e1-9c09-44ba-82b5-4874bfd6a73d > label: <none> > > Format super block (17): > plugin: format40 > description: Disk-format for reiser4. > magic: ReIsEr40FoRmAt > flushes: 0 > mkfs id: 0x75315ca > blocks: 9770662 > free blocks: 9676935 > root block: 25 > tail policy: 0x2 (smart) > next oid: 0x17d22 > file count: 32034 > tree height: 4 > key policy: LARGE > > > CHECKING STORAGE TREE > > FSCK: Node (25): failed to open the root node. The whole filter pass is > skipped. > Warn : Reiser4 storage tree does not exist. Filter pass skipped. > > Read nodes 0 > > Nodes left in the tree 0 > Leaves of them 0, Twigs of them 0 > Zeroed node pointers 1 > Time interval: Fri Mar 18 19:48:59 2005 - Fri Mar 18 19:48:59 2005 > CHECKING EXTENT REGIONS. > > Read twigs 0 > > Time interval: Fri Mar 18 19:48:59 2005 - Fri Mar 18 19:48:59 2005 > LOOKING FOR UNCONNECTED NODES > > Read nodes 93393 > > Good nodes 0 > Leaves of them 0, Twigs of them 0 > Time interval: Fri Mar 18 19:49:00 2005 - Fri Mar 18 19:49:09 2005 > CHECKING EXTENT REGIONS. > > Read twigs 0 > > Time interval: Fri Mar 18 19:49:09 2005 - Fri Mar 18 19:49:09 2005 > INSERTING UNCONNECTED NODES > > 1. Twigs: done > > 2. Twigs by item: done > > 3. Leaves: done > > 4. Leaves by item: done > > Twigs: read 0, inserted 0, by item 0, empty 0 > > Leaves: read 0, inserted 0, by item 0 > Time interval: Fri Mar 18 19:49:10 2005 - Fri Mar 18 19:49:10 2005 > Fatal: No reiser4 metadata were found. Semantic pass is skipped. > > ***** fsck.reiser4 finished at Fri Mar 18 19:49:10 2005 > Closing fs...done > > NO REISER4 METADATA WERE FOUND. FS RECOVERY IS NOT POSSIBLE. > > 8<--- snip > -- Thanks, Vitaly Fertman ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-03-19 14:23 ` Vitaly Fertman @ 2005-03-19 18:03 ` Jindrich Makovicka 2005-03-21 13:30 ` Vitaly Fertman 0 siblings, 1 reply; 11+ messages in thread From: Jindrich Makovicka @ 2005-03-19 18:03 UTC (permalink / raw) To: Vitaly Fertman; +Cc: reiserfs-list Vitaly Fertman wrote: > On Friday 18 March 2005 21:59, Jindrich Makovicka wrote: > >>Vitaly Fertman wrote: >> >>>>so 1.0.3 & 1.0.4 bail out. Using fsck.reiser4 --build-sb from >>>>reiser4progs 1.0.3 rendered the filesystem created under 1.0.0 unusable, >>> >>> >>>fsck.reiser4 --build-sb is supposed to fix evth. what goes wrong? >> >>sorry I didn't replied earlier, but I didn't have a spare disk >>available. here it goes. 40GB partition was mkfs'ed with 1.0.0, >>populated somehow (about 32k files, 400MB), then fsck --build-sb from >>1.0.4 was run: I think I didn't run mkfs 1.0.4. I once tried debugfs.reiser4 -C on the test partition before fsck, as I had run it on one of my live partitions previously, because I originally thought it does the migration (the partition seems to have survived). Can this be the cause too? Is it still possible to migrate such partition to 1.0.4 or I should do full backup & dd if=/dev/zero /dev/hdXX & mkfs & restore? -- Jindrich Makovicka ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: reiser4progs 1.0.4 2005-03-19 18:03 ` Jindrich Makovicka @ 2005-03-21 13:30 ` Vitaly Fertman 0 siblings, 0 replies; 11+ messages in thread From: Vitaly Fertman @ 2005-03-21 13:30 UTC (permalink / raw) To: Jindrich Makovicka; +Cc: reiserfs-list [-- Attachment #1: Type: text/plain, Size: 1338 bytes --] On Saturday 19 March 2005 21:03, Jindrich Makovicka wrote: > Vitaly Fertman wrote: > > On Friday 18 March 2005 21:59, Jindrich Makovicka wrote: > > > >>Vitaly Fertman wrote: > >> > >>>>so 1.0.3 & 1.0.4 bail out. Using fsck.reiser4 --build-sb from > >>>>reiser4progs 1.0.3 rendered the filesystem created under 1.0.0 unusable, > >>> > >>> > >>>fsck.reiser4 --build-sb is supposed to fix evth. what goes wrong? > >> > >>sorry I didn't replied earlier, but I didn't have a spare disk > >>available. here it goes. 40GB partition was mkfs'ed with 1.0.0, > >>populated somehow (about 32k files, 400MB), then fsck --build-sb from > >>1.0.4 was run: > > I think I didn't run mkfs 1.0.4. I once tried debugfs.reiser4 -C on the which progs version debugfs was from? > test partition before fsck, as I had run it on one of my live partitions > previously, because I originally thought it does the migration (the > partition seems to have survived). Can this be the cause too? Is it it should not, there were found fs super block backups of some previous fs on the device you were fscking. > still possible to migrate such partition to 1.0.4 or I should do full > backup & dd if=/dev/zero /dev/hdXX & mkfs & restore? the patch should be able to fix fs metadata. Run fsck.reiser4 --build-fs --nomkid <device> -- Thanks, Vitaly Fertman [-- Attachment #2: reiser4progs-nomkid.patch --] [-- Type: text/x-diff, Size: 1702 bytes --] ===== progs/fsck/fsck.c 1.160 vs edited ===== --- 1.160/progs/fsck/fsck.c 2005-02-10 13:18:59 +03:00 +++ edited/progs/fsck/fsck.c 2005-03-21 14:36:06 +03:00 @@ -148,6 +148,7 @@ static errno_t fsck_init(fsck_parse_t *d {"bitmap", required_argument, 0, 'B'}, {"unused", no_argument, NULL, 'u'}, {"oldfs", no_argument, NULL, 'O'}, + {"nomkid", no_argument, NULL, 'N'}, {0, 0, 0, 0} }; @@ -161,7 +162,7 @@ static errno_t fsck_init(fsck_parse_t *d return USER_ERROR; } - while ((c = getopt_long(argc, argv, "L:VhnqafU:b:r?dB:plo:c:uyO", + while ((c = getopt_long(argc, argv, "L:VhnqafU:b:r?dB:plo:c:uyON", options, &option_index)) >= 0) { switch (c) { @@ -238,6 +239,9 @@ static errno_t fsck_init(fsck_parse_t *d case 'O': aal_set_bit(&data->options, FSCK_OPT_OLD); break; + case 'N': + aal_set_bit(&data->options, FSCK_OPT_OLD); + break; } } @@ -534,6 +538,7 @@ int main(int argc, char *argv[]) { fsck_opt(&parse_data, FSCK_OPT_WHOLE) << REPAIR_WHOLE | fsck_opt(&parse_data, FSCK_OPT_OLD) << REPAIR_WHOLE | fsck_opt(&parse_data, FSCK_OPT_OLD) << REPAIR_NO_MKID | + fsck_opt(&parse_data, FSCK_OPT_NOMKID) << REPAIR_NO_MKID | fsck_opt(&parse_data, FSCK_OPT_YES) << REPAIR_YES; repair.bitmap_file = parse_data.bitmap_file; ===== progs/fsck/fsck.h 1.28 vs edited ===== --- 1.28/progs/fsck/fsck.h 2005-01-17 14:57:42 +03:00 +++ edited/progs/fsck/fsck.h 2005-03-21 14:33:42 +03:00 @@ -40,7 +40,8 @@ typedef enum fsck_options { FSCK_OPT_RO = 0x3, FSCK_OPT_DEBUG = 0x4, FSCK_OPT_WHOLE = 0x5, - FSCK_OPT_OLD = 0x6 + FSCK_OPT_OLD = 0x6, + FSCK_OPT_NOMKID = 0x7 } fsck_options_t; typedef struct fsck_parse { ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2005-03-21 13:30 UTC | newest] Thread overview: 11+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2005-02-20 10:44 reiser4progs 1.0.4 Vitaly Fertman 2005-02-21 13:10 ` Ookhoi 2005-02-21 13:59 ` Vitaly Fertman 2005-02-21 17:01 ` Ookhoi 2005-02-22 20:08 ` Sander 2005-02-21 14:35 ` Jindrich Makovicka 2005-02-21 16:49 ` Vitaly Fertman 2005-03-18 18:59 ` Jindrich Makovicka 2005-03-19 14:23 ` Vitaly Fertman 2005-03-19 18:03 ` Jindrich Makovicka 2005-03-21 13:30 ` Vitaly Fertman
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.