From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sd: do not set changed flag on all unit attention conditions
Date: Fri, 27 Jul 2012 12:16:04 +0200 [thread overview]
Message-ID: <50126A64.9040206@suse.de> (raw)
In-Reply-To: <1342562390.3039.100.camel@dabdike.int.hansenpartnership.com>
On 07/17/2012 11:59 PM, James Bottomley wrote:
> On Tue, 2012-07-17 at 12:36 -0400, Christoph Hellwig wrote:
>> On Tue, Jul 17, 2012 at 10:11:57AM +0100, James Bottomley wrote:
>>> There's no such thing in the market today as a removable disk that's
>>> resizeable. Removable disks are for things like backup cartridges and
>>> ageing jazz drives. Worse: most removeable devices today are USB card
>>> readers whose standards compliance varies from iffy to non existent.
>>> Resizeable disks are currently the province of storage arrays.
>>
>> The virtual disks exported by aacraid are both marked removable and
>> can be resized.
>
> So what are properties of these things? ... or is this just an instance
> of a RAID manufacturer hacking around a problem by adding a removable
> flag?
>
Presumably.
The general intention is to automatically catch any disk resizing.
As the SCSI stack (used to) ignore these things that was their way
of working around it.
Curiously, though; the aacraid driver is the only one doing this,
plus the process is quite involved (using a proprietary application
for doing so etc).
None of the FC driver do this, despite the fact that resizing a disk
is even easier here.
I even tried to remove that line once, but then got told off by then
Adaptec that I would break their apps.
Since then there's a patch in the SLES kernel for adding a module
option switching off this behaviour.
We should ask Adaptec/PMC-Sierra here.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2012-07-27 10:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 16:06 [PATCH] sd: do not set changed flag on all unit attention conditions Paolo Bonzini
2012-07-16 16:18 ` James Bottomley
2012-07-16 17:20 ` Paolo Bonzini
2012-07-17 7:45 ` James Bottomley
2012-07-17 8:34 ` Paolo Bonzini
2012-07-17 8:40 ` James Bottomley
2012-07-17 8:54 ` Paolo Bonzini
2012-07-17 9:11 ` James Bottomley
2012-07-17 9:28 ` Paolo Bonzini
2012-07-17 12:21 ` James Bottomley
2012-07-17 12:31 ` Paolo Bonzini
2012-07-17 13:32 ` James Bottomley
2012-07-17 16:36 ` Christoph Hellwig
2012-07-17 16:47 ` Paolo Bonzini
2012-07-17 16:50 ` Christoph Hellwig
2012-07-17 18:45 ` Mike Christie
2012-07-17 18:49 ` Mike Christie
2012-07-17 21:12 ` Paolo Bonzini
2012-07-17 21:59 ` James Bottomley
2012-07-27 10:16 ` Hannes Reinecke [this message]
2012-07-25 12:09 ` Hannes Reinecke
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=50126A64.9040206@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pbonzini@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