Sponsored Content
Operating Systems Linux Red Hat Removing LVM Volume Group that doesn't exist anymore Post 302737791 by thmnetwork on Thursday 29th of November 2012 03:42:25 PM
Old 11-29-2012
No-go:

Code:
[root@dfletcher ~]# lvs
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 142811791360: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 142811848704: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 530428395520: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 530428452864: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 4096: Input/output error
  LV               VG          Attr   LSize    Origin Snap%  Move Log Copy%  Convert
  lv_domino8_base  vg2_domino8 -wi-ao  780.96G
  lv_domino8_daos  vg2_domino8 -wi-ao  315.00G
  lv_domino8_tlogs vg2_domino8 -wi-ao   65.00G
  lv_dom14_base    vg_domino14 -wi-ao 1023.00G
  lv_dom14_daos    vg_domino14 -wi-ao  562.41G
  lv_dom14_tlogs   vg_domino14 -wi-ao  135.55G
[root@dfletcher ~]# lvchange -an /dev/vg_domino8/lv_domino8_base
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 142811791360: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 142811848704: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 530428395520: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 530428452864: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 4096: Input/output error
  Volume group "vg_domino8" not found
  Skipping volume group vg_domino8
[root@dfletcher ~]# lvs
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 142811791360: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 142811848704: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_domino8/lv_domino8_tlogs: read failed after 0 of 4096 at 4096: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 530428395520: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 530428452864: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 0: Input/output error
  /dev/vg_domino8/lv_domino8_base: read failed after 0 of 4096 at 4096: Input/output error
  LV               VG          Attr   LSize    Origin Snap%  Move Log Copy%  Convert
  lv_domino8_base  vg2_domino8 -wi-ao  780.96G
  lv_domino8_daos  vg2_domino8 -wi-ao  315.00G
  lv_domino8_tlogs vg2_domino8 -wi-ao   65.00G
  lv_dom14_base    vg_domino14 -wi-ao 1023.00G
  lv_dom14_daos    vg_domino14 -wi-ao  562.41G
  lv_dom14_tlogs   vg_domino14 -wi-ao  135.55G

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

What hapens if a group member doesn't exist?

As part of a NIS implementation, (I think) I want to create a group (in /etc/group) that has users that do not exist on the target machine. What effect will this have? Will it cause any problems? Thanks, Gary Cooper (1 Reply)
Discussion started by: Gary Cooper
1 Replies

2. AIX

Having problems with removing a volume group..

Dear all, I would be very grateful if you could help me with removing the volume group.. The case is that, I was trying to create a volume group with 4 disk eligible, but the system has hang .. Maybe because the disks that I was trying to include into the new volume group were of too large size... (5 Replies)
Discussion started by: dilshik
5 Replies

3. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

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

4. UNIX for Dummies Questions & Answers

connection doesn't work anymore

Hello, first of all, I want to make myself clear about my language. I'm brazilian, so I ask you all to understand if i commit any mistake with the grammar. Here is the problem. Some days ago I needed to use a "sh" command in the Terminal (I use a Mac OSX 10.5.6) followed by a file... (0 Replies)
Discussion started by: anubisbr
0 Replies

5. UNIX for Dummies Questions & Answers

Removing a user that doesnt exist from a group

Hi there, normally if I want to remove a user tht I have added to a specific group, i would do the following this is what my group2 looks like # grep group2 /etc/group group2:x:7777:user2,user1,user4 user1 has been defined in a few groups # id -nG user1 group1 group2 group3 So... (3 Replies)
Discussion started by: rethink
3 Replies

6. UNIX for Dummies Questions & Answers

How to create a volume group, logical volume group and file system?

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

7. Filesystems, Disks and Memory

Expanding a volume group with system-config-lvm

Good morning, I'm working in a lab that generates a good amount of data and we've just about filled our 9.1TB RAID. The system is a Dell PowerEdge 2950 running Scientific Linux 5.4 with a PERC H800 and a Dell PowerVault MD1200. The MD1200 has 12 bays, 6 of which were filled with 2TB drives... (1 Reply)
Discussion started by: mmulqu
1 Replies

8. Homework & Coursework Questions

