Sponsored Content
Operating Systems Solaris LUn' unmapped from storage still showing on Solaris 10 Post 302947036 by bentech4u on Monday 15th of June 2015 12:20:26 AM
Old 06-15-2015
Thanks

Seems like your 1st suggestion is more matching bcoz i am not using NIS

The filesystem is unmounted completely from the system. My storage is EMC

Regarding process id, i will check and update you
 

8 More Discussions You Might Find Interesting

1. Solaris

command to scan Enterprise storage Lun disk in Solaris

I just installed IBMsdd on Solaris diver along with the patches recommended. I also installed 2 - 2Gigs qlogic fiber cards & the corresponding pkges for the cards. What command can I use to scan this LUN disks from my Soalris servers. Solaris doen't seem to be seeing this disks presented on it.... (2 Replies)
Discussion started by: Remi
2 Replies

2. Solaris

Solaris 9 or 10 LUN Limitations

Is there a limit to the number of LUNS that can be concatenated using Solaris Volume manager with Soft partitions? I have worked with some AIX admins in the past and there was such a limitation therefore limiting the size the filesystem could grow to. Is there such a limitation in Solaris 9... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies

3. Solaris

new attached lun in solaris 10

hi, what are the steps to detect and configure a new attached lun in Solaris 10. Is there any difference between cfgadm and luxadm command ? rgds, snjksh (5 Replies)
Discussion started by: snjksh
5 Replies

4. Solaris

How to get LUN WWN in Solaris?

How to get LUN WWN (i.e LUN mapped from a storage box say Symmetrix or clariion) in Solaris. fcinfo command does give the Target port wwn but what i'm looking for is the LUN WWN. Any help is appreciated. (2 Replies)
Discussion started by: Manish00712
2 Replies

5. Solaris

Solaris 10, adding new LUN from SAN storage

Hello to all, Actually, currently on my Solaris box, I've a LUN (5TB space) from a EMC storage which is working fine, and a partition with ZFS filesystem is created for that LUN. as further you'll see in the logs, the "c4t6006016053802E00E6A9196B6506E211d0s2" is the current configured LUN in the... (4 Replies)
Discussion started by: Anti_Evil
4 Replies

6. Solaris

Mpathadm showing no paths to 1 lun, others luns are fine

Hi, I've noticed that mpathadm states that one of our luns has no active paths: /dev/rdsk/c6t60000970000298700009533031324333d0s2 Total Path Count: 4 Operational Path Count: 4 /dev/rdsk/c6t60000970000298700009533031333037d0s2 ... (3 Replies)
Discussion started by: badoshi
3 Replies

7. Solaris

Luxadm display not showing a LUN as expected

Hi all, I have the following LUN which is showing OK with its two paths: DEVICE PROPERTIES for disk: /dev/rdsk/c23t500507630A3BC579d123s2 Vendor: IBM Product ID: 2107900 Revision: 3010 Serial Num: 75WB0114900 Unformatted capacity:... (13 Replies)
Discussion started by: ludiegu
13 Replies

8. Post Here to Contact Site Administrators and Moderators

AIX server do not detect LUN from HP storage

ssssssssssss (0 Replies)
Discussion started by: sampathenjoy
0 Replies
gfs2_grow(8)						      System Manager's Manual						      gfs2_grow(8)

NAME
gfs2_grow - Expand a GFS2 filesystem SYNOPSIS
gfs2_grow [OPTION]... <DEVICE|MOUNTPOINT>... DESCRIPTION
gfs2_grow is used to expand a GFS2 filesystem after the device upon which the filesystem resides has also been expanded. By running gfs2_grow on a GFS2 filesystem, you are requesting that any spare space between the current end of the filesystem and the end of the device is filled with a newly initialized GFS2 filesystem extension. When this operation is complete, the resource group index for the filesystem is updated so that all nodes in the cluster can use the extra storage space that has been added. You may only run gfs2_grow on a mounted filesystem; expansion of unmounted filesystems is not supported. You only need to run gfs2_grow on one node in the cluster. All the other nodes will see the expansion has occurred and automatically start to use the newly available space. You must be superuser to execute gfs2_grow. The gfs2_grow tool tries to prevent you from corrupting your filesystem by checking as many of the likely problems as it can. When expanding a filesystem, only the last step of updating the resource index affects the currently mounted filesystem and so failure part way through the expansion process should leave your filesystem in its original unexpanded state. You can run gfs2_grow with the -T flag to get a display of the current state of a mounted GFS2 filesystem. The gfs2_grow tool uses the resource group (RG) size that was originally calculated when mkfs.gfs2 was done. This allows tools like fsck.gfs2 to better ensure the integrity of the file system. Since the new free space often does not lie on even boundaries based on that RG size, there may be some unused space on the device after gfs2_grow is run. OPTIONS
-D Print out debugging information about the filesystem layout. -h Prints out a short usage message and exits. -q Be quiet. Don't print anything. -T Test. Do all calculations, but do not write any data to the disk and do not expand the filesystem. This is used to discover what the tool would have done were it run without this flag. -V Version. Print out version information, then exit. BUGS
There is no way to shrink a GFS2 filesystem. SEE ALSO
mkfs.gfs2(8) gfs2_jadd(8) gfs2_grow(8)
All times are GMT -4. The time now is 10:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy