Netware 6.5 Expanding a LUN

I have a Netware 6.5 SP7 server that we are trying to add space.
It is running on a ProLiant BL460c G1 blade with a QLogic QMH2462 4Gb FC HBA Mezzanine card. My SAN team has expanded the LUN from 1.5TB to 1.75TB but I do not see the additional space on the server. I have rebooted the server twice now. When I go into nssmu and try to create the new partition I do not see the free 250GB of space. Is their a limit on the number of NSS partitions I can have on one device, there is 4 there now. When I look at the device in NSSMU it only shows 1500.00GB capacity. Is there some command that I need to run to get it to do a refresh or rescan that a reboot did not do?
I have the latest Qlogic QL2X00.HAM drivers that I could find dated Dec 8, 2006. The SAN is an EMC Clariion.
Here are my startup.ncf file
LOAD ACPIDRV.PSM
######## End PSM Drivers ########
#LOAD CPQSHD.CDM
######## End CDM Drivers ########
LOAD POWPATH.CDM
LOAD HPQCISS.HAM SLOT=10038
LOAD QL2X00.HAM SLOT=101 /LUNS /ALLPATHS /PORTNAMES /QUALIFIED
LOAD QL2X00.HAM SLOT=102 /LUNS /ALLPATHS /PORTNAMES /QUALIFIED
######## End HAM Drivers ########
Thanks
- jason

Hi.
On 29.09.2011 03:56, jeisenst wrote:
> When I look at the device in NSSMU it only shows 1500.00GB
> capacity.
Sorry, to say, but your SAN team failed. Sometimes the explanations of
such issues is just "human error".
When the *device* after a reboot is still shown as 1500GB, then the
device *is* 1500GB, and the expand just never happened.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

Similar Messages

Expand LUN using Striping method

We have run out of space on one of our Lab Manager Datastores and I need to expand it this weekend. We can't move the data that is in there because they are Thin Provisioned templates w/ linked clones.
My understanding is that I can expand a LUN using Concatenation or Striping. I believe striping results in better performance but I want to make sure that the data on the LUN\datastore I want to expand will not be affected by this expansion. Below is the environment info.
Has anyone expanded a LUN using the Striping method on a LUN presented to VMware Lab Manager? If so are there any other steps after expanding besides Recanning the datastore? IS there any risk to the data?
Clarion CX4-240
Lab Manager 4.0.2
VSphere 4.1 Update 1
ESX 4.0 Update 1
Thanks for any feedback or advice!

Lab Manager itself is only minimally aware of what happens in the fabric layer (storage/ESX).
The key point to know is if the UUID will change. If the UUID changes, you will have some problems ... but this can be resolved.
I have done a soft expand before, and it seemed to work well. Expand the LUN from the storage server, then use the vSphere client to expand the VMFS volume ... this is assuming you have the versions which support doing this function.
Another, less fun way, undeploy all ... make a new LUN and use your storage system to replicate the data into the new VMFS volume.
the UUID will change, but this can be fixed with assistance from tech support (assuming you still have a valid support contract).

NSS and LUN expanding - what you need to know before you migrate

Thought I'd share, since this isn't in any documentation or TID that I
can find.
Before you move to OES2 Linux with NSS or multipathing code or EVMS, you
may want to consider this limitation (IMO, a major limitation if you're
running an Enterprise).
If you SAN allows you to grow/expand a LUN (ie, LUN1 was 50 GB and now
you grow it to 100 GB), you cannot use the new space until you reboot
the server itself. If you're running NCS, then you need to reboot every
node that can host the clustered resource before you can expand the NSS
pool.
The issue is a bug in the devmapper portion of SLES. ANYTHING that uses
devmapper will prevent the further layers (ie, multipathing or EVMS)
from seeing the additional space until you reboot the server.
Obviously rebooting servers in the middle of the day to add more space
affects Enterprise services to your users. As does making them wait
until off-hours before they can write/save any data to the servers. Not
to mention rebooting multiple nodes in your NCS cluster.
Novell won't fix this until SLES 11. Even then (ie, if you implement
OES2 now and can live with the limitation it won't be truly fixed in
SLES 11 if you're using NSS/EVMS), as the limitation will still be in
EVMS in SLES 11. Therefore, you'd have to migrate your data to LVM2 (I
believe that's what Novell is switching to). Yet another major
disruption for your users.
So, if you're thinking about OES2 with NSS/EVMS or multipathing, you may
want to consider the effect this will have to your userbase (ie, how
many times do you want to migrate your data?)
In our case, looks like it's goint to be one migration --- to MS
Windows.

