mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: elgaard@agol.dk
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem loopmounting CD on 2.6.0
Date: Fri, 19 Dec 2003 14:00:29 -0800	[thread overview]
Message-ID: <20031219140029.346f2523.rddunlap@osdl.org> (raw)
In-Reply-To: <3FE2F8D4.1030903@agol.dk>

On Fri, 19 Dec 2003 14:10:44 +0100 Niels Elgaard Larsen <elgaard@agol.dk> wrote:

| A similar (probably the same) problem have been reported for cryptoloop.
| With a ISO9660 CD (actually Knoppix) in drive /dev/hdc, no SCSI emulation:
| 
| amigos20:/mnt# losetup /dev/loop5 /dev/hdc
| amigos20:/mnt# mount -r /dev/loop5 /mnt/foo
| 
| Gives kernel output:
| 
| ===
| hdc: cdrom_read_intr: data underrun (2 blocks)
| end_request: I/O error, dev hdc, sector 64
| isofs_fill_super: bread failed, dev=loop5, iso_blknum=16, block=32
| ===
| 
| It works in 2.4.20
| 
| Also
| 
| dd if=/dev/hdc of=/tmp/foo
| losetup /dev/loop5 /tmp/foo
| mount -r /dev/loop5 /mnt/foo
| 
| works

I see differing sector size and block size reports by blockdev
as follows.  Is this OK/expected or does it hint at a problem?

(all without ide-scsi:)

2.6.0, non-loopback case:

# mount
/dev/hdd on /mnt/disk type iso9660 (ro)

[root@gargoyle rddunlap]# blockdev --getss /dev/hdd
2048
[root@gargoyle rddunlap]# blockdev --getbsz  /dev/hdd
2048


2.6.0, loopback case:

I usually see the same error that you reported.
I did mount the cdrom successfully one time, with about 50
error messages like below[1], and saw this blocksize difference:
Is this OK or indicative of a (the) problem?


[root@gargoyle rddunlap]# blockdev --getss /dev/hdd
2048
[root@gargoyle rddunlap]# blockdev --getbsz  /dev/hdd
4096


[1]
hdd: cdrom_read_intr: data underrun (2 blocks)
end_request: I/O error, dev hdd, sector 64
hdd: cdrom_read_intr: data underrun (2 blocks)
end_request: I/O error, dev hdd, sector 68
hdd: cdrom_read_intr: data underrun (2 blocks)
end_request: I/O error, dev hdd, sector 72
...
hdd: cdrom_read_intr: data underrun (2 blocks)
end_request: I/O error, dev hdd, sector 388
hdd: cdrom_read_intr: data underrun (2 blocks)
end_request: I/O error, dev hdd, sector 392
hdd: cdrom_read_intr: data underrun (2 blocks)
end_request: I/O error, dev hdd, sector 396

2.4.2x:

[root@gargoyle rddunlap]# blockdev --getss /dev/hdd
512
[root@gargoyle rddunlap]# blockdev --getbsz  /dev/hdd
2048


--
~Randy
MOTD:  Always include version info.

  reply	other threads:[~2003-12-19 22:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 13:10 Niels Elgaard Larsen
2003-12-19 22:00 ` Randy.Dunlap [this message]
2003-12-22 14:27   ` OGAWA Hirofumi

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=20031219140029.346f2523.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=elgaard@agol.dk \
    --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®