How to Remove a Drive from LVM - Revision history

Bigfoot65 at 20:13, 2 January 2015

2015-01-02T20:13:37Z

Petercross at 15:13, 3 May 2010

2010-05-03T15:13:55Z

Petercross at 14:55, 3 May 2010

2010-05-03T14:55:48Z

Petercross at 14:54, 3 May 2010

2010-05-03T14:54:58Z

Petercross at 14:52, 3 May 2010

2010-05-03T14:52:05Z

Petercross at 14:48, 3 May 2010

2010-05-03T14:48:24Z

Petercross at 14:47, 3 May 2010

2010-05-03T14:47:23Z

Petercross at 14:40, 3 May 2010

2010-05-03T14:40:00Z

Petercross at 14:36, 3 May 2010

2010-05-03T14:36:51Z

Petercross at 14:32, 3 May 2010

2010-05-03T14:32:20Z

← Older revision		Revision as of 20:13, 2 January 2015
Line 1:		Line 1:
		+	{{NeedsUpdate}}
	A hard drives can be removed from your Amahi HDA for replacement or to reduce storage space.		A hard drives can be removed from your Amahi HDA for replacement or to reduce storage space.

← Older revision		Revision as of 15:13, 3 May 2010
Line 14:		Line 14:
	Say you have an old IDE drive on /dev/hdb. You want to remove that old disk but a lot of files are on it.		Say you have an old IDE drive on /dev/hdb. You want to remove that old disk but a lot of files are on it.

−	'''Caution Backup Your System'''	+	=='''Caution Backup Your System'''==

@@ Line 9: / Line 9: @@
 * This was copied from the LVM project at http://tldp.org/HOWTO/LVM-HOWTO/removeadisk.html
-.5. Removing an Old Disk
+=Step by step instructions=
 Say you have an old IDE drive on /dev/hdb. You want to remove that old disk but a lot of files are on it.
-'''Caution	Backup Your System'''
+'''Caution Backup Your System'''
@@ Line 19: / Line 20: @@
 ==Distributing Old Extents to Existing Disks in Volume Group==

← Older revision		Revision as of 14:54, 3 May 2010
Line 13:		Line 13:
	Say you have an old IDE drive on /dev/hdb. You want to remove that old disk but a lot of files are on it.		Say you have an old IDE drive on /dev/hdb. You want to remove that old disk but a lot of files are on it.

−	Caution Backup Your System	+	'''Caution Backup Your System'''

← Older revision		Revision as of 14:52, 3 May 2010
Line 98:		Line 98:
	The drive can now be either physically removed when the machine is next powered down or reallocated to some other users.		The drive can now be either physically removed when the machine is next powered down or reallocated to some other users.

−	If you need to add a disk please go <a ~~href="http://wiki.amahi.org/index.php/Adding_a_second_hard_drive_to_your_HDA"> here </a>.~~	+	If you need to add a disk please go to [[Adding a second hard drive to your HDA]]

← Older revision		Revision as of 14:48, 3 May 2010
Line 98:		Line 98:
	The drive can now be either physically removed when the machine is next powered down or reallocated to some other users.		The drive can now be either physically removed when the machine is next powered down or reallocated to some other users.

−	If you need to add a disk please go <a href="http://wiki.amahi.org/index.php/Adding_a_second_hard_drive_to_your_HDA">here</a>.	+	If you need to add a disk please go <a href="http://wiki.amahi.org/index.php/Adding_a_second_hard_drive_to_your_HDA"> here </a>.

← Older revision		Revision as of 14:47, 3 May 2010
Line 97:		Line 97:

	The drive can now be either physically removed when the machine is next powered down or reallocated to some other users.		The drive can now be either physically removed when the machine is next powered down or reallocated to some other users.
		+
		+	If you need to add a disk please go <a href="http://wiki.amahi.org/index.php/Adding_a_second_hard_drive_to_your_HDA">here</a>.

← Older revision		Revision as of 14:40, 3 May 2010
Line 1:		Line 1:
		+	A hard drives can be removed from your Amahi HDA for replacement or to reduce storage space.
		+
		+	We'll detail how to remove such hard drives.
		+
		+	=Important Notes=
		+
		+	* This is an '''advanced''' how-to on how to remove drives from your HDA.
		+	* Amahi cannot be held responsible for any data breakage or destruction arising from the use or misuse of this script. We provide it as a service in good will. You accept this automatically if you use the script.
		+	* This was copied from the LVM project at http://tldp.org/HOWTO/LVM-HOWTO/removeadisk.html
		+
	13.5. Removing an Old Disk		13.5. Removing an Old Disk

@@ Line 7: / Line 7: @@
 You should always backup your system before attempting a pvmove operation.
