From: Hans Reiser <reiser@namesys.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: David Dabbs <david@dabbs.net>, reiserfs-list@namesys.com
Subject: Re: mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error
Date: Wed, 04 Aug 2004 01:59:13 -0700 [thread overview]
Message-ID: <4110A561.9050200@namesys.com> (raw)
In-Reply-To: <4110A38E.6070905@namesys.com>
Vladimir V. Saveliev wrote:
> Hello
>
> Hans Reiser wrote:
>
>> David Dabbs wrote:
>>
>>> I was running mongo when the following occurred:
>>>
>>> cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error
>>> cp: cannot stat `/mnt/testfs/testdir0-0-0/f93': Input/output error
>>> cp: cannot stat `/mnt/testfs/testdir0-0-0/f94': Input/output error
>>> cp: cannot stat `/mnt/testfs/testdir0-0-0/f95': Input/output error
>>> cp: cannot stat `/mnt/testfs/testdir0-0-0/f97': Input/output error
>>>
>>>
>>> I found the following in the log:
>>>
>>> Aug 3 21:59:58 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:58 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:58 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:58 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:58 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:58 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:58 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:58 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:58 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:58 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:58 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:58 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:58 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:59 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:59 linux kernel: reiser4[cp(10066)]: key_warning
>>> (fs/reiser4/plugin/object.c:97)[nikita-717]:
>>> Aug 3 21:59:59 linux kernel: WARNING: Error for inode 661097 (-5)
>>> Aug 3 21:59:59 linux kernel: reiser4[cp(10066)]:
>>> write_sd_by_inode_common
>>> (fs/reiser4/plugin/object.c:480)[nikita-2221]:
>>> Aug 3 21:59:59 linux kernel: WARNING: Failed to save sd for 661097: -5
>>> Aug 3 21:59:59 linux kernel: reiser4[cp(10066)]: create_child_common
>>> (fs/reiser4/plugin/dir/dir.c:499)[nikita-2219]:
>>> Aug 3 21:59:59 linux kernel: WARNING: Failed to create sd for 661097
>>> Aug 3 21:59:59 linux kernel: reiser4[cp(10066)]: cbk_level_lookup
>>> (fs/reiser4/search.c:1033)[vs-3533]:
>>> Aug 3 21:59:59 linux kernel: WARNING: Keys are inconsistent. Fsck?
>>> Aug 3 21:59:59 linux kernel: reiser4[cp(10066)]: key_warning
>>>
>>> I had been switching back and forth between computers via a kvm
>>> switch. I
>>> attempted to reproduce the error by rerunning the benchmark and
>>> figddling
>>> with the switch, but was not able to see the same behavior.
>>>
>>> Running with latest auto-snapshot and reiser4fsprogs.
>>>
>>> David
>>>
>>>
>>>
>>>
>>>
>>>
>> Well, it seems you found a bug just as we were about to ship. Sigh.
>>
>>
>
> Hans, should we solve this before sending reiser4 to Andrew?
>
>
>
>
>
If it is due to 4k stacks, then find a way to ensure that use of reiser4
turns off 4k stacks before sending to Andrew.
Hans
next prev parent reply other threads:[~2004-08-04 8:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 6:55 mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error David Dabbs
2004-08-04 8:40 ` Hans Reiser
2004-08-04 8:51 ` Vladimir V. Saveliev
2004-08-04 8:59 ` Hans Reiser [this message]
2004-08-04 12:51 ` Vladimir V. Saveliev
2004-08-04 18:38 ` mjt
2004-08-04 21:47 ` Hans Reiser
2004-08-04 22:46 ` Christophe Saout
2004-08-04 23:57 ` Hans Reiser
2004-08-05 0:06 ` Christophe Saout
2004-08-05 0:14 ` Lamont R. Peterson
2004-08-05 1:44 ` Hans Reiser
2004-08-05 2:24 ` Carl-Daniel Hailfinger
2004-08-05 13:38 ` Chris Mason
2004-08-04 14:14 ` David Dabbs
2004-08-04 17:38 ` Hans Reiser
2004-08-04 17:46 ` Chris Mason
2004-08-04 18:24 ` David Dabbs
2004-08-04 10:02 ` mjt
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 17:41 David Dabbs
2004-08-04 18:11 ` Hans Reiser
2004-08-04 18:29 ` David Dabbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4110A561.9050200@namesys.com \
--to=reiser@namesys.com \
--cc=david@dabbs.net \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.