From: Hans Reiser <reiser@namesys.com>
To: Kevin <coggy@redefine.org>
Cc: Yury Umanets <umka@namesys.com>, reiserfs-list@namesys.com
Subject: Re: access beyond end of device
Date: Sun, 16 Jun 2002 00:07:14 +0400 [thread overview]
Message-ID: <3D0B9E72.8040209@namesys.com> (raw)
In-Reply-To: 71556690578.20020615113756@redefine.org
Kevin wrote:
>I'll give it a shot. So far I've only seen that one file generate the
>error, so hopefully I can just tiptoe over it and back everything else
>up. I'll let you know how it goes. Thanks.
>
>
>
>>Anyway you may backup your data and try to rebuild tree by fsck.
>>
>>
>
>
>
>
>
You might want to backup using ddrescue on the device.....
--
Hans
next prev parent reply other threads:[~2002-06-15 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 18:03 access beyond end of device Kevin
2002-06-15 18:13 ` Yury Umanets
2002-06-15 18:37 ` Kevin
2002-06-15 20:07 ` Hans Reiser [this message]
2002-06-16 5:45 ` Kevin
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 18:04 Access " Luiz Fernando N. Capitulino
2007-07-31 18:15 ` Luiz Fernando N. Capitulino
2007-08-01 0:12 ` Alan Cox
2007-08-01 14:17 ` Luiz Fernando N. Capitulino
2007-08-01 16:03 ` Alan Cox
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=3D0B9E72.8040209@namesys.com \
--to=reiser@namesys.com \
--cc=coggy@redefine.org \
--cc=reiserfs-list@namesys.com \
--cc=umka@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.