read_pnode: error -22 reading pnode at XX:YYYYY

[Rick Johnson]

We were able to gather more debug this time when the error reoccurred. 
I thought I'd post it, just in case something jumps out.  The strange 
thing is that 'num' seems to have a value that resembles an address.  In 
the example below, num is set to 0xC72EB990.  That's been true every 
time we've seen any debug.  Maybe it doesn't mean anything.

Thanks for taking a look.

UBIFS DBG (pid 30): get_znodes_to_commit: committing 135 znodes
UBIFS DBG (pid 30): alloc_idx_lebs: need about 0 empty LEBS for TNC commit
UBIFS DBG (pid 30): ubifs_lpt_lookup_dirty: LEB 8007, free 120832, dirty 
8192, flags 48
UBIFS DBG (pid 30): ubifs_change_lp: LEB 8007, free 96256, dirty 9656, 
flags 48
UBIFS DBG (pid 30): ubifs_lpt_lookup_dirty: LEB 8007, free 120832, dirty 
8192, flags 48
UBIFS DBG (pid 30): ubifs_save_dirty_idx_lnums: found 1 dirty index LEBs
UBIFS DBG (pid 30): ubifs_save_dirty_idx_lnums: dirtiest index LEB is 
106 with dirty 39616 and free 0
UBIFS DBG (pid 30): ubifs_tnc_start_commit: number of index LEBs 2
UBIFS DBG (pid 30): ubifs_tnc_start_commit: size of index 112520
UBIFS DBG (pid 30): ubifs_lpt_start_commit:
UBIFS error (pid 30): dbg_chk_pnode: pnode num -953239152 expected 1980 
parent num 2029 iip 0
UBIFS error (pid 30): do_commit: commit failed, error -22
UBIFS warning (pid 30): ubifs_ro_mode: switched to read-only mode, error -22