From: Oleg Drokin <green@namesys.com>
To: "Robin H. Johnson" <robbat2@orbis-terrarum.net>
Cc: reiserfs-list@namesys.com
Subject: Re: possible bug - fsck shows perfect results, linux refuses to mount
Date: Mon, 31 Mar 2003 13:24:54 +0400 [thread overview]
Message-ID: <20030331132454.L25533@namesys.com> (raw)
In-Reply-To: <20030331091621.GA23666@cherenkov.orbis-terrarum.net>
Hello!
On Mon, Mar 31, 2003 at 01:16:21AM -0800, Robin H. Johnson wrote:
> > What if you run that debugreiserfs command again and see if it
> > complains about being unable to read 18th block?
> No change in the output of debugreiserfs.
Ok, plase run it under strace, kind of like this:
"strace -o /tmp/out debugreiserfs -p /dev/hdb1 >/dev/null" and
send me this /tmp/out file.
> > > But I suspect that may be a much larger task (and I certianly don't want
> > > my drives and RAID arrays ever getting that full in the first place).
> > Repacker is not that trivialindeed, if you read this list for some
> > time already, you might have noticed discussion in which Hans and
> > Chris have agreed that while repacker is cool and can be implemented,
> > nobody knows what layout for the data should be chosen.
> Nope, I just subscribed to the list today, when I had this problem.
> I've taken the system home for now, I so I can hack on it some more.
> Mostly to find what was causing the reboots previously, but also so this
> can get worked on.
Hmm, I also wonder what happens if you dd the whole partition (/dev/hdb1) to
some file and then run debugreiserfs on that file will it succeed?
If not, then probably you can compress the file and somehow make it available for
download?
If it will succeed, then there is certainly some interaction between harware and
debugreiserfs is going on.
Bye,
Oleg
next prev parent reply other threads:[~2003-03-31 9:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 7:22 possible bug - fsck shows perfect results, linux refuses to mount Robin H. Johnson
2003-03-31 7:34 ` Oleg Drokin
2003-03-31 7:49 ` Robin H. Johnson
2003-03-31 8:00 ` Oleg Drokin
2003-03-31 8:34 ` Soeren Sonnenburg
2003-03-31 8:41 ` Oleg Drokin
2003-03-31 8:48 ` Soeren Sonnenburg
2003-03-31 9:02 ` Oleg Drokin
2003-03-31 8:37 ` Robin H. Johnson
2003-03-31 8:56 ` Oleg Drokin
2003-03-31 9:16 ` Robin H. Johnson
2003-03-31 9:24 ` Oleg Drokin [this message]
2003-03-31 10:17 ` Robin H. Johnson
2003-03-31 10:36 ` Oleg Drokin
2003-03-31 11:13 ` Robin H. Johnson
2003-03-31 11:33 ` Oleg Drokin
2003-03-31 13:57 ` Oleg Drokin
2003-03-31 16:03 ` Hans Reiser
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=20030331132454.L25533@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=robbat2@orbis-terrarum.net \
/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.