-.5.1. Distributing Old Extents to Existing Disks in Volume Group
 If you have enough free extents on the other disks in the volume group, you have it easy. Simply run
@@ Line 25: / Line 28: @@
 Be aware that pvmove is quite slow as it has to copy the contents of a disk block by block to one or more disks. If you want more steady status reports from pvmove, use the -v flag.
-.5.1.1. Remove the unused disk
+==Remove the unused disk==
 We can now remove the old IDE disk from the volume group.
@@ Line 37: / Line 40: @@
 The drive can now be either physically removed when the machine is next powered down or reallocated to other users.
-.5.2. Distributing Old Extents to a New Replacement Disk
+==Distributing Old Extents to a New Replacement Disk==
 If you do not have enough free physical extents to distribute the old physical extents to, you will have to add a disk to the volume group and move the extents to it.
-.5.2.1. Prepare the disk
+==Prepare the disk==
 First, you need to pvcreate the new disk to make it available to LVM. In this recipe we show that you don't need to partition a disk to be able to use it.
@@ Line 49: / Line 52: @@
 </div>
-.5.2.2. Add it to the volume group
+==Add it to the volume group==
 As developers use a lot of disk space this is a good volume group to add it into.
@@ Line 60: / Line 63: @@
 </div>
-.5.2.3. Move the data
+==Move the data==
 Next we move the data from the old disk onto the new one. Note that it is not necessary to unmount the file system before doing this. Although it is *highly* recommended that you do a full backup before attempting this operation in case of a power outage or some other problem that may interrupt it. The pvmove command can take a considerable amount of time to complete and it also exacts a performance hit on the two volumes so, although it isn't necessary, it is advisable to do this when the volumes are not too busy.
@@ Line 72: / Line 75: @@
 </div>
-.5.2.4. Remove the unused disk
+==Remove the unused disk==
 We can now remove the old IDE disk from the volume group.

@@ Line 11: / Line 11: @@
 If you have enough free extents on the other disks in the volume group, you have it easy. Simply run
 # pvmove /dev/hdb
 pvmove -- moving physical extents in active volume group "dev"
 pvmove -- WARNING: moving of active logical volumes may cause data loss!
 pvmove -- do you want to continue? [y/n] y
 pvmove -- 249 extents of physical volume "/dev/hdb" successfully moved
+</div>
 This will move the allocated physical extents from /dev/hdb onto the rest of the disks in the volume group.
@@ Line 28: / Line 29: @@
 We can now remove the old IDE disk from the volume group.
 # vgreduce dev /dev/hdb
 vgreduce -- doing automatic backup of volume group "dev"
 vgreduce -- volume group "dev" successfully reduced by physical volume:
 vgreduce -- /dev/hdb
+</div>
 The drive can now be either physically removed when the machine is next powered down or reallocated to other users.
@@ Line 42: / Line 44: @@
 First, you need to pvcreate the new disk to make it available to LVM. In this recipe we show that you don't need to partition a disk to be able to use it.
 # pvcreate /dev/sdf
 pvcreate -- physical volume "/dev/sdf" successfully created
+</div>
 .5.2.2. Add it to the volume group
@@ Line 50: / Line 53: @@
 As developers use a lot of disk space this is a good volume group to add it into.
 # vgextend dev /dev/sdf
 vgextend -- INFO: maximum logical volume size is 255.99 Gigabyte
 vgextend -- doing automatic backup of volume group "dev"
 vgextend -- volume group "dev" successfully extended
+</div>
 .5.2.3. Move the data
@@ Line 60: / Line 64: @@
 Next we move the data from the old disk onto the new one. Note that it is not necessary to unmount the file system before doing this. Although it is *highly* recommended that you do a full backup before attempting this operation in case of a power outage or some other problem that may interrupt it. The pvmove command can take a considerable amount of time to complete and it also exacts a performance hit on the two volumes so, although it isn't necessary, it is advisable to do this when the volumes are not too busy.
 # pvmove /dev/hdb /dev/sdf
 pvmove -- moving physical extents in active volume group "dev"
 pvmove -- WARNING: moving of active logical volumes may cause data loss!
 pvmove -- do you want to continue? [y/n] y
 pvmove -- 249 extents of physical volume "/dev/hdb" successfully moved
+</div>
 .5.2.4. Remove the unused disk
@@ Line 71: / Line 76: @@
 We can now remove the old IDE disk from the volume group.
 # vgreduce dev /dev/hdb
 vgreduce -- doing automatic backup of volume group "dev"
 vgreduce -- volume group "dev" successfully reduced by physical volume:
 vgreduce -- /dev/hdb
+</div>
 The drive can now be either physically removed when the machine is next powered down or reallocated to some other users.