Prev: Changing HostID of a Solaris 10 Zone
Next: ddi_remove_minor_node not working
From: Darren Dunham on 12 Dec 2008 13:12
Cydrome Leader <presence(a)mungepanix.com> wrote:
>> Which is the procedure above, yes? I don't know what "formated them in
>> the SAN" means.
>
> formatted them in the SAN is supposed to the SAN was told to completely erase anything on the LUN.

Ah. Most folks only care about this because they're trying to keep the
existing data on the disk. So destroying the data is to be avoided.

If the LUN is zeroed, I've never seen any Solaris machine have some sort
of "memory" about the old size. Even without a reboot "format" is good
about resetting that.
--
Darren
From: Cydrome Leader on 13 Dec 2008 16:14
Darren Dunham <ddunham(a)taos.com> wrote:
> Cydrome Leader <presence(a)mungepanix.com> wrote:
>>> Which is the procedure above, yes? I don't know what "formated them in
>>> the SAN" means.
>>
>> formatted them in the SAN is supposed to the SAN was told to completely erase anything on the LUN.
>
> Ah. Most folks only care about this because they're trying to keep the
> existing data on the disk. So destroying the data is to be avoided.
>
> If the LUN is zeroed, I've never seen any Solaris machine have some sort
> of "memory" about the old size. Even without a reboot "format" is good
> about resetting that.

I think the issue stemmed from re-using luns and then growing them on the
SAN- say a previous 10GB lun was grown on the san to 20GB and whatever was
on the old 10GB confused solaris into not seeing the full LUN size.

I wasn't able to "clear" this from solaris, and just had to do a format on
the SAN to blow away whatever was there first.

removing the disk device and adding it again didn't seem to ever help.
First  |  Prev  | 
Pages: 1 2
Prev: Changing HostID of a Solaris 10 Zone
Next: ddi_remove_minor_node not working