reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Gleb Baryshev <gleb.baryshev@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: fsck.reiser4 (libaal-1.0.5) segfault
Date: Sun, 06 Feb 2011 23:28:09 +0100	[thread overview]
Message-ID: <4D4F2079.2080407@gmail.com> (raw)
In-Reply-To: <4D4B1887.3020306@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Hello.

I have taken a look at your problem on weekends.

Please, apply the attached patch to reiser4progs-1.0.7,
and check your partition again. The patched fsck after
check phase should report about minor corruption and
suggest to repair it with --fix option.

Please, report about results.

Thanks,
Edward.


On 02/03/2011 10:05 PM, Gleb Baryshev wrote:
> 03.02.2011 22:09, Edward Shishkin writes:
>> Sorry, but this file looks corrupted.
>> Could you please try again?
>>
>> Also make sure that packed meta-data are
>> extracted correctly by the following way:
>>
>> #touch meta_tmp
>> #bzcat meta.bz2 | debugfs.reiser4 -U meta_tmp
>
> For some reason, debugfs was adding junk every time - 8 bytes (1B 5B 3F
> 31 30 33 34 68) before 'VRSN'; in other respects the metadata file is
> all right. Finally I ran debugfs from LiveCD and got correct dump:
> http://tootiny.net/813h25
>
> BTW, fsck from LiveCD segfaulted, too.
>
> Gleb
> --
> To unsubscribe from this list: send the line "unsubscribe
> reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: fsck-dont-allocate-unalloc-extents.patch --]
[-- Type: text/plain, Size: 867 bytes --]

Don't try to allocate unallocated extents.

Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
---
 libreiser4/tree.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- reiser4progs-1.0.7.orig/libreiser4/tree.c
+++ reiser4progs-1.0.7/libreiser4/tree.c
@@ -1346,7 +1346,7 @@ errno_t reiser4_tree_adjust(reiser4_tree
 #ifndef ENABLE_MINIMAL
 			res = reiser4_tree_walk_node(tree, tree->root, 
 						     cb_node_adjust,
-						     cb_nodeptr_adjust,
+						     NULL,
 						     cb_node_unload);
 #else
 			res = reiser4_tree_walk_node(tree, tree->root, 
@@ -1586,7 +1586,7 @@ errno_t reiser4_tree_sync(reiser4_tree_t
 	   everything. */
 	if ((res = reiser4_tree_walk_node(tree, tree->root, 
 					  cb_node_adjust,
-					  cb_nodeptr_adjust,
+					  NULL,
 					  cb_node_unload)))
 	{
 		aal_error("Can't save formatted nodes to device.");

  parent reply	other threads:[~2011-02-06 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 21:05 fsck.reiser4 (libaal-1.0.5) segfault Gleb Baryshev
2011-02-03 22:09 ` Edward Shishkin
2011-02-06 22:28 ` Edward Shishkin [this message]
2011-02-07  9:21   ` Gleb Baryshev
2011-02-07 10:27     ` Edward Shishkin
  -- strict thread matches above, loose matches on Subject: below --
2011-02-03  8:20 Gleb Baryshev
2011-02-03 11:33 ` Edward Shishkin
2011-02-03 18:32   ` Gleb Baryshev
2011-02-03 19:09     ` Edward Shishkin

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=4D4F2079.2080407@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=gleb.baryshev@gmail.com \
    --cc=reiserfs-devel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).