From: Ric Wheeler <rwheeler@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Matthew Wilcox <matthew@wil.cx>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
Jim Meyering <jim@meyering.net>,
linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Matt Domsch <Matt_Domsch@Dell.com>
Subject: Re: tools support for non-512 byte sector sizes
Date: Tue, 29 Jul 2008 14:54:16 -0400 [thread overview]
Message-ID: <488F6758.8080907@redhat.com> (raw)
In-Reply-To: <yq13alsr0g0.fsf@sermon.lab.mkp.net>
Martin K. Petersen wrote:
>>>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:
>>>>>>
>
> James> The problem, which ata_ram also suffers, is that the tools we
> James> most need to test are the ones for manipulating non volatile
> James> characteristics (like partition tables). We'd really like the
> James> disk contents to survive reboot for this ...
>
> Yeah, I should add that I wanted persistence too. I went through a
> whole stack (well, 5-6 or so) fibre channel drives from various
> vendors and attempted to low-level format them to 4KB sectors. Most
> of them laughed in my face. One of them tried to comply and
> irreparably confused its firmware in the process.
>
> Just yesterday I received a couple of prototype drives in the mail.
> I'll ask the vendor whether they support 4KB and if so I'll give them
> a whirl.
>
Isn't this a great use case for a SCSI target device where our target
can be a software disk on a remote host? What is missing for us to put
something like that together?
ric
next prev parent reply other threads:[~2008-07-29 18:54 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 [this message]
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
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=488F6758.8080907@redhat.com \
--to=rwheeler@redhat.com \
--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=martin.petersen@oracle.com \
--cc=matthew@wil.cx \
/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).