From: James Bottomley <James.Bottomley@steeleye.com>
To: Stefan Voelkel <Stefan.Voelkel@millenux.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: LUN resizing
Date: 25 Nov 2003 09:43:02 -0600 [thread overview]
Message-ID: <1069774983.2061.28.camel@mulgrave> (raw)
In-Reply-To: <1069708054.26088.127.camel@lt-sv>
On Tue, 2003-11-25 at 03:34, Stefan Voelkel wrote:
> I have a Linux box connected to a Fibre SAN. Now I'd like to resize one
> LUN and tell my Linux box what happened. In other words can I _live_
> resize a SCSI disk?
>
> [ let's not talk about which filesystems are capable of live
> resizing :) ]
>
> * Is this possible at all, eg does the SCSI Standard include
> something to enable a device to tell the host about the changed
> geometry (SENSE DATA, ...) ?
The pull command is READ_CAPACITY. For pushing this information,
there's nothing really standard, although some type of proprietary AEN
could be adapted.
> * Is it possible with Linux, eg does the block layer/scsi layer
> support it? any problems with the partition code?
> * If there are problems, are they solveable, any plans on working
> on them or is already someone working on this?
You simply do
echo 1 > /sys/bus/scsi/<device>/rescan
It will re-read the capacity and partition table (as long as the device
is unmounted and none of the partitions open).
James
next prev parent reply other threads:[~2003-11-25 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 9:34 LUN resizing Stefan Voelkel
2003-11-25 15:43 ` James Bottomley [this message]
2003-11-25 16:11 ` James Bottomley
2003-11-26 9:45 ` Stefan Voelkel
2003-11-26 9:48 ` Christoph Hellwig
2003-11-28 10:08 ` Stefan Voelkel
2003-11-28 10:23 ` Christoph Hellwig
2003-11-28 16:18 ` James Bottomley
2003-11-25 19:34 ` Lincoln Dale
-- strict thread matches above, loose matches on Subject: below --
2003-11-28 22:29 christophe varoqui
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=1069774983.2061.28.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Stefan.Voelkel@millenux.com \
--cc=linux-scsi@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 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.