From: Michael Zhu <mylinuxk@yahoo.ca>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "dd" collapsed the loop device
Date: Mon, 14 Jan 2002 13:40:10 -0500 (EST) [thread overview]
Message-ID: <20020114184010.66277.qmail@web14908.mail.yahoo.com> (raw)
In-Reply-To: <20020114111843.P26688@lynx.adilger.int>
That means that I couldn't access /dev/fd0 directly
when I use it via loopback? Is there any way that I
can use to avoid this accident erase?
Michael
--- Andreas Dilger <adilger@turbolabs.com> wrote:
> On Jan 14, 2002 12:54 -0500, Michael Zhu wrote:
> > Hello,everyone,I have a problem when I used the
> loop
> > device. I don't know whether is a loop device bug.
>
> User bug.
>
> > I used the following commands to connect the loop
> device
> > with the floppy disk device.
> >
> > losetup -e xor /dev/loop0 /dev/fd0
> > mke2fs /dev/loop0
> > mount /dev/loop0 /floppy
> >
> > Then I copy something to the floppy and read it
> back.
> > Everything is OK. It works perfectly.
>
> Great.
>
> > The problem was happened when I try to copy
> something
> > directly from the /dev/fd0. I use the following
> > demand.
> >
> > dd if=test.c of=/dev/fd0
> >
> > The output of the upper command is:
> > 50+1 records in
> > 50+1 records out
> >
> > Then I used the "ls /floppy". I found nothing
> copied
> > to the floppy.
>
> Well, this is wrong for several reasons:
> 1) don't access /dev/fd0 when you use it via
> loopback, use /dev/loop0
> 2) don't use "dd" to copy a file, use "cp"
> 3) don't write into the device, but the filesystem
> instead:
> cp test.c /floppy
>
> > Then I used "umount /floppy" to umount the floppy
> disk
> > device. After that I used the following command to
> try
> > to mount the floppy disk again.
> >
> > mount /dev/loop0 /floppy
> >
> > It returned an error. Say:
> >
> > mount: wrong fs type. bad option. bad superblock
> on
> > /dev/loop0. or too many mounted file systems
> >
> > It seemed that the "dd if=test.c of=/dev/fd0"
> > corrupted the data on the floppy disk. What is
> wrong?
>
> Because test.c is not a filesystem, and you have
> overwritten
> the filesystem on /dev/fd0 with junk. This is not a
> bug
> in the loop driver.
>
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
>
______________________________________________________________________
Web-hosting solutions for home and business! http://website.yahoo.ca
next prev parent reply other threads:[~2002-01-14 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 17:54 Michael Zhu
2002-01-14 18:18 ` Andreas Dilger
2002-01-14 18:40 ` Michael Zhu [this message]
2002-01-14 20:06 ` Andreas Dilger
2002-01-14 18:09 Jesse Pollard
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=20020114184010.66277.qmail@web14908.mail.yahoo.com \
--to=mylinuxk@yahoo.ca \
--cc=adilger@turbolabs.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
all inboxes | Powered by JetHome®