Hi,
General rule, if you think rebooting is NOT an option AND you are not using clustering - you're looking for trouble.
I know I can increase space to my cluster with out kicking my users offline.
Worked for NSS.
Worked for OCFS.
Limitation noted and ignored.
-M
Originally Posted by KittyNoLegs
Thought I'd share, since this isn't in any documentation or TID that I
can find.
Before you move to OES2 Linux with NSS or multipathing code or EVMS, you
may want to consider this limitation (IMO, a major limitation if you're
running an Enterprise).
If you SAN allows you to grow/expand a LUN (ie, LUN1 was 50 GB and now
you grow it to 100 GB), you cannot use the new space until you reboot
the server itself. If you're running NCS, then you need to reboot every
node that can host the clustered resource before you can expand the NSS
pool.
The issue is a bug in the devmapper portion of SLES. ANYTHING that uses
devmapper will prevent the further layers (ie, multipathing or EVMS)
from seeing the additional space until you reboot the server.
Obviously rebooting servers in the middle of the day to add more space
affects Enterprise services to your users. As does making them wait
until off-hours before they can write/save any data to the servers. Not
to mention rebooting multiple nodes in your NCS cluster.
Novell won't fix this until SLES 11. Even then (ie, if you implement
OES2 now and can live with the limitation it won't be truly fixed in
SLES 11 if you're using NSS/EVMS), as the limitation will still be in
EVMS in SLES 11. Therefore, you'd have to migrate your data to LVM2 (I
believe that's what Novell is switching to). Yet another major
disruption for your users.
So, if you're thinking about OES2 with NSS/EVMS or multipathing, you may
want to consider the effect this will have to your userbase (ie, how
many times do you want to migrate your data?)
In our case, looks like it's goint to be one migration --- to MS
Windows.

Unable to expand/extend partition after growing SAN-based iSCSI target

Hello, all. I have odd situation regarding how to expand iSCSI-based partitions.
Here is my setup:
I use the GlobalSAN iSCSI initiator on 10.6.x server (Snow Leopard).
The iSCSI LUN is formatted with the GPT partition table.
The filesystem is Journaled HFS+
My iSCSI SAN has the ability to non-destructively grow a LUN (iSCSI target).
With this in mind, I wanted to experiment with growing a LUN/target on the SAN and then expanding the Apple partition within it using disk utility. I have been unable to do so.
Here is my procedure:
1) Eject the disk (iSCSI targets show up as external hard drives)
2) Disconnect the iSCSI target using the control panel applet (provided by GlobalSAN)
3) Grow the LUN/target on the SAN.
4) Reconnect the iSCSI initiator
5) Expand/extend the partition using Disk Utility to consume the (newly created) free space.
It works until the last step. When I reconnect to the iSCSI target after expanding it on the SAN, it shows up Disk Utility as being larger than it was (so far, so expected). When I go to expand the partition, however, it errors out saying that there is not enough space.
Investigating further, I went the command line and performed a
"diskutil resizeVolume <identifier> limits"
to determine what the limit was to the partition. The limits did NOT reflect the newly-created space.
My suspicion is that the original partition map, since it was created as 100% of the volume, does not allow room for growth despite the fact that the disk suddenly (and, to the system, unexpectedly) became larger.
Is this assumption correct? Is there any way around this? I would like to be able to expand my LUNs/targets (since the SAN can grow with the business), but this has no value if I cannot also extend the partition table to use the new space.
If anyone has any insight, I would greatly appreciate it. Thank you!

I have exactly the same problem that you describe above. My iSCSI LUN was near capacity and therefore i extended the iSCSI LUN from 100G to 150G. No problem so far.
Disk Utility shows the iSCSI device as 150G but i cannot extend the volume to the new size. It gives me the same error (in Dutch).
Please someone help us out !

Growing a LUN in a zpool?

I have a zpool with an EMC/Clariion LUN underneath it. I need to grow the zpool and I would like to grow the size of the existing LUN instead of adding a new LUN. Once the storage folks expand the LUN, can this be done while preserving the zpool? If so what are the steps?

IIRC there is a way to grow the LUN but it requires fiddling with the VTOC and is of course not officially supported.
I think I read it on blogs.sun.com, try googling around for "LUN resizing solaris".
A better method that works would be to create a new LUN in your Clariion, create a mirror and then detach the old LUN.
After (and only after!) detaching the old LUN, your pool will have the new size.
If it is possible for you to go the second way, I suggest to take it, as it is much more secure than fiddling with your live data.

