On Fri, 2006-06-23 at 02:51 +0300, Jussi Judin wrote: > After that I upgraded to Debian patched kernel 2.6.16-14 and to reiser4 > patch 2.6.16-4 for that kernel and ran fsck.reiser4. Then I got errors > like this in kern.log after a while: > > WARNING: Error for inode 1731981 (-2) > reiser4[nfsd(3817)]: key_warning > (fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]: > WARNING: Error for inode 1703086 (-2) > reiser4[nfsd(3818)]: key_warning > (fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]: > WARNING: Error for inode 1726433 (-2) > reiser4[nfsd(3818)]: key_warning > (fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]:
I too am getting these warnings: Jul 27 06:28:15 prometheus kernel: reiser4[find(10770)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]: Jul 27 06:28:15 prometheus kernel: WARNING: Error for inode 3922698 (-2) [REPEATED 17 TIMES] Jul 27 06:28:15 prometheus kernel: reiser4[find(10770)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]: Jul 27 06:28:15 prometheus kernel: WARNING: Error for inode 3922697 (-2) [REPEATED 17 TIMES] Jul 27 06:28:16 prometheus kernel: reiser4[find(10770)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]: Jul 27 06:28:16 prometheus kernel: WARNING: Error for inode 3922696 (-2) [REPEATED 17 TIMES] ... ... Jul 27 06:28:19 prometheus kernel: reiser4[find(10770)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: Jul 27 06:28:19 prometheus kernel: WARNING: Keys are inconsistent. Fsck? Jul 27 06:28:19 prometheus kernel: reiser4[find(10770)]: key_warning (fs/reiser4/plugin/file_plugin_common.c:513)[nikita-717]: Jul 27 06:28:19 prometheus kernel: WARNING: Error for inode 3922690 (-5) System information: Kernel: 2.6.16.20 Patches: reiser4-for-2.6.16-4.patch.gz Reiser4progs: 1.0.5 This machine is used for recording TV using a DVB card, compresses the files, and serves them via NFS and Samba. Until recently, the system ran kernel linux-2.6.11.6, and performed flawlessly for over a year. After upgrading the kernel, I upgraded reiser4progs, and fscked all reiser4 partitions. No errors were found. The system is run on a UPS, and does not have a history of memory or IO trouble. I am currently investigating why the samba shares have failed, and noticed this in the log. I believe problem/bug this is related to the kernel upgrade, rather than some random corruption because it seem too much of a coincidence to happen so soon after upgrading the kernel. Any help/advice is greatly appreciated. ...back to the samba investigation. Many Thanks, -- Craig Shelley EMail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
