All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:00:14 +0400	[thread overview]
Message-ID: <20030331120014.C25533@namesys.com> (raw)
In-Reply-To: <20030331074957.GD22731@cherenkov.orbis-terrarum.net>

Hello!

On Sun, Mar 30, 2003 at 11:49:57PM -0800, Robin H. Johnson wrote:
> > Can you please make a metadata dump for us?
> > "debugreiserfs -p /dev/hdb1 | bzip2 -9c >metadata.bz2" and make this file
> > available for us to download.
> Stderr output of debugreiserfs here:
> http://www.orbis-terrarum.net/~robbat2/reiserfs/debugreiserfs.run

"bread: Cannot read the block (18)."
Well, now this is something.
Do you have I/O errors messages in kernel logs, or do you know another reason for
it to fail reading 18th block?
Perhaps try to run "badblocks -b 4096" to find out if there are more blocks
that cannot be read?

> > Thank you.
> No, most definitely thank you. Now I have more ammunition against my boss
> as to why Open Source is better. You guys really rock. I'd never get a
> response from any other vendor this quickly (even though we pay some of
> them a fair sum).

We accept money too ;)

> A question for you, so I can support things. Is there a list somewhere
> of features requested, and how much you money you want to be paid to add
> them in? Especially the smaller features (hint hint).

Well, there is http://namesys.com/support.html , as of features, usually
we expect customers to come up with features they need. If you lack something
in reiserfs and you are willing to pay, we can implement it.
If you are happy with the current features-set, why to pay for features that
would be never used?

Bye,
    Oleg

  reply	other threads:[~2003-03-31  8:00 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 [this message]
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
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=20030331120014.C25533@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.