From: Mikael Pettersson <mikpe@csd.uu.se>
To: Alexander Viro <viro@math.psu.edu>
Cc: Jens Axboe <axboe@suse.de>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.37 broke the floppy driver
Date: Mon, 23 Sep 2002 22:04:05 +0200 [thread overview]
Message-ID: <15759.29621.741797.479861@kim.it.uu.se> (raw)
In-Reply-To: <Pine.GSO.4.21.0209231507370.3948-100000@weyl.math.psu.edu>
Alexander Viro writes:
>
>
> On Mon, 23 Sep 2002, Mikael Pettersson wrote:
>
> > With O100-get_gendisk-C38 the oops is cured, but the floppy size is
> > still wrong. Freshly booted, dd if=/dev/fd0H1440 bs=72k of=/dev/null
> > reads only 720K instead of 1440K. Same thing on write: trying to
> > write more than 720K results in an ENOSPC error.
>
>
> Arrrgh. O/O101-floppy_sizes-C38 and it's also my fsckup - missed the
> size in kilobytes/size in sectors. Fortunately that kind of crap is
> over - blk_size[] is no more...
With that patch the /dev/fd0H1440 device now seems to work. However,
the /dev/fd0 (autosensing) device gets its very first read or write
after boot wrong. For example, dd if=/dev/fd0 bs=8k count=1 of=/dev/null
only reads 4096 bytes, and likewise a write will only write 4096 bytes
before reporting ENOSPC. Accesses after the first work though.
next prev parent reply other threads:[~2002-09-23 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 13:05 2.5.37 broke the floppy driver Mikael Pettersson
2002-09-23 14:52 ` Jens Axboe
[not found] ` <Pine.GSO.4.21.0209231104090.3948-100000@weyl.math.psu.edu>
2002-09-23 18:53 ` Mikael Pettersson
2002-09-23 19:09 ` Alexander Viro
2002-09-23 20:04 ` Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-21 23:01 Mikael Pettersson
2002-09-22 18:37 ` Thomas Molina
2002-09-23 9:10 ` Jens Axboe
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=15759.29621.741797.479861@kim.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).