From: Spam <spam@tnonline.net>
To: reiserfs-list@namesys.com
Subject: Re: rebuild-tree working for more then 3 days- what to do?
Date: Fri, 7 Jan 2005 13:43:30 +0100 [thread overview]
Message-ID: <1332240552.20050107134330@tnonline.net> (raw)
In-Reply-To: <1105101220.4192.68.camel@tribesman.namesys.com>
> Hello
> On Fri, 2005-01-07 at 15:11, Shoshannah Forbes wrote:
>> On 07/01/2005, at 12:20, Vladimir Saveliev wrote:
>>
>> > I would move the problem hard disk to mashine which has (or can
>> > download) latest reiserfsck
>> > (http://thebsh.namesys.com/pub/reiserfsprogs/reiserfsprogs
>> > -3.6.19.tar.gz),
>> > make sure that it performs I/O of that disk decently (hdparm -t
>> > /dev/problem-disk) and run reiserfsck --rebuild-tree for broken
>> > filesystem there.
>>
>> Thanks for the fast reply.
>> The only other machine I have here is a Mac running OSX. Would it even
>> be possible to do this from a Mac?
>> If not, can anything be done from a LiveCD?
> When you boot off liveCD - do you have a network and place where
> reiserfsprogs can be put and compiled besides that 60gb device with
> broken reiserfs?
> Then boot liveCD, download reiserfsprogs and fsck.
There are liveCD's with reiser4 and reiser4progs. For example: http://lxnay.dnsalias.org/livecd-iso/index.php
~S
next prev parent reply other threads:[~2005-01-07 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 8:50 rebuild-tree working for more then 3 days- what to do? Shoshannah Forbes
2005-01-07 9:02 ` Shoshannah Forbes
2005-01-07 10:20 ` Vladimir Saveliev
2005-01-07 12:11 ` Shoshannah Forbes
2005-01-07 12:33 ` Vladimir Saveliev
2005-01-07 12:43 ` Spam [this message]
2005-01-07 13:03 ` Shoshannah Forbes
2005-01-07 13:13 ` Vladimir Saveliev
2005-01-07 22:29 ` Shoshannah Forbes
2005-01-07 23:35 ` Chris Cox
2005-01-08 4:46 ` Shoshannah Forbes
2005-01-07 12:44 ` Shoshannah Forbes
2005-01-07 13:03 ` Vladimir Saveliev
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 12:57 Yiannis Mavroukakis
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=1332240552.20050107134330@tnonline.net \
--to=spam@tnonline.net \
--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.