From: Vipin Malik <vmalik@danielind.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mendel@mobach.nl, "mtd@infradead.org" <mtd@infradead.org>
Subject: Re: Errors with M-Systems' DOC v MD2200 D16 and ext2
Date: Mon, 12 Feb 2001 10:24:23 -0600 [thread overview]
Message-ID: <3A880E37.E5D3DFC8@danielind.com> (raw)
In-Reply-To: 19636.981968145@redhat.com
David,
I got something similar. I'm (I think) using the latest versions from CVS
(nftl.c is ver. 1.66 and
nftlmount.c is ver. 1.12). I just did a cvs update and no new versions came
down.
Here is my situation:
I have a DOC2000 32MB w/ 0x4000 (16k) erase size.
This causes nftl_format to bail out as it explicitely checks for an erase
size of 0x2000 (8k) before it does anything.
Since not having much to loose, I removed that check and went ahead and
formatted the disk anyway. It did not complain.
I could then modprobe in docprobe (After removing the module after the
format). This time, it detected AND installed the NFTL device under
/dev/nftla.
I could then fdisk it and create a partition on it, create a fs on (ext2
with mke2fs) and mount it.
My question is: Why was the explicit check being done? Are there any traps
"lurking" for me now that I have removed the check and formatted my disk with
nftl_format?
While copying data to the disk (cp -a /bin /mnt/doc2000 etc.) I would get
the data to copy, but after a few seconds (I guess when the cache is flushed
to disk) I would get a bunch of ext2-fs errors like:
end_request: I/O error, dev 5d:01 (unknown) sector 28
EXT2-fs error (device nftl(93,1)): ext2_write_inode: unable to read inode
block - inode=73, block=14
....
...
repeat above for inodes 74...80 rest of error same (same sector (28), block
=14).
I then unmounted the fs and did an e2fsck on /dev/nftl1
I then got error messages regarding short reads reading block 14 (on sector
28). Same problem as above.
Is this related to the format kludge that I did or something else?
Thanks
Vipin
Vipin Malik
Sr. Design Engr.
Daniel Industries
Houston, TX
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.
>
> --
> dwmw2
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-02-12 15:58 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 [this message]
2001-02-13 13:24 ` Mendel Mobach
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=3A880E37.E5D3DFC8@danielind.com \
--to=vmalik@danielind.com \
--cc=dwmw2@infradead.org \
--cc=mendel@mobach.nl \
--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.