Group Doesn't Exist

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: I'm able to create a group but when I'm trying to delete the group it keeps stating Group Doesn't Exist. I know... (2 Replies)
Discussion started by: GoBoyGo
2 Replies

9. Red Hat

No space in volume group. How to create a file system using existing logical volume

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

Trouble removing Physical Disk from Volume Group

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
xfs_growfs(8)						      System Manager's Manual						     xfs_growfs(8)

NAME
xfs_growfs, xfs_info - expand an XFS filesystem SYNOPSIS
xfs_growfs [ -dilnrxV ] [ -D size ] [ -e rtextsize ] [ -L size ] [ -m maxpct ] [ -t mtab ] [ -R size ] mount-point xfs_info [ -t mtab ] mount-point DESCRIPTION
xfs_growfs expands an existing XFS filesystem (see xfs(5)). The mount-point argument is the pathname of the directory where the filesystem is mounted. The filesystem must be mounted to be grown (see mount(8)). The existing contents of the filesystem are undisturbed, and the added space becomes available for additional file storage. xfs_info is equivalent to invoking xfs_growfs with the -n option (see discussion below). OPTIONS
-d | -D size Specifies that the data section of the filesystem should be grown. If the -D size option is given, the data section is grown to that size, otherwise the data section is grown to the largest size possible with the -d option. The size is expressed in filesystem blocks. -e Allows the real-time extent size to be specified. In mkfs.xfs(8) this is specified with -r extsize=nnnn. -i The new log is an internal log (inside the data section). [NOTE: This option is not implemented] -l | -L size Specifies that the log section of the filesystem should be grown, shrunk, or moved. If the -L size option is given, the log section is changed to be that size, if possible. The size is expressed in filesystem blocks. The size of an internal log must be smaller than the size of an allocation group (this value is printed at mkfs(8) time). If neither -i nor -x is given with -l, the log contin- ues to be internal or external as it was before. [NOTE: These options are not implemented] -m Specify a new value for the maximum percentage of space in the filesystem that can be allocated as inodes. In mkfs.xfs(8) this is specified with -i maxpct=nn. -n Specifies that no change to the filesystem is to be made. The filesystem geometry is printed, and argument checking is performed, but no growth occurs. See output examples below. -r | -R size Specifies that the real-time section of the filesystem should be grown. If the -R size option is given, the real-time section is grown to that size, otherwise the real-time section is grown to the largest size possible with the -r option. The size is expressed in filesystem blocks. The filesystem does not need to have contained a real-time section before the xfs_growfs operation. -t Specifies an alternate mount table file (default is /proc/mounts if it exists, else /etc/mtab). This is used when working with filesystems mounted without writing to /etc/mtab file - refer to mount(8) for further details. -V Prints the version number and exits. The mount-point argument is not required with -V. xfs_growfs is most often used in conjunction with logical volumes (see md(4) and lvm(8) on Linux). However, it can also be used on a regu- lar disk partition, for example if a partition has been enlarged while retaining the same starting block. PRACTICAL USE
Filesystems normally occupy all of the space on the device where they reside. In order to grow a filesystem, it is necessary to provide added space for it to occupy. Therefore there must be at least one spare new disk partition available. Adding the space is often done through the use of a logical volume manager. EXAMPLES
Understanding xfs_info output. Suppose one has the following "xfs_info /dev/sda" output: meta-data=/dev/sda isize=256 agcount=32, agsize=16777184 blks = sectsz=512 attr=2 data = bsize=4096 blocks=536869888, imaxpct=5 = sunit=32 swidth=128 blks naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=2 = sectsz=512 sunit=32 blks, lazy-count=1 realtime =none extsz=524288 blocks=0, rtextents=0 Here, the data section of the output indicates "bsize=4096", meaning the data block size for this filesystem is 4096 bytes. This section also shows "sunit=32 swidth=128 blks", which means the stripe unit is 32*4096 bytes = 128 kibibytes and the stripe width is 128*4096 bytes = 512 kibibytes. A single stripe of this filesystem therefore consists of four stripe units (128 blocks / 32 blocks per unit). SEE ALSO
mkfs.xfs(8), md(4), lvm(8), mount(8). xfs_growfs(8)
All times are GMT -4. The time now is 04:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy