From: Alex Zarochentsev <zam@namesys.com>
To: Henning Westerholt <henning-04@die.informatik.uni-siegen.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Problem with the latest auto snapshot
Date: Tue, 15 Jun 2004 08:34:32 +0400 [thread overview]
Message-ID: <20040615043432.GV8091@backtop.namesys.com> (raw)
In-Reply-To: <200406150055.50380.henning-04@die.informatik.uni-siegen.de>
On Tue, Jun 15, 2004 at 12:55:50AM +0200, Henning Westerholt wrote:
> Am Montag, 14. Juni 2004 20:22 schrieb Alex Zarochentsev:
> > On Sat, Jun 12, 2004 at 09:31:25PM +0200, Henning Westerholt wrote:
> > Thanks for the report.
> >
> > do you use SMP, RAID, LVM ?
>
> No.
>
> > > After some few disk operation a process try to access some data on the
> > > partition, and hung forever. I got the following log entries:
>
> > Were there reiser4 messages in the log before "[nikita-2219]... Failed to
> > initialize dir for..."?
>
> No other messages, sorry.
>
> > > [snip...]
> > >
> > The latest officially released reiser4 utils are not aware of recent stat
> > data extensions. That can explain "item has wrong length" errors.
> > However, that does not explain "points to the already used block" errors
> > :(.
>
> Thank you for the explanation. Is the reiser4progs-0.5.5 release aware of
> these extensions?
yes.
>
> Best regards,
>
> Henning
--
Alex.
prev parent reply other threads:[~2004-06-15 4:34 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
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 [this message]
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=20040615043432.GV8091@backtop.namesys.com \
--to=zam@namesys.com \
--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.