All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mendel Mobach <mendel@mobach.nl>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "mtd@infradead.org" <mtd@infradead.org>
Subject: Re: Errors with M-Systems' DOC v MD2200 D16 and ext2
Date: Tue, 13 Feb 2001 14:24:08 +0100	[thread overview]
Message-ID: <3A893578.DB8FA7B4@mobach.nl> (raw)
In-Reply-To: 19636.981968145@redhat.com

David Woodhouse wrote:
> 
> mendel@mobach.nl said:
> >  With the 2800 I've got no problems but with the  2200 I've got
> > problems and get some very strange kernel messages
> 
> Running out of free blocks to write to - again. This has happened to a few
> people. I'm confused. I put a change into the CVS tree to attempt to fix
> this - can you try it? Just drop nftl.c and nftlmount.c from CVS on top of
> the versions in your kernel tree.
I trid this from the latest version of the CVS tree..
($Id: nftl.c,v 1.57 2000/12/01 17:51:54 dwmw2 Exp $)
But I'v got still the same errors
(I build from a clean kernel source tree)

Regards

Mendel Mobach
> 
> --
> dwmw2

-- 
Mendel Mobach aka BugBlue - mendel@mobach.nl - bugblue@dds.nl
ICQ: 40200278 - IRC: BugBlue (ircnet:#ne2000 undernet:#groningen)
/"\                        |   [Student]           
\ /                        |   [IPv6 tester]
 X  ASCII RIBBON CAMPAIGN  |   [coder]
/ \ AGAINST HTML MAIL      |   [Possible security tester]


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  parent reply	other threads:[~2001-02-13 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11 20:33 Errors with M-Systems' DOC v MD2200 D16 and ext2 Mendel Mobach
2001-02-12  8:55 ` David Woodhouse
2001-02-12 16:24   ` Vipin Malik
2001-02-13 13:24   ` Mendel Mobach [this message]
2001-02-13 14:04     ` David Woodhouse

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=3A893578.DB8FA7B4@mobach.nl \
    --to=mendel@mobach.nl \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.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.