From: mjt@nysv.org
To: Henning Westerholt <henning-04@die.informatik.uni-siegen.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Problem with the latest auto snapshot
Date: Sat, 12 Jun 2004 22:46:49 +0300 [thread overview]
Message-ID: <20040612194649.GF4990@nysv.org> (raw)
In-Reply-To: <200406122131.25974.henning-04@die.informatik.uni-siegen.de>
On Sat, Jun 12, 2004 at 09:31:25PM +0200, Henning Westerholt wrote:
>After some few disk operation a process try to access some data on the
>partition, and hung forever. I got the following log entries:
[snip]
>I could not kill the process, a reboot was needed.
I had something similar, with an old auto-snapshot, but I didn't get
those log messages. It also repeated on, 2004.06.09 under some mild load,
compiling .11-19.36 and doing a dist-upgrade. I'll dig out some traces
if it still repeats with this kernel, as they seem to have systematically
receeded.
I wonder if we have something different concerning debug?
mjt@shrike:~$ zgrep -i reiser4 /proc/config.gz
CONFIG_REISER4_FS=y
# CONFIG_REISER4_FS_SYSCALL is not set
CONFIG_REISER4_LARGE_KEY=y
# CONFIG_REISER4_CHECK is not set
CONFIG_REISER4_USE_EFLUSH=y
# CONFIG_REISER4_COPY_ON_CAPTURE is not set
# CONFIG_REISER4_BADBLOCKS is not set
mjt@shrike:~$
>Any operation on the fs fail with a input/ output error. I try to fix this
>with fsck, but it found no errors. I attached the output from the first fsck
>runs.
>I'll rebuild the partition tomorow, and give it another try..
I just ran a bonnie++ without any problems. The machine isn't under any
real load, though.
top - 22:42:30 up 58 min, 16 users, load average: 3.29, 2.37, 1.42
I'm just watching Threshold's Critical Energy live DVD, so all that is all
bonnie's doing.
Version 1.03 ------Sequential Output------ --Sequential Input- --Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
shrike 1G 11969 50 38699 19 16239 16 13620 62 29511 16 166.2 1
------Sequential Create------ --------Random Create--------
-Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
16 16636 62 +++++ +++ 5849 62 6758 64 +++++ +++ 5921 64
shrike,1G,11969,50,38699,19,16239,16,13620,62,29511,16,166.2,1,16,16636,62,+++++,+++,5849,62,6758,64,+++++,+++,5921,64
--
mjt
next prev parent reply other threads:[~2004-06-12 19:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 19:31 Problem with the latest auto snapshot Henning Westerholt
2004-06-12 19:46 ` mjt [this message]
2004-06-13 13:37 ` Henning Westerholt
2004-06-13 13:43 ` mjt
2004-06-14 9:13 ` Henning Westerholt
2004-06-14 9:21 ` mjt
2004-06-14 18:08 ` Hans Reiser
2004-06-15 8:06 ` Alex Zarochentsev
2004-06-15 8:14 ` Alex Zarochentsev
2004-06-15 16:50 ` Henning Westerholt
2004-06-15 17:44 ` Alex Zarochentsev
2004-06-15 18:19 ` Henning Westerholt
2004-06-14 18:22 ` Alex Zarochentsev
2004-06-14 22:55 ` Henning Westerholt
2004-06-15 4:34 ` Alex Zarochentsev
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=20040612194649.GF4990@nysv.org \
--to=mjt@nysv.org \
--cc=henning-04@die.informatik.uni-siegen.de \
--cc=reiserfs-list@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.