"get_cnode failed" error

"get_cnode failed" error

[Alexandre Ratti]

Hello,


I got a "get_cnode failed" error while running a script on a large ReiserFS 
partition (120 GB). Snippet from /var/syslog is included below. The system 
did not crash. I did not find any other error in the system log.

When the error happened, the system was running a Linux 2.4.18 kernel 
(compiled with source package from Debian stable). System is Debian Woody. 
I've just moved to a 2.4.19 kernel.

I checked the partition with reiserfsck. No corruption found.

The FS looks OK, but I'm curious. What does this error mean? It is serious?


Thanks.

Alexandre

----------
Dec 10 00:15:01 p120 /USR/SBIN/CRON[7356]: (backup) CMD 
(/usr/local/bin/roller.py)
Dec 10 00:18:39 p120 kernel:  <0>get_cnode failed!
Dec 10 00:18:40 p120 kernel: invalid operand: 0000
Dec 10 00:18:40 p120 kernel: CPU:    0
Dec 10 00:18:40 p120 kernel: EIP:    0010:[reiserfs_panic+41/88]    Not tainted
Dec 10 00:18:40 p120 kernel: EFLAGS: 00010282
Dec 10 00:18:40 p120 kernel: eax: 00000015   ebx: c0215ada   ecx: 
c087e000   edx: c118da80
Dec 10 00:18:40 p120 kernel: esi: c13be000   edi: 00000000   ebp: 
c13be000   esp: c087fe30
Dec 10 00:18:40 p120 kernel: ds: 0018   es: 0018   ss: 0018
Dec 10 00:18:40 p120 kernel: Process cp (pid: 7360, stackpage=c087f000)
Dec 10 00:18:40 p120 kernel: Stack: c0212f5a c02909e0 c0215ada c087fe54 
c087ff2c c20d7140 c01813d9 c13be000
Dec 10 00:18:40 p120 kernel:        c0215ada 0141411a c20d7140 c087fe98 
c087ff08 c016cfb0 ffffffff 00000000
Dec 10 00:18:40 p120 kernel:        c016d11b c087ff2c c13be000 c20d7140 
c087feb0 c0392460 c0392460 c087ff2c
Dec 10 00:18:40 p120 kernel: Call Trace: [journal_mark_dirty+501/772] 
[update_st at_data+224/232] [reiserfs_update_sd+355/380] 
[reiserfs_link+199/256] [vfs_link+137/188]
Dec 10 00:18:41 p120 kernel:    [sys_link+212/308] [sys_lstat64+100/112] 
[system_call+51/64]
Dec 10 00:18:41 p120 kernel:
Dec 10 00:18:41 p120 kernel: Code: 0f 0b 68 e0 09 29 c0 85 f6 74 11 31 c0 
66 8b 46 08 50 e8 88
----------

Re: "get_cnode failed" error

[Oleg Drokin]

Hello!

On Tue, Dec 10, 2002 at 08:55:08PM +0100, Alexandre Ratti wrote:

> The FS looks OK, but I'm curious. What does this error mean? It is serious?

This error means there was some journaling code screwup. So FS panicked
before it could do any harm to on-disk data.
What does your script does with cp? Do you have at least some aproximate ideas
on what it copied and from where to where?

> Dec 10 00:18:39 p120 kernel:  <0>get_cnode failed!
> Dec 10 00:18:40 p120 kernel: invalid operand: 0000
> Dec 10 00:18:40 p120 kernel: CPU:    0
> Dec 10 00:18:40 p120 kernel: EIP:    0010:[reiserfs_panic+41/88]    Not 
> tainted
> Dec 10 00:18:40 p120 kernel: EFLAGS: 00010282
> Dec 10 00:18:40 p120 kernel: eax: 00000015   ebx: c0215ada   ecx: 
> c087e000   edx: c118da80
> Dec 10 00:18:40 p120 kernel: esi: c13be000   edi: 00000000   ebp: 
> c13be000   esp: c087fe30
> Dec 10 00:18:40 p120 kernel: ds: 0018   es: 0018   ss: 0018
> Dec 10 00:18:40 p120 kernel: Process cp (pid: 7360, stackpage=c087f000)
> Dec 10 00:18:40 p120 kernel: Stack: c0212f5a c02909e0 c0215ada c087fe54 
> c087ff2c c20d7140 c01813d9 c13be000
> Dec 10 00:18:40 p120 kernel:        c0215ada 0141411a c20d7140 c087fe98 
> c087ff08 c016cfb0 ffffffff 00000000
> Dec 10 00:18:40 p120 kernel:        c016d11b c087ff2c c13be000 c20d7140 
> c087feb0 c0392460 c0392460 c087ff2c
> Dec 10 00:18:40 p120 kernel: Call Trace: [journal_mark_dirty+501/772] 
> [update_st at_data+224/232] [reiserfs_update_sd+355/380] 
> [reiserfs_link+199/256] [vfs_link+137/188]
> Dec 10 00:18:41 p120 kernel:    [sys_link+212/308] [sys_lstat64+100/112] 
> [system_call+51/64]
> Dec 10 00:18:41 p120 kernel:
> Dec 10 00:18:41 p120 kernel: Code: 0f 0b 68 e0 09 29 c0 85 f6 74 11 31 c0 
> 66 8b 46 08 50 e8 88

