Re: Growing a UFS filesystem on an IBM SAN LUN
- From: Cydrome Leader <presence@xxxxxxxxxxxxxx>
- Date: Sat, 13 Dec 2008 21:14:44 +0000 (UTC)
Darren Dunham <ddunham@xxxxxxxx> wrote:
Cydrome Leader <presence@xxxxxxxxxxxxxx> 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.
.
- References:
- Growing a UFS filesystem on an IBM SAN LUN
- From: Mark
- Re: Growing a UFS filesystem on an IBM SAN LUN
- From: Darren Dunham
- Re: Growing a UFS filesystem on an IBM SAN LUN
- From: Cydrome Leader
- Re: Growing a UFS filesystem on an IBM SAN LUN
- From: Darren Dunham
- Re: Growing a UFS filesystem on an IBM SAN LUN
- From: Cydrome Leader
- Re: Growing a UFS filesystem on an IBM SAN LUN
- From: Darren Dunham
- Growing a UFS filesystem on an IBM SAN LUN
- Prev by Date: Re: Install Solaris PXE via tftp server on Windows
- Next by Date: Re: U6 and zfs smb shares
- Previous by thread: Re: Growing a UFS filesystem on an IBM SAN LUN
- Next by thread: ddi_remove_minor_node not working
- Index(es):
Relevant Pages
|