All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zarochentsev <zam@namesys.com>
To: Spam <spam@tnonline.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Repacker cause fs corruption:
Date: Tue, 14 Sep 2004 14:11:20 +0400	[thread overview]
Message-ID: <20040914101120.GF2252@backtop.namesys.com> (raw)
In-Reply-To: <981213141.20040914120831@tnonline.net>

On Tue, Sep 14, 2004 at 12:08:31PM +0200, Spam wrote:
> 
> > On Tue, Sep 14, 2004 at 10:59:08AM +0200, Spam wrote:
> >> 
> >>   I tried the resier4 repacker yesterday on a 2GB device that I use
> >>   for /usr/portage in Gentoo. This morning I found these errors in the
> >>   kernel log:
> 
> > Thanks for the report.  
> 
> > How did you start the repacker?  which direction did you run it in?
> 
>   The direction is "0". I started by issuing:
>   echo 1 >/sys/fs/reiser4/loop0/repacker/start

It looks like the repacker triggers a bug in reiser4.  the forward run does not
modify reiser4 nodes by itself.

>   ~S
> 
> >> 
> >> ##########################################################
> >> 
> >> Repacker: I am alive, pid = 32717
> >> reiser4[k_reiser4_repac(32717)]: renew_sibling_link
> >> (fs/reiser4/tree_walk.c:441)[nikita-3532]:
> >> WARNING: Sibling nodes on the different levels: 1 != 1
> >> reiser4 repacker: 659 formatted node(s) processed, 170984
> >> unformatted node(s) processed, ret = -5
> 
 

-- 
Alex.

  reply	other threads:[~2004-09-14 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14  8:59 Repacker cause fs corruption: Spam
2004-09-14  9:42 ` Alex Zarochentsev
2004-09-14 10:08   ` Spam
2004-09-14 10:11     ` Alex Zarochentsev [this message]
2004-09-14 14:26       ` Spam

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=20040914101120.GF2252@backtop.namesys.com \
    --to=zam@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=spam@tnonline.net \
    /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.