linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	Ric Wheeler <rwheeler@redhat.com>,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	Jim Meyering <jim@meyering.net>,
	linux-kernel@vger.kernel.org, Martin Petersen <mkp@mkp.net>,
	Jeff Garzik <jeff@garzik.org>, Matt Domsch <Matt_Domsch@Dell.com>
Subject: Re: tools support for non-512 byte sector sizes
Date: Wed, 30 Jul 2008 09:51:03 +0400	[thread overview]
Message-ID: <48900147.7030106@vlnb.net> (raw)
In-Reply-To: <1217356645.6103.48.camel@localhost.localdomain>

James Bottomley wrote:
> On Tue, 2008-07-29 at 12:26 -0600, Matthew Wilcox wrote:
>> On Tue, Jul 29, 2008 at 01:24:31PM -0400, Ric Wheeler wrote:
>>> Jim pinged me about the use case for having our tool chain (parted 
>>> specifically) support devices with non-512 bytes sectors.
>> Matt Domsch spoke with me about this at OLS.  I took that opportunity,
>> and I'll take this one, to pimp my ata-ram driver which allows you to
>> alter the sector sizse to whatever you want:
>>
>> http://git.kernel.org/?p=linux/kernel/git/willy/misc.git;a=shortlog;h=ata-ram
>>
>> I'll admit to having not tested it with anything other than 512, but it
>> ought to support 4096 byte sectors just fine.  I haven't looked at what
>> would be required to support 520-byte sectors.
> 
> scsi_debug does exactly the same thing, so it reports anything you tell
> it (Martin Petersen actually added this so he could test with 4k
> sectors).
> 
> The problem, which ata_ram also suffers, is that the tools we most need
> to test are the ones for manipulating non volatile characteristics (like
> partition tables).  We'd really like the disk contents to survive reboot
> for this ...

SCST (http://scst.sf.net) fully supports non-512 bytes sectors up to 
4096. Available target drivers for transports: software iSCSI, FC, 
InfiniBand SRP, parallel SCSI, SAS (not much tested, because of lack of 
hardware). With VDISK dev handler you can use files as a backstorage.

I personally for a long time have been working with 4K sectors, because 
it's better for performance, but so far found the only tool, which 
doesn't support them: disktest.

> James
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  parent reply	other threads:[~2008-07-30  5:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 17:24 tools support for non-512 byte sector sizes Ric Wheeler
2008-07-29 18:21 ` Alan Cox
2008-07-29 18:55   ` Matthew Wilcox
2008-07-29 21:07     ` Alan Cox
2008-07-29 18:26 ` Matthew Wilcox
2008-07-29 18:37   ` James Bottomley
2008-07-29 18:42     ` Matthew Wilcox
2008-07-29 18:44       ` James Bottomley
2008-07-29 18:50         ` Matthew Wilcox
2008-07-29 19:00           ` James Bottomley
2008-07-29 18:48     ` Martin K. Petersen
2008-07-29 18:54       ` Ric Wheeler
2008-07-29 18:56         ` James Bottomley
2008-07-29 23:41           ` FUJITA Tomonori
2008-07-30 13:51       ` Matt Domsch
2008-07-30 17:16         ` Jim Meyering
2008-07-30 17:29           ` Matt Domsch
2008-07-30 17:24             ` Alan Cox
2008-07-30 18:13             ` Theodore Tso
2008-07-30 18:28               ` Ric Wheeler
2008-07-30 18:45                 ` Theodore Tso
2008-08-09 13:21             ` Pavel Machek
2008-08-01 16:11         ` Matthew Wilcox
2008-08-05 16:54           ` Matthew Wilcox
2008-08-05 16:57             ` Matthew Wilcox
2008-08-05 16:57           ` Matt Domsch
2008-07-30  5:51     ` Vladislav Bolkhovitin [this message]
2008-07-29 18:41   ` Martin K. Petersen
2008-07-29 21:54   ` Jeff Garzik
2008-07-29 18:43 ` Moore, Eric
2008-07-29 19:03   ` Martin K. Petersen
2008-07-29 19:14     ` Douglas Gilbert

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=48900147.7030106@vlnb.net \
    --to=vst@vlnb.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=jeff@garzik.org \
    --cc=jim@meyering.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mkp@mkp.net \
    --cc=rwheeler@redhat.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;
as well as URLs for NNTP newsgroup(s).