Bye,
    Oleg

Re: "get_cnode failed" error

[Alexandre Ratti]

Hi Oleg,


At 10:26 11/12/2002 +0300, Oleg Drokin wrote:
>On Tue, Dec 10, 2002 at 08:55:08PM +0100, Alexandre Ratti wrote:
> > The FS looks OK, but I'm curious. What does this error mean? It is serious?
>
>This error means there was some journaling code screwup. So FS panicked 
>before it could do any harm to on-disk data.
>What does your script does with cp? Do you have at least some aproximate 
>ideas on what it copied and from where to where?

Yes, this is a backup script in Python. It first duplicate an existing 
directory tree into a new tree using hard links, then it synchronise the 
new tree with files located on another server using rsync. This create an 
incremental backup. See [1] for theory and [2] for code.

[1] http://www.mikerubel.org/computers/rsync_snapshots/
[2] http://web2.airmail.net/lelie/roller.py

I think the script was running "cp -al old_dir new_dir" to duplicate a 
directory tree (16 GB) on the same partition. This is a large (120 GB) 
partition I use to back up files; it is 30% full.

The script ran 99 times without any glitch. Yesterday, after the error, I 
upgraded the system to 2.4.19 and I ran the script again; it ran with no 
error.


Cheers.

Alexandre


> > Dec 10 00:18:39 p120 kernel:  <0>get_cnode failed!
> > Dec 10 00:18:40 p120 kernel: invalid operand: 0000
> > Dec 10 00:18:40 p120 kernel: CPU:    0
> > Dec 10 00:18:40 p120 kernel: EIP:    0010:[reiserfs_panic+41/88]    Not
> > tainted
> > Dec 10 00:18:40 p120 kernel: EFLAGS: 00010282
> > Dec 10 00:18:40 p120 kernel: eax: 00000015   ebx: c0215ada   ecx:
> > c087e000   edx: c118da80
> > Dec 10 00:18:40 p120 kernel: esi: c13be000   edi: 00000000   ebp:
> > c13be000   esp: c087fe30
> > Dec 10 00:18:40 p120 kernel: ds: 0018   es: 0018   ss: 0018
> > Dec 10 00:18:40 p120 kernel: Process cp (pid: 7360, stackpage=c087f000)
> > Dec 10 00:18:40 p120 kernel: Stack: c0212f5a c02909e0 c0215ada c087fe54
> > c087ff2c c20d7140 c01813d9 c13be000
> > Dec 10 00:18:40 p120 kernel:        c0215ada 0141411a c20d7140 c087fe98
> > c087ff08 c016cfb0 ffffffff 00000000
> > Dec 10 00:18:40 p120 kernel:        c016d11b c087ff2c c13be000 c20d7140
> > c087feb0 c0392460 c0392460 c087ff2c
> > Dec 10 00:18:40 p120 kernel: Call Trace: [journal_mark_dirty+501/772]
> > [update_st at_data+224/232] [reiserfs_update_sd+355/380]
> > [reiserfs_link+199/256] [vfs_link+137/188]
> > Dec 10 00:18:41 p120 kernel:    [sys_link+212/308] [sys_lstat64+100/112]
> > [system_call+51/64]
> > Dec 10 00:18:41 p120 kernel:
> > Dec 10 00:18:41 p120 kernel: Code: 0f 0b 68 e0 09 29 c0 85 f6 74 11 31 c0
> > 66 8b 46 08 50 e8 88