* [BUG] nikita-1481, nikita-717 and nikita-373 here and there @ 2006-06-22 23:51 Jussi Judin 2006-06-23 10:11 ` Łukasz Mierzwa 2006-08-01 20:39 ` Craig Shelley 0 siblings, 2 replies; 4+ messages in thread From: Jussi Judin @ 2006-06-22 23:51 UTC (permalink / raw) To: reiserfs-list I was using some Debian patched 2.6.16 kernel and reiser4-2.6.16-1 patch for that and suddenly got the error messages attached. The java program in those error messages is doing a huge amount of writes all the time and probably in many threads at the same time. <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 16384 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 32768 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 65536 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 131072 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 262144 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:733)[nikita-373]: WARNING: reiser-2018: Too many iterations. Tree corrupted, or (less likely) starvation occurring.: level: 5, lock_level: 2, stop_level: 1 lock_mode: read, bias: left-slant <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 128 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 256 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 512 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 1024 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 2048 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 4096 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 8192 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 16384 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 32768 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 65536 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 131072 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 262144 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:733)[nikita-373]: WARNING: reiser-2018: Too many iterations. Tree corrupted, or (less likely) starvation occurring.: level: 5, lock_level: 2, stop_level: 1 lock_mode: read, bias: left-slant <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: WARNING: Too many iterations: 128 <4>reiser4[java(4496)]: traverse_tree (fs/reiser4/search.c:700)[nikita-1481]: 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]: The nfsd in question was trying to read the file system and didn't succeed in that. It showed file names but no other information for them. I have ran fsck.reiser4 again but haven't done any heavy writing on that file system for now. The version of fsck.reiser4 and other reiser4progs is 1.0.5-1 (the version in Debian testing). - Jussi Judin ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] nikita-1481, nikita-717 and nikita-373 here and there 2006-06-22 23:51 [BUG] nikita-1481, nikita-717 and nikita-373 here and there Jussi Judin @ 2006-06-23 10:11 ` Łukasz Mierzwa 2006-08-01 20:39 ` Craig Shelley 1 sibling, 0 replies; 4+ messages in thread From: Łukasz Mierzwa @ 2006-06-23 10:11 UTC (permalink / raw) To: Jussi Judin, reiserfs-list@namesys.com Dnia Fri, 23 Jun 2006 01:51:57 +0200, Jussi Judin <jjudin+reiser@iki.fi> napisa³: > I was using some Debian patched 2.6.16 kernel and reiser4-2.6.16-1 patch > for that and suddenly got the error messages attached. The java program > in those error messages is doing a huge amount of writes all the time > and probably in many threads at the same time. > I'm using 2.6.16 + reiser4-2.6.16-4 patch and I just got those errors while running emerge --sync on gentoo: reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9583)]: cbk_level_lookup (fs/reiser4/search.c:961)[vs-3533]: WARNING: Keys are inconsistent. Fsck? reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 128 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 256 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 512 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 1024 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 2048 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 4096 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 8192 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 16384 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 32768 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 65536 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 131072 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:690)[nikita-1481]: WARNING: Too many iterations: 262144 reiser4[rsync(9588)]: traverse_tree (fs/reiser4/search.c:723)[nikita-373]: WARNING: reiser-2018: Too many iterations. Tree corrupted, or (less likely) starvation occurring.: level: 5, lock_level: 1, stop_level: 1 lock_mode: write, bias: exact After running fsck.reiser4 --fix the only corruption found was error in amount of free space ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] nikita-1481, nikita-717 and nikita-373 here and there 2006-06-22 23:51 [BUG] nikita-1481, nikita-717 and nikita-373 here and there Jussi Judin 2006-06-23 10:11 ` Łukasz Mierzwa @ 2006-08-01 20:39 ` Craig Shelley 2006-08-02 14:58 ` Alexander Zarochentsev 1 sibling, 1 reply; 4+ messages in thread From: Craig Shelley @ 2006-08-01 20:39 UTC (permalink / raw) To: reiserfs-list [-- Attachment #1: Type: text/plain, Size: 2763 bytes --] 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: craig@microtron.org.uk Jabber: shell@jabber.earth.li [-- Attachment #2: This is a digitally signed message part --] [-- Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [BUG] nikita-1481, nikita-717 and nikita-373 here and there 2006-08-01 20:39 ` Craig Shelley @ 2006-08-02 14:58 ` Alexander Zarochentsev 0 siblings, 0 replies; 4+ messages in thread From: Alexander Zarochentsev @ 2006-08-02 14:58 UTC (permalink / raw) To: Craig Shelley; +Cc: reiserfs-list Hello, On Wednesday 02 August 2006 00:39, Craig Shelley wrote: > 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 please upgrade to 2.6.17 and reiser4-for-2.6.17-3 or apply the following patch: Index: linux-2.6.16/fs/reiser4/plugin/file/file.c =================================================================== --- linux-2.6.16.orig/fs/reiser4/plugin/file/file.c +++ linux-2.6.16/fs/reiser4/plugin/file/file.c @@ -1633,14 +1633,18 @@ static size_t read_file(hint_t * hint, s /* error happened */ break; - if (coord->between != AT_UNIT) + if (coord->between != AT_UNIT) { /* there were no items corresponding to given offset */ + done_lh(hint->ext_coord.lh); break; + } loaded = coord->node; result = zload(loaded); - if (unlikely(result)) + if (unlikely(result)) { + done_lh(hint->ext_coord.lh); break; + } if (hint->ext_coord.valid == 0) validate_extended_coord(&hint->ext_coord, @@ -1725,13 +1729,15 @@ ssize_t read_unix_file(struct file *file left = size - *off; /* faultin user page */ - result = fault_in_pages_writeable(buf, left > PAGE_CACHE_SIZE ? PAGE_CACHE_SIZE : left); - if (result) { + if(fault_in_pages_writeable(buf, left > PAGE_CACHE_SIZE ? PAGE_CACHE_SIZE : left)) { drop_nonexclusive_access(uf_info); - return RETERR(-EFAULT); + result = RETERR(-EFAULT); + break; } - read = read_file(hint, file, buf, left, off); + read = read_file(hint, file, buf, + left > PAGE_CACHE_SIZE ? PAGE_CACHE_SIZE : left, + off); drop_nonexclusive_access(uf_info); @@ -1748,6 +1754,7 @@ ssize_t read_unix_file(struct file *file count += read; } save_file_hint(file, hint); + done_lh(&hint->lh); kfree(hint); if (count) { Index: linux-2.6.16/fs/reiser4/as_ops.c =================================================================== --- linux-2.6.16.orig/fs/reiser4/as_ops.c +++ linux-2.6.16/fs/reiser4/as_ops.c @@ -350,6 +350,9 @@ int reiser4_releasepage(struct page *pag if (PageDirty(page)) return 0; + if (page_count(page) > 3) + return 0; + /* releasable() needs jnode lock, because it looks at the jnode fields * and we need jload_lock here to avoid races with jload(). */ spin_lock_jnode(node); > 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, -- Alex. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-08-02 14:58 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2006-06-22 23:51 [BUG] nikita-1481, nikita-717 and nikita-373 here and there Jussi Judin 2006-06-23 10:11 ` Łukasz Mierzwa 2006-08-01 20:39 ` Craig Shelley 2006-08-02 14:58 ` Alexander Zarochentsev
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.