search for: journal_recover

...S: 00010282 eax: 00000074 ebx: cffe3c80 ecx: ca5b6000 edx: 0000003a esi: cb34eec0 edi: c40a5640 ebp: c8f697e0 esp: c5125f14 ds: 0018 es: 0018 ss: 0018 Whilst booting after the crash the following output was recorded while mounting the ext3 filsystems; JFS DEBUG: (recovery.c, 255): journal_recover: JFS: recovery, exit status 0, recovered transactions 13283215 to 13283259 JFS DEBUG: (recovery.c, 257): journal_recover: JFS: Replayed 477 and revoked 0/0 blocks EXT3-fs: 30:05: 3 orphan inodes deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with journal data mode. EXT3-fs: mounted...

...locks: bit already cleared for block 4466464 EXT3-fs warning (device sd(8,49)): empty_dir: bad directory (dir #2933557) - no `.' or `..' EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 4466464 EIP: 0010:[<c01564a5>]JFS DEBUG: (recovery.c, 255): journal_recover: JFS: recovery, exit status 0, recovered transactions 35634 to 35641 EFLAGS: 00010282 eax: 00000070 ebx: e9173c80 ecx: c0250808 edx: f87dc000 esi: dff81a40 edi: ccc57d40 ebp: ccc57d40 esp: f8491db0 ds: 0018 es: 0018 ss: 0018 Process nfsd (pid: 615, process nr: 40, stackpage=f849100...

...f course :-). If I want to alleviate this problem with the first boot, I can change the root filesystem type in fstab to ext3, install the e2fsprogs-1.20.WIP.sct-20001207.i386.rpm (so that I have an fsck.ext3) but then the system complains with: /: recovering journal JFS DEBUG: (recovery.c, 254): journal_recover: JFS: recovery, exit status 0, recovered transactions 1 to 4 JFS DEBUG: (recovery.c, 256): journal_recover: JFS: Replayed 16 and revoked 0/0 blockes Warning... fsck.ext3 for device /dev/hda5 exited with singal 11. fsck.ext3: Bad magic number in super-block while trying to re-open / when booting up...

...overy map is not empty, but must master $RECOVERY lock now (6968,7):dlm_do_recovery:524 (6968) Node 1 is the Recovery Master for the Dead Node 0 for Domain F59B45831EEA41F384BADE6C4B7A932B (12281,2):ocfs2_replay_journal:1004 Recovering node 0 from slot 0 on device (8,33) (fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0, recovered transactions 66251376 to 66251415 (fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 3176 and revoked 0/0 blocks kjournald starting. Commit interval 5 seconds We restarted the nfsd on node #1: (seems OK) nfsd: non-standard errno: -512 nfsd: non-sta...

...remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features - journal.c: journal_recover Please check which of these changes do make sense. Signed-off-by: Adrian Bunk <bunk at stusta.de> --- fs/jbd/journal.c | 41 ++++++++++++++++++----------------------- fs/jbd/revoke.c | 3 ++- include/linux/jbd.h | 3 --- 3 files changed, 20 insertions(+), 27 deletions(-)...

...needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL: - journal.c: journal_recover Signed-off-by: Adrian Bunk <bunk at stusta.de> --- fs/jbd/journal.c | 34 ++++++++++++++-------------------- fs/jbd/revoke.c | 3 ++- include/linux/jbd.h | 1 - 3 files changed, 16 insertions(+), 22 deletions(-) --- linux-2.6.12-rc6-mm1-full/include/linux/jbd.h.old 2005-06...

...following unused global functions: - journal.c: __journal_internal_check - journal.c: journal_ack_err - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features - journal.c: journal_recover - journal.c: journal_ack_err Please check which of these changes do make sense. Signed-off-by: Adrian Bunk <bunk at stusta.de> --- fs/jbd/journal.c | 28 ++++++++++++++-------------- fs/jbd/revoke.c | 3 ++- include/linux/jbd.h | 4 ---- 3 files changed, 16 insertions(+)...

...- cut here -- cut here -- cut here -- cut here -- Then on the reboot, the boot message included this: -- cut here -- cut here -- cut here -- cut here -- cut here -- EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. (recovery.c, 253): journal_recover: JBD: recovery, exit status 0, recovered tran sactions 20383 to 20655 (recovery.c, 255): journal_recover: JBD: Replayed 5021 and revoked 37/134 blocks kjournald starting. Commit interval 5 seconds EXT3-fs: md(9,0): orphan cleanup on readonly fs ext3_orphan_cleanup: truncating inode 100113 to 894...

...mounted. but when I mount the filesystem on the slave, I see the following messages in /var/log/messages: EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. (fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0, recovered transactions 99610 to 100072 (fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 12498 and revoked 589/918 blocks kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. since I test this, the master server had occassional problem...

...lock mastery can begin Mar 8 07:23:49 groupwise-1-mht kernel: kjournald starting. Commit interval 5 seconds Mar 8 07:23:49 groupwise-1-mht kernel: (4431,0):ocfs2_replay_journal:1176 Recovering node 2 from slot 1 on device (253,0) Mar 8 07:23:55 groupwise-1-mht kernel: (fs/jbd/recovery.c, 255): journal_recover: JBD: recovery, exit status 0, recovered transactions 599034 to 599035 Mar 8 07:23:55 groupwise-1-mht kernel: (fs/jbd/recovery.c, 257): journal_recover: JBD: Replayed 8 and revoked 0/0 blocks Mar 8 07:23:55 groupwise-1-mht kernel: kjournald starting. Commit interval 5 seconds Mar 8 07:25:51 gro...