public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@shiny.it>
To: Jurgen Kramer <GTM.Kramer@inter.nl.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: 2048 byte/sector problems with kernel 2.4
Date: Wed, 04 Apr 2001 11:24:22 +0200 (CEST)	[thread overview]
Message-ID: <XFMail.010404112422.pochini@shiny.it> (raw)
In-Reply-To: <3ACA41D6.83718034@inter.nl.net>


> I recently acquired a 1.3GB MO drive. When I use small (230MB and 540MB)
>
> MO disks which have normal 512 bytes/sector it all works flawlessly but
> as soon
> as a put in a 1.3GB disk which uses the 2048 bytes/sector format it all
> goes
> wrong. As soon as I write something to the disk by issuing a cp command
> the command
> just eats 99% CPU time and does not write a single byte to disk (it
> seems).

Hmm, I have no problems with 640MB disks with 2KB/sector (bot normal and
"overwrite" media). This  night I'll try with a 1.2GB disk. I'll let
you know.

> Is this a known problem ?

Only with FAT fs AFAIK. ext2 should work fine (or at least it works
fine for me since 2.1.153).

> I also tried it with 2.2.18 there it works but it seems to be utterly
> slow.

Yes, it's a request merging problem, fixed in 2.4.


Bye.
    Giuliano Pochini ->)|(<- Shiny Network {AS6665} ->)|(<-


  parent reply	other threads:[~2001-04-04  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-03 21:34 2048 byte/sector problems with kernel 2.4 Jurgen Kramer
2001-04-03 21:58 ` Alan Cox
2001-04-03 22:48   ` Harvey Fishman
2001-04-04  9:24 ` Giuliano Pochini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-04  4:37 John William
2001-04-04 19:39 ` Giuliano Pochini

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=XFMail.010404112422.pochini@shiny.it \
    --to=pochini@shiny.it \
    --cc=GTM.Kramer@inter.nl.net \
    --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