public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andries.Brouwer@cwi.nl
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	zzed@cyberdude.com
Subject: Re: [PROBLEM] 2.4.1 can't mount ext2 CD-ROM
Date: Mon, 19 Feb 2001 02:43:30 +0100	[thread overview]
Message-ID: <20010219024330.B8227@suse.de> (raw)
In-Reply-To: <UTC200102182111.WAA170825.aeb@vlet.cwi.nl>
In-Reply-To: <UTC200102182111.WAA170825.aeb@vlet.cwi.nl>; from Andries.Brouwer@cwi.nl on Sun, Feb 18, 2001 at 10:11:36PM +0100

On Sun, Feb 18 2001, Andries.Brouwer@cwi.nl wrote:
>     > Strange. The twelve or so CD readers I have here are all
>     > able to read 512-byte sectors. I am quite willing to believe
> 
>     I think most Plextor and Yamaha do, but it's not guaranteed to
>     be supported. And it definitely won't for ATAPI with ide-scsi.
> 
> Strange. I just used ATAPI with ide-scsi as test. It works.

Yeah it works because sr does read padding on drives that can't dish
out 512b sectors... This is my point.

> Setting hardsect_size to 2048 means: this hardware is unable
> to use smaller blocks, give an error to whoever asks for
> something smaller.

Which is the case for some drives. The error now occurs when ext2
forcibly tries to set the block size.

> Not setting hardsect_size at all means: I have no idea what this
> hardware can do. Now it is up to the user. If the user tries
> something the hardware cannot do, she will get EIO.
> Limiting the user in advance is a bad idea.

Ok agreed, just forcing 2048 is a bit harsh but it was nicer than
letting sr bomb on 512b requests at the time.

-- 
Jens Axboe


  reply	other threads:[~2001-02-19  1:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-18 21:11 [PROBLEM] 2.4.1 can't mount ext2 CD-ROM Andries.Brouwer
2001-02-19  1:43 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-18 19:34 Andries.Brouwer
2001-02-18 20:49 ` Jens Axboe
2001-02-18 17:49 Andries.Brouwer
2001-02-18 19:16 ` Jens Axboe
2001-02-19  1:40   ` Alan Cox
2001-02-19  1:47     ` Jens Axboe
2001-02-19  2:02       ` Alan Cox
2001-02-18 14:26 Jon Forsberg

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=20010219024330.B8227@suse.de \
    --to=axboe@suse.de \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zzed@cyberdude.com \
    /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