All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PATCH] scsi updates for post 2.6.18
Date: Thu, 05 Oct 2006 16:12:24 -0400	[thread overview]
Message-ID: <45256728.2060004@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0610052129020.6619@poirot.grange>

Guennadi Liakhovetski wrote:
> Sure, it WOULD be nice, but I don't know how. The "don't know" refers to 
> the case 16MB block size, my tape supports only 16MB - 1 byte (according 
> to st report). Is there a way to test various block sizes with CDs / 
> hard-disks / ZIP / scanners? Would something with sg_dd work? Looks like 
> it must be only sector size. Can I low-level format a disk with 16M 
> sector?:-)
> 
> Another possibility is to limit the block size at 8MB - I can test that.

I would say, increase it to whatever the max is you can test...

	Jeff



  reply	other threads:[~2006-10-05 20:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 21:01 [GIT PATCH] scsi updates for post 2.6.18 James Bottomley
2006-10-05 19:11 ` Guennadi Liakhovetski
2006-10-05 19:16   ` Jeff Garzik
2006-10-05 19:56     ` Guennadi Liakhovetski
2006-10-05 20:12       ` Jeff Garzik [this message]
2006-10-05 22:12         ` Guennadi Liakhovetski
2006-10-05 23:34       ` Douglas Gilbert
  -- strict thread matches above, loose matches on Subject: below --
2006-09-24  2:37 James Bottomley
2006-09-24  3:30 ` Linus Torvalds
2006-09-24  3:36   ` James Bottomley
2006-09-24  3:46     ` Linus Torvalds
2006-09-24 14:37 ` Douglas Gilbert
2006-09-24 15:34   ` Douglas Gilbert
2006-09-24 16:51     ` James Bottomley

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=45256728.2060004@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.