All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Traby <stefan@hello-penguin.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adam Radford <aradford@3WARE.com>,
	"'Stefan Traby'" <stefan@hello-penguin.com>,
	Larry McVoy <lm@bitmover.com>,
	linux-kernel@vger.kernel.org, tytso@thunk.org
Subject: Re: 2.4.5 data corruption
Date: Tue, 19 Jun 2001 22:06:02 +0200	[thread overview]
Message-ID: <20010619220602.B27273@stefan.sime.com> (raw)
In-Reply-To: <53B208BD9A7FD311881A009027B6BBFB9EACFE@siamese> <E15CQkR-0006Tj-00@the-village.bc.nu>
In-Reply-To: <E15CQkR-0006Tj-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Jun 19, 2001 at 08:01:11PM +0100

On Tue, Jun 19, 2001 at 08:01:11PM +0100, Alan Cox wrote:

> > Sometimes it takes either the kernel tree or our website some time to get 
> > in 'sync' with the latest driver version. The latest driver version is 
> > 1.02.00.007.  
> > 
> > There may be DAC960 like /proc support at some point for GUI haters.
> 
> Publishing enough info to let people write a GPL non gui management tool would
> be a win in itself

And on-disk superblock documentation.
I want to be able to recover from a single disk-failure and
power-fail conditions in all cases, not just in 50%.

3ware is simply unable to recover from some situations where recovery
is possible (reported to them at least two times).

Maybe they will understand this sometimes. I think that I have
a right to get my data back if it's possible.
It was extremly hard to explain them LGPL and the
fact that they violated it; so I expect not too much.

To not publish the specs is really extremly unfair;
it just shows how they care about my data.

-- 

  ciao - 
    Stefan

  reply	other threads:[~2001-06-19 20:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53B208BD9A7FD311881A009027B6BBFB9EACFE@siamese>
2001-06-19 19:01 ` 2.4.5 data corruption Alan Cox
2001-06-19 20:06   ` Stefan Traby [this message]
2001-06-12 20:17 Larry McVoy
2001-06-13 15:09 ` Nathan Straz
2001-06-13 23:39 ` Chris Mason
2001-06-14 18:20 ` Alan Cox
2001-06-14 22:27   ` Eugene Crosser
2001-06-14 22:49     ` Alan Cox
2001-06-15 19:54       ` Eugene Crosser
2001-06-15 20:17         ` Larry McVoy
2001-06-15 12:02     ` Russell Leighton
2001-06-19  3:00   ` Stefan Traby
2001-06-19  7:49     ` Alan Cox
2001-06-19  9:13   ` Pedro M. Rodrigues

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=20010619220602.B27273@stefan.sime.com \
    --to=stefan@hello-penguin.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=aradford@3WARE.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=tytso@thunk.org \
    /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.