01-26-2009
Unmount and remove all Logical vol.Volume group and physical disk
Hi,
Someone please help me with how i can unmount and remove all the files systems from a cluster. This is being shared by two servers that are active_standby.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Everyone,
Can someone tell me the effect of the pp size of the volume group created for Oracle data.
It would seem that creating small pp's will cause more overhead. What if you make the pp to large? What should I base this size on?
Thanks, (4 Replies)
Discussion started by: kburrows
4 Replies
2. UNIX for Advanced & Expert Users
Hello,
I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB.
If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information
Regards
Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies
3. AIX
Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies
4. AIX
Hi!
Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes?
What items should I check, like where do I look at in smit? Or are there commands that I should execute?
I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies
1)Physical Volume
2)Volume Group
3)Logical Volume
4)Physical Partition
Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies
6. AIX
Hello everyone,
I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created.
When I say region I mean: outer edge - outer middle - center - inner middle and inner edge.
Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies
7. UNIX for Dummies Questions & Answers
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies
8. Linux
When installing Linux, I choose some default setting to use all the disk space.
My server has a single internal 250Gb SCSI disk. By default the install appears to have created 3 logical volumes
lv_root, lv_home and lv_swap.
fdisk -l shows the following
lab3.nms:/dev>fdisk -l
Disk... (2 Replies)
Discussion started by: jimthompson
2 Replies
9. Red Hat
Hello Guys,
I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var.
I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
10. AIX
I want to remove hdisk1 from volume group diskpool_4 and migrate PV from hdisk1 to hdisk2 , but facing problems, so what is the quickest way to migratepv and remove hdisk1 --
# lspv | grep diskpool_4
hdisk1 00c7780e2e21ec86 diskpool_4 active
hdisk2 ... (2 Replies)
Discussion started by: filosophizer
2 Replies
LEARN ABOUT CENTOS
fsck.gfs2
fsck.gfs2(8) System Manager's Manual fsck.gfs2(8)
NAME
fsck.gfs2 - Offline GFS and GFS2 file system checker
SYNOPSIS
fsck.gfs2 [OPTION]... DEVICE
WARNING
All computers must have the filesystem unmounted before running fsck.gfs2. Failure to unmount from all nodes in a cluster will likely
result in filesystem corruption.
DESCRIPTION
fsck.gfs2 will check that the GFS or GFS2 file system on a device is structurally valid. It should not be run on a mounted file system.
If file system corruption is detected, it will attempt to repair the file system. There is a limit to what fsck.gfs2 can do. If important
file system structures are destroyed, such that the checker cannot determine what the repairs should be, reparations could fail.
GFS2 is a journaled file system, and as such should be able to repair damage to the file system on its own. However, faulty hardware has
the ability to write incomplete blocks to a file system thereby causing corruption that GFS2 cannot fix. The first step to ensuring a
healthy file system is the selection of reliable hardware (i.e. storage systems that will write complete blocks - even in the event of
power failure).
Note: Most file system checkers will not check the file system if it is "clean" (i.e. unmounted since the last use). The fsck.gfs program
behaves differently because the storage may be shared among several nodes in a cluster, and therefore problems may have been introduced on
a different computer. Therefore, fsck.gfs2 will always check the file system unless the -p (preen) option is used, in which case it fol-
lows special rules (see below).
OPTIONS
-a Same as the -p (preen) option.
-f Force checking even if the file system seems clean.
-h Help.
This prints out the proper command line usage syntax.
-q Quiet.
-n No to all questions.
By specifying this option, fsck.gfs2 will only show the changes that would be made, but not make any changes to the filesystem.
-p Preen (same as -a: automatically repair the file system if it is dirty, and safe to do so, otherwise exit.)
Note: If the file system has locking protocol lock_nolock, the file system is considered a non-shared storage device and the fsck is
deemed safe. However, fsck.gfs2 does not know whether it was called automatically from the init process, due to options in the
/etc/fstab file. Therefore, if the locking protocol is lock_dlm and -a or -p was specified, fsck.gfs2 cannot determine whether the
disk is mounted by other nodes in the cluster. Therefore, the fsck is deemed to be unsafe and a warning is given if any damage or
dirty journals are found. In that case, the file system should be unmounted from all nodes in the cluster and fsck.gfs2 should be
run manually without the -a or -p options.
-V Version.
Print out the program version information.
-v Verbose operation.
Print more information while running.
-y Yes to all questions.
By specifying this option, fsck.gfs2 will not prompt before making changes.
fsck.gfs2(8)