Novell Cluster Services on VMWARE

I am currently running a 3 node cluster (oes2sp2 Linux) connected to an EMC SAN. This cluster was commissioned, fully patched, etc 250 days ago. It's been running smoothly and hasn't missed a beat :-) The nodes are bare-metal installs.
Now I've been tasked with investigating the possibility of virtualizing the nodes using VMWare (and making use of VMotion).
This will give us the ability to have 6 virtual nodes rather than 3 physical nodes.
What is the general feeling of the community with regards to:
1. Virtualizing cluster nodes
2. How complex is the setup on VMWare
3. Could I do a rolling migration from physical to virtual
Many thanks in advance for any comments, tips, advice, etc

On 11.03.2011 14:06, laurabuckley wrote:
>
> Now I've been tasked with investigating the possibility of virtualizing
> the nodes using VMWare (and making use of VMotion).
>
> This will give us the ability to have 6 virtual nodes rather than 3
> physical nodes.
>
> What is the general feeling of the community with regards to:
>
> 1. Virtualizing cluster nodes
> 2. How complex is the setup on VMWare
> 3. Could I do a rolling migration from physical to virtual
lot of talks about this, many things to consider.. here are few atleast;
If you have (or buy) VMware HA and vMotion, do you even need Novell
Cluster Services anymore?
if you want vMotion, you need to use vmdk for storage, which might be an
issue for large volumes.. or not?
For large storage you could use RDM LUNs directly from SAN. But then you
cannot use vMotion or run many nodes (of the same cluster) on one
physical server.
We are running multiple three node OES2 NCS clusters on three VMware
servers, using RDM LUNs from EMC SAN. Did a rolling migration from
physical Netware clusters using the same LUNs.
-sk

CFMX7 - Linux - Novell Cluster Services

I have a 2 node cluster set up with Suse Linux and Novell
Cluster Services. There is a cluster resource of apache that is set
up in the cluster, as well as a shared volume as a cluster
resource. THe apache running as the cluster resource is using the
shared volume for the web root home. Furthermore, apache is running
individually on each node. Can anyone offer any opinions on setting
up CFMX7 in this environment. We are not worried about load
balancing, this is strictly needed for failover. My concerns are
which install config I could be using, Individual Server,
MultiServer, or J2EE? Can we use 1 CFADMIN for both nodes to
minimize the overhead of keeping the configs in sync? During the
install, can we use the cluster resource instance of apache to
install to? My concern here is when we install it on the second
node and point to the shared volume for the web root home, it's
going to have a problem since it already exists? Any input is
appreciated. Thanks.

On 11.03.2011 14:06, laurabuckley wrote:
>
> Now I've been tasked with investigating the possibility of virtualizing
> the nodes using VMWare (and making use of VMotion).
>
> This will give us the ability to have 6 virtual nodes rather than 3
> physical nodes.
>
> What is the general feeling of the community with regards to:
>
> 1. Virtualizing cluster nodes
> 2. How complex is the setup on VMWare
> 3. Could I do a rolling migration from physical to virtual
lot of talks about this, many things to consider.. here are few atleast;
If you have (or buy) VMware HA and vMotion, do you even need Novell
Cluster Services anymore?
if you want vMotion, you need to use vmdk for storage, which might be an
issue for large volumes.. or not?
For large storage you could use RDM LUNs directly from SAN. But then you
cannot use vMotion or run many nodes (of the same cluster) on one
physical server.
We are running multiple three node OES2 NCS clusters on three VMware
servers, using RDM LUNs from EMC SAN. Did a rolling migration from
physical Netware clusters using the same LUNs.
-sk

Increasing Size of ASM.....

Expanding the Lun was quite easy. I happen to increase /dev/sdb from 200G to 250G
I then started the ASM instance and issued following command.
alter diskgroup TTGS_GROUP1 resize all size 50000M;
This is so it did not understand the same disk name '/dev/sdb' . it use to say /dev/sdb not in TTG_GROUP1.
I am unable to locate the new space. What could be the reason.
Thanks
Shiva

Hi
Here are the few commands that you can try, I had used these on a Windows box:
C:\Documents and Settings\gurpartap>sqlplus / as sysdba
SQL*Plus: Release 10.1.0.2.0 - Production on Fri May 11 19:57:11 2007
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Enter value for usr: sys
Enter value for db: +ASM
sys@+ASM>select * from v$instance;
INSTANCE_NUMBER INSTANCE_NAME
HOST_NAME
VERSION STARTUP_T STATUS PAR THREAD# ARCHIVE
LOG_SWITCH_
LOGINS SHU DATABASE_STATUS INSTANCE_ROLE ACTIVE_ST
1 +asm
GURPARTA-MLCJZI
10.1.0.2.0 10-MAY-07 STARTED 0 STOPPED
ALLOWED NO ACTIVE UNKNOWN NORMAL
sys@+ASM>alter diskgroup DGROUP add disk 'c:\asmfiles\disk2';
Diskgroup altered.
sys@+ASM>alter diskgroup DGROUP rebalance power 5;
Diskgroup altered.
sys@+ASM>
ALTER DISKGROUP asm1dg2 RESIZE ALL SIZE 32M;
Can you see the increaased space from Unix in the RAW devices.
Hope this Heps
Regards

Reduce size of LUN that has already been expanded in Diskpart

Hi Guys
As the title suggests i'm looking for help reducing the size of a LUN that has already been expanded.
Recently I was asked to extend a drive on a server. The drive in question was on top of a 600GB LUN connecting over Fibre Channel. So I extended the LUN to 850GB and used DISKPART to extend the drive so it now appears as 850GB within Server 2008.
However, The request was wrong and instead they have asked me to expand a different LUN by 250GB which I've now done. But as you can imagine I would like to reclaim the 250GB that I previously added.
What is the best way to go about this?
I've tested my backups so i'm confident that I can recover the data if something goes wrong but obviously i'd like to avoid that :)
Can I simply shrink the size of the partition in Disk Management and then reduce the size of the LUN on my SAN? or do I need to create a new LUN and move the data onto the new drive?
I can confirm that no new data has been written to this drive since the expansion.
Many thanks
RC

Hi,
It should be depended on SAN.
If it supports to "shrink" a lun without affecting data on it, it will work. If not, it will still damage the data even you shrink the volume in Disk Management first.
As you already have a backup, you can try to shrink the lun on SAN and the worse thing is to restore data from backup.
Of course create a new lun is another workaround to avoiding test on your luns.
If you have any feedback on our support, please send to [email protected]

Can we expand OCFS2 mount point Size by adding additional LUN?

can we expand OCFS2 mount point Size by adding additional LUN?

Looks like it should be possible....see if this helps:
extract from:http://oss.oracle.com/projects/ocfs2/dist/documentation/ocfs2_faq.html
# Can OCFS2 file systems be grown in size?
Yes, you can grow an OCFS2 file system using tunefs.ocfs2. It should be noted that the tool will only resize the file system and not the underlying partition. You can use fdisk(8) (or any appropriate tool for your disk array) to resize the partition.
# What do I need to know to use fdisk(8) to resize the partition?
To grow a partition using fdisk(8), you will have to delete it and recreate it with a larger size. When recreating it, ensure you specify the same starting disk cylinder as before and a ending disk cylinder that is greater than the existing one. Otherwise, not only will the resize operation fail, but you may lose your entire file system. Backup your data before performing this task.
HTH
Thanks
Chandra

Miggui : Expand NetWare Volume fails

Hi,
When I use miggui it fails to expand the NetWare NSS source volume when doing "Configure File System". The volumes are listed on the "Volume Information" tab however they do not expand. This issue does not always happen but it does happen more often than not. I've tested with different source servers and run into the same issue. I have also tested miggui on a different target server and it does not happen on the alternate target server. This leads me to think it is likely a problem with the specific target server. Has anyone else run into this issue? Or do you have any idea how I could troubleshoot this - increasing logging levels etc.
The source servers are running NetWare 6.5 sp8 and the latest nss and tsa patch sets.
The target servers are running OES/Linux 11 sp2.
Cheers,
Ron

Originally Posted by rjneilly
I applied the May 2014 OES11SP2 Scheduled Maintenance Update and Patch 2 for eDir 8.8.8. Rebooted and now all is working as it should. Could be the updates or simply the reboot. Either way, Yay!
Cheers,
Ron
Good to hear you got that sorted Ron!
Also, thanks for feeding that info back info the thread. It might well be a fix included in the latest versions you patched the OES11 system to.
Cheers,
Willem

Does expanding LUN where oracle db resides will make it corrupt?

as the question goes, regarding 11g, 10g db etc.;
i'm about to do a LUN expansion for an oracle database and i thought i might need a few advices from oracle dba in here or anyone who had the experience doing LUN expansion thathas a oracle database resides in it.
i concerns (naturally, since i had never done this):
* will this excercise corrupt oracle database?
* what sort of contigencies should i make? will it be enough doing a full backup and running backup check or do i need to try to restore the backup on a similar setup somewhere?

863805 wrote:
as the question goes, regarding 11g, 10g db etc.;
i'm about to do a LUN expansion for an oracle database and i thought i might need a few advices from oracle dba in here or anyone who had the experience doing LUN expansion thathas a oracle database resides in it.Define LUN expansion. Resizing it to be bigger? And how is that LUN used? Cooked file system? Raw? ASM? Another storage management device?
* will this excercise corrupt oracle database?Potentially yes.
* what sort of contigencies should i make? will it be enough doing a full backup and running backup check or do i need to try to restore the backup on a similar setup somewhere?Any major storage change should ideally be preceded with a full backup. Better safe than sorry.

Expanding Raid 5 array (with windows 2003)

I recently put 2 more 500GB drives into my existing 4 drive Raid 5 setup. I went through the expansion through RAID ADMIN 1.5. It synced the array which took about a day and inside the RAID ADMIN 1.5 tool it says the array is now 2.27 TB.
Inside windows 2003, the size of the drive still says 1.36 TB. I've restarted the windows server, and restart the x-serve RAID. Still it wont update the size of the drive.
I have read some PDFs from apple that expanding is a 2 stage process, doing the expansion followed by merging the slices together afterwards. When i goto the merge slicing tool, it says the array has 1 slice, but underneath it there is a checkbox that says "I understand that slicing an array or merging slices will cause data on the array to be lost"
I'm not sure if thats what i need to do, i'm worried that im going to loose all my data on the drive by just wanting to expand it. If you have any information that can help that would be appreciated. Thank you!

I recently put 2 more 500GB drives into my existing 4
drive Raid 5 setup. I went through the expansion
through RAID ADMIN 1.5. It synced the array which
took about a day and inside the RAID ADMIN 1.5 tool
it says the array is now 2.27 TB.
Inside windows 2003, the size of the drive still says
1.36 TB. I've restarted the windows server, and
restart the x-serve RAID. Still it wont update the
size of the drive.
Windows 2003 can extend the disk using disk administrator on file system/volume level. I have tried it and it worked just fine.
http://www.windowsitpro.com/Article/ArticleID/48992/48992.html
Would I not backup my data before doing this? NO WAY. Always backup your data before you do any volume expansion or re-layout.
Would this work every time? I do not know if Apple test Xserve RAID for ALL Xserve RAID features such as LUN expansion or LUN masking, etc. It's certified though.
I have read some PDFs from apple that expanding is a
2 stage process, doing the expansion followed by
merging the slices together afterwards. When i goto
the merge slicing tool, it says the array has 1
slice, but underneath it there is a checkbox that
says "I understand that slicing an array or merging
slices will cause data on the array to be lost"
I'm not sure if thats what i need to do, i'm worried
that im going to loose all my data on the drive by
just wanting to expand it. If you have any
information that can help that would be appreciated.
Thank you!

Resize a LUN?

I'm using Xsan with an Xserve RAID and I'm trying to get the resize LUN feature to work.
As a test I had three 750 GB drives in a RAID 5 array. This was initialized in Xsan as a LUN and added to a storage pool. I then used RAID Admin to add two more 750 GB drives to that LUN. The resize in RAID admin completed fine but I can't see the extra space in Xsan.
Does this not work at all or am I doing something wrong?

there is a post here
"Once LUNs are labeled in Xsan Admin, they are identified with a specific sector size that cannot be altered without recreating the volume. Therefore using RAID admin to expand LUNs is completely incompatible with Xsan. This issue has been discussed in other posts on this site" from the link..
why not just create the new lun and add it to your storage pool?
http://www.xsanity.com/forum/viewtopic.php?t=365&sid=cfdcaade7919f42936ceb85a9c0 cb32e
Mac OS X (10.4.7)

Block alignment for NetWare 6.5 Virtual Machines

I have an enviornment with multiple virtualized Netware VM's running on vSphere. Some were converted using VMware's P2V software other's were migrated using the SCMT.
My question relates to block alignment at the NSS layer. I have the block alignment handled up to this point:
SAN Luns: 64kb
VMFS Partitions: 64kb
VMDK files: If created using the vSphere client 64kb. If P2V ???
NSS partitions within VMDK: ???
What is the default block size for the NSS partitions in Netware? I there a way to check?
If they are not at 64KB, Is there a tool available to re-align them to 64kb?
Thanks for the help!

The default and only available block size for NSS is 4k. No alignment should be necessary as 4 divides evenly into 64.

Netware 6.5 Expanding a LUN

Similar Messages

Maybe you are looking for