From: Kevin <coggy@redefine.org>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: access beyond end of device again
Date: Tue, 25 Jun 2002 06:08:21 +0000 (UTC) [thread overview]
Message-ID: <1141375583133.20020626230935@redefine.org> (raw)
In-Reply-To: <20020625095409.A6209@namesys.com>
> Reformatted as in mkreiserfs?
Correct. That's the only change I've made to it though. Would
rebuilding the superblocks help? Last time it happened, I rebuilt the
tree, and it deleted the files that I had trouble with. So it's hard
to say if it really fixed it, or if it was just waiting for me to
write to that spot again. I'm about to run the Maxtor diags on the
drive and do a factory recertification, just to make sure.
next prev parent reply other threads:[~2002-06-25 6:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 14:35 access beyond end of device again Kevin
2002-06-24 14:35 ` Oleg Drokin
2002-06-24 14:45 ` Dirk Mueller
2002-06-24 14:49 ` Oleg Drokin
2002-06-24 16:46 ` Hans Reiser
2002-06-25 5:11 ` Oleg Drokin
2002-06-24 16:59 ` Dirk Mueller
2002-06-24 14:37 ` Robert Brockway
2002-06-24 14:48 ` Oleg Drokin
2002-06-24 14:49 ` Robert Brockway
2002-06-24 17:30 ` Kevin
2002-06-25 5:54 ` Oleg Drokin
2002-06-25 6:08 ` Kevin [this message]
2002-06-25 6:15 ` Oleg Drokin
2002-06-25 7:46 ` Kevin
2002-06-25 7:55 ` Oleg Drokin
2002-06-25 8:07 ` Kevin
2002-06-25 8:13 ` Oleg Drokin
2002-06-25 8:46 ` Hans Reiser
2002-06-25 8:58 ` Oleg Drokin
2002-06-25 9:06 ` Hans Reiser
2002-06-25 9:41 ` Oleg Drokin
[not found] ` <353485111.20020627013212@redefine.org>
2002-06-25 23:22 ` Kevin
2002-06-26 4:53 ` Oleg Drokin
2002-07-10 18:04 ` Tim Small
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=1141375583133.20020626230935@redefine.org \
--to=coggy@redefine.org \
--cc=green@namesys.com \
--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.