From: Kir Kostuchenko <kir@users.sf.net>
To: Vitaly Fertman <vitaly@namesys.com>, reiserfs-list@namesys.com
Subject: Re: reiserfsck bug
Date: Thu, 06 May 2004 14:14:54 +0600 [thread overview]
Message-ID: <4099F3FE.5080902@users.sf.net> (raw)
In-Reply-To: <200405061159.59882.vitaly@namesys.com>
Vitaly Fertman wrote:
>Hello,
>
>On Thursday 06 May 2004 00:24, Kir Kostuchenko wrote:
>
>
>> hi, I've got error message from the reiserfsck 'out of disk space',
>>in the rebuild tree mode.
>>
>> I think it's a bug of reiserfsck, I can send you bzip2'ed image of
>>the partition.
>>
>> Please help.
>>
>>
>
>If a file item offset is broken this sometimes looks like some items
>are lost and the hole is inserted, the needed space is proportional to
>the hole size in reiserfs, this is why fsck may run of disk space. The
>standard solution here is to find a larger partition, zero it (or enlarge
>the existent one and zero the added part), make a raw copy of the
>problem partition to it, run reiserfsck --rebuild-sb and then reiserfsck
>--rebuild-tree.
>
>
Thanks.
So, if I only have a file with raw copy of my partition, I should do
something like:
// make 1 gb additional space
# dd if=/dev/zero of=additional_space bs=1000k count=1000
// add to my raw bad partition copy
# cat additional_space >> bad_partition
// map to the loop device
# losetup /dev/loop0 bad_partition
// run reiserfsck with --rebuild-sb
# reiserfsck --rebuild-sb --rebuild-tree /dev/loop0
Am I right?
>Although it could be another reason, if you make the packed metadata:
> debugreiserfs -p /dev/xxx | bzip2 -c > xxx.bz2
>and provide them for downloading, I will investigate if there is some
>bug.
>
If my previous step will cause an error, send metadata to you?
next parent reply other threads:[~2004-05-06 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40994D84.1010901@users.sf.net>
[not found] ` <200405061159.59882.vitaly@namesys.com>
2004-05-06 8:14 ` Kir Kostuchenko [this message]
2004-05-06 9:18 ` reiserfsck bug Vitaly Fertman
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=4099F3FE.5080902@users.sf.net \
--to=kir@users.sf.net \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.