From: "Stuart MacDonald" <stuartm@connecttech.com>
To: <linux-kernel@vger.kernel.org>
Subject: [BUG] dd, floppy, 2.5.18
Date: Thu, 6 Jun 2002 14:19:22 -0400 [thread overview]
Message-ID: <02aa01c20d86$ae9e8bc0$294b82ce@connecttech.com> (raw)
# uname -a
Linux moll 2.5.18 #1 SMP Wed May 29 15:18:20 EDT 2002 i686 unknown
[insert floppy]
# dd if=/dev/fd0 of=diskette.image
8+0 records in
8+0 records out
# ls -alF diskette.image
-rw-r--r-- 1 root root 4096 Jun 6 11:49 test
This is obviously wrong. But a second try at it:
# dd if=/dev/fd0 of=diskette.image
2880+0 records in
2880+0 records out
# ls -alF diskette.image
-rw-r--r-- 1 root root 1474560 Jun 6 11:49 test
However:
# tar xvf diskette.image
wget-1.8.1.tar.gz
# cmp wget-1.8.1.tar.gz wget-181.tar.gz
wget-1.8.1.tar.gz wget-181.tar.gz differ: char 7681, line 34
So that's wrong too. This works under RedHat's 2.4.7-10, and has
worked previously in various 2.4 and 2.2 kernels.
I'm willing to help with some testing to figure out the problem; I use
this dd method to make diskette images for customers all the time, and
I will need it fixed for 2.6.x.
Some things I've noticed:
- the 8 records attempt always happens after a new media insertion. To
say it another way, the "good" 2880 attempt only happens on the second
and subsequent attempts on an already inserted floppy.
- I though I'd noticed that this would corrupt the floppy itself, but
have been unable to reproduce. May have been two bad floppies in a row
coincidentally.
..Stu
next reply other threads:[~2002-06-06 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 18:19 Stuart MacDonald [this message]
2002-06-06 18:53 ` [BUG] dd, floppy, 2.5.18 Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 18:48 Mikael Pettersson
2002-06-07 19:02 ` Stuart MacDonald
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='02aa01c20d86$ae9e8bc0$294b82ce@connecttech.com' \
--to=stuartm@connecttech.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox