msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2008-11-16 23:47-0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: LVM-HOWTO.xml:7(title) msgid "LVM HOWTO" msgstr "" #: LVM-HOWTO.xml:10(firstname) msgid "AJ" msgstr "" #: LVM-HOWTO.xml:11(surname) msgid "Lewis" msgstr "" #: LVM-HOWTO.xml:14(email) msgid "alewis(at)rackable.com" msgstr "" #: LVM-HOWTO.xml:21(revnumber) msgid "0.19" msgstr "" #: LVM-HOWTO.xml:22(date) LVM-HOWTO.xml:32(date) msgid "2006-11-27" msgstr "" #: LVM-HOWTO.xml:23(authorinitials) LVM-HOWTO.xml:33(authorinitials) #: LVM-HOWTO.xml:43(authorinitials) LVM-HOWTO.xml:53(authorinitials) #: LVM-HOWTO.xml:63(authorinitials) LVM-HOWTO.xml:74(authorinitials) #: LVM-HOWTO.xml:84(authorinitials) LVM-HOWTO.xml:97(authorinitials) #: LVM-HOWTO.xml:106(authorinitials) LVM-HOWTO.xml:115(authorinitials) #: LVM-HOWTO.xml:125(authorinitials) LVM-HOWTO.xml:139(authorinitials) #: LVM-HOWTO.xml:150(authorinitials) LVM-HOWTO.xml:164(authorinitials) #: LVM-HOWTO.xml:175(authorinitials) LVM-HOWTO.xml:188(authorinitials) #: LVM-HOWTO.xml:197(authorinitials) LVM-HOWTO.xml:208(authorinitials) msgid "ajl" msgstr "" #: LVM-HOWTO.xml:24(revremark) msgid "" "Clarified full snapshot conditions in and and added a note about resizing " "the origin of a snapshot; Fixed Rackable copyright; Fixed e-mail address" msgstr "" #: LVM-HOWTO.xml:31(revnumber) msgid "0.18" msgstr "" #: LVM-HOWTO.xml:34(revremark) msgid "" "Clarify whole disk usage in ; Updated copyright; Updated e-mail address" msgstr "" #: LVM-HOWTO.xml:41(revnumber) msgid "0.17" msgstr "" #: LVM-HOWTO.xml:42(date) msgid "2005-10-03" msgstr "" #: LVM-HOWTO.xml:44(revremark) msgid "" "Added FAQ entry for max size of LVs in LVM2; Did some cleanup of \"Recover " "physical volume metadata\" section; Updated e-mail address" msgstr "" #: LVM-HOWTO.xml:51(revnumber) msgid "0.16" msgstr "" #: LVM-HOWTO.xml:52(date) msgid "2005-07-15" msgstr "" #: LVM-HOWTO.xml:54(revremark) msgid "" "Added lvm2 boot-time scripts info; Added \"Recover physical volume metadata" "\" section - thanks to Maximilian Attems for the patch" msgstr "" #: LVM-HOWTO.xml:61(revnumber) msgid "0.15" msgstr "" #: LVM-HOWTO.xml:62(date) msgid "2005-06-09" msgstr "" #: LVM-HOWTO.xml:64(revremark) msgid "" "Removed references to xfs_freeze - it is no longer needed; Updated snapshots " "subsection in Anatomy of LVM section; Added a couple entries to the LVM2 " "FAQ; Fixed a couple typos" msgstr "" #: LVM-HOWTO.xml:72(revnumber) msgid "0.14" msgstr "" #: LVM-HOWTO.xml:73(date) msgid "2004-10-06" msgstr "" #: LVM-HOWTO.xml:75(revremark) msgid "" "Added reference to lvm2_createinitrd in source tree; Adjusted lvcreate " "example slightly; Added 'vgchange -ay' in 'Moving a volume group to another " "system' recipe" msgstr "" #: LVM-HOWTO.xml:82(revnumber) msgid "0.13" msgstr "" #: LVM-HOWTO.xml:83(date) msgid "2004-08-16" msgstr "" #: LVM-HOWTO.xml:85(revremark) msgid "" "Clarify symlink farm description; Fix dm control device major number; " "Remove /boot from vg in small lvm setup example; Add notes about /boot and / " "on LVM; Remove outdated link;" msgstr "" #: LVM-HOWTO.xml:95(revnumber) msgid "0.12" msgstr "" #: LVM-HOWTO.xml:96(date) msgid "2004-06-07" msgstr "" #: LVM-HOWTO.xml:98(revremark) LVM-HOWTO.xml:107(revremark) msgid "Updated LVM2 FAQ entries" msgstr "" #: LVM-HOWTO.xml:104(revnumber) msgid "0.11" msgstr "" #: LVM-HOWTO.xml:105(date) msgid "2004-05-03" msgstr "" #: LVM-HOWTO.xml:113(revnumber) msgid "0.10" msgstr "" #: LVM-HOWTO.xml:114(date) msgid "2004-04-22" msgstr "" #: LVM-HOWTO.xml:116(revremark) msgid "" "removed -print0 from find command after receiving reports that it doesn't " "work" msgstr "" #: LVM-HOWTO.xml:123(revnumber) msgid "0.9" msgstr "" #: LVM-HOWTO.xml:124(date) msgid "2004-04-16" msgstr "" #: LVM-HOWTO.xml:126(revremark) msgid "" "Added -print0 to find command before piping it to cpio; Changed vgimport " "command line for LVM 2; Added ext3 to the ext2 resize section; Updated FAQ; " "Updated Links section" msgstr "" #: LVM-HOWTO.xml:137(revnumber) msgid "0.8" msgstr "" #: LVM-HOWTO.xml:138(date) msgid "2004-02-25" msgstr "" #: LVM-HOWTO.xml:140(revremark) msgid "" "Updated CVS locations and FTP links; Added section on extending a JFS " "filesystem; Fixed typos - Ran aspell against document" msgstr "" #: LVM-HOWTO.xml:148(revnumber) msgid "0.7" msgstr "" #: LVM-HOWTO.xml:149(date) msgid "2004-02-16" msgstr "" #: LVM-HOWTO.xml:151(revremark) msgid "" "Updated to include LVM 2 and device mapper information; Updated email " "addresses; Updated copyright; Added FAQ section; Added document license; " "Updated to docbook 4.2" msgstr "" #: LVM-HOWTO.xml:162(revnumber) msgid "0.6" msgstr "" #: LVM-HOWTO.xml:163(date) msgid "2003-12-09" msgstr "" #: LVM-HOWTO.xml:165(revremark) msgid "" "Updated for LVM 1.0.8; fixed broken link; Clarified redhat init script " "section;" msgstr "" #: LVM-HOWTO.xml:173(revnumber) msgid "0.5" msgstr "" #: LVM-HOWTO.xml:174(date) msgid "2003-02-10" msgstr "" #: LVM-HOWTO.xml:176(revremark) msgid "" "Updated Redhat initscript information for 7.0 and above; Added information " "on removing a partition table from a disk if pvcreate fails; Default PE size " "is 32MB now; Updated method for snapshotting under XFS." msgstr "" #: LVM-HOWTO.xml:186(revnumber) msgid "0.4" msgstr "" #: LVM-HOWTO.xml:187(date) msgid "2002-12-16" msgstr "" #: LVM-HOWTO.xml:189(revremark) msgid "Updated for LVM 1.0.6" msgstr "" #: LVM-HOWTO.xml:195(revnumber) msgid "0.3" msgstr "" #: LVM-HOWTO.xml:196(date) msgid "2002-09-16" msgstr "" #: LVM-HOWTO.xml:198(revremark) msgid "" "removed example pvmove from Command Operations section - we now just point " "to the more detailed recipe on pvmove that contains various warnings and such" msgstr "" #: LVM-HOWTO.xml:206(revnumber) msgid "0.2" msgstr "" #: LVM-HOWTO.xml:207(date) msgid "2002-09-11" msgstr "" #: LVM-HOWTO.xml:209(revremark) msgid "Updated for LVM 1.0.5 and converted to DocBook XML 4.1.2." msgstr "" #: LVM-HOWTO.xml:215(revnumber) msgid "0.1" msgstr "" #: LVM-HOWTO.xml:216(date) msgid "2002-04-28" msgstr "" #: LVM-HOWTO.xml:217(authorinitials) msgid "gf" msgstr "" #: LVM-HOWTO.xml:218(revremark) msgid "" "Initial conversion from Sistina's LaTeX source and import to tLDP in " "LinuxDoc format." msgstr "" #: LVM-HOWTO.xml:226(year) msgid "2002-2003" msgstr "" #: LVM-HOWTO.xml:227(holder) msgid "Sistina Software, Inc" msgstr "" #: LVM-HOWTO.xml:230(year) msgid "2004-2005" msgstr "" #: LVM-HOWTO.xml:231(holder) msgid "Red Hat, Inc" msgstr "" #: LVM-HOWTO.xml:234(year) msgid "2005-2006" msgstr "" #: LVM-HOWTO.xml:235(holder) msgid "Terrascale Technologies, Inc" msgstr "" #: LVM-HOWTO.xml:238(year) msgid "2006" msgstr "" #: LVM-HOWTO.xml:239(holder) msgid "Rackable Systems, Inc" msgstr "" #: LVM-HOWTO.xml:242(para) msgid "" "Permission is granted to copy, distribute and/or modify this document under " "the terms of the GNU Free Documentation License, Version 1.2 published by " "the Free Software Foundation; with no Invariant Sections, no Front-Cover " "Texts and no Back-Cover Texts. A copy of the license is included in the " "section entitled \"GNU Free Documentation License\"." msgstr "" #: LVM-HOWTO.xml:251(para) LVM-HOWTO.xml:304(para) msgid "" "This document is distributed in the hope that it will be useful, but WITHOUT " "ANY WARRANTY, either expressed or implied. While every effort has been taken " "to ensure the accuracy of the information documented herein, the author(s)/" "editor(s)/maintainer(s)/contributor(s) assumes NO RESPONSIBILITY for any " "errors, or for any damages, direct or consequential, as a result of the use " "of the information documented herein." msgstr "" #: LVM-HOWTO.xml:264(para) msgid "" "This document describes how to build, install, and configure LVM for Linux. " "A basic description of LVM is also included. This version of the HowTo is " "for LVM 2 with device-mapper, as well as LVM 1.0.8." msgstr "" #: LVM-HOWTO.xml:274(title) msgid "Introduction" msgstr "" #: LVM-HOWTO.xml:276(para) msgid "" "This is an attempt to collect everything needed to know to get LVM up and " "running. The entire process of getting, compiling, installing, and setting " "up LVM will be covered. Pointers to LVM configurations that have been tested " "with will also be included. This version of the HowTo is for LVM 2 with " "device-mapper and LVM 1.0.8." msgstr "" #: LVM-HOWTO.xml:284(para) msgid "" "All previous versions of LVM are considered obsolete and are only kept for " "historical reasons. This document makes no attempt to explain or describe " "the workings or use of those versions." msgstr "" #: LVM-HOWTO.xml:290(title) msgid "Latest Version" msgstr "" #: LVM-HOWTO.xml:291(para) msgid "" "We will keep the latest version of this HowTo in the CVS with the other LDP " "Howtos. You can get it by checking out ``LDP/howto/docbook/LVM-HOWTO.xml'' " "from the tLDP CVS server. You should always be able to get a human readable " "version of this HowTo from the http://www.tldp.org/HOWTO/LVM-HOWTO.html " msgstr "" #: LVM-HOWTO.xml:303(title) msgid "Disclaimer" msgstr "" #: LVM-HOWTO.xml:316(title) msgid "Contributors" msgstr "" #: LVM-HOWTO.xml:317(para) msgid "List of everyone who has put words into this file." msgstr "" #: LVM-HOWTO.xml:323(ulink) msgid "AJ Lewis" msgstr "" #: LVM-HOWTO.xml:327(ulink) msgid "Joe Thornber" msgstr "" #: LVM-HOWTO.xml:331(ulink) msgid "Patrick Caulfield" msgstr "" #: LVM-HOWTO.xml:335(ulink) msgid "Alasdair Kergon" msgstr "" #: LVM-HOWTO.xml:338(para) msgid "" " Jochen Radmacher - " "JFS extend information" msgstr "" #: LVM-HOWTO.xml:345(para) msgid "" "Please notify the HowTo maintainer if you believe you should be listed above." msgstr "" #: LVM-HOWTO.xml:353(title) msgid "What is LVM?" msgstr "" #: LVM-HOWTO.xml:360(para) msgid "LVM 2 - The latest and greatest version of LVM for Linux." msgstr "" #: LVM-HOWTO.xml:363(para) msgid "" "LVM 2 is almost completely backward compatible with volumes created with LVM " "1. The exception to this is snapshots (You must remove snapshot volumes " "before upgrading to LVM 2)" msgstr "" #: LVM-HOWTO.xml:369(para) msgid "" "LVM 2 uses the device mapper kernel driver. Device mapper support is in the " "2.6 kernel tree and there are patches available for current 2.4 kernels." msgstr "" #: LVM-HOWTO.xml:376(para) msgid "LVM 1 - The version that is in the 2.4 series kernel," msgstr "" #: LVM-HOWTO.xml:379(para) msgid "" "LVM 1 is a mature product that has been considered stable for a couple of " "years. The kernel driver for LVM 1 is included in the 2.4 series kernels, " "but this does not mean that your 2.4.x kernel is up to date with the latest " "version of LVM. Look at the README for the latest information about which kernels have " "the current code in them." msgstr "" #: LVM-HOWTO.xml:355(para) msgid "" "LVM is a Logical Volume Manager for the Linux operating system. There are " "now two version of LVM for Linux: " msgstr "" #: LVM-HOWTO.xml:395(title) msgid "What is Logical Volume Management?" msgstr "" #: LVM-HOWTO.xml:396(para) msgid "" "Logical volume management provides a higher-level view of the disk storage " "on a computer system than the traditional view of disks and partitions. This " "gives the system administrator much more flexibility in allocating storage " "to applications and users." msgstr "" #: LVM-HOWTO.xml:403(para) msgid "" "Storage volumes created under the control of the logical volume manager can " "be resized and moved around almost at will, although this may need some " "upgrading of file system tools." msgstr "" #: LVM-HOWTO.xml:409(para) msgid "" "The logical volume manager also allows management of storage volumes in user-" "defined groups, allowing the system administrator to deal with sensibly " "named volume groups such as \"development\" and \"sales\" rather than " "physical disk names such as \"sda\" and \"sdb\"." msgstr "" #: LVM-HOWTO.xml:416(title) msgid "Why would I want it?" msgstr "" #: LVM-HOWTO.xml:417(para) msgid "" "Logical volume management is traditionally associated with large " "installations containing many disks but it is equally suited to small " "systems with a single disk or maybe two." msgstr "" #: LVM-HOWTO.xml:424(title) msgid "Benefits of Logical Volume Management on a Small System" msgstr "" #: LVM-HOWTO.xml:425(para) msgid "" "One of the difficult decisions facing a new user installing Linux for the " "first time is how to partition the disk drive. The need to estimate just how " "much space is likely to be needed for system files and user files makes the " "installation more complex than is necessary and some users simply opt to put " "all their data into one large partition in an attempt to avoid the issue." msgstr "" #: LVM-HOWTO.xml:434(para) msgid "" "Once the user has guessed how much space is needed for /home /usr / (or has " "let the installation program do it) then is quite common for one of these " "partitions to fill up even if there is plenty of disk space in one of the " "other partitions." msgstr "" #: LVM-HOWTO.xml:441(para) msgid "" "With logical volume management, the whole disk would be allocated to a " "single volume group and logical volumes created to hold the / /usr and /home " "file systems. If, for example the /home logical volume later filled up but " "there was still space available on /usr then it would be possible to shrink /" "usr by a few megabytes and reallocate that space to /home." msgstr "" #: LVM-HOWTO.xml:450(para) msgid "" "Another alternative would be to allocate minimal amounts of space for each " "logical volume and leave some of the disk unallocated. Then, when the " "partitions start to fill up, they can be expanded as necessary." msgstr "" #: LVM-HOWTO.xml:457(para) msgid "" "As an example: Joe buys a PC with an 8.4 Gigabyte disk on it and installs " "Linux using the following partitioning system: \n" "/boot /dev/hda1 10 Megabytes\n" "swap /dev/hda2 256 Megabytes\n" "/ /dev/hda3 2 Gigabytes\n" "/home /dev/hda4 6 Gigabytes\n" " This, he thinks, will maximize the amount of space " "available for all his MP3 files." msgstr "" #: LVM-HOWTO.xml:472(para) msgid "" "Sometime later Joe decides that he want to install the latest office suite " "and desktop UI available but realizes that the root partition isn't large " "enough. But, having archived all his MP3s onto a new writable DVD drive " "there is plenty of space on /home." msgstr "" #: LVM-HOWTO.xml:479(para) msgid "His options are not good:" msgstr "" #: LVM-HOWTO.xml:486(para) msgid "Reformat the disk, change the partitioning scheme and reinstall." msgstr "" #: LVM-HOWTO.xml:493(para) msgid "" "Buy a new disk and figure out some new partitioning scheme that will require " "the minimum of data movement." msgstr "" #: LVM-HOWTO.xml:500(para) msgid "" "Set up a symlink farm on / pointing to /home and install the new software " "on /home" msgstr "" #: LVM-HOWTO.xml:508(para) msgid "With LVM this becomes much easier:" msgstr "" #: LVM-HOWTO.xml:512(para) msgid "" "Jane buys a similar PC but uses LVM to divide up the disk in a similar " "manner:" msgstr "" #: LVM-HOWTO.xml:517(screen) #, no-wrap msgid "" "\n" "/boot /dev/hda1 10 Megabytes\n" "swap /dev/vg00/swap 256 Megabytes\n" "/ /dev/vg00/root 2 Gigabytes\n" "/home /dev/vg00/home 6 Gigabytes\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:526(para) msgid "" "boot is not included on the LV because bootloaders don't understand LVM " "volumes yet. It's possible boot on LVM will work, but you run the risk of " "having an unbootable system." msgstr "" #: LVM-HOWTO.xml:533(title) msgid "root on LV should be used by advanced users only" msgstr "" #: LVM-HOWTO.xml:535(para) msgid "" "root on LVM requires an initrd image that activates the root LV. If a kernel " "is upgraded without building the necessary initrd image, that kernel will be " "unbootable. Newer distributions support lvm in their mkinitrd scripts as " "well as their packaged initrd images, so this becomes less of an issue over " "time." msgstr "" #: LVM-HOWTO.xml:545(para) msgid "" "When she hits a similar problem she can reduce the size of /home by a " "gigabyte and add that space to the root partition." msgstr "" #: LVM-HOWTO.xml:550(para) msgid "" "Suppose that Joe and Jane then manage to fill up the /home partition as well " "and decide to add a new 20 Gigabyte disk to their systems." msgstr "" #: LVM-HOWTO.xml:556(para) msgid "" "Joe formats the whole disk as one partition (/dev/hdb1) and moves his " "existing /home data onto it and uses the new disk as /home. But he has 6 " "gigabytes unused or has to use symlinks to make that disk appear as an " "extension of /home, say /home/joe/old-mp3s." msgstr "" #: LVM-HOWTO.xml:563(para) msgid "" "Jane simply adds the new disk to her existing volume group and extends her /" "home logical volume to include the new disk. Or, in fact, she could move the " "data from /home on the old disk to the new disk and then extend the existing " "root volume to cover all of the old disk." msgstr "" #: LVM-HOWTO.xml:572(title) msgid "Benefits of Logical Volume Management on a Large System" msgstr "" #: LVM-HOWTO.xml:573(para) msgid "" "The benefits of logical volume management are more obvious on large systems " "with many disk drives." msgstr "" #: LVM-HOWTO.xml:578(para) msgid "" "Managing a large disk farm is a time-consuming job, made particularly " "complex if the system contains many disks of different sizes. Balancing the " "(often conflicting) storage requirements of various users can be a nightmare." msgstr "" #: LVM-HOWTO.xml:585(para) msgid "" "User groups can be allocated to volume groups and logical volumes and these " "can be grown as required. It is possible for the system administrator to " "\"hold back\" disk storage until it is required. It can then be added to the " "volume(user) group that has the most pressing need." msgstr "" #: LVM-HOWTO.xml:593(para) msgid "" "When new drives are added to the system, it is no longer necessary to move " "users files around to make the best use of the new storage; simply add the " "new disk into an existing volume group or groups and extend the logical " "volumes as necessary." msgstr "" #: LVM-HOWTO.xml:600(para) msgid "" "It is also easy to take old drives out of service by moving the data from " "them onto newer drives - this can be done online, without disrupting user " "service." msgstr "" #: LVM-HOWTO.xml:609(title) msgid "Anatomy of LVM" msgstr "" #: LVM-HOWTO.xml:610(para) msgid "" "This diagram gives a overview of the main elements in an LVM system: " "\n" "+-- Volume Group --------------------------------+\n" "| |\n" "| +----------------------------------------+\t |\n" "| PV | PE | PE | PE | PE | PE | PE | PE | PE |\t |\n" "| +----------------------------------------+\t |\n" "| . \t . \t . \t .\t \t |\n" "| . . \t . .\t |\n" "| +----------------------------------------+\t |\n" "| LV | LE | LE | LE | LE | LE | LE | LE | LE |\t |\n" "| +----------------------------------------+\t |\n" "| . . . \t . |\n" "| . \t . . \t . |\n" "| +----------------------------------------+\t |\n" "| PV | PE | PE | PE | PE | PE | PE | PE | PE |\t |\n" "| +----------------------------------------+\t |\n" "| |\n" "+------------------------------------------------+\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:634(para) msgid "" "Another way to look at is this (courtesy of Erik Bågfors on the linux-lvm mailing list): \n" " hda1 hdc1 (PV:s on partitions or whole " "disks) \n" " \\ / \n" " \\ / \n" " diskvg " "(VG) \n" " / | " "\\ \n" " / | " "\\ \n" " usrlv rootlv varlv (LV:s)\n" " | | " "| \n" " ext2 reiserfs xfs (filesystems) \n" "\n" " " msgstr "" #: LVM-HOWTO.xml:652(title) msgid "volume group (VG)" msgstr "" #: LVM-HOWTO.xml:653(para) msgid "" "The Volume Group is the highest level abstraction used within the LVM. It " "gathers together a collection of Logical Volumes and Physical Volumes into " "one administrative unit." msgstr "" #: LVM-HOWTO.xml:660(title) msgid "physical volume (PV)" msgstr "" #: LVM-HOWTO.xml:661(para) msgid "" "A physical volume is typically a hard disk, though it may well just be a " "device that 'looks' like a hard disk (eg. a software raid device)." msgstr "" #: LVM-HOWTO.xml:668(title) msgid "logical volume (LV)" msgstr "" #: LVM-HOWTO.xml:669(para) msgid "" "The equivalent of a disk partition in a non-LVM system. The LV is visible as " "a standard block device; as such the LV can contain a file system (eg. " "/home)." msgstr "" #: LVM-HOWTO.xml:676(title) msgid "physical extent (PE)" msgstr "" #: LVM-HOWTO.xml:677(para) msgid "" "Each physical volume is divided chunks of data, known as physical extents, " "these extents have the same size as the logical extents for the volume group." msgstr "" #: LVM-HOWTO.xml:685(title) msgid "logical extent (LE)" msgstr "" #: LVM-HOWTO.xml:686(para) msgid "" "Each logical volume is split into chunks of data, known as logical extents. " "The extent size is the same for all logical volumes in the volume group." msgstr "" #: LVM-HOWTO.xml:693(title) msgid "Tying it all together" msgstr "" #: LVM-HOWTO.xml:694(para) msgid "A concrete example will help:" msgstr "" #: LVM-HOWTO.xml:698(para) msgid "" "Lets suppose we have a volume group called VG1, this volume group has a " "physical extent size of 4MB. Into this volume group we introduce 2 hard disk " "partitions, /dev/hda1 and /dev/hdb1. These partitions will become physical " "volumes PV1 and PV2 (more meaningful names can be given at the " "administrators discretion). The PV's are divided up into 4MB chunks, since " "this is the extent size for the volume group. The disks are different sizes " "and we get 99 extents in PV1 and 248 extents in PV2. We now can create " "ourselves a logical volume, this can be any size between 1 and 347 (248 + " "99) extents. When the logical volume is created a mapping is defined between " "logical extents and physical extents, eg. logical extent 1 could map onto " "physical extent 51 of PV1, data written to the first 4 MB of the logical " "volume in fact be written to the 51st extent of PV1." msgstr "" #: LVM-HOWTO.xml:716(title) msgid "mapping modes (linear/striped)" msgstr "" #: LVM-HOWTO.xml:717(para) msgid "" "The administrator can choose between a couple of general strategies for " "mapping logical extents onto physical extents:" msgstr "" #: LVM-HOWTO.xml:724(para) msgid "" "Linear mapping will assign a range of " "PE's to an area of an LV in order eg., LE 1 - 99 map to PV1 and LE 100 - 347 " "map onto PV2." msgstr "" #: LVM-HOWTO.xml:747(title) msgid "LVM 1 Caveat" msgstr "" #: LVM-HOWTO.xml:748(para) msgid "" "LVs created using striping cannot be extended past the PVs they were " "originally created on in LVM 1." msgstr "" #: LVM-HOWTO.xml:730(para) msgid "" "Striped mapping will interleave the " "chunks of the logical extents across a number of physical volumes eg., " "\n" "1st chunk of LE[1] -> PV1[1],\n" "\n" "2nd chunk of LE[1] -> PV2[1],\n" "\n" "3rd chunk of LE[1] -> PV3[1],\n" "\n" "4th chunk of LE[1] -> PV1[2],\n" " and so on. In certain situations this strategy can " "improve the performance of the logical volume. In LVM 2, " "striped LVs can be extended by concatenating another set of devices onto the " "end of the first set. So you can get into a situation where your LV is a 2 " "stripe set concatenated with a linear set concatenated with a 4 stripe set. " "Are you confused yet?" msgstr "" #: LVM-HOWTO.xml:764(title) msgid "Snapshots" msgstr "" #: LVM-HOWTO.xml:765(para) msgid "" "A wonderful facility provided by LVM is 'snapshots'. This allows the " "administrator to create a new block device which presents an exact copy of a " "logical volume, frozen at some point in time. Typically this would be used " "when some batch processing, a backup for instance, needs to be performed on " "the logical volume, but you don't want to halt a live system that is " "changing the data. When the snapshot device has been finished with the " "system administrator can just remove the device. This facility does require " "that the snapshot be made at a time when the data on the logical volume is " "in a consistent state - the VFS-lock patch for LVM1 makes sure that some " "filesystems do this automatically when a snapshot is created, and many of " "the filesystems in the 2.6 kernel do this automatically when a snapshot is " "created without patching." msgstr "" #: LVM-HOWTO.xml:782(title) LVM-HOWTO.xml:3749(title) msgid "Full snapshot are automatically disabled" msgstr "" #: LVM-HOWTO.xml:783(para) LVM-HOWTO.xml:3750(para) msgid "" "If the snapshot logical volume becomes full it will be dropped (become " "unusable) so it is vitally important to allocate enough space. The amount of " "space necessary is dependent on the usage of the snapshot, so there is no " "set recipe to follow for this. If the snapshot size equals the origin size, " "it will never overflow." msgstr "" #: LVM-HOWTO.xml:792(para) msgid "" "LVM1 has read-only snapshots. Read-only snapshots work by creating an " "exception table, which is used to keep track of which " "blocks have been changed. If a block is to be changed on the origin, it is " "first copied to the snapshot, marked as copied in the exception table, and " "then the new data is written to the original volume." msgstr "" #: LVM-HOWTO.xml:801(para) msgid "" "In LVM2, snapshots are read/write by default. Read/write snapshots work like " "read-only snapshots, with the additional feature that if data is written to " "the snapshot, that block is marked in the exception table as used, and never " "gets copied from the original volume. This opens up many new possibilities " "that were not possible with LVM1's read-only snapshots. One example is to " "snapshot a volume, mount the snapshot, and try an experimental program that " "change files on that volume. If you don't like what it did, you can unmount " "the snapshot, remove it, and mount the original filesystem in its place. It " "is also useful for creating volumes for use with Xen. You can create a disk " "image, then snapshot it and modify the snapshot for a particular domU " "instance. You can then create another snapshot of the original volume, and " "modify that one for a different domU instance. Since the only storage used " "by a snapshot is blocks that were changed on the origin or the snapshot, the " "majority of the volume is shared by the domU's." msgstr "" #: LVM-HOWTO.xml:824(para) msgid "" "With the current LVM2/device-mapper code, the origin can be grown, but not " "shrunk. With LVM1, you cannot resize the origin." msgstr "" #: LVM-HOWTO.xml:830(title) msgid "LVM 1 -> LVM 2 Upgrade Info" msgstr "" #: LVM-HOWTO.xml:831(para) msgid "" "Make sure to remove snapshot LVs before upgrading from LVM 1 to LVM 2. (See " ")" msgstr "" #: LVM-HOWTO.xml:840(title) msgid "Frequently Asked Questions" msgstr "" #: LVM-HOWTO.xml:841(title) msgid "LVM 2 FAQ" msgstr "" #: LVM-HOWTO.xml:845(para) msgid "" "I have LVM 1 installed and running on my system. How do I start using LVM 2?" msgstr "" #: LVM-HOWTO.xml:855(para) msgid "" "Start by removing any snapshot LVs on the system. These are not handled by " "LVM 2 and will prevent the origin from being activated when LVM 2 comes up." msgstr "" #: LVM-HOWTO.xml:863(para) msgid "" "Make sure you have some way of booting the system other than from your " "standard boot partition. Have the LVM 1 tools, standard system tools (mount) " "and an LVM 1 compatible kernel on it in case you need to get back and fix " "some things." msgstr "" #: LVM-HOWTO.xml:873(para) msgid "" "Grab the LVM 2 tools source and the device mapper source and compile them. " "You need to install the device mapper library using make install before compiling the LVM 2 tools. Also copy the dm/scripts/" "devmap_mknod.sh script into /sbin. I recommend only installing the 'lvm' " "binary for now so you have access to the LVM 1 tools if you need them. If " "you have access to packages for LVM 2 and device-mapper, you can install " "those instead, but beware of them overwriting your LVM 1 tool set." msgstr "" #: LVM-HOWTO.xml:888(para) msgid "" "Get a device mapper compatible kernel, either built in or as a kernel module." msgstr "" #: LVM-HOWTO.xml:895(para) msgid "" "Figure out where LVM 1 was activated in your startup scripts. Make sure the " "device-mapper module is loaded by that point (if you are using device mapper " "as a module) and add '/sbin/devmap_mknod.sh; lvm vgscan; lvm vgchange -ay' " "afterward." msgstr "" #: LVM-HOWTO.xml:905(para) msgid "" "Install the kernel with device mapper support in it. Reboot. If all goes " "well, you should be running with lvm2." msgstr "" #: LVM-HOWTO.xml:851(para) msgid "Here's the Quick Start instructions :) " msgstr "" #: LVM-HOWTO.xml:919(para) msgid "Do I need a special lvm2 kernel module?" msgstr "" #: LVM-HOWTO.xml:924(para) msgid "" "No. You need device-mapper. The lvm2 tools use device-mapper to interface " "with the kernel and do all their device mapping (hence the name device-" "mapper). As long as you have device-mapper, you should be able to use LVM2." msgstr "" #: LVM-HOWTO.xml:936(para) msgid "" "I get errors about /dev/mapper/control when I try to " "use the LVM 2 tools. What's going on?" msgstr "" #: LVM-HOWTO.xml:943(para) msgid "" "The primary cause of this is not having run the dmsetup mknodes after rebooting into a dm capable kernel. This script generates the " "control node for device mapper." msgstr "" #: LVM-HOWTO.xml:957(para) msgid "" "Make sure you have the device-mapper module loaded (if you didn't build it " "into your kernel)." msgstr "" #: LVM-HOWTO.xml:963(para) msgid "" "Run # cat /proc/misc | grep device-mapper | awk '{print $1}' and note the number printed. (If you don't get any output, refer to " "step 1.)" msgstr "" #: LVM-HOWTO.xml:972(para) msgid "" "Run # mkdir /dev/mapper - if you get an error saying " "/dev/mapper already exists, make sure it's a directory " "and move on." msgstr "" #: LVM-HOWTO.xml:980(para) msgid "" "Run # mknod /dev/mapper/control c 10 $number where $number " "is the number printed in step 2." msgstr "" #: LVM-HOWTO.xml:949(para) msgid "" "If you don't have the dmsetup mknodes, don't despair! (Though " "you should probably upgrade to the latest version of device-mapper.) It's " "pretty easy to create the /dev/mapper/control file on " "your own: You should be all set now!" msgstr "" #: LVM-HOWTO.xml:995(para) msgid "" "Which commands and types of logical volumes are currently supported in LVM 2?" msgstr "" #: LVM-HOWTO.xml:1001(para) msgid "" "If you are using the stable 2.4 device mapper patch from the lvm2 tarball, " "all the major functionality you'd expect using lvm1 is supported with the " "lvm2 tools. (You still need to remove snapshots before upgrading from lvm1 " "to lvm2)" msgstr "" #: LVM-HOWTO.xml:1014(para) msgid "pvmove" msgstr "" #: LVM-HOWTO.xml:1017(para) msgid "snapshots" msgstr "" #: LVM-HOWTO.xml:1008(para) msgid "" "If you are using the version of device mapper in the 2.6 kernel.org kernel " "series the following commands and LV types are not supported: The beginnings of support for these features are in the unstable device mapper patches maintained by Joe Thornber." msgstr "" #: LVM-HOWTO.xml:1030(para) msgid "" "Does LVM 2 use a different format from LVM 1 for it's ondisk representation " "of Volume Groups and Logical Volumes?" msgstr "" #: LVM-HOWTO.xml:1037(para) msgid "" "Yes. LVM 2 uses lvm 2 format metadata. This format is much more flexible " "than the LVM 1 format metadata, removing or reducing most of the limitations " "LVM 1 had." msgstr "" #: LVM-HOWTO.xml:1047(para) msgid "Does LVM 2 support VGs and LVs created with LVM 1?" msgstr "" #: LVM-HOWTO.xml:1052(para) msgid "" "Yes. LVM 2 will activate and operate on VG and LVs created with LVM 1. The " "exception to this is snapshots created with LVM 1 - these should be removed " "before upgrading. Snapshots that remain after upgrading will have to be " "removed before their origins can be activated by LVM 2." msgstr "" #: LVM-HOWTO.xml:1064(para) msgid "Can I upgrade my LVM 1 based VGs and LVs to LVM 2 native format?" msgstr "" #: LVM-HOWTO.xml:1070(para) msgid "" "Yes. Use vgconvert to convert your VG and all LVs contained within it to the " "new lvm 2 format metadata. Be warned that it's not always possible to revert " "back to lvm 1 format metadata." msgstr "" #: LVM-HOWTO.xml:1080(para) msgid "" "I've upgraded to LVM 2, but the tools keep failing with out of memory " "errors. What gives?" msgstr "" #: LVM-HOWTO.xml:1086(para) msgid "" "One possible cause of this is that some versions of LVM 1 (The user that " "reported this bug originally was using Mandrake 9.2, but it is not " "necessarily limited to that distribution) did not put a UUID into the PV and " "VG structures as they were supposed to. The most current versions of the LVM " "2 tools automatically fill UUIDs in for the structures if they see they are " "missing, so you should grab a more current version and your problem should " "be solved. If not, post to the linux-lvm mailing " "list" msgstr "" #: LVM-HOWTO.xml:1103(para) msgid "" "I have my root partition on an LV in LVM 1. How do I upgrade to LVM 2? And " "what happened to lvmcreate_initrd?" msgstr "" #: LVM-HOWTO.xml:1109(para) msgid "" "Upgrading to LVM 2 is a bit trickier with root on LVM, but it's not " "impossible. You need to queue up a kernel with device-mapper support and " "install the lvm2 tools (you might want to make a backup of the lvm 1 tools, " "or find a rescue disk with the lvm tools built in, in case you need them " "before you're done). Then find a mkinitrd script that has support for your " "distro and lvm 2." msgstr "" #: LVM-HOWTO.xml:1121(title) msgid "mkinitrd scripts with lvm 2 support" msgstr "" #: LVM-HOWTO.xml:1122(term) msgid "fedora" msgstr "" #: LVM-HOWTO.xml:1124(para) msgid "" "The latest fedora core 2 mkinitrd handles lvm2, but it relies on a statically " "built lvm binary from the latest lvm 2 tarball." msgstr "" #: LVM-HOWTO.xml:1130(para) msgid "Redhat 9 users may be able to use this as well" msgstr "" #: LVM-HOWTO.xml:1135(term) LVM-HOWTO.xml:1920(title) msgid "Debian" msgstr "" #: LVM-HOWTO.xml:1137(para) msgid "" "There is an unofficial version here" msgstr "" #: LVM-HOWTO.xml:1143(term) msgid "Generic" msgstr "" #: LVM-HOWTO.xml:1145(para) msgid "" "There is a version in the lvm2 source tree under scripts/" "lvm2_createinitrd/. See the documentation in that directory for " "more details." msgstr "" #: LVM-HOWTO.xml:1118(para) msgid "" "Currently, this is the list of mkinitrd scripts that I know support lvm2, " "sorted by distro: " msgstr "" #: LVM-HOWTO.xml:1161(para) msgid "How resilient is LVM to a sudden renumbering of physical hard disks?" msgstr "" #: LVM-HOWTO.xml:1167(para) msgid "It's fine - LVM identifies PVs by UUID, not by device name." msgstr "" #: LVM-HOWTO.xml:1171(para) msgid "" "Each disk (PV) is labeled with a UUID, which uniquely identifies it to the " "system. 'vgscan' identifies this after a new disk is added that changes your " "drive numbering. Most distros run vgscan in the lvm startup scripts to cope " "with this on reboot after a hardware addition. If you're doing a hot-add, " "you'll have to run this by hand I think. On the other hand, if your vg is " "activated and being used, the renumbering should not affect it at all. It's " "only the activation that needs the identifier, and the worst case scenario " "is that the activation will fail without a vgscan with a complaint about a " "missing PV." msgstr "" #: LVM-HOWTO.xml:1186(para) msgid "" "The failure or removal of a drive that LVM is currently using will cause " "problems with current use and future activations of the VG that was using it." msgstr "" #: LVM-HOWTO.xml:1197(para) msgid "" "I'm trying to fill my vg, and vgdisplay/vgs says that I have 1.87 GB free, " "but when I do an lvcreate vg -L1.87G it says \"insufficient free extends\". " "What's going on?" msgstr "" #: LVM-HOWTO.xml:1204(para) msgid "" "The 1.87 GB figure is rounded to 2 decimal places, so it's probably 1.866 GB " "or something. This is a human-readable output to give you a general idea of " "how big the VG is. If you want to specify an exact size, you must use " "extents instead of some multiple of bytes." msgstr "" #: LVM-HOWTO.xml:1211(para) msgid "" "In the case of vgdisplay, use the Free PE count instead of the human " "readable capacity. \n" " Free PE / Size 478 / 1.87 GB\n" " ^^^\n" " So, this would indicate that you should do run " "\n" "# lvcreate vg -l478 Note that instead of an upper-case 'L', we " "used a lower-case 'l' to tell lvm to use extents instead of bytes." msgstr "" #: LVM-HOWTO.xml:1224(para) msgid "" "In the case of vgs, you need to instruct it to tell you how many extents are " "available: \n" "# vgs -o +vg_free_count,vg_extent_count\n" " This tell vgs to add the free extents and the total " "number of extents to the end of the vgs listing. Use the free extent number " "the same way you would in the above vgdisplay case." msgstr "" #: LVM-HOWTO.xml:1239(para) msgid "How are snapshots in LVM2 different from LVM1?" msgstr "" #: LVM-HOWTO.xml:1244(para) msgid "" "In LVM2 snapshots are read/write by default, whereas in LVM1, snapshots were " "only read-only. See for more details" msgstr "" #: LVM-HOWTO.xml:1254(para) msgid "What is the maximum size of a single LV?" msgstr "" #: LVM-HOWTO.xml:1265(para) msgid "" "For 2.4 based kernels, the maximum LV size is 2TB. For some older kernels, " "however, the limit was 1TB due to signedness problems in the block layer. " "Red Hat Enterprise Linux 3 Update 5 has fixes to allow the full 2TB LVs. " "Consult your distribution for more information in this regard." msgstr "" #: LVM-HOWTO.xml:1275(para) msgid "For 32-bit CPUs on 2.6 kernels, the maximum LV size is 16TB." msgstr "" #: LVM-HOWTO.xml:1280(para) msgid "" "For 64-bit CPUs on 2.6 kernels, the maximum LV size is 8EB. (Yes, that is a " "very large number.)" msgstr "" #: LVM-HOWTO.xml:1259(para) msgid "" "The answer to this question depends upon the CPU architecture of your " "computer and the kernel you are a running: " msgstr "" #: LVM-HOWTO.xml:1292(title) msgid "LVM 1 FAQ" msgstr "" #: LVM-HOWTO.xml:1296(para) msgid "When will there be info here?" msgstr "" #: LVM-HOWTO.xml:1301(para) msgid "When people start submitting FAQ entries ;)" msgstr "" #: LVM-HOWTO.xml:1312(title) msgid "Acquiring LVM" msgstr "" #: LVM-HOWTO.xml:1319(para) msgid "Download via FTP a tarball of LVM." msgstr "" #: LVM-HOWTO.xml:1323(para) msgid "Download the source that is under active development via CVS" msgstr "" #. label id="getlvm" #: LVM-HOWTO.xml:1313(para) msgid "The first thing you need to do is get a copy of LVM. " msgstr "" #: LVM-HOWTO.xml:1331(title) msgid "Download the source" msgstr "" #: LVM-HOWTO.xml:1336(ulink) msgid "Device Mapper" msgstr "" #: LVM-HOWTO.xml:1344(ulink) LVM-HOWTO.xml:1472(emphasis) msgid "LVM 2" msgstr "" #: LVM-HOWTO.xml:1349(para) msgid "Make sure you also grab the device mapper source" msgstr "" #: LVM-HOWTO.xml:1358(ulink) LVM-HOWTO.xml:1506(emphasis) msgid "LVM 1" msgstr "" #: LVM-HOWTO.xml:1367(para) msgid "" "The LVM 1 kernel patch must be generated using the LVM 1 source. More " "information regarding this can be found in " msgstr "" #: LVM-HOWTO.xml:1376(title) msgid "Download the development source via CVS" msgstr "" #. label id="PublicCVS" #: LVM-HOWTO.xml:1377(para) msgid "" "Note: the state of code in the CVS " "repository fluctuates wildly. It will contain bugs. Maybe ones that will " "crash LVM or the kernel. It may not even compile. Consider it alpha-quality " "code. You could lose data. You have been warned." msgstr "" #: LVM-HOWTO.xml:1386(title) msgid "Before You Begin" msgstr "" #: LVM-HOWTO.xml:1387(para) msgid "" "To follow the development progress of LVM, subscribe to the LVM mailing " "lists, linux-lvm and the appropriate commit list (see )." msgstr "" #: LVM-HOWTO.xml:1393(para) msgid "" "To build LVM from the CVS sources, you must have several GNU tools:" msgstr "" #: LVM-HOWTO.xml:1399(para) msgid "the CVS client version 1.9 or better" msgstr "" #: LVM-HOWTO.xml:1400(para) msgid "GCC 2.95.2" msgstr "" #: LVM-HOWTO.xml:1401(para) msgid "GNU make 3.79" msgstr "" #: LVM-HOWTO.xml:1402(para) msgid "autoconf, version 2.13 or better" msgstr "" #: LVM-HOWTO.xml:1408(title) msgid "Initial Setup" msgstr "" #: LVM-HOWTO.xml:1409(para) msgid "" "To make life easier in the future with regards to updating the CVS tree " "create the file $HOME/.cvsrc and insert the following " "lines. This configures useful defaults for the three most commonly used CVS " "commands. Do this now before proceeding any further." msgstr "" #: LVM-HOWTO.xml:1416(screen) #, no-wrap msgid "" "\n" "diff -u -b -B\n" "checkout -P\n" "update -d -P\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:1423(para) msgid "" "Also, if you are on a slow net link (like a dialup), you will want to add a " "line containing cvs -z5 in this file. This turns on a " "useful compression level for all CVS commands." msgstr "" #: LVM-HOWTO.xml:1431(title) msgid "Checking Out Source Code" msgstr "" #: LVM-HOWTO.xml:1435(emphasis) msgid "Device Mapper library and tools" msgstr "" #: LVM-HOWTO.xml:1438(para) msgid "The device mapper library is required to build LVM 2." msgstr "" #: LVM-HOWTO.xml:1440(para) msgid "" "The first time you download from cvs, you must login \n" " # cvs -d :pserver:cvs@sources.redhat.com:/cvs/dm login cvs\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:1447(para) LVM-HOWTO.xml:1481(para) LVM-HOWTO.xml:1515(para) msgid "" "The password is `cvs'. The command outputs nothing if successful and an " "error message if it fails. Only an initial login is required. All subsequent " "CVS commands read the password stored in the file $HOME/.cvspass for authentication." msgstr "" #: LVM-HOWTO.xml:1455(para) LVM-HOWTO.xml:1489(para) LVM-HOWTO.xml:1523(para) msgid "Use the following to check out a copy of the code" msgstr "" #: LVM-HOWTO.xml:1459(command) msgid "# cvs -d :pserver:cvs@sources.redhat.com:/cvs/dm checkout device-mapper" msgstr "" #: LVM-HOWTO.xml:1462(para) msgid "" "This will create a new directory device-mapper in your " "current directory containing the latest, up-to-the-minute device mapper code." msgstr "" #: LVM-HOWTO.xml:1474(para) msgid "" "The first time you download from cvs, you must login \n" " # cvs -d :pserver:cvs@sources.redhat.com:/cvs/lvm2 login cvs\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:1493(command) msgid "# cvs -d :pserver:cvs@sources.redhat.com:/cvs/lvm2 checkout LVM2" msgstr "" #: LVM-HOWTO.xml:1496(para) msgid "" "This will create a new directory LVM2 in your current " "directory containing the latest, up-to-the-minute LVM 2 code." msgstr "" #: LVM-HOWTO.xml:1508(para) msgid "" "The first time you download from cvs, you must login \n" " # cvs -d :pserver:cvs@sources.redhat.com:/cvs/lvm login cvs\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:1527(command) msgid "# cvs -d :pserver:cvs@sources.redhat.com:/cvs/lvm checkout LVM" msgstr "" #: LVM-HOWTO.xml:1530(para) msgid "" "This will create a new directory LVM in your current " "directory containing the latest, up-to-the-minute LVM 1 code." msgstr "" #: LVM-HOWTO.xml:1540(para) msgid "" "CVS commands work from anywhere inside the source tree, " "and recurse downward. So if you happen to issue an update from inside the " "`tools' subdirectory it will work fine, but only update the tools directory " "and it's subdirectories. In the following command examples it is assumed " "that you are at the top of the source tree." msgstr "" #: LVM-HOWTO.xml:1551(title) msgid "Code Updates" msgstr "" #: LVM-HOWTO.xml:1552(para) msgid "" "Code changes are made fairly frequently in the CVS repository. Announcements " "of this are automatically sent to the lvm-commit list." msgstr "" #: LVM-HOWTO.xml:1558(para) msgid "" "You can update your copy of the sources to match the master repository with " "the update command. It is not necessary to check out a new copy. Using " "update is significantly faster and simpler, as it will download only patches " "instead of entire files and update only those files that have changed since " "your last update. It will automatically merge any changes in the CVS " "repository with any local changes you have made as well. Just cd to the " "directory you'd like to update and then type the following." msgstr "" #: LVM-HOWTO.xml:1570(command) LVM-HOWTO.xml:1625(command) msgid "# cvs update" msgstr "" #: LVM-HOWTO.xml:1573(para) msgid "" "If you did not specify a tag when you checked out the source, this will " "update your sources to the latest version on the main branch. If you " "specified a branch tag, it will update to the latest version on that branch. " "If you specified a version tag, it will not do anything." msgstr "" #: LVM-HOWTO.xml:1583(title) msgid "Starting a Project" msgstr "" #: LVM-HOWTO.xml:1584(para) msgid "" "Discuss your ideas on the developers list before you start. Someone may be " "working on the same thing you have in mind or they may have some good ideas " "about how to go about it." msgstr "" #: LVM-HOWTO.xml:1591(title) msgid "Hacking the Code" msgstr "" #: LVM-HOWTO.xml:1592(para) msgid "" "So, have you found a bug you want to fix? Want to implement a feature from " "the TODO list? Got a new feature to implement? Hacking the code couldn't be " "easier. Just edit your copy of the sources. No need to copy files to " ".orig or anything. CVS has copies of the originals." msgstr "" #: LVM-HOWTO.xml:1600(para) msgid "" "When you have your code in a working state and have tested as best you can " "with the hardware you have, generate a patch against the current sources in the CVS repository." msgstr "" #: LVM-HOWTO.xml:1607(command) msgid "# cvs update # cvs diff > patchfile" msgstr "" #: LVM-HOWTO.xml:1611(para) msgid "" "Mail the patch to the linux-lvm or dm-devel list () with a description of what changes or additions you implemented." msgstr "" #: LVM-HOWTO.xml:1617(title) msgid "Conflicts" msgstr "" #: LVM-HOWTO.xml:1618(para) msgid "" "If someone else has been working on the same files as you have, you may find " "that there are conflicting modifications. You'll discover this when you try " "to update your sources." msgstr "" #: LVM-HOWTO.xml:1626(computeroutput) #, no-wrap msgid "" "\n" " RCS file: LVM/tools/pvcreate.c,v\n" " retrieving revision 1.5\n" " retrieving revision 1.6\n" " Merging differences between 1.5 and 1.6 into pvcreate.c\n" " rcsmerge: warning: conflicts during merge\n" " cvs server: conflicts found in tools/pvcreate.c\n" " C tools/pvcreate.c\n" msgstr "" #: LVM-HOWTO.xml:1637(para) msgid "" "Don't panic! Your working file, as it existed before the update, is saved " "under the filename .#pvcreate.c.1.5. You can always " "recover it should things go horribly wrong. The file named `pvcreate.c' now " "contains both the old (i.e. your) " "version and new version of lines that conflicted. You simply edit the file " "and resolve each conflict by deleting the unwanted version of the lines " "involved." msgstr "" #: LVM-HOWTO.xml:1648(screen) #, no-wrap msgid "" "\n" " <<<<<<< pvcreate.c\n" " j++;\n" " =======\n" " j--;\n" " >>>>>>> 1.6\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:1657(para) msgid "" "Don't forget to delete the lines with all the ``<'', ``='', and ``>'' " "symbols." msgstr "" #: LVM-HOWTO.xml:1665(title) msgid "Building the kernel modules" msgstr "" #: LVM-HOWTO.xml:1667(title) msgid "Building the device-mapper module" msgstr "" #: LVM-HOWTO.xml:1668(para) msgid "" "Device mapper is in 2.6.9 and later, so you just need to make sure it is " "enabled either as a module or builtin to the kernel. Look for /sys/class/" "misc/device-mapper or look in /proc/devices for a device-mapper entry to see " "if it is enabled. If neither are there, try modprobe dm_mod, then check " "again. For versions previous to 2.6.9, either you or your distro must patch " "the kernel to support it. Check the device mapper web page for more information." msgstr "" #: LVM-HOWTO.xml:1681(title) msgid "Build the LVM 1 kernel module" msgstr "" #: LVM-HOWTO.xml:1682(para) msgid "" "To use LVM 1 you will have to build the LVM 1 kernel module (recommended), " "or if you prefer rebuild the kernel with the LVM 1 code statically linked " "into it." msgstr "" #: LVM-HOWTO.xml:1688(para) msgid "" "Your Linux system is probably based on one of the popular distributions " "(eg., Red Hat, SuSE, Debian) in which case it is possible that you already " "have the LVM 1 module. Check the version of the tools you have on your " "system. You can do this by running any of the LVM command line tools with " "the '-h' flag. Use pvscan -h if you don't know any of the " "commands. If the version number listed at the top of the help listing is LVM " "1.0.8, use your current setup and avoid " "the rest of this section." msgstr "" #: LVM-HOWTO.xml:1701(title) msgid "Building a patch for your kernel" msgstr "" #: LVM-HOWTO.xml:1708(para) msgid "Unpack LVM 1.0.8" msgstr "" #: LVM-HOWTO.xml:1710(command) msgid "# tar zxf lvm_1.0.8.tar.gz" msgstr "" #: LVM-HOWTO.xml:1714(para) msgid "Enter the root directory of that version." msgstr "" #: LVM-HOWTO.xml:1716(command) msgid "# cd LVM/1.0.8" msgstr "" #: LVM-HOWTO.xml:1721(para) msgid "Run configure" msgstr "" #: LVM-HOWTO.xml:1723(command) msgid "# ./configure" msgstr "" #: LVM-HOWTO.xml:1726(para) msgid "" "You will need to pass the option to " "configure if your linux kernel source is not in /usr/src/linux. (Run ./configure --help to " "see all the options available)" msgstr "" #: LVM-HOWTO.xml:1736(para) msgid "Enter the PATCHES directory" msgstr "" #: LVM-HOWTO.xml:1738(command) msgid "# cd PATCHES" msgstr "" #: LVM-HOWTO.xml:1742(para) msgid "Run 'make'" msgstr "" #: LVM-HOWTO.xml:1744(command) msgid "# make" msgstr "" #: LVM-HOWTO.xml:1747(para) msgid "" "You should now have a patch called lvm-1.0.8-$KERNELVERSION.patch in the patches directory. This is the LVM kernel patch referenced " "in later sections of the howto." msgstr "" #: LVM-HOWTO.xml:1755(para) msgid "Patch the kernel" msgstr "" #: LVM-HOWTO.xml:1757(command) msgid "" "# cd /usr/src/linux ; patch -pX < /directory/lvm-1.0.8-$KERNELVERSION." "patch" msgstr "" #. label id="buildlvmpatch" #: LVM-HOWTO.xml:1702(para) msgid "" "In order to patch the linux kernel to support LVM 1.0.8, you must do the " "following: " msgstr "" #: LVM-HOWTO.xml:1764(title) msgid "Building the LVM module for Linux 2.2.17+" msgstr "" #: LVM-HOWTO.xml:1765(para) msgid "" "The 2.2 series kernel needs to be patched before you can start building, " "look elsewhere for instructions on how to patch your kernel." msgstr "" #: LVM-HOWTO.xml:1771(para) msgid "Patches:" msgstr "" #: LVM-HOWTO.xml:1779(emphasis) msgid "rawio patch" msgstr "" #: LVM-HOWTO.xml:1782(para) msgid "" "Stephen Tweedie's raw_io patch which can be found at http://www.kernel.org/pub/" "linux/kernel/people/sct/raw-io" msgstr "" #: LVM-HOWTO.xml:1791(emphasis) msgid "lvm patch" msgstr "" #: LVM-HOWTO.xml:1794(para) msgid "" "The relevant LVM 1 patch which should be built out of the PATCHES sub-" "directory of the LVM distribution. More information can be found in , Building a patch for your kernel." msgstr "" #: LVM-HOWTO.xml:1804(para) msgid "" "Once the patches have been correctly applied, you need to make sure that the " "module is actually built, LVM 1 lives under the block devices section of the " "kernel config, you should probably request that the LVM /proc information is " "compiled as well." msgstr "" #: LVM-HOWTO.xml:1811(para) msgid "Build the kernel modules as usual." msgstr "" #: LVM-HOWTO.xml:1817(title) msgid "Building the LVM modules for Linux 2.4" msgstr "" #: LVM-HOWTO.xml:1818(para) msgid "" "The 2.4 kernel comes with LVM 1 already included although you should check " "at the Sistina web site for updates, (eg. v2.4.9 kernels and earlier must " "have the latest LVM 1 patch " "applied ). When configuring your kernel look for LVM 1 under Multi-device support (RAID and LVM). LVM 1 can be " "compiled into the kernel or as a module. Build your kernel and modules and " "install then in the usual way. If you chose to build LVM as a module it will " "be called lvm-mod.o" msgstr "" #: LVM-HOWTO.xml:1831(para) msgid "" "If you want to use snapshots with ReiserFS, make sure you apply the " "linux-2.4.x-VFS-lock patch (there are copies of this in " "the LVM/1.0.8/PATCHES directory.)" msgstr "" #: LVM-HOWTO.xml:1839(title) msgid "Checking the proc file system" msgstr "" #: LVM-HOWTO.xml:1840(para) msgid "" "If your kernel was compiled with the /proc file system (most are) then you " "can verify that LVM is present by looking for a /proc/lvm directory. If this " "doesn't exist then you may have to load the module with the command" msgstr "" #: LVM-HOWTO.xml:1848(command) msgid "# modprobe lvm-mod" msgstr "" #: LVM-HOWTO.xml:1851(para) msgid "" "If /proc/lvm still does not exist then check your " "kernel configuration carefully." msgstr "" #: LVM-HOWTO.xml:1856(para) msgid "" "When LVM is active you will see entries in /proc/lvm " "for all your physical volumes, volume groups and logical volumes. In " "addition there is a file called /proc/lvm/global which gives a summary of the LVM status and also shows just which " "version of the LVM kernel you are using." msgstr "" #: LVM-HOWTO.xml:1871(title) msgid "LVM 1 Boot time scripts" msgstr "" #: LVM-HOWTO.xml:1872(para) msgid "" "Boot-time scripts are not provided as part of the LVM distribution, however " "these are quite simple to do for yourself." msgstr "" #: LVM-HOWTO.xml:1877(para) msgid "The startup of LVM requires just the following two commands:" msgstr "" #: LVM-HOWTO.xml:1882(command) msgid "# vgscan # vgchange -ay" msgstr "" #: LVM-HOWTO.xml:1886(para) msgid "And the shutdown only one:" msgstr "" #: LVM-HOWTO.xml:1891(command) msgid "# vgchange -an" msgstr "" #: LVM-HOWTO.xml:1894(para) msgid "" "Follow the instructions below depending on the distribution of Linux you are " "running." msgstr "" #: LVM-HOWTO.xml:1899(title) msgid "Caldera" msgstr "" #: LVM-HOWTO.xml:1900(para) msgid "" "It is necessary to edit the file /etc/rc.d/rc.boot. " "Look for the line that says Mounting local filesystems and " "insert the vgscan and vgchange commands just before it." msgstr "" #: LVM-HOWTO.xml:1907(para) msgid "" "You may also want to edit the the file /etc/rc.d/init.d/halt to deactivate the volume groups at shutdown. Insert the \n" " vgchange -an \n" " command near the end of this file just after the " "filesystems are unmounted or mounted read-only, before the comment that says " "Now halt or reboot." msgstr "" #: LVM-HOWTO.xml:1921(para) msgid "" "If you download the Debian lvm tool package, an initscript should be " "installed for you." msgstr "" #: LVM-HOWTO.xml:1926(para) msgid "" "If you are installing LVM from source, you will still need to build your own " "initscript:" msgstr "" #: LVM-HOWTO.xml:1931(para) msgid "" "Create a startup script in /etc/init.d/lvm containing " "the following: \n" "#!/bin/sh\n" "\n" "case \"$1\" in\n" " start)\n" "\t/sbin/vgscan\n" "\t/sbin/vgchange -ay\n" " ;;\n" " stop)\n" "\t/sbin/vgchange -an\n" " ;;\n" " restart|force-reload)\n" "\t;;\n" "esac\n" "\n" "exit 0\n" " " msgstr "" #: LVM-HOWTO.xml:1953(para) msgid "" "Then execute the commands \n" "\n" " # chmod 0755 /etc/init.d/lvm\n" " # update-rc.d lvm start 26 S . stop 82 1 .\n" "\n" " Note the dots in the last command." msgstr "" #: LVM-HOWTO.xml:1965(title) msgid "Mandrake" msgstr "" #: LVM-HOWTO.xml:1966(para) msgid "" "No initscript modifications should be necessary for current versions of " "Mandrake." msgstr "" #: LVM-HOWTO.xml:1972(title) msgid "Redhat" msgstr "" #: LVM-HOWTO.xml:1987(para) msgid "" "This init script fragment is from Red Hat 7.3 - other versions of Redhat may " "look slightly different." msgstr "" #: LVM-HOWTO.xml:1973(para) msgid "" "For Redhat 7.0 and up, you should not need to modify any initscripts to " "enable LVM at boot time if LVM is built into the kernel. If LVM is built as " "a module, it may be necessary to modify /etc/rc.d/rc.sysinit to load the LVM module by adding modprobe lvm-mod " "before the section that reads: # LVM initialization, take 2 (it " "could be on top of RAID)\n" "if [ -e /proc/lvm -a -x /sbin/vgchange -a -f /etc/lvmtab ]; then\n" " action $\"Setting up Logical Volume Management:\" /sbin/vgscan &" "&\n" " /sbin/vgchange -a y\n" " fi" msgstr "" #: LVM-HOWTO.xml:1995(para) msgid "" "For versions of Redhat older than 7.0, it is necessary to edit the file " "/etc/rc.d/rc.sysinit. Look for the line that says " "Mount all other filesystems and insert the vgscan and " "vgchange commands just before it. You should be sure that your root file " "system is mounted read/write before you run the LVM commands." msgstr "" #: LVM-HOWTO.xml:2004(para) msgid "" "You may also want to edit the the file /etc/rc.d/init.d/halt to deactivate the volume groups at shutdown. Insert the \n" "vgchange -an\n" " command near the end of this file just after the " "filesystems are mounted read-only, before the comment that says Now " "halt or reboot." msgstr "" #: LVM-HOWTO.xml:2018(title) msgid "Slackware" msgstr "" #: LVM-HOWTO.xml:2019(para) msgid "" "Slackware 8.1 requires no updating of boot time scripts in order to make LVM " "work." msgstr "" #: LVM-HOWTO.xml:2024(para) msgid "" "For versions previous to Slackware 8.1, you should apply the following patch " "to /etc/rc.d/rc.S\n" "cd /etc/rc.d\n" "cp -a rc.S rc.S.old\n" "patch -p0 < rc.S.diff\n" " (the cp part to make a backup in case)." msgstr "" #: LVM-HOWTO.xml:2035(screen) #, no-wrap msgid "" "\n" "----- snip snip file: rc.S.diff---------------\n" "--- rc.S.or\tTue Jul 17 18:11:20 2001\n" "+++ rc.S\tTue Jul 17 17:57:36 2001\n" "@@ -4,6 +4,7 @@\n" " #\n" " # Mostly written by: Patrick J. Volkerding, <volkerdi@slackware.com>\n" " #\n" "+# Added LVM support <tgs@iafrica.com>\n" "\n" " PATH=/sbin:/usr/sbin:/bin:/usr/bin\n" "\n" "@@ -28,19 +29,21 @@\n" " READWRITE=yes\n" " fi\n" "\n" "+\n" " # Check the integrity of all filesystems\n" " if [ ! READWRITE = yes ]; then\n" "- /sbin/fsck -A -a\n" "+ /sbin/fsck -a /\n" "+ # Check only the root fs first, but no others\n" " # If there was a failure, drop into single-user mode.\n" " if [ ? -gt 1 ] ; then\n" " echo\n" " echo\n" "- echo \"*******************************************************\"\n" "- echo \"*** An error occurred during the file system check. ***\"\n" "- echo \"*** You will now be given a chance to log into the ***\"\n" "- echo \"*** system in single-user mode to fix the problem. ***\"\n" "- echo \"*** Running 'e2fsck -v -y <partition>' might help. ***\"\n" "- echo \"*******************************************************\"\n" "+ echo \"************************************************************\"\n" "+ echo \"*** An error occurred during the root file system check. ***\"\n" "+ echo \"*** You will now be given a chance to log into the ***\"\n" "+ echo \"*** system in single-user mode to fix the problem. ***\"\n" "+ echo \"*** Running 'e2fsck -v -y <partition>' might help. ***\"\n" "+ echo \"************************************************************\"\n" " echo\n" " echo \"Once you exit the single-user shell, the system will reboot.\"\n" " echo\n" "@@ -82,6 +85,44 @@\n" " echo -n \"get into your machine and start looking for the problem. \"\n" " read junk;\n" " fi\n" "+ # okay / fs is clean, and mounted as rw\n" "+ # This was an addition, limits vgscan to /proc thus\n" "+ # speeding up the scan immensely.\n" "+ /sbin/mount /proc\n" "+\n" "+ # Initialize Logical Volume Manager\n" "+ /sbin/vgscan\n" "+ /sbin/vgchange -ay\n" "+\n" "+ /sbin/fsck -A -a -R\n" "+ #Check all the other filesystem, including the LVM's, excluding /\n" "+\n" "+ # If there was a failure, drop into single-user mode.\n" "+ if [ ? -gt 1 ] ; then\n" "+ echo\n" "+ echo\n" "+ echo \"*******************************************************\"\n" "+ echo \"*** An error occurred during the file system check. ***\"\n" "+ echo \"*** You will now be given a chance to log into the ***\"\n" "+ echo \"*** system in single-user mode to fix the problem. ***\"\n" "+ echo \"*** Running 'e2fsck -v -y <partition>' might help. ***\"\n" "+ echo \"*** The root filesystem is ok and mounted readwrite ***\"\n" "+ echo \"*******************************************************\"\n" "+ echo\n" "+ echo \"Once you exit the single-user shell, the system will reboot.\"\n" "+ echo\n" "+\n" "+ PS1=\"(Repair filesystem) #\"; export PS1\n" "+ sulogin\n" "+\n" "+ echo \"Unmounting file systems.\"\n" "+ umount -a -r\n" "+ mount -n -o remount,ro /\n" "+ echo \"Rebooting system.\"\n" "+ sleep 2\n" "+ reboot\n" "+ fi\n" "+\n" " else\n" " echo \"Testing filesystem status: read-write filesystem\"\n" " if cat /etc/fstab | grep ' / ' | grep umsdos 1> /dev/null 2> /dev/null ;\n" "then\n" "@@ -111,14 +152,16 @@\n" " echo -n \"Press ENTER to continue. \"\n" " read junk;\n" " fi\n" "+\n" " fi\n" "\n" "+\n" " # remove /etc/mtab* so that mount will create it with a root entry\n" " /bin/rm -f /etc/mtab* /etc/nologin /etc/shutdownpid\n" "\n" " # mount file systems in fstab (and create an entry for /)\n" " # but not NFS or SMB because TCP/IP is not yet configured\n" "-/sbin/mount -a -v -t nonfs,nosmbfs\n" "+/sbin/mount -a -v -t nonfs,nosmbfs,proc\n" "\n" " # Clean up temporary files on the /var volume:\n" " /bin/rm -f /var/run/utmp /var/run/*.pid /var/log/setup/tmp/*\n" "--snip snip snip end of file---------------\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:2145(title) msgid "SuSE" msgstr "" #: LVM-HOWTO.xml:2146(para) msgid "No changes should be necessary from 6.4 onward as LVM is included" msgstr "" #: LVM-HOWTO.xml:2153(title) msgid "LVM 2 Boot Time Scripts" msgstr "" #: LVM-HOWTO.xml:2154(para) msgid "" "For initrds, you should have: \n" " dmsetup mknodes\n" " vgscan --ignorelockingfailure\n" " vgchange -ay --ignorelockingfailure\n" " in the linuxrc to get the root LV activated before the root " "volume is accessed. Most distros seem to have this setup in their mkinitrd " "scripts now, and they also tend to have them in rc.sysinit or equivilant, so " "all volumes get activated on bootup." msgstr "" #: LVM-HOWTO.xml:2173(title) msgid "Building LVM from the Source" msgstr "" #: LVM-HOWTO.xml:2175(title) msgid "Make LVM library and tools" msgstr "" #: LVM-HOWTO.xml:2176(para) msgid "" "Change into the LVM directory and do a ./configure " "followed by make. This will make all of the libraries and " "programs." msgstr "" #: LVM-HOWTO.xml:2183(para) msgid "" "If the need arises you can change some options with the configure script. Do " "a ./configure --help to determine which options are " "supported. Most of the time this will not be necessary." msgstr "" #: LVM-HOWTO.xml:2190(para) msgid "" "There should be no errors from the build process. If there are, see Reporting Errors and Bugs on how to report this." msgstr "" #: LVM-HOWTO.xml:2196(para) msgid "" "You are welcome to fix them and send us the patches too. Patches are " "generally sent to the linux-lvm list." msgstr "" #: LVM-HOWTO.xml:2203(title) msgid "Install LVM library and tools" msgstr "" #: LVM-HOWTO.xml:2204(para) msgid "" "After the LVM source compiles properly, simply run make install to install the LVM library and tools onto your system." msgstr "" #: LVM-HOWTO.xml:2211(title) msgid "Removing LVM library and tools" msgstr "" #: LVM-HOWTO.xml:2212(para) msgid "" "To remove the library and tools you just installed, run make " "remove. You must have the original source tree you used to install " "LVM to use this feature." msgstr "" #: LVM-HOWTO.xml:2220(title) msgid "Transitioning from previous versions of LVM to LVM 1.0.8" msgstr "" #: LVM-HOWTO.xml:2221(para) msgid "" "Transitioning from previous versions of LVM to LVM 1.0.8 should be fairly " "painless. We have come up with a method to read in PV version 1 metadata " "(LVM 0.9.1 Beta7 and earlier) as well as PV version 2 metadata (LVM 0.9.1 " "Beta8 and LVM 1.0)." msgstr "" #: LVM-HOWTO.xml:2228(para) msgid "" "Warning: New PVs initialized with LVM 1.0.8 are created " "with the PV version 1 on-disk structure. This means that LVM 0.9.1 Beta8 and " "LVM 1.0 cannot read or use PVs created with 1.0.8." msgstr "" #: LVM-HOWTO.xml:2234(title) msgid "Upgrading to LVM 1.0.8 with a non-LVM root partition" msgstr "" #: LVM-HOWTO.xml:2244(emphasis) LVM-HOWTO.xml:2355(emphasis) msgid "Build LVM kernel and modules" msgstr "" #: LVM-HOWTO.xml:2247(para) LVM-HOWTO.xml:2360(para) msgid "" "Follow the steps outlined in - for instructions on how to get and build the necessary " "kernel components of LVM." msgstr "" #: LVM-HOWTO.xml:2256(emphasis) LVM-HOWTO.xml:2370(emphasis) msgid "Build the LVM user tools" msgstr "" #: LVM-HOWTO.xml:2259(para) msgid "" "Follow the steps in to build and install the " "user tools for LVM." msgstr "" #: LVM-HOWTO.xml:2268(emphasis) msgid "Setup your init scripts" msgstr "" #: LVM-HOWTO.xml:2271(para) msgid "" "Make sure you have the proper init scripts setup as per ." msgstr "" #: LVM-HOWTO.xml:2279(emphasis) msgid "Boot into the new kernel" msgstr "" #: LVM-HOWTO.xml:2282(para) msgid "" "Make sure your boot-loader is setup to load the new LVM-enhanced kernel and, " "if you are using LVM modules, put an insmod lvm-mod into " "your startup script OR extend /etc/modules.conf " "(formerly /etc/conf.modules) by adding \n" " alias block-major-58 lvm-mod\n" " alias char-major-109 lvm-mod\n" " to enable modprobe to load the LVM module (don't " "forget to enable kmod)." msgstr "" #: LVM-HOWTO.xml:2296(para) msgid "Reboot and enjoy." msgstr "" #: LVM-HOWTO.xml:2235(para) msgid "" "There are just a few simple steps to transition this setup, but it is still " "recommended that you backup your data before you try it. You have been " "warned. " msgstr "" #: LVM-HOWTO.xml:2304(title) msgid "Upgrading to LVM 1.0.8 with an LVM root partition and initrd" msgstr "" #: LVM-HOWTO.xml:2305(para) msgid "" "This is relatively straightforward if you follow the steps carefully. It is " "recommended you have a good backup and a suitable rescue disk handy just in " "case." msgstr "" #: LVM-HOWTO.xml:2375(para) msgid "" "Follow the steps in to build and install the " "user tools for LVM." msgstr "" #: LVM-HOWTO.xml:2381(para) msgid "" "Install the new tools. Once you have done this you cannot do any LVM " "manipulation as they are not compatible with the kernel you are currently " "running." msgstr "" #: LVM-HOWTO.xml:2390(emphasis) msgid "Rename the existing initrd.gz" msgstr "" #: LVM-HOWTO.xml:2395(para) msgid "" "This is so it doesn't get overwritten by the new one \n" "# mv /boot/initrd.gz /boot/initrd08.gz\n" " " msgstr "" #: LVM-HOWTO.xml:2406(filename) msgid "/etc/lilo.conf" msgstr "" #: LVM-HOWTO.xml:2405(emphasis) msgid "Edit " msgstr "" #: LVM-HOWTO.xml:2410(para) msgid "" "Make the existing boot entry point to the renamed file. You will need to " "reboot using this if something goes wrong in the next reboot. The changed " "entry will look something like this: \n" "image=/boot/vmlinux-2.2.16lvm\n" " label=lvm08\n" " read-only\n" " root=/dev/rootvg/root\n" " initrd=/boot/initrd08.gz\n" " append=\"ramdisk_size=8192\"\n" " " msgstr "" #: LVM-HOWTO.xml:2427(para) msgid "" " Run lvmcreate_initrd to create a new initial RAM " "disk \n" "# lvmcreate_initrd 2.4.9\n" " Don't forget the put the new kernel version " "in there so that it picks up the correct modules." msgstr "" #: LVM-HOWTO.xml:2441(emphasis) msgid "Add a new entry into /etc/lilo.conf" msgstr "" #: LVM-HOWTO.xml:2446(para) msgid "" "This new entry is to boot the new kernel with its new initrd. \n" "image=/boot/vmlinux-2.4.9lvm\n" " label=lvm10\n" " read-only\n" " root=/dev/rootvg/root\n" " initrd=/boot/initrd.gz\n" " append=\"ramdisk_size=8192\"\n" " " msgstr "" #: LVM-HOWTO.xml:2462(emphasis) msgid "Re-run lilo" msgstr "" #: LVM-HOWTO.xml:2467(para) msgid "" "This will install the new boot block \n" "# /sbin/lilo\n" " " msgstr "" #: LVM-HOWTO.xml:2477(emphasis) LVM-HOWTO.xml:4298(title) msgid "Reboot" msgstr "" #: LVM-HOWTO.xml:2482(para) msgid "" "When you get the LILO prompt select the new entry name (in this example " "lvm10) and your system should boot into Linux using the new LVM version." msgstr "" #: LVM-HOWTO.xml:2488(para) msgid "" "If the new kernel does not boot, then simply boot the old one and try to fix " "the problem. It may be that the new kernel does not have all the correct " "device drivers built into it, or that they are not available in the initrd. " "Remember that all device drivers (apart from LVM) needed to access the root " "device should be compiled into the kernel and not as modules." msgstr "" #: LVM-HOWTO.xml:2498(para) msgid "" "If you need to do any LVM manipulation when booted back into the old " "version, then simply recompile the old tools and install them with \n" "# make install\n" " If you do this, don't forget to install the " "new tools when you reboot into the new LVM version." msgstr "" #: LVM-HOWTO.xml:2311(para) msgid "" "The normal way of running an LVM root file system is to have " "a single non-LVM partition called /boot which contains the kernel and initial RAM disk needed to start the " "system. The system I upgraded was as follows: \n" " # df\n" "\n" "Filesystem 1k-blocks Used Available Use% Mounted on\n" "/dev/rootvg/root 253871 93384 147380 39% /\n" "/dev/hda1 17534 12944 3685 78% /boot\n" "/dev/rootvg/home 4128448 4568 3914168 0% /home\n" "/dev/rootvg/usr 1032088 332716 646944 34% /usr\n" "/dev/rootvg/var 253871 31760 209004 13% /var\n" "\n" " /boot contains " "the old kernel and an initial RAM disk as well as the LILO boot files and " "the following entry in /etc/lilo.conf\n" " # ls /boot\n" "\n" "System.map lost+found vmlinux-2.2.16lvm\n" "map module-info\t boot.0300 \n" "boot.b os2_d.b chain.b\n" "initrd.gz \n" "\n" " # tail /etc/lilo.conf\n" "\n" "image=/boot/vmlinux-2.2.16lvm\n" " label=lvm08\n" " read-only\n" " root=/dev/rootvg/root\n" " initrd=/boot/initrd.gz\n" " append=\"ramdisk_size=8192\"\n" "\n" " When you are happy with the new system " "remember to change the ``default='' entry in your lilo.conf file so that it " "is the default kernel." msgstr "" #: LVM-HOWTO.xml:2518(title) msgid "Common Tasks" msgstr "" #: LVM-HOWTO.xml:2519(para) msgid "" "The following sections outline some common administrative tasks for an LVM " "system. This is no substitute for reading the man pages." msgstr "" #: LVM-HOWTO.xml:2525(title) msgid "Initializing disks or disk partitions" msgstr "" #: LVM-HOWTO.xml:2526(para) msgid "" "Before you can use a disk or disk partition as a physical volume you will " "have to initialize it:" msgstr "" #: LVM-HOWTO.xml:2543(title) msgid "Not Recommended" msgstr "" #: LVM-HOWTO.xml:2544(para) msgid "" "Using the whole disk as a PV (as opposed to a partition spanning the whole " "disk) is not recommended because of the management issues it can create. Any " "other OS that looks at the disk will not recognize the LVM metadata and " "display the disk as being free, so it is likely it will be overwritten. LVM " "itself will work fine with whole disk PVs." msgstr "" #: LVM-HOWTO.xml:2536(para) msgid "" "Run pvcreate on the disk: \n" "# pvcreate /dev/hdb\n" " This creates a volume group descriptor at the " "start of disk. " msgstr "" #: LVM-HOWTO.xml:2558(title) msgid "DANGEROUS" msgstr "" #: LVM-HOWTO.xml:2559(para) msgid "" "The following commands will destroy the partition table on the disk being " "operated on. Be very sure it is the correct disk." msgstr "" #: LVM-HOWTO.xml:2552(para) msgid "" "If you get an error that LVM can't initialize a disk with a partition table " "on it, first make sure that the disk you are operating on is the correct " "one. If you are very sure that it is, run the following: \n" "# dd if=/dev/zero of=/dev/diskname bs=1k count=1\n" "# blockdev --rereadpt /dev/diskname\n" "" msgstr "" #: LVM-HOWTO.xml:2577(para) msgid "" "When using LVM 1 on PCs with DOS partitions, set the partition type to 0x8e " "using fdisk or some other similar program. This step is unnecessary on PPC " "systems or when using LVM 2." msgstr "" #: LVM-HOWTO.xml:2586(para) msgid "" "Run pvcreate on the partition: \n" "# pvcreate /dev/hdb1\n" " This creates a volume group descriptor at the start " "of the /dev/hdb1 partition." msgstr "" #: LVM-HOWTO.xml:2531(para) msgid "For entire disks: For partitions: " msgstr "" #: LVM-HOWTO.xml:2600(title) msgid "Creating a volume group" msgstr "" #: LVM-HOWTO.xml:2601(para) msgid "" "Use the 'vgcreate' program: \n" "# vgcreate my_volume_group /dev/hda1 /dev/hdb1 \n" " NOTE: If you are using LVM 1 with " "devfs it is essential to use the full devfs name of the device rather than " "the symlinked name in /dev. So the " "above would be: \n" "# vgcreate my_volume_group /dev/ide/host0/bus0/target0/lun0/part1 " "\\\n" " /dev/ide/host0/bus0/target1/lun0/part1\n" " LVM 2 does not have this restriction." msgstr "" #: LVM-HOWTO.xml:2617(para) msgid "" "You can also specify the extent size with this command if the default of " "32MB is not suitable for you with the '-s' switch. In addition you can put " "some limits on the number of physical or logical volumes the volume can have." msgstr "" #: LVM-HOWTO.xml:2626(title) msgid "Activating a volume group" msgstr "" #: LVM-HOWTO.xml:2627(para) msgid "" "After rebooting the system or running vgchange -an, you " "will not be able to access your VGs and LVs. To reactivate the volume group, " "run: \n" "# vgchange -a y my_volume_group\n" " " msgstr "" #: LVM-HOWTO.xml:2637(title) msgid "Removing a volume group" msgstr "" #: LVM-HOWTO.xml:2638(para) msgid "" "Make sure that no logical volumes are present in the volume group, see later " "section for how to do this." msgstr "" #: LVM-HOWTO.xml:2643(para) msgid "" "Deactivate the volume group: \n" "# vgchange -a n my_volume_group\n" " " msgstr "" #: LVM-HOWTO.xml:2650(para) msgid "" "Now you actually remove the volume group: \n" "# vgremove my_volume_group\n" " " msgstr "" #: LVM-HOWTO.xml:2658(title) msgid "Adding physical volumes to a volume group" msgstr "" #: LVM-HOWTO.xml:2659(para) msgid "" "Use 'vgextend' to add an initialized physical volume to an existing volume " "group. \n" "# vgextend my_volume_group /dev/hdc1\n" " ^^^^^^^^^ new physical volume\n" " " msgstr "" #: LVM-HOWTO.xml:2669(title) msgid "Removing physical volumes from a volume group" msgstr "" #: LVM-HOWTO.xml:2670(para) msgid "" "Make sure that the physical volume isn't used by any logical volumes by " "using then 'pvdisplay' command: \n" "# pvdisplay /dev/hda1\n" "\n" "--- Physical volume ---\n" "PV Name /dev/hda1\n" "VG Name myvg\n" "PV Size 1.95 GB / NOT usable 4 MB [LVM: 122 KB]\n" "PV# 1\n" "PV Status available\n" "Allocatable yes (but full)\n" "Cur LV 1\n" "PE Size (KByte) 4096\n" "Total PE 499\n" "Free PE 0\n" "Allocated PE 499\n" "PV UUID Sd44tK-9IRw-SrMC-MOkn-76iP-iftz-OVSen7\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:2693(para) msgid "" "If the physical volume is still used you will have to migrate the data to " "another physical volume using pvmove." msgstr "" #: LVM-HOWTO.xml:2698(para) msgid "" "Then use 'vgreduce' to remove the physical volume: \n" "# vgreduce my_volume_group /dev/hda1\n" " " msgstr "" #: LVM-HOWTO.xml:2706(title) msgid "Creating a logical volume" msgstr "" #: LVM-HOWTO.xml:2708(para) msgid "" "To create a 1500MB linear LV named 'testlv' and its block device special '/" "dev/testvg/testlv': \n" "# lvcreate -L1500 -ntestlv testvg\n" " " msgstr "" #: LVM-HOWTO.xml:2716(para) msgid "" "To create a 100 LE large logical volume with 2 stripes and stripe size 4 KB. " "\n" "# lvcreate -i2 -I4 -l100 -nanothertestlv testvg\n" " " msgstr "" #: LVM-HOWTO.xml:2724(para) msgid "" "If you want to create an LV that uses the entire VG, use vgdisplay to find " "the Total PE size, then use that when running lvcreate. " "\n" "# vgdisplay testvg | grep \"Total PE\"\n" "Total PE 10230\n" "# lvcreate -l 10230 testvg -n mylv\n" " This will create an LV called mylv filling the testvg " "VG." msgstr "" #: LVM-HOWTO.xml:2738(para) msgid "" "If you want the logical volume to be allocated from a specific physical " "volume in the volume group, specify the PV or PVs at the end of the lvcreate " "command line. \n" "# lvcreate -L 1500 -ntestlv testvg /dev/sdg\n" " " msgstr "" #: LVM-HOWTO.xml:2749(title) msgid "Removing a logical volume" msgstr "" #: LVM-HOWTO.xml:2750(para) msgid "" "A logical volume must be closed before it can be removed: \n" "# umount /dev/myvg/homevol\n" "# lvremove /dev/myvg/homevol\n" "lvremove -- do you really want to remove \"/dev/myvg/homevol\"? [y/" "n]: y\n" "lvremove -- doing automatic backup of volume group \"myvg\"\n" "lvremove -- logical volume \"/dev/myvg/homevol\" successfully removed\n" " " msgstr "" #: LVM-HOWTO.xml:2762(title) msgid "Extending a logical volume" msgstr "" #: LVM-HOWTO.xml:2763(para) msgid "" "To extend a logical volume you simply tell the lvextend command how much you " "want to increase the size. You can specify how much to grow the volume, or " "how large you want it to grow to: \n" "# lvextend -L12G /dev/myvg/homevol\n" "lvextend -- extending logical volume \"/dev/myvg/homevol\" " "to 12 GB\n" "lvextend -- doing automatic backup of volume group \"myvg\"\n" "lvextend -- logical volume \"/dev/myvg/homevol\" successfully extended\n" " will extend /dev/myvg/homevol to 12 " "Gigabytes." msgstr "" #: LVM-HOWTO.xml:2776(para) msgid "" "\n" "# lvextend -L+1G /dev/myvg/homevol\n" "lvextend -- extending logical volume \"/dev/myvg/homevol\" " "to 13 GB\n" "lvextend -- doing automatic backup of volume group \"myvg\"\n" "lvextend -- logical volume \"/dev/myvg/homevol\" successfully extended\n" " will add another gigabyte to /dev/myvg/homevol." msgstr "" #: LVM-HOWTO.xml:2786(para) msgid "" "After you have extended the logical volume it is necessary to increase the " "file system size to match. how you do this depends on the file system you " "are using." msgstr "" #: LVM-HOWTO.xml:2792(para) msgid "" "By default, most file system resizing tools will increase the size of the " "file system to be the size of the underlying logical volume so you don't " "need to worry about specifying the same size for each of the two commands." msgstr "" #: LVM-HOWTO.xml:2803(emphasis) msgid "ext2/ext3" msgstr "" #: LVM-HOWTO.xml:2808(para) msgid "" "Unless you have patched your kernel with the ext2online patch it is " "necessary to unmount the file system before resizing it. (It seems that the " "online resizing patch is rather dangerous, so use at your own risk) " "\n" " # umount /dev/myvg/homevol/dev/myvg/homevol\n" " # resize2fs /dev/myvg/homevol\n" " # mount /dev/myvg/homevol /home\n" " " msgstr "" #: LVM-HOWTO.xml:2820(para) msgid "" "If you don't have e2fsprogs 1.19 or later, you can download the ext2resize " "command from ext2resize." "sourceforge.net and use that: \n" " # umount /dev/myvg/homevol/dev/myvg/homevol\n" " # ext2resize /dev/myvg/homevol\n" " # mount /dev/myvg/homevol /home\n" " " msgstr "" #: LVM-HOWTO.xml:2837(title) LVM-HOWTO.xml:2981(title) msgid "LVM 2 Caveat" msgstr "" #: LVM-HOWTO.xml:2838(para) LVM-HOWTO.xml:2982(para) msgid "" "There is currently no e2fsadm equivalent for LVM 2 and the e2fsadm that " "ships with LVM 1 does not work with LVM 2." msgstr "" #: LVM-HOWTO.xml:2854(title) LVM-HOWTO.xml:3335(title) #: LVM-HOWTO.xml:3441(title) msgid "Note" msgstr "" #: LVM-HOWTO.xml:2855(para) msgid "You will still need to unmount the file system before running e2fsadm." msgstr "" #: LVM-HOWTO.xml:2832(para) msgid "" "For ext2 there is an easier way. LVM 1 ships with a utility called e2fsadm " "which does the lvextend and resize2fs for you (it can also do file system " "shrinking, see the next section). so the single command " "\n" " # e2fsadm -L+1G /dev/myvg/homevol\n" " is equivalent to the two commands: \n" " # lvextend -L+1G /dev/myvg/homevol\n" " # resize2fs /dev/myvg/homevol\n" " " msgstr "" #: LVM-HOWTO.xml:2865(emphasis) LVM-HOWTO.xml:3005(emphasis) msgid "reiserfs" msgstr "" #: LVM-HOWTO.xml:2875(para) msgid "" "Online: \n" " # resize_reiserfs -f /dev/myvg/homevol\n" " " msgstr "" #: LVM-HOWTO.xml:2884(para) msgid "" "Offline: \n" " # umount /dev/myvg/homevol\n" " # resize_reiserfs /dev/myvg/homevol\n" " # mount -treiserfs /dev/myvg/homevol /home\n" " " msgstr "" #: LVM-HOWTO.xml:2870(para) msgid "" "Reiserfs file systems can be resized when mounted or unmounted as you " "prefer: " msgstr "" #: LVM-HOWTO.xml:2899(emphasis) LVM-HOWTO.xml:3023(emphasis) msgid "xfs" msgstr "" #: LVM-HOWTO.xml:2904(para) msgid "" "XFS file systems must be mounted to be resized and the mount-point is " "specified rather than the device name. \n" " # xfs_growfs /home\n" " " msgstr "" #: LVM-HOWTO.xml:2915(emphasis) LVM-HOWTO.xml:3035(emphasis) msgid "jfs" msgstr "" #: LVM-HOWTO.xml:2920(para) msgid "" "Just like XFS the JFS file system must be mounted to be resized and the " "mount-point is specified rather than the device name. You need at least " "Version 1.0.21 of the jfs-utils to do this. \n" "# mount -o remount,resize /home\n" " " msgstr "" #: LVM-HOWTO.xml:2929(title) msgid "Known Kernel Bug" msgstr "" #: LVM-HOWTO.xml:2930(para) msgid "" "Some kernel versions have problems with this syntax (2.6.0 is known to have " "this problem). In this case you have to explicitly specify the new size of " "the filesystem in blocks. This is extremely error prone as you " "must know the blocksize of your filesystem and " "calculate the new size based on those units." msgstr "" #: LVM-HOWTO.xml:2939(para) msgid "" "Example: If you were to resize a JFS file system to 4 gigabytes that has 4k " "blocks, you would write: \n" "# mount -o remount,resize=1048576 /home\n" " " msgstr "" #: LVM-HOWTO.xml:2952(title) msgid "Reducing a logical volume" msgstr "" #: LVM-HOWTO.xml:2953(para) msgid "" "Logical volumes can be reduced in size as well as increased. However, it is " "very important to remember to reduce the size of the " "file system or whatever is residing in the volume before shrinking the " "volume itself, otherwise you risk losing data." msgstr "" #: LVM-HOWTO.xml:2965(emphasis) msgid "ext2" msgstr "" #: LVM-HOWTO.xml:2970(para) msgid "" "If you are using LVM 1 with ext2 as the file system then you can use the " "e2fsadm command mentioned earlier to take care of both the file system and " "volume resizing as follows: \n" "# umount /home\n" "# e2fsadm -L-1G /dev/myvg/homevol\n" "# mount /home\n" " " msgstr "" #: LVM-HOWTO.xml:2991(para) msgid "" "If you prefer to do this manually you must know the new size of the volume " "in blocks and use the following commands: \n" "# umount /home\n" "# resize2fs /dev/myvg/homevol 524288\n" "# lvreduce -L-1G /dev/myvg/homevol\n" "# mount /home\n" " " msgstr "" #: LVM-HOWTO.xml:3010(para) msgid "" "Reiserfs seems to prefer to be unmounted when shrinking \n" "# umount /home\n" "# resize_reiserfs -s-1G /dev/myvg/homevol\n" "# lvreduce -L-1G /dev/myvg/homevol\n" "# mount -treiserfs /dev/myvg/homevol /home\n" " " msgstr "" #: LVM-HOWTO.xml:3028(para) msgid "There is no way to shrink XFS file systems." msgstr "" #: LVM-HOWTO.xml:3040(para) msgid "There is no way to shrink JFS file systems." msgstr "" #: LVM-HOWTO.xml:3047(title) msgid "Migrating data off of a physical volume" msgstr "" #: LVM-HOWTO.xml:3048(para) msgid "" "To take a disk out of service it must first have all of its active physical " "extents moved to one or more of the remaining disks in the volume group. " "There must be enough free physical extents in the remaining PVs to hold the " "extents to be copied from the old disk. For further detail see ." msgstr "" #: LVM-HOWTO.xml:3058(title) msgid "Disk partitioning" msgstr "" #: LVM-HOWTO.xml:3060(title) msgid "Multiple partitions on the same disk" msgstr "" #: LVM-HOWTO.xml:3061(para) msgid "" "LVM allows you to create PVs (physical volumes) out of almost any block " "device so, for example, the following are all valid commands and will work " "quite happily in an LVM environment: \n" "# pvcreate /dev/sda1\n" "# pvcreate /dev/sdf\n" "# pvcreate /dev/hda8\n" "# pvcreate /dev/hda6\n" "# pvcreate /dev/md1\n" " " msgstr "" #: LVM-HOWTO.xml:3080(para) msgid "Administrative convenience" msgstr "" #: LVM-HOWTO.xml:3084(para) msgid "" "It's easier to keep track of the hardware in a system if each real disk only " "appears once. This becomes particularly true if a disk fails." msgstr "" #: LVM-HOWTO.xml:3092(para) msgid "To avoid striping performance problems" msgstr "" #: LVM-HOWTO.xml:3096(para) msgid "" "LVM can't tell that two PVs are on the same physical disk, so if you create " "a striped LV then the stripes could be on different partitions on the same " "disk resulting in a decrease in " "performance rather than an increase." msgstr "" #: LVM-HOWTO.xml:3109(para) msgid "Migration of existing system to LVM" msgstr "" #: LVM-HOWTO.xml:3113(para) msgid "" "On a system with few disks it may be necessary to move data around " "partitions to do the conversion (see )" msgstr "" #: LVM-HOWTO.xml:3121(para) msgid "Splitting one big disk between Volume Groups" msgstr "" #: LVM-HOWTO.xml:3125(para) msgid "" "If you have a very large disk and want to have more than one volume group " "for administrative purposes then it is necessary to partition the drive into " "more than one area." msgstr "" #: LVM-HOWTO.xml:3074(para) msgid "" "In a normal production system it is recommended that only one " "PV exists on a single real disk, for the following reasons: " "However it may be desirable to do this for some reasons: " msgstr "" #: LVM-HOWTO.xml:3134(para) msgid "" "If you do have a disk with more than one partition and both of those " "partitions are in the same volume group, take care to specify which " "partitions are to be included in a logical volume when creating striped " "volumes." msgstr "" #: LVM-HOWTO.xml:3141(para) msgid "" "The recommended method of partitioning a disk is to create a single " "partition that covers the whole disk. This avoids any nasty accidents with " "whole disk drive device nodes and prevents the kernel warning about unknown " "partition types at boot-up." msgstr "" #: LVM-HOWTO.xml:3149(title) msgid "Sun disk labels" msgstr "" #: LVM-HOWTO.xml:3150(para) msgid "" "You need to be especially careful on SPARC systems where the disks have Sun " "disk labels on them." msgstr "" #: LVM-HOWTO.xml:3155(para) msgid "" "The normal layout for a Sun disk label is for the first partition to start " "at block zero of the disk, thus the first partition also covers the area " "containing the disk label itself. This works fine for ext2 filesystems (and " "is essential for booting using SILO) but such partitions should not be used " "for LVM. This is because LVM starts writing at the very start of the device " "and will overwrite the disk label." msgstr "" #: LVM-HOWTO.xml:3165(para) msgid "" "If you want to use a disk with a Sun disk label with LVM, make sure that the " "partition you are going to use starts at cylinder 1 or higher." msgstr "" #: LVM-HOWTO.xml:3173(title) msgid "Recipes" msgstr "" #: LVM-HOWTO.xml:3174(para) msgid "" "This section details several different recipes for setting up " "lvm. The hope is that the reader will adapt these recipes to their own " "system and needs." msgstr "" #: LVM-HOWTO.xml:3180(title) msgid "Setting up LVM on three SCSI disks" msgstr "" #: LVM-HOWTO.xml:3181(para) LVM-HOWTO.xml:3329(para) msgid "" "For this recipe, the setup has three SCSI disks that will be put into a " "logical volume using LVM. The disks are at /dev/sda, /dev/sdb, and /dev/sdc." msgstr "" #: LVM-HOWTO.xml:3187(title) msgid "Preparing the disks" msgstr "" #: LVM-HOWTO.xml:3188(para) LVM-HOWTO.xml:3347(para) msgid "" "Before you can use a disk in a volume group you will have to prepare it:" msgstr "" #: LVM-HOWTO.xml:3193(title) LVM-HOWTO.xml:3352(title) msgid "Warning!" msgstr "" #: LVM-HOWTO.xml:3195(emphasis) LVM-HOWTO.xml:3354(emphasis) msgid "The following will destroy any data on /dev/sda, /dev/sdb, and /dev/sdc" msgstr "" #: LVM-HOWTO.xml:3202(para) msgid "" "Run pvcreate on the disks \n" "# pvcreate /dev/sda\n" "# pvcreate /dev/sdb\n" "# pvcreate /dev/sdc\n" " This creates a volume group descriptor area (VGDA) at " "the start of the disks." msgstr "" #: LVM-HOWTO.xml:3214(title) LVM-HOWTO.xml:3373(title) msgid "Setup a Volume Group" msgstr "" #: LVM-HOWTO.xml:3217(para) msgid "" "Create a volume group \n" "# vgcreate my_volume_group /dev/sda /dev/sdb /dev/sdc/\n" " " msgstr "" #: LVM-HOWTO.xml:3226(para) msgid "" "Run vgdisplay to verify volume group \n" "# vgdisplay\n" "# vgdisplay\n" "--- Volume Group ---\n" "VG Name\t my_volume_group\n" "VG Access read/write\n" "VG Status available/resizable\n" "VG # 1\n" "MAX LV 256\n" "Cur LV 0\n" "Open LV 0\n" "MAX LV Size 255.99 GB\n" "Max PV 256\n" "Cur PV 3\n" "Act PV 3\n" "VG Size 1.45 GB\n" "PE Size 4 MB\n" "Total PE 372\n" "Alloc PE / Size 0 / 0\n" "Free PE / Size 372/ 1.45 GB\n" "VG UUID nP2PY5-5TOS-hLx0-FDu0-2a6N-f37x-0BME0Y\n" " The most important things to verify are that the " "first three items are correct and that the VG Size item is the proper size " "for the amount of space in all four of your disks." msgstr "" #: LVM-HOWTO.xml:3260(title) LVM-HOWTO.xml:3419(title) msgid "Creating the Logical Volume" msgstr "" #: LVM-HOWTO.xml:3261(para) LVM-HOWTO.xml:3420(para) msgid "" "If the volume group looks correct, it is time to create a logical volume on " "top of the volume group." msgstr "" #: LVM-HOWTO.xml:3266(para) msgid "" "You can make the logical volume any size you like. (It is similar to a " "partition on a non LVM setup.) For this example we will create just a single " "logical volume of size 1GB on the volume group. We will not use striping " "because it is not currently possible to add a disk to a stripe set after the " "logical volume is created. \n" "# lvcreate -L1G -nmy_logical_volume my_volume_group\n" "lvcreate -- doing automatic backup of \"my_volume_group\"\n" "lvcreate -- logical volume \"/dev/my_volume_group/my_logical_volume\" " "successfully created\n" " " msgstr "" #: LVM-HOWTO.xml:3281(title) LVM-HOWTO.xml:3451(title) msgid "Create the File System" msgstr "" #: LVM-HOWTO.xml:3282(para) msgid "" "Create an ext2 file system on the logical volume \n" "# mke2fs /dev/my_volume_group/my_logical_volume\n" "mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09\n" "Filesystem label=\n" "OS type: Linux\n" "Block size=4096 (log=2)\n" "Fragment size=4096 (log=2)\n" "131072 inodes, 262144 blocks\n" "13107 blocks (5.00%) reserved for the super user\n" "First data block=0\n" "9 block groups\n" "32768 blocks per group, 32768 fragments per group\n" "16384 inodes per group\n" "Superblock backups stored on blocks:\n" " 32768, 98304, 163840, 229376\n" "\n" "Writing inode tables: done\n" "Writing superblocks and filesystem accounting information: done\n" " " msgstr "" #: LVM-HOWTO.xml:3306(title) LVM-HOWTO.xml:3476(title) msgid "Test the File System" msgstr "" #: LVM-HOWTO.xml:3307(para) msgid "" "Mount the logical volume and check to make sure everything looks correct " "\n" "# mount /dev/my_volume_group/my_logical_volume /mnt\n" "# df\n" "Filesystem 1k-blocks Used Available Use% " "Mounted on\n" "/dev/hda1 1311552 628824 616104 51% /\n" "/dev/my_volume_group/my_logical_volume\n" " 1040132 20 987276 0% /mnt\n" " " msgstr "" #: LVM-HOWTO.xml:3320(para) msgid "" "If everything worked properly, you should now have a logical volume with and " "ext2 file system mounted at /mnt." msgstr "" #: LVM-HOWTO.xml:3328(title) msgid "Setting up LVM on three SCSI disks with striping" msgstr "" #: LVM-HOWTO.xml:3337(emphasis) msgid "" "It is not currently possible to add a disk to a striped logical volume in " "LVM 1. Use LVM 2 with the lvm 2 format metadata if you wish to be able to do " "so able to do so." msgstr "" #: LVM-HOWTO.xml:3346(title) msgid "Preparing the disk partitions" msgstr "" #: LVM-HOWTO.xml:3361(para) msgid "" "Run pvcreate on the disks: \n" "# pvcreate /dev/sda\n" "# pvcreate /dev/sdb\n" "# pvcreate /dev/sdc\n" " This creates a volume group descriptor area (VGDA) at " "the start of the disks." msgstr "" #: LVM-HOWTO.xml:3378(para) msgid "" "Create a volume group \n" "# vgcreate my_volume_group /dev/sda /dev/sdb /dev/sdc\n" " " msgstr "" #: LVM-HOWTO.xml:3387(para) msgid "" "Run vgdisplay to verify volume group \n" "# vgdisplay\n" "--- Volume Group ---\n" "VG Name\t my_volume_group\n" "VG Access read/write\n" "VG Status available/resizable\n" "VG # 1\n" "MAX LV 256\n" "Cur LV 0\n" "Open LV 0\n" "MAX LV Size 255.99 GB\n" "Max PV 256\n" "Cur PV 3\n" "Act PV 3\n" "VG Size 1.45 GB\n" "PE Size 4 MB\n" "Total PE 372\n" "Alloc PE / Size 0 / 0\n" "Free PE / Size 372/ 1.45 GB\n" "VG UUID nP2PY5-5TOS-hLx0-FDu0-2a6N-f37x-0BME0Y\n" " The most important things to verify are that the " "first three items are correct and that the VG Size item is the proper size " "for the amount of space in all four of your disks." msgstr "" #: LVM-HOWTO.xml:3425(para) msgid "" "You can make the logical volume any size you like (up to the size of the VG " "you are creating it on; it is similar to a partition on a non LVM setup). " "For this example we will create just a single logical volume of size 1GB on " "the volume group. The logical volume will be a striped set using for the 4k " "stripe size. This should increase the performance of the logical volume. " "\n" "# lvcreate -i3 -I4 -L1G -nmy_logical_volume my_volume_group\n" "lvcreate -- rounding 1048576 KB to stripe boundary size " "1056768 KB / 258 PE\n" "lvcreate -- doing automatic backup of \"my_volume_group\"\n" "lvcreate -- logical volume \"/dev/my_volume_group/my_logical_volume\" " "successfully created\n" " " msgstr "" #: LVM-HOWTO.xml:3442(para) msgid "" "If you create the logical volume with a '-i2' you will only use two of the " "disks in your volume group. This is useful if you want to create two logical " "volumes out of the same physical volume, but we will not touch that in this " "recipe." msgstr "" #: LVM-HOWTO.xml:3452(para) msgid "" "Create an ext2 file system on the logical volume \n" "# mke2fs /dev/my_volume_group/my_logical_volume\n" "mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09\n" "Filesystem label=\n" "OS type: Linux\n" "Block size=4096 (log=2)\n" "Fragment size=4096 (log=2)\n" "132192 inodes, 264192 blocks\n" "13209 blocks (5.00%) reserved for the super user\n" "First data block=0\n" "9 block groups\n" "32768 blocks per group, 32768 fragments per group\n" "14688 inodes per group\n" "Superblock backups stored on blocks:\n" " 32768, 98304, 163840, 229376\n" "\n" "Writing inode tables: done\n" "Writing superblocks and filesystem accounting information: done\n" " " msgstr "" #: LVM-HOWTO.xml:3477(para) msgid "" "Mount the file system on the logical volume \n" "# mount /dev/my_volume_group/my_logical_volume /mnt\n" " and check to make sure everything looks correct " "\n" "# df\n" "Filesystem 1k-blocks Used Available Use% " "Mounted on\n" "/dev/hda1 1311552 628824 616104 51% /\n" "/dev/my_volume_group/my_logical_volume\n" " 1040132 20 987276 0% /mnt\n" " If everything worked properly, you should now have a " "logical volume mounted at /mnt." msgstr "" #: LVM-HOWTO.xml:3496(title) msgid "Add a new disk to a multi-disk SCSI system" msgstr "" #: LVM-HOWTO.xml:3497(title) msgid "Current situation" msgstr "" #: LVM-HOWTO.xml:3498(para) msgid "" "A data centre machine has 6 disks attached as follows: \n" "# pvscan\n" "pvscan -- ACTIVE PV \"/dev/sda\" of VG \"dev\" [1.95 " "GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sdb\" of VG \"sales\" [1.95 GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sdc\" of VG \"ops\" [1.95 GB / 44 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdd\" of VG \"dev\" [1.95 GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sde1\" of VG \"ops\" [996 MB / 52 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sde2\" of VG \"sales\" [996 MB / 944 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdf1\" of VG \"ops\" [996 MB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sdf2\" of VG \"dev\" [996 MB / 72 MB free]\n" "pvscan -- total: 8 [11.72 GB] / in use: 8 [11.72 GB] / in no VG: 0 [0]\n" "\n" "# df\n" "Filesystem 1k-blocks Used Available Use% " "Mounted on\n" "/dev/dev/cvs 1342492 516468 757828 41% /mnt/dev/cvs\n" "/dev/dev/users 2064208 2060036 4172 100% /mnt/dev/users\n" "/dev/dev/build 1548144 1023041 525103 66% /mnt/dev/build\n" "/dev/ops/databases 2890692 2302417 588275 79% /mnt/ops/databases\n" "/dev/sales/users 2064208 871214 1192994 42% /mnt/sales/users\n" "/dev/ops/batch 1032088 897122 134966 86% /mnt/ops/batch\n" " As you can see the \"dev\" and \"ops\" groups are " "getting full so a new disk is purchased and added to the system. It becomes " "/dev/sdg." msgstr "" #: LVM-HOWTO.xml:3527(title) msgid "Prepare the disk partitions" msgstr "" #: LVM-HOWTO.xml:3528(para) msgid "" "The new disk is to be shared equally between ops and dev so it is " "partitioned into two physical volumes /dev/sdg1 and /dev/sdg2 : \n" "# fdisk /dev/sdg\n" "\n" "Device contains neither a valid DOS partition table, nor Sun or SGI\n" "disklabel Building a new DOS disklabel. Changes will remain in memory\n" "only, until you decide to write them. After that, of course, the\n" "previous content won't be recoverable.\n" "\n" "Command (m for help): n\n" "Command action\n" " e extended\n" " p primary partition (1-4)\n" "p\n" "Partition number (1-4): 1\n" "First cylinder (1-1000, default 1):\n" "Using default value 1\n" "Last cylinder or +size or +sizeM or +sizeK (1-1000, default 1000): 500\n" "\n" "Command (m for help): n\n" "Command action\n" " e extended\n" " p primary partition (1-4)\n" "p\n" "Partition number (1-4): 2\n" "First cylinder (501-1000, default 501): \n" "Using default value 501\n" "Last cylinder or +size or +sizeM or +sizeK (501-1000, default 1000):" " \n" "Using default value 1000\n" "\n" "Command (m for help): t\n" "Partition number (1-4): 1\n" "Hex code (type L to list codes): 8e\n" "Changed system type of partition 1 to 8e (Unknown)\n" "\n" "Command (m for help): t\n" "Partition number (1-4): 2\n" "Hex code (type L to list codes): 8e\n" "Changed system type of partition 2 to 8e (Unknown)\n" "\n" "Command (m for help): w\n" "The partition table has been altered!\n" "\n" "Calling ioctl() to re-read partition table.\n" "\n" "WARNING: If you have created or modified any DOS 6.x partitions,\n" "please see the fdisk manual page for additional information.\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:3582(para) msgid "" "Next physical volumes are created on this partition: \n" "# pvcreate /dev/sdg1\n" "pvcreate -- physical volume \"/dev/sdg1\" successfully " "created\n" "\n" "# pvcreate /dev/sdg2\n" "pvcreate -- physical volume \"/dev/sdg2\" successfully " "created\n" " " msgstr "" #: LVM-HOWTO.xml:3594(title) msgid "Add the new disks to the volume groups" msgstr "" #: LVM-HOWTO.xml:3595(para) msgid "" "The volumes are then added to the dev and ops volume groups: \n" "# vgextend ops /dev/sdg1\n" "vgextend -- INFO: maximum logical volume size is 255.99 " "Gigabyte\n" "vgextend -- doing automatic backup of volume group \"ops\"\n" "vgextend -- volume group \"ops\" successfully extended\n" "\n" "# vgextend dev /dev/sdg2\n" "vgextend -- INFO: maximum logical volume size is 255.99 " "Gigabyte\n" "vgextend -- doing automatic backup of volume group \"dev\"\n" "vgextend -- volume group \"dev\" successfully extended\n" "\n" "# pvscan\n" "pvscan -- reading all physical volumes (this may take a " "while...)\n" "pvscan -- ACTIVE PV \"/dev/sda\" of VG \"dev\" [1.95 GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sdb\" of VG \"sales\" [1.95 GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sdc\" of VG \"ops\" [1.95 GB / 44 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdd\" of VG \"dev\" [1.95 GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sde1\" of VG \"ops\" [996 MB / 52 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sde2\" of VG \"sales\" [996 MB / 944 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdf1\" of VG \"ops\" [996 MB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sdf2\" of VG \"dev\" [996 MB / 72 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdg1\" of VG \"ops\" [996 MB / 996 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdg2\" of VG \"dev\" [996 MB / 996 MB free]\n" "pvscan -- total: 10 [13.67 GB] / in use: 10 [13.67 GB] / in no VG: 0 [0]\n" " " msgstr "" #: LVM-HOWTO.xml:3625(title) msgid "Extend the file systems" msgstr "" #: LVM-HOWTO.xml:3626(para) msgid "" "The next thing to do is to extend the file systems so that the users can " "make use of the extra space." msgstr "" #: LVM-HOWTO.xml:3631(para) msgid "" "There are tools to allow online-resizing of ext2 file systems but here we " "take the safe route and unmount the two file systems before resizing them: " "\n" "# umount /mnt/ops/batch\n" "# umount /mnt/dev/users\n" " " msgstr "" #: LVM-HOWTO.xml:3641(para) msgid "" "We then use the e2fsadm command to resize the logical volume and the ext2 " "file system on one operation. We are using ext2resize instead of resize2fs " "(which is the default command for e2fsadm) so we define the environment " "variable E2FSADM_RESIZE_CMD to tell e2fsadm to use that command. \n" "# export E2FSADM_RESIZE_CMD=ext2resize\n" "# e2fsadm /dev/ops/batch -L+500M\n" "e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09\n" "Pass 1: Checking inodes, blocks, and sizes\n" "Pass 2: Checking directory structure\n" "Pass 3: Checking directory connectivity\n" "Pass 4: Checking reference counts\n" "Pass 5: Checking group summary information\n" "/dev/ops/batch: 11/131072 files (0.0<!-- non-contiguous), 4127/262144 " "blocks\n" "lvextend -- extending logical volume \"/dev/ops/batch\" to 1.49 GB\n" "lvextend -- doing automatic backup of volume group \"ops\"\n" "lvextend -- logical volume \"/dev/ops/batch\" successfully extended\n" "\n" "ext2resize v1.1.15 - 2000/08/08 for EXT2FS 0.5b\n" "e2fsadm -- ext2fs in logical volume \"/dev/ops/batch\" successfully extended " "to 1.49 GB\n" "\n" "\n" "# e2fsadm /dev/dev/users -L+900M\n" "e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09\n" "Pass 1: Checking inodes, blocks, and sizes\n" "Pass 2: Checking directory structure\n" "Pass 3: Checking directory connectivity\n" "Pass 4: Checking reference counts\n" "Pass 5: Checking group summary information\n" "/dev/dev/users: 12/262144 files (0.0% non-contiguous), 275245/524288 blocks\n" "lvextend -- extending logical volume \"/dev/dev/users\" to 2.88 GB\n" "lvextend -- doing automatic backup of volume group \"dev\"\n" "lvextend -- logical volume \"/dev/dev/users\" successfully extended\n" "\n" "ext2resize v1.1.15 - 2000/08/08 for EXT2FS 0.5b\n" "e2fsadm -- ext2fs in logical volume \"/dev/dev/users\" successfully extended " "to 2.88 GB\n" " " msgstr "" #: LVM-HOWTO.xml:3683(title) msgid "Remount the extended volumes" msgstr "" #: LVM-HOWTO.xml:3684(para) msgid "" "We can now remount the file systems and see that the is plenty of space. " "\n" "# mount /dev/ops/batch\n" "# mount /dev/dev/users\n" "# df\n" "Filesystem 1k-blocks Used Available Use% " "Mounted on\n" "/dev/dev/cvs 1342492 516468 757828 41% /mnt/dev/cvs\n" "/dev/dev/users 2969360 2060036 909324 69% /mnt/dev/users\n" "/dev/dev/build 1548144 1023041 525103 66% /mnt/dev/build\n" "/dev/ops/databases 2890692 2302417 588275 79% /mnt/ops/databases\n" "/dev/sales/users 2064208 871214 1192994 42% /mnt/sales/users\n" "/dev/ops/batch 1535856 897122 638734 58% /mnt/ops/batch\n" " " msgstr "" #: LVM-HOWTO.xml:3703(title) msgid "Taking a Backup Using Snapshots" msgstr "" #: LVM-HOWTO.xml:3704(para) msgid "" "Following on from the previous example we now want to use the extra space in " "the \"ops\" volume group to make a database backup every evening. To ensure " "that the data that goes onto the tape is consistent we use an LVM snapshot " "logical volume." msgstr "" #: LVM-HOWTO.xml:3711(para) msgid "" "A snapshot volume is a special type of volume that presents all the data " "that was in the volume at the time the snapshot was created. For a more " "detailed description, see , Snapshots. This " "means we can back up that volume without having to worry about data being " "changed while the backup is going on, and we don't have to take the database " "volume offline while the backup is taking place." msgstr "" #: LVM-HOWTO.xml:3724(para) msgid "" "In LVM1, this type of volume was read-only, but LVM2 creates read/write " "snapshots by default." msgstr "" #: LVM-HOWTO.xml:3730(title) msgid "Create the snapshot volume" msgstr "" #: LVM-HOWTO.xml:3731(para) msgid "" "There is a little over 500 Megabytes of free space in the \"ops\" volume " "group, so we will use all of it to allocate space for the snapshot logical " "volume. A snapshot volume can be as large or a small as you like but it must " "be large enough to hold all the changes that are likely to happen to the " "original volume during the lifetime of the snapshot. So here, allowing 500 " "megabytes of changes to the database volume which should be plenty. " "\n" "# lvcreate -L592M -s -n dbbackup /dev/ops/databases \n" "lvcreate -- WARNING: the snapshot must be disabled if it " "gets full\n" "lvcreate -- INFO: using default snapshot chunk size of 64 KB for \"/dev/ops/" "dbbackup\"\n" "lvcreate -- doing automatic backup of \"ops\"\n" "lvcreate -- logical volume \"/dev/ops/dbbackup\" successfully created\n" "\n" " " msgstr "" #: LVM-HOWTO.xml:3760(title) msgid "Mount the snapshot volume" msgstr "" #: LVM-HOWTO.xml:3761(para) msgid "" "We can now create a mount-point and mount the volume \n" "# mkdir /mnt/ops/dbbackup\n" "# mount /dev/ops/dbbackup /mnt/ops/dbbackup\n" "mount: block device /dev/ops/dbbackup is write-protected, " "mounting read-only\n" " " msgstr "" #: LVM-HOWTO.xml:3770(para) msgid "" "If you are using XFS as the filesystem you will need to add the " " option to the mount command: \n" "# mount /dev/ops/dbbackup /mnt/ops/dbbackup -onouuid,ro\n" " " msgstr "" #: LVM-HOWTO.xml:3780(title) msgid "Do the backup" msgstr "" #: LVM-HOWTO.xml:3781(para) msgid "" "I assume you will have a more sophisticated backup strategy than this! " "\n" "# tar -cf /dev/rmt0 /mnt/ops/dbbackup\n" "tar: Removing leading `/' from member names\n" " " msgstr "" #: LVM-HOWTO.xml:3791(title) msgid "Remove the snapshot" msgstr "" #: LVM-HOWTO.xml:3792(para) msgid "" "When the backup has finished you can now unmount the volume and remove it " "from the system. You should remove snapshot volume when you have finished " "with them because they take a copy of all data written to the original " "volume and this can hurt performance. \n" "# umount /mnt/ops/dbbackup\n" "# lvremove /dev/ops/dbbackup \n" "lvremove -- do you really want to remove \"/dev/ops/dbbackup\"? [y/" "n]: y\n" "lvremove -- doing automatic backup of volume group \"ops\"\n" " lvremove -- logical volume \"/dev/ops/dbbackup\" successfully " "removed\n" " " msgstr "" #: LVM-HOWTO.xml:3809(title) msgid "Removing an Old Disk" msgstr "" #: LVM-HOWTO.xml:3811(para) msgid "" "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." msgstr "" #: LVM-HOWTO.xml:3816(title) LVM-HOWTO.xml:4177(title) msgid "Backup Your System" msgstr "" #: LVM-HOWTO.xml:3817(para) msgid "" "You should always backup your system before attempting a pvmove operation." msgstr "" #: LVM-HOWTO.xml:3823(title) msgid "Distributing Old Extents to Existing Disks in Volume Group" msgstr "" #: LVM-HOWTO.xml:3824(para) msgid "" "If you have enough free extents on the other disks in the volume group, you " "have it easy. Simply run \n" "# pvmove /dev/hdb\n" "pvmove -- moving physical extents in active volume group " "\"dev\"\n" "pvmove -- WARNING: moving of active logical volumes may cause data loss!\n" "pvmove -- do you want to continue? [y/n] y\n" "pvmove -- 249 extents of physical volume \"/dev/hdb\" " "successfully moved\n" " This will move the allocated physical extents from /dev/" "hdb onto the rest of the disks in the volume group." msgstr "" #: LVM-HOWTO.xml:3838(title) msgid "pvmove is Slow" msgstr "" #: LVM-HOWTO.xml:3839(para) msgid "" "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 flag." msgstr "" #: LVM-HOWTO.xml:3847(title) LVM-HOWTO.xml:3915(title) msgid "Remove the unused disk" msgstr "" #: LVM-HOWTO.xml:3848(para) msgid "" "We can now remove the old IDE disk from the volume group. \n" "# vgreduce dev /dev/hdb\n" "vgreduce -- doing automatic backup of volume group \"dev\"\n" "vgreduce -- volume group \"dev\" successfully reduced by physical volume:\n" "vgreduce -- /dev/hdb\n" " The drive can now be either physically removed when " "the machine is next powered down or reallocated to other users." msgstr "" #: LVM-HOWTO.xml:3862(title) msgid "Distributing Old Extents to a New Replacement Disk" msgstr "" #: LVM-HOWTO.xml:3863(para) msgid "" "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." msgstr "" #: LVM-HOWTO.xml:3869(title) msgid "Prepare the disk" msgstr "" #: LVM-HOWTO.xml:3870(para) msgid "" "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. \n" "# pvcreate /dev/sdf\n" "pvcreate -- physical volume \"/dev/sdf\" successfully " "created\n" " " msgstr "" #: LVM-HOWTO.xml:3881(title) msgid "Add it to the volume group" msgstr "" #: LVM-HOWTO.xml:3882(para) msgid "" "As developers use a lot of disk space this is a good volume group to add it " "into. \n" "# vgextend dev /dev/sdf\n" "vgextend -- INFO: maximum logical volume size is 255.99 " "Gigabyte\n" "vgextend -- doing automatic backup of volume group \"dev\"\n" "vgextend -- volume group \"dev\" successfully extended\n" " " msgstr "" #: LVM-HOWTO.xml:3894(title) msgid "Move the data" msgstr "" #: LVM-HOWTO.xml:3895(para) msgid "" "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. \n" "# pvmove /dev/hdb /dev/sdf\n" "pvmove -- moving physical extents in active volume group " "\"dev\"\n" "pvmove -- WARNING: moving of active logical volumes may cause data loss!\n" "pvmove -- do you want to continue? [y/n] y\n" "pvmove -- 249 extents of physical volume \"/dev/hdb\" " "successfully moved\n" " " msgstr "" #: LVM-HOWTO.xml:3916(para) msgid "" "We can now remove the old IDE disk from the volume group. \n" "# vgreduce dev /dev/hdb\n" "vgreduce -- doing automatic backup of volume group \"dev\"\n" "vgreduce -- volume group \"dev\" successfully reduced by physical volume:\n" "vgreduce -- /dev/hdb\n" " The drive can now be either physically removed when " "the machine is next powered down or reallocated to some other users." msgstr "" #: LVM-HOWTO.xml:3932(title) msgid "Moving a volume group to another system" msgstr "" #: LVM-HOWTO.xml:3933(para) msgid "" "It is quite easy to move a whole volume group to another system if, for " "example, a user department acquires a new server. To do this we use the " "vgexport and vgimport commands." msgstr "" #: LVM-HOWTO.xml:3939(para) msgid "" "vgexport/vgimport is not necessary to move drives from one system to " "another. It is an administrative policy tool to prevent access to volumes in " "the time it takes to move them." msgstr "" #: LVM-HOWTO.xml:3947(title) msgid "Unmount the file system" msgstr "" #: LVM-HOWTO.xml:3948(para) msgid "" "First, make sure that no users are accessing files on the active volume, " "then unmount it \n" "# unmount /mnt/design/users\n" " " msgstr "" #: LVM-HOWTO.xml:3957(title) msgid "Mark the volume group inactive" msgstr "" #: LVM-HOWTO.xml:3958(para) msgid "" "Marking the volume group inactive removes it from the kernel and prevents " "any further activity on it. \n" "# vgchange -an design\n" "vgchange -- volume group \"design\" successfully " "deactivated\n" " " msgstr "" #: LVM-HOWTO.xml:3968(title) msgid "Export the volume group" msgstr "" #: LVM-HOWTO.xml:3969(para) msgid "" "It is now necessary to export the volume group. This prevents it from being " "accessed on the ``old'' host system and prepares it to be removed. \n" "# vgexport design\n" "vgexport -- volume group \"design\" successfully exported\n" " When the machine is next shut down, the disk can be " "unplugged and then connected to it's new machine" msgstr "" #: LVM-HOWTO.xml:3982(title) msgid "Import the volume group" msgstr "" #: LVM-HOWTO.xml:3983(para) msgid "" "When plugged into the new system it becomes /dev/sdb so an initial pvscan " "shows: \n" "# pvscan\n" "pvscan -- reading all physical volumes (this may take a " "while...)\n" "pvscan -- inactive PV \"/dev/sdb1\" is in EXPORTED VG \"design\" [996 MB / " "996 MB free]\n" "pvscan -- inactive PV \"/dev/sdb2\" is in EXPORTED VG \"design\" [996 MB / " "244 MB free]\n" "pvscan -- total: 2 [1.95 GB] / in use: 2 [1.95 GB] / in no VG: 0 [0]\n" " We can now import the volume group (which also activates " "it) and mount the file system." msgstr "" #: LVM-HOWTO.xml:3996(para) msgid "" "If you are importing on an LVM 2 system, run: \n" "# vgimport design\n" " Volume group \"vg\" successfully imported\n" " " msgstr "" #: LVM-HOWTO.xml:4003(para) msgid "" "If you are importing on an LVM 1 system, add the PVs that need to be " "imported: \n" "# vgimport design /dev/sdb1 /dev/sdb2\n" "vgimport -- doing automatic backup of volume group \"design" "\"\n" "vgimport -- volume group \"design\" successfully imported and activated\n" " " msgstr "" #: LVM-HOWTO.xml:4014(title) msgid "Activate the volume group" msgstr "" #: LVM-HOWTO.xml:4015(para) msgid "" "You must activate the volume group before you can access it. \n" "# vgchange -ay design\n" " " msgstr "" #: LVM-HOWTO.xml:4023(title) msgid "Mount the file system" msgstr "" #: LVM-HOWTO.xml:4024(para) msgid "" "\n" "# mkdir -p /mnt/design/users\n" "# mount /dev/design/users /mnt/design/users\n" " The file system is now available for use." msgstr "" #: LVM-HOWTO.xml:4034(title) msgid "Splitting a volume group" msgstr "" #: LVM-HOWTO.xml:4035(para) msgid "" "There is a new group of users \"design\" to add to the system. One way of " "dealing with this is to create a new volume group to hold their data. There " "are no new disks but there is plenty of free space on the existing disks " "that can be reallocated." msgstr "" #: LVM-HOWTO.xml:4042(title) msgid "Determine free space" msgstr "" #: LVM-HOWTO.xml:4043(para) msgid "" "\n" "# pvscan \n" "pvscan -- reading all physical volumes (this may take a " "while...)\n" "pvscan -- ACTIVE PV \"/dev/sda\" of VG \"dev\" [1.95 GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sdb\" of VG \"sales\" [1.95 GB / 1.27 GB " "free]\n" "pvscan -- ACTIVE PV \"/dev/sdc\" of VG \"ops\" [1.95 GB / 564 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdd\" of VG \"dev\" [1.95 GB / 0 free]\n" "pvscan -- ACTIVE PV \"/dev/sde\" of VG \"ops\" [1.95 GB / 1.9 GB free]\n" "pvscan -- ACTIVE PV \"/dev/sdf\" of VG \"dev\" [1.95 GB / 1.33 GB " "free]\n" "pvscan -- ACTIVE PV \"/dev/sdg1\" of VG \"ops\" [996 MB / 432 MB free]\n" "pvscan -- ACTIVE PV \"/dev/sdg2\" of VG \"dev\" [996 MB / 632 MB free]\n" "pvscan -- total: 8 [13.67 GB] / in use: 8 [13.67 GB] / in no VG: 0 [0]\n" " We decide to reallocate /dev/sdg1 and /dev/sdg2 to " "design so first we have to move the physical extents into the free areas of " "the other volumes (in this case /dev/sdf for volume group dev and /dev/sde " "for volume group ops)." msgstr "" #: LVM-HOWTO.xml:4064(title) msgid "Move data off the disks to be used" msgstr "" #: LVM-HOWTO.xml:4065(para) msgid "" "Some space is still used on the chosen volumes so it is necessary to move " "that used space off onto some others." msgstr "" #: LVM-HOWTO.xml:4070(para) msgid "" "Move all the used physical extents from /dev/sdg1 to /dev/sde and from /dev/" "sdg2 to /dev/sdf \n" "# pvmove /dev/sdg1 /dev/sde\n" "pvmove -- moving physical extents in active volume group " "\"ops\"\n" "pvmove -- WARNING: moving of active logical volumes may cause data loss!\n" "pvmove -- do you want to continue? [y/n] y\n" "pvmove -- doing automatic backup of volume group \"ops\"\n" "pvmove -- 141 extents of physical volume \"/dev/sdg1\" successfully moved\n" "\n" "# pvmove /dev/sdg2 /dev/sdf\n" "pvmove -- moving physical extents in active volume group " "\"dev\"\n" "pvmove -- WARNING: moving of active logical volumes may cause data loss!\n" "pvmove -- do you want to continue? [y/n] y\n" "pvmove -- doing automatic backup of volume group \"dev\"\n" "pvmove -- 91 extents of physical volume \"/dev/sdg2\" successfully moved\n" " " msgstr "" #: LVM-HOWTO.xml:4091(title) msgid "Create the new volume group" msgstr "" #: LVM-HOWTO.xml:4092(para) msgid "" "Now, split /dev/sdg2 from dev and add it into a new group called \"design\". " "it is possible to do this using vgreduce and vgcreate but the vgsplit " "command combines the two. \n" "# vgsplit dev design /dev/sdg2\n" "vgsplit -- doing automatic backup of volume group \"dev\"\n" "vgsplit -- doing automatic backup of volume group \"design\"\n" "vgsplit -- volume group \"dev\" successfully split into \"dev\" and \"design" "\"\n" " " msgstr "" #: LVM-HOWTO.xml:4105(title) msgid "Remove remaining volume" msgstr "" #: LVM-HOWTO.xml:4106(para) msgid "" "Next, remove /dev/sdg1 from ops and add it into design. \n" "# vgreduce ops /dev/sdg1\n" "vgreduce -- doing automatic backup of volume group \"ops\"\n" "vgreduce -- volume group \"ops\" successfully reduced by physical volume:\n" "vgreduce -- /dev/sdg1\n" "\n" "# vgextend design /dev/sdg1\n" "vgextend -- INFO: maximum logical volume size is 255.99 " "Gigabyte\n" "vgextend -- doing automatic backup of volume group \"design\"\n" "vgextend -- volume group \"design\" successfully extended\n" " " msgstr "" #: LVM-HOWTO.xml:4122(title) msgid "Create new logical volume" msgstr "" #: LVM-HOWTO.xml:4123(para) msgid "" "Now create a logical volume. Rather than allocate all of the available " "space, leave some spare in case it is needed elsewhere. \n" "# lvcreate -L750M -n users design\n" "lvcreate -- rounding up size to physical extent boundary " "\"752 MB\"\n" "lvcreate -- doing automatic backup of \"design\"\n" "lvcreate -- logical volume \"/dev/design/users\" successfully created\n" " " msgstr "" #: LVM-HOWTO.xml:4136(title) msgid "Make a file system on the volume" msgstr "" #: LVM-HOWTO.xml:4138(command) msgid "# mke2fs /dev/design/users" msgstr "" #: LVM-HOWTO.xml:4139(computeroutput) #, no-wrap msgid "" "mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09\n" "Filesystem label=\n" "OS type: Linux\n" "Block size=4096 (log=2)\n" "Fragment size=4096 (log=2)\n" "96384 inodes, 192512 blocks\n" "9625 blocks (5.00<!-- ) reserved for the super user\n" "First data block=0\n" "6 block groups\n" "32768 blocks per group, 32768 fragments per group\n" "16064 inodes per group\n" "Superblock backups stored on blocks: \n" " 32768, 98304, 163840\n" "\n" "Writing inode tables: done \n" "Writing superblocks and filesystem accounting information: done" msgstr "" #: LVM-HOWTO.xml:4158(title) msgid "Mount the new volume" msgstr "" #: LVM-HOWTO.xml:4160(command) msgid "# mkdir -p /mnt/design/users mount /dev/design/users /mnt/design/users/" msgstr "" #: LVM-HOWTO.xml:4163(para) msgid "" "It's also a good idea to add an entry for this file system in your /etc/" "fstab file as follows: \n" "/dev/design/user\n" "/mnt/design/users ext2 defaults 1 2\n" " " msgstr "" #: LVM-HOWTO.xml:4174(title) msgid "Converting a root filesystem to LVM 1" msgstr "" #: LVM-HOWTO.xml:4178(para) msgid "" "It is strongly recommended that you take a full backup of your system before " "attempting to convert to root on LVM 1." msgstr "" #: LVM-HOWTO.xml:4184(title) msgid "Upgrade Complications" msgstr "" #: LVM-HOWTO.xml:4185(para) msgid "" "Having your root filesystem on LVM 1 can significantly complicate upgrade " "procedures (depending on your distribution) so it should not be attempted " "lightly. Particularly, you must consider how you will insure that the LVM 1 " "kernel module (if you do not have LVM 1 compiled into the kernel) as well as " "the vgscan/vgchange tools are available before, during, and after the " "upgrade." msgstr "" #: LVM-HOWTO.xml:4195(title) msgid "Recovery Complications" msgstr "" #: LVM-HOWTO.xml:4196(para) msgid "" "Having your root filesystem on LVM 1 can significantly complicate recovery " "of damaged filesystems. If you lose your initrd, it will be very difficult " "to boot your system. You will need to have a recover disk that contains the " "kernel, LVM 1 module, and LVM 1 tools, as well as any tools necessary to " "recover a damaged filesystem. Be sure to make regular backups and have an up-" "to-date alternative boot method that allows for recovery of LVM 1." msgstr "" #: LVM-HOWTO.xml:4209(para) msgid "" "In this example the whole system was installed in a single root partition " "with the exception of /boot. The system had a 2 gig disk partitioned as: " "\n" "/dev/hda1 /boot \n" "/dev/hda2 swap\n" "/dev/hda3 /\n" " " msgstr "" #: LVM-HOWTO.xml:4220(para) msgid "" "The / partition covered all of the disk not used by /boot and swap. An " "important prerequisite of this procedure is that the root partition is less " "that half full (so that a copy of it can be created in a logical volume). If " "this is not the case then a second disk drive should be used. The procedure " "in that case is similar but there is no need to shrink the existing root " "partition and /dev/hda4 should be replaced with (eg) /dev/hdb1 in the " "examples." msgstr "" #: LVM-HOWTO.xml:4231(para) msgid "" "To do this it is easiest to use GNU parted. This software allows you to grow " "and shrink partitions that contain filesystems. It is possible to use " "resize2fs and fdisk to do this but GNU parted makes it much less prone to " "error. It may be included in your distribution, if not you can download it " "from ftp://ftp.gnu.org/pub/" "gnu/parted." msgstr "" #: LVM-HOWTO.xml:4240(para) msgid "Once you have parted on your system AND YOU HAVE BACKED THE SYSTEM UP:" msgstr "" #: LVM-HOWTO.xml:4245(title) msgid "Boot single user" msgstr "" #: LVM-HOWTO.xml:4246(para) msgid "" "Boot into single user mode (type linux S at the LILO " "prompt) This is important. Booting single-user ensures that the root " "filesystem is mounted read-only and no programs are accessing the disk." msgstr "" #: LVM-HOWTO.xml:4254(title) msgid "Run Parted" msgstr "" #: LVM-HOWTO.xml:4255(para) msgid "" "Run parted to shrink the root partition Do this so there is room on the disk " "for a complete copy of it in a logical volume. In this example a 1.8 gig " "partition is shrunk to 1 gigabyte This displays the sizes and names of the " "partitions on the disk \n" "# parted /dev/hda\n" "(parted) p\n" ".\n" ".\n" ".\n" " " msgstr "" #: LVM-HOWTO.xml:4269(para) msgid "" "Now resize the partition: \n" "(parted) resize 3 145 999\n" " The first number here the partition number (hda3), the " "second is the same starting position that hda3 currently has. Do not change " "this. The last number should make the partition around half the size it " "currently is." msgstr "" #: LVM-HOWTO.xml:4280(para) msgid "" "Create a new partition \n" "(parted) mkpart primary ext2 1000 1999\n" " This makes a new partition to hold the initial LVM 1 " "data. It should start just beyond the newly shrunk hda3 and finish at the " "end of the disk." msgstr "" #: LVM-HOWTO.xml:4290(para) msgid "" "Quit parted \n" "(parted) q\n" " " msgstr "" #: LVM-HOWTO.xml:4299(para) msgid "Reboot the system" msgstr "" #: LVM-HOWTO.xml:4304(title) msgid "Verify kernel config options" msgstr "" #: LVM-HOWTO.xml:4305(para) msgid "" "Make sure that the kernel you are currently running works with LVM 1 and has " "CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_INITRD set in the config file." msgstr "" #: LVM-HOWTO.xml:4312(title) msgid "Adjust partition type" msgstr "" #: LVM-HOWTO.xml:4313(para) msgid "" "Change the partition type on the newly created partition from Linux to LVM " "(8e). Parted doesn't understand LVM 1 partitions so this has to be done " "using fdisk. \n" "# fdisk /dev/hda\n" "Command (m for help): t\n" "Partition number (1-4): 4\n" "Hex code (type L to list codes): 8e\n" "Changed system type of partition 4 to 8e (Unknown)\n" "Command (m for help): w\n" " " msgstr "" #: LVM-HOWTO.xml:4328(title) msgid "Set up LVM 1 for the new scheme" msgstr "" #: LVM-HOWTO.xml:4331(para) msgid "" "Initialize LVM 1 (vgscan) \n" "# vgscan\n" " " msgstr "" #: LVM-HOWTO.xml:4340(para) msgid "" "Make the new partition into a PV \n" "# pvcreate /dev/hda4\n" " " msgstr "" #: LVM-HOWTO.xml:4349(para) msgid "" "create a new volume group \n" "# vgcreate vg /dev/hda4\n" " " msgstr "" #: LVM-HOWTO.xml:4358(para) msgid "" "Create a logical volume to hold the new root. \n" "# lvcreate -L250M -n root vg\n" " " msgstr "" #: LVM-HOWTO.xml:4368(title) msgid "Create the Filesystem" msgstr "" #: LVM-HOWTO.xml:4369(para) msgid "" "Make a filesystem in the logical volume and copy the root files onto it. " "\n" "# mke2fs /dev/vg/root\n" "# mount /dev/vg/root /mnt/\n" "# find / -xdev | cpio -pvmd /mnt\n" " " msgstr "" #: LVM-HOWTO.xml:4380(title) msgid "Update /etc/fstab" msgstr "" #: LVM-HOWTO.xml:4381(para) msgid "" "Edit /mnt/etc/fstab on the new root so that / is mounted on /dev/vg/root. " "For example: \n" " /dev/hda3 / ext2 defaults 1 1\n" " becomes: \n" " /dev/vg/root / ext2 defaults 1 1\n" " " msgstr "" #: LVM-HOWTO.xml:4394(title) msgid "Create an LVM 1 initial RAM disk" msgstr "" #: LVM-HOWTO.xml:4396(command) msgid "# lvmcreate_initrd" msgstr "" #: LVM-HOWTO.xml:4399(para) msgid "" "Make sure you note the name that lvmcreate_initrd calls the initrd image. It " "should be in /boot." msgstr "" #: LVM-HOWTO.xml:4405(title) msgid "Update /etc/lilo.conf" msgstr "" #: LVM-HOWTO.xml:4406(para) msgid "" "Add an entry in /etc/lilo.conf for LVM 1. This should look similar to the " "following: \n" " image = /boot/KERNEL_IMAGE_NAME\n" " label = lvm\n" " root = /dev/vg/root\n" " initrd = /boot/INITRD_IMAGE_NAME\n" " ramdisk = 8192\n" " Where KERNEL_IMAGE_NAME is the name of your LVM 1 " "enabled kernel, and INITRD_IMAGE_NAME is the name of the initrd image " "created by lvmcreate_initrd. The ramdisk line may need to be increased if " "you have a large LVM 1 configuration, but 8192 should suffice for most " "users. The default ramdisk size is 4096. If in doubt check the output from " "the lvmcreate_initrd command, the line that says: \n" "lvmcreate_initrd -- making loopback file (6189 kB)\n" " and make the ramdisk the size given in brackets." msgstr "" #: LVM-HOWTO.xml:4429(para) msgid "" "You should copy this new lilo.conf onto /etc in the new root fs as well. " "\n" "# cp /etc/lilo.conf /mnt/etc/\n" " " msgstr "" #: LVM-HOWTO.xml:4439(title) msgid "Run LILO to write the new boot sector" msgstr "" #: LVM-HOWTO.xml:4441(command) msgid "# lilo" msgstr "" #: LVM-HOWTO.xml:4445(title) msgid "Reboot to lvm" msgstr "" #: LVM-HOWTO.xml:4446(para) msgid "" "Reboot - at the LILO prompt type \"lvm\" The system should reboot into Linux " "using the newly created Logical Volume." msgstr "" #: LVM-HOWTO.xml:4452(para) msgid "" "If that worked then you should make lvm the default LILO boot destination by " "adding the line \n" "default=lvm\n" " in the first section of /etc/lilo.conf" msgstr "" #: LVM-HOWTO.xml:4461(para) msgid "" "If it did not work then reboot normally and try to diagnose the problem. It " "could be a typing error in lilo.conf or LVM 1 not being available in the " "initial RAM disk or its kernel. Examine the message produced at boot time " "carefully." msgstr "" #: LVM-HOWTO.xml:4469(title) msgid "Add remainder of disk" msgstr "" #: LVM-HOWTO.xml:4470(para) msgid "" "Add the rest of the disk into LVM 1. When you are happy with this setup you " "can then add the old root partition to LVM 1 and spread out over the disk." msgstr "" #: LVM-HOWTO.xml:4476(para) msgid "" "First set the partition type to 8e(LVM) \n" "# fdisk /dev/hda\n" "\n" "Command (m for help): t\n" "Partition number (1-4): 3\n" "Hex code (type L to list codes): 8e\n" "Changed system type of partition 3 to 8e (Unknown)\n" "Command (m for help): w\n" " " msgstr "" #: LVM-HOWTO.xml:4489(para) msgid "" "Convert it into a PV and add it to the volume group: \n" "# pvcreate /dev/hda3\n" "# vgextend vg /dev/hda3\n" " " msgstr "" #: LVM-HOWTO.xml:4498(title) msgid "Recover physical volume metadata" msgstr "" #: LVM-HOWTO.xml:4499(para) msgid "" "If you get the warning \"incorrect metadata area header checksum\" or " "something about not being able to find PV with UUID foo, you probably " "toasted the volume group descriptor area and lvm startup can't occur." msgstr "" #: LVM-HOWTO.xml:4505(title) msgid "Only run on non-functional VG" msgstr "" #: LVM-HOWTO.xml:4506(para) msgid "" "Don't do this on a properly working lvm. You need to specify the correct " "physical volume to pvcreate or you may lose your data." msgstr "" #: LVM-HOWTO.xml:4512(para) msgid "" "Extract the exact uuid for the PV that was overwritten from the file " "/etc/lvm/archive/VolumeGroupName_XXXXX.vg. (Where XXXXX " "represents the number of the last known good archived lvm metadata)." msgstr "" #: LVM-HOWTO.xml:4519(para) msgid "" "Use pvcreate to restore the metadata: pvcreate --" "uuid \"<some_long_string>\" --restorefile /etc/lvm/archive/" "VolumeGroupName_XXXXX.vg <PhysicalVolume>" msgstr "" #: LVM-HOWTO.xml:4523(para) msgid "" "If you are lucky you'll find that the on-disk lvm metadata takes at least so " "much space as what it was overwritten with. The above command has been know " "to recover a PV overwritten with mkswap. If whatever overwrote the VGDA " "writes past that area, LVs may be affected. In this case, fsck might be able " "to fix the filesystem on the LV, or you may need more drastic measures to " "pull data off of it. Contact your local friendly filesystem expert for help " "in that case." msgstr "" #: LVM-HOWTO.xml:4533(para) msgid "" "pvcreate only overwrites the lvm metadata areas on disk " "and doesn't touch the data areas (the logical volumes)." msgstr "" #: LVM-HOWTO.xml:4541(title) msgid "Dangerous Operations" msgstr "" #: LVM-HOWTO.xml:4542(title) msgid "Warning" msgstr "" #: LVM-HOWTO.xml:4543(para) msgid "" "Don't do this unless you're really sure of what you're doing. You'll " "probably lose all your data." msgstr "" #: LVM-HOWTO.xml:4549(title) msgid "Restoring the VG UUIDs using uuid_fixer" msgstr "" #: LVM-HOWTO.xml:4550(para) msgid "" "If you've upgraded LVM from previous versions to early 0.9 and 0.9.1 " "versions of LVM and vgscan says vgscan -- " "no volume groups found, this is one way to fix it." msgstr "" #: LVM-HOWTO.xml:4559(para) msgid "" "Download the UUID fixer program from the contributor directory at Sistina." msgstr "" #: LVM-HOWTO.xml:4564(para) msgid "" "It is located at ftp://ftp.sistina.com/pub/LVM/contrib/" "uuid_fixer-0.3-IOP10.tar.gz\"" msgstr "" #: LVM-HOWTO.xml:4571(para) msgid "" "Extract uuid_fixer-0.3-IOP10.tar.gz\n" "# tar zxf uuid_fixer-0.3-IOP10.tar.gz\n" " " msgstr "" #: LVM-HOWTO.xml:4580(para) msgid "" "cd to uuid_fixer \n" "# cd uuid_fixer\n" " " msgstr "" #: LVM-HOWTO.xml:4587(para) msgid "You have one of two options at this point:" msgstr "" #: LVM-HOWTO.xml:4594(para) msgid "Use the prebuild binary (it is build for i386 architecture)." msgstr "" #: LVM-HOWTO.xml:4599(para) msgid "" "Make sure you list all the PVs in the VG you are restoring, and follow the " "prompts \n" "# ./uuid_fixer <LIST OF ALL PVS IN VG TO " "BE RESTORED>\n" " " msgstr "" #: LVM-HOWTO.xml:4609(para) msgid "Build the uuid_builder program from source" msgstr "" #: LVM-HOWTO.xml:4613(para) msgid "" "Edit the Makefile with your favorite editor, and make sure LVMDIR points to " "your LVM source." msgstr "" #: LVM-HOWTO.xml:4618(para) msgid "" "Then run make. \n" "# make\n" " " msgstr "" #: LVM-HOWTO.xml:4625(para) msgid "" "Now run uuid_fixer. Make sure you list all the PVs in the VG you are " "restoring, and follow the prompts. \n" "# ./uuid_fixer <LIST OF ALL PVS IN VG TO " "BE RESTORED>\n" " " msgstr "" #: LVM-HOWTO.xml:4637(para) msgid "" "Deactivate any active Volume Groups (optional) " "\n" "# vgchange -an\n" " " msgstr "" #: LVM-HOWTO.xml:4647(para) msgid "" "Run vgscan \n" "# vgscan\n" " " msgstr "" #: LVM-HOWTO.xml:4656(para) msgid "" "Reactivate Volume Groups \n" "# vgchange -ay\n" " " msgstr "" #: LVM-HOWTO.xml:4666(title) msgid "Sharing LVM volumes" msgstr "" #: LVM-HOWTO.xml:4667(title) msgid "LVM is not cluster aware" msgstr "" #: LVM-HOWTO.xml:4668(para) msgid "" "Be very careful doing this, LVM is not currently cluster-aware and it is " "very easy to lose all your data." msgstr "" #: LVM-HOWTO.xml:4674(para) msgid "" "If you have a fibre-channel or shared-SCSI environment where more than one " "machine has physical access to a set of disks then you can use LVM to divide " "these disks up into logical volumes. If you want to share data you should " "really be looking at GFS " "or other cluster filesystems." msgstr "" #: LVM-HOWTO.xml:4683(para) msgid "" "The key thing to remember when sharing volumes is that all the LVM " "administration must be done on one node only and that all other nodes must " "have LVM shut down before changing anything on the admin node. Then, when " "the changes have been made, it is necessary to run vgscan on the other nodes " "before reloading the volume groups. Also, unless you are running a cluster-" "aware filesystem (such as GFS) or application on the volume, only one node " "can mount each filesystem. It is up to you, as system administrator to " "enforce this, LVM will not stop you corrupting your data." msgstr "" #: LVM-HOWTO.xml:4695(para) msgid "" "The startup sequence of each node is the same as for a single-node setup " "with \n" "vgscan\n" "vgchange -ay\n" " in the startup scripts." msgstr "" #: LVM-HOWTO.xml:4705(para) msgid "" "If you need to do any changes to the " "LVM metadata (regardless of whether it affects volumes mounted on other " "nodes) you must go through the following sequence. In the steps below " "``admin node'' is any arbitrarily chosen node in the cluster. \n" "Admin node Other nodes\n" "---------- -----------\n" " Close all Logical volumes (umount)\n" " vgchange -an\n" "<make changes, eg lvextend>\n" " vgscan\n" " vgchange -ay\n" " " msgstr "" #: LVM-HOWTO.xml:4722(title) msgid "VGs should be active on the admin node" msgstr "" #: LVM-HOWTO.xml:4723(para) msgid "" "You do not need to, nor should you, unload the VGs on the admin node, so " "this can be the node with the highest uptime requirement." msgstr "" #: LVM-HOWTO.xml:4730(para) msgid "" "I'll say it again: Be very careful doing this" msgstr "" #: LVM-HOWTO.xml:4739(title) msgid "Reporting Errors and Bugs" msgstr "" #: LVM-HOWTO.xml:4740(para) msgid "" "Just telling us that LVM did not work does not provide us with enough " "information to help you. We need to know about your setup and the various " "components of your configuration. The first thing you should do is check the " "linux-lvm " "mailing list archives to see if someone else has already reported " "the same bug. If you do not find a bug report for a problem similar to yours " "you should collect as much of the following information as possible. The " "list is grouped into three categories of errors." msgstr "" #: LVM-HOWTO.xml:4754(para) msgid "For compilation errors:" msgstr "" #: LVM-HOWTO.xml:4760(para) msgid "" "Detail the specific version of LVM you have. If you extracted LVM from a " "tarball give the name of the tar file and list any patches you applied. If " "you acquired LVM from the Public CVS server, give the date and time you " "checked it out." msgstr "" #: LVM-HOWTO.xml:4770(para) msgid "" "Provide the exact error message. Copy the lines of output before the actual " "error message as well as the lines after. These lines occasionally give " "hints as to why the error occurred." msgstr "" #: LVM-HOWTO.xml:4779(para) msgid "" "List the steps, in order, that produced the error. Is the error " "reproducible? If you start from a clean state does the same sequence of " "steps reproduce the error?" msgstr "" #: LVM-HOWTO.xml:4789(para) msgid "For LVM errors:" msgstr "" #: LVM-HOWTO.xml:4795(para) msgid "Include all of the information requested in the compilation section." msgstr "" #: LVM-HOWTO.xml:4802(para) msgid "" "Attach a short description of your hardware: types of machines and disks, " "disks interface (SCSI, FC, NBD). Any other tidbits about your hardware you " "feel is important." msgstr "" #: LVM-HOWTO.xml:4810(para) msgid "The command lines used with LVM to produce the error." msgstr "" #: LVM-HOWTO.xml:4816(para) msgid "" "A log file produced when running the offending commands. Make sure you have " "the following in your /etc/lvm/lvm.conf file: \n" "log {\n" " file=\"/tmp/lvm2.log\"\n" " level=7\n" " activation=1\n" "}\n" " " msgstr "" #: LVM-HOWTO.xml:4834(para) msgid "When LVM trips a panic trap:" msgstr "" #: LVM-HOWTO.xml:4840(para) msgid "Include all of the information requested in two sections above." msgstr "" #: LVM-HOWTO.xml:4847(para) msgid "" "Provide the debug dump for the machine. This is best accomplished if you are " "watching the console output of the computer over a serial link, since you " "can't very well copy and paste from a panic'd machine, and it is very easy " "to mistype something if you try to copy the output by hand." msgstr "" #: LVM-HOWTO.xml:4860(para) msgid "" "This can be a lot of information. If you end up with more than a couple of " "files, tar and gzip them into a single archive. Submit a link to where this " "file can be found to the appropriate mailing list (see ) along with a short description of the error. If you do not " "have a public web or ftp site that you can post the information to, you can " "try to submit the file to the list." msgstr "" #: LVM-HOWTO.xml:4872(title) msgid "Contact and Links" msgstr "" #: LVM-HOWTO.xml:4874(title) msgid "Mail lists" msgstr "" #: LVM-HOWTO.xml:4875(para) msgid "" "Before you post to any of our lists please read the all of this document and " "check the archives to see if your question has already been answered. Please " "post in text only to our lists, fancy formated messages are near impossible " "to read if someone else is not running a mail client that understands it. " "Standard mailing list etiquette applies. Incomplete questions or " "configuration data make it very hard for us to answer your questions." msgstr "" #: LVM-HOWTO.xml:4887(title) msgid "LVM Discussion Mailing Lists" msgstr "" #: LVM-HOWTO.xml:4888(term) msgid "linux-lvm" msgstr "" #: LVM-HOWTO.xml:4890(para) msgid "" "This list is aimed at user-related questions and comments. You may be able " "to get the answers you need from other people who have the same issues. Open " "discussion is encouraged. Bug reports should be sent to this list." msgstr "" #: LVM-HOWTO.xml:4896(para) msgid "" "Subscribe using the web interface." msgstr "" #: LVM-HOWTO.xml:4901(para) msgid "" "Look at the " "archives" msgstr "" #: LVM-HOWTO.xml:4909(term) msgid "dm-devel" msgstr "" #: LVM-HOWTO.xml:4911(para) msgid "" "This list is not specifically for lvm, but since device mapper is used by " "LVM 2, it is mentioned here." msgstr "" #: LVM-HOWTO.xml:4916(para) msgid "" "Subscribe using the web interface." msgstr "" #: LVM-HOWTO.xml:4921(para) msgid "" "Look at the " "archives" msgstr "" #: LVM-HOWTO.xml:4930(title) msgid "LVM-Related Commit Lists" msgstr "" #: LVM-HOWTO.xml:4931(term) msgid "lvm2-commit" msgstr "" #: LVM-HOWTO.xml:4933(para) msgid "" "This list gets messages automatically whenever someone commits to the lvm2 " "cvs tree. Its main purpose is to keep up with the cvs tree." msgstr "" #: LVM-HOWTO.xml:4938(para) msgid "" "Look at the archives" msgstr "" #: LVM-HOWTO.xml:4946(term) msgid "lvm-commit" msgstr "" #: LVM-HOWTO.xml:4948(para) msgid "" "This list gets messages automatically whenever someone commits to the lvm " "cvs tree. Its main purpose is to keep up with the cvs tree." msgstr "" #: LVM-HOWTO.xml:4953(para) msgid "" "Look at the archives" msgstr "" #: LVM-HOWTO.xml:4961(term) msgid "dm-commit" msgstr "" #: LVM-HOWTO.xml:4963(para) msgid "" "This list gets messages automatically whenever someone commits to the dm cvs " "tree. Its main purpose is to keep up with the cvs tree." msgstr "" #: LVM-HOWTO.xml:4968(para) msgid "" "Look at the archives" msgstr "" #: LVM-HOWTO.xml:4977(title) msgid "Discontinued Lists" msgstr "" #: LVM-HOWTO.xml:4978(term) msgid "lvm-devel" msgstr "" #: LVM-HOWTO.xml:4980(para) msgid "" "This list has been discontinued; please use linux-lvm for lvm development " "discussion." msgstr "" #: LVM-HOWTO.xml:4987(term) msgid "lvm-bugs" msgstr "" #: LVM-HOWTO.xml:4989(para) msgid "" "This list has been discontinued; Bug reports should be sent to the linux-lvm " "list." msgstr "" #: LVM-HOWTO.xml:4998(title) msgid "Links" msgstr "" #: LVM-HOWTO.xml:5000(para) msgid "LVM Links:" msgstr "" #: LVM-HOWTO.xml:5006(para) msgid "" "The Logical Volume Manager home page." msgstr "" #: LVM-HOWTO.xml:5013(para) msgid "" "The LVM 1 home page." msgstr "" #: LVM-HOWTO.xml:5020(para) msgid "" "The Device Mapper home " "page." msgstr "" #: LVM-HOWTO.xml:5027(para) msgid "" "The LVM 2 ftp site." msgstr "" #: LVM-HOWTO.xml:5034(para) msgid "" "The LVM 1 ftp site." msgstr "" #: LVM-HOWTO.xml:5041(para) msgid "" "The Device Mapper ftp site." msgstr "" #: LVM-HOWTO.xml:5052(title) msgid "GNU Free Documentation License" msgstr "" #: LVM-HOWTO.xml:5053(subtitle) msgid "Version 1.2, November 2002" msgstr "" #: LVM-HOWTO.xml:5056(para) msgid "" "Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. 59 Temple Place, " "Suite 330, Boston, MA 02111-1307 USA Everyone is permitted to copy and " "distribute verbatim copies of this license document, but changing it is not " "allowed." msgstr "" #: LVM-HOWTO.xml:5063(title) msgid "PREAMBLE" msgstr "" #: LVM-HOWTO.xml:5065(para) msgid "" "The purpose of this License is to make a manual, textbook, or other " "functional and useful document \"free\" in the sense of freedom: to assure " "everyone the effective freedom to copy and redistribute it, with or without " "modifying it, either commercially or noncommercially. Secondarily, this " "License preserves for the author and publisher a way to get credit for their " "work, while not being considered responsible for modifications made by " "others." msgstr "" #: LVM-HOWTO.xml:5074(para) msgid "" "This License is a kind of \"copyleft\", which means that derivative works of " "the document must themselves be free in the same sense. It complements the " "GNU General Public License, which is a copyleft license designed for free " "software." msgstr "" #: LVM-HOWTO.xml:5080(para) msgid "" "We have designed this License in order to use it for manuals for free " "software, because free software needs free documentation: a free program " "should come with manuals providing the same freedoms that the software does. " "But this License is not limited to software manuals; it can be used for any " "textual work, regardless of subject matter or whether it is published as a " "printed book. We recommend this License principally for works whose purpose " "is instruction or reference." msgstr "" #: LVM-HOWTO.xml:5091(title) msgid "APPLICABILITY AND DEFINITIONS" msgstr "" #: LVM-HOWTO.xml:5093(para) msgid "" "This License applies to any manual or other work, in any medium, that " "contains a notice placed by the copyright holder saying it can be " "distributed under the terms of this License. Such a notice grants a world-" "wide, royalty-free license, unlimited in duration, to use that work under " "the conditions stated herein. The \"Document\", below, refers to any such " "manual or work. Any member of the public is a licensee, and is addressed as " "\"you\". You accept the license if you copy, modify or distribute the work " "in a way requiring permission under copyright law." msgstr "" #: LVM-HOWTO.xml:5104(para) msgid "" "A \"Modified Version\" of the Document means any work containing the " "Document or a portion of it, either copied verbatim, or with modifications " "and/or translated into another language." msgstr "" #: LVM-HOWTO.xml:5109(para) msgid "" "A \"Secondary Section\" is a named appendix or a front-matter section of the " "Document that deals exclusively with the relationship of the publishers or " "authors of the Document to the Document's overall subject (or to related " "matters) and contains nothing that could fall directly within that overall " "subject. (Thus, if the Document is in part a textbook of mathematics, a " "Secondary Section may not explain any mathematics.) The relationship could " "be a matter of historical connection with the subject or with related " "matters, or of legal, commercial, philosophical, ethical or political " "position regarding them." msgstr "" #: LVM-HOWTO.xml:5121(para) msgid "" "The \"Invariant Sections\" are certain Secondary Sections whose titles are " "designated, as being those of Invariant Sections, in the notice that says " "that the Document is released under this License. If a section does not fit " "the above definition of Secondary then it is not allowed to be designated as " "Invariant. The Document may contain zero Invariant Sections. If the Document " "does not identify any Invariant Sections then there are none." msgstr "" #: LVM-HOWTO.xml:5130(para) msgid "" "The \"Cover Texts\" are certain short passages of text that are listed, as " "Front-Cover Texts or Back-Cover Texts, in the notice that says that the " "Document is released under this License. A Front-Cover Text may be at most 5 " "words, and a Back-Cover Text may be at most 25 words." msgstr "" #: LVM-HOWTO.xml:5137(para) msgid "" "A \"Transparent\" copy of the Document means a machine-readable copy, " "represented in a format whose specification is available to the general " "public, that is suitable for revising the document straightforwardly with " "generic text editors or (for images composed of pixels) generic paint " "programs or (for drawings) some widely available drawing editor, and that is " "suitable for input to text formatters or for automatic translation to a " "variety of formats suitable for input to text formatters. A copy made in an " "otherwise Transparent file format whose markup, or absence of markup, has " "been arranged to thwart or discourage subsequent modification by readers is " "not Transparent. An image format is not Transparent if used for any " "substantial amount of text. A copy that is not \"Transparent\" is called " "\"Opaque\"." msgstr "" #: LVM-HOWTO.xml:5153(para) msgid "" "Examples of suitable formats for Transparent copies include plain ASCII " "without markup, Texinfo input format, LaTeX input format, SGML or XML using " "a publicly available DTD, and standard-conforming simple HTML, PostScript or " "PDF designed for human modification. Examples of transparent image formats " "include PNG, XCF and JPG. Opaque formats include proprietary formats that " "can be read and edited only by proprietary word processors, SGML or XML for " "which the DTD and/or processing tools are not generally available, and the " "machine-generated HTML, PostScript or PDF produced by some word processors " "for output purposes only." msgstr "" #: LVM-HOWTO.xml:5165(para) msgid "" "The \"Title Page\" means, for a printed book, the title page itself, plus " "such following pages as are needed to hold, legibly, the material this " "License requires to appear in the title page. For works in formats which do " "not have any title page as such, \"Title Page\" means the text near the most " "prominent appearance of the work's title, preceding the beginning of the " "body of the text." msgstr "" #: LVM-HOWTO.xml:5173(para) msgid "" "A section \"Entitled XYZ\" means a named subunit of the Document whose title " "either is precisely XYZ or contains XYZ in parentheses following text that " "translates XYZ in another language. (Here XYZ stands for a specific section " "name mentioned below, such as \"Acknowledgements\", \"Dedications\", " "\"Endorsements\", or \"History\".) To \"Preserve the Title\" of such a " "section when you modify the Document means that it remains a section " "\"Entitled XYZ\" according to this definition." msgstr "" #: LVM-HOWTO.xml:5183(para) msgid "" "The Document may include Warranty Disclaimers next to the notice which " "states that this License applies to the Document. These Warranty Disclaimers " "are considered to be included by reference in this License, but only as " "regards disclaiming warranties: any other implication that these Warranty " "Disclaimers may have is void and has no effect on the meaning of this " "License." msgstr "" #: LVM-HOWTO.xml:5192(title) msgid "VERBATIM COPYING" msgstr "" #: LVM-HOWTO.xml:5194(para) msgid "" "You may copy and distribute the Document in any medium, either commercially " "or noncommercially, provided that this License, the copyright notices, and " "the license notice saying this License applies to the Document are " "reproduced in all copies, and that you add no other conditions whatsoever to " "those of this License. You may not use technical measures to obstruct or " "control the reading or further copying of the copies you make or distribute. " "However, you may accept compensation in exchange for copies. If you " "distribute a large enough number of copies you must also follow the " "conditions in section 3." msgstr "" #: LVM-HOWTO.xml:5207(para) msgid "" "You may also lend copies, under the same conditions stated above, and you " "may publicly display copies." msgstr "" #: LVM-HOWTO.xml:5211(title) msgid "COPYING IN QUANTITY" msgstr "" #: LVM-HOWTO.xml:5213(para) msgid "" "If you publish printed copies (or copies in media that commonly have printed " "covers) of the Document, numbering more than 100, and the Document's license " "notice requires Cover Texts, you must enclose the copies in covers that " "carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the " "front cover, and Back-Cover Texts on the back cover. Both covers must also " "clearly and legibly identify you as the publisher of these copies. The front " "cover must present the full title with all words of the title equally " "prominent and visible. You may add other material on the covers in addition. " "Copying with changes limited to the covers, as long as they preserve the " "title of the Document and satisfy these conditions, can be treated as " "verbatim copying in other respects." msgstr "" #: LVM-HOWTO.xml:5228(para) msgid "" "If the required texts for either cover are too voluminous to fit legibly, " "you should put the first ones listed (as many as fit reasonably) on the " "actual cover, and continue the rest onto adjacent pages." msgstr "" #: LVM-HOWTO.xml:5233(para) msgid "" "If you publish or distribute Opaque copies of the Document numbering more " "than 100, you must either include a machine-readable Transparent copy along " "with each Opaque copy, or state in or with each Opaque copy a computer-" "network location from which the general network-using public has access to " "download using public-standard network protocols a complete Transparent copy " "of the Document, free of added material. If you use the latter option, you " "must take reasonably prudent steps, when you begin distribution of Opaque " "copies in quantity, to ensure that this Transparent copy will remain thus " "accessible at the stated location until at least one year after the last " "time you distribute an Opaque copy (directly or through your agents or " "retailers) of that edition to the public." msgstr "" #: LVM-HOWTO.xml:5248(para) msgid "" "It is requested, but not required, that you contact the authors of the " "Document well before redistributing any large number of copies, to give them " "a chance to provide you with an updated version of the Document." msgstr "" #: LVM-HOWTO.xml:5254(title) msgid "MODIFICATIONS" msgstr "" #: LVM-HOWTO.xml:5256(para) msgid "" "You may copy and distribute a Modified Version of the Document under the " "conditions of sections 2 and 3 above, provided that you release the Modified " "Version under precisely this License, with the Modified Version filling the " "role of the Document, thus licensing distribution and modification of the " "Modified Version to whoever possesses a copy of it. In addition, you must do " "these things in the Modified Version:" msgstr "" #: LVM-HOWTO.xml:5266(simpara) msgid "" "Use in the Title Page (and on the covers, if any) a title distinct from that " "of the Document, and from those of previous versions (which should, if there " "were any, be listed in the History section of the Document). You may use the " "same title as a previous version if the original publisher of that version " "gives permission." msgstr "" #: LVM-HOWTO.xml:5274(simpara) msgid "" "List on the Title Page, as authors, one or more persons or entities " "responsible for authorship of the modifications in the Modified Version, " "together with at least five of the principal authors of the Document (all of " "its principal authors, if it has fewer than five), unless they release you " "from this requirement." msgstr "" #: LVM-HOWTO.xml:5282(simpara) msgid "" "State on the Title page the name of the publisher of the Modified Version, " "as the publisher." msgstr "" #: LVM-HOWTO.xml:5286(simpara) msgid "Preserve all the copyright notices of the Document." msgstr "" #: LVM-HOWTO.xml:5289(simpara) msgid "" "Add an appropriate copyright notice for your modifications adjacent to the " "other copyright notices." msgstr "" #: LVM-HOWTO.xml:5293(simpara) msgid "" "Include, immediately after the copyright notices, a license notice giving " "the public permission to use the Modified Version under the terms of this " "License, in the form shown in the Addendum below." msgstr "" #: LVM-HOWTO.xml:5299(simpara) msgid "" "Preserve in that license notice the full lists of Invariant Sections and " "required Cover Texts given in the Document's license notice." msgstr "" #: LVM-HOWTO.xml:5303(simpara) msgid "Include an unaltered copy of this License." msgstr "" #: LVM-HOWTO.xml:5306(simpara) msgid "" "Preserve the section Entitled \"History\", Preserve its Title, and add to it " "an item stating at least the title, year, new authors, and publisher of the " "Modified Version as given on the Title Page. If there is no section Entitled " "\"History\" in the Document, create one stating the title, year, authors, " "and publisher of the Document as given on its Title Page, then add an item " "describing the Modified Version as stated in the previous sentence." msgstr "" #: LVM-HOWTO.xml:5316(simpara) msgid "" "Preserve the network location, if any, given in the Document for public " "access to a Transparent copy of the Document, and likewise the network " "locations given in the Document for previous versions it was based on. These " "may be placed in the \"History\" section. You may omit a network location " "for a work that was published at least four years before the Document " "itself, or if the original publisher of the version it refers to gives " "permission." msgstr "" #: LVM-HOWTO.xml:5326(simpara) msgid "" "For any section Entitled \"Acknowledgements\" or \"Dedications\", Preserve " "the Title of the section, and preserve in the section all the substance and " "tone of each of the contributor acknowledgements and/or dedications given " "therein." msgstr "" #: LVM-HOWTO.xml:5332(simpara) msgid "" "Preserve all the Invariant Sections of the Document, unaltered in their text " "and in their titles. Section numbers or the equivalent are not considered " "part of the section titles." msgstr "" #: LVM-HOWTO.xml:5337(simpara) msgid "" "Delete any section Entitled \"Endorsements\". Such a section may not be " "included in the Modified Version." msgstr "" #: LVM-HOWTO.xml:5341(simpara) msgid "" "Do not retitle any existing section to be Entitled \"Endorsements\" or to " "conflict in title with any Invariant Section." msgstr "" #: LVM-HOWTO.xml:5345(simpara) msgid "Preserve any Warranty Disclaimers." msgstr "" #: LVM-HOWTO.xml:5350(para) msgid "" "If the Modified Version includes new front-matter sections or appendices " "that qualify as Secondary Sections and contain no material copied from the " "Document, you may at your option designate some or all of these sections as " "invariant. To do this, add their titles to the list of Invariant Sections in " "the Modified Version's license notice. These titles must be distinct from " "any other section titles." msgstr "" #: LVM-HOWTO.xml:5358(para) msgid "" "You may add a section Entitled \"Endorsements\", provided it contains " "nothing but endorsements of your Modified Version by various parties--for " "example, statements of peer review or that the text has been approved by an " "organization as the authoritative definition of a standard." msgstr "" #: LVM-HOWTO.xml:5364(para) msgid "" "You may add a passage of up to five words as a Front-Cover Text, and a " "passage of up to 25 words as a Back-Cover Text, to the end of the list of " "Cover Texts in the Modified Version. Only one passage of Front-Cover Text " "and one of Back-Cover Text may be added by (or through arrangements made by) " "any one entity. If the Document already includes a cover text for the same " "cover, previously added by you or by arrangement made by the same entity you " "are acting on behalf of, you may not add another; but you may replace the " "old one, on explicit permission from the previous publisher that added the " "old one." msgstr "" #: LVM-HOWTO.xml:5376(para) msgid "" "The author(s) and publisher(s) of the Document do not by this License give " "permission to use their names for publicity for or to assert or imply " "endorsement of any Modified Version." msgstr "" #: LVM-HOWTO.xml:5382(title) msgid "COMBINING DOCUMENTS" msgstr "" #: LVM-HOWTO.xml:5384(para) msgid "" "You may combine the Document with other documents released under this " "License, under the terms defined in section 4 above for modified versions, provided that you include in the " "combination all of the Invariant Sections of all of the original documents, " "unmodified, and list them all as Invariant Sections of your combined work in " "its license notice, and that you preserve all their Warranty Disclaimers." msgstr "" #: LVM-HOWTO.xml:5393(para) msgid "" "The combined work need only contain one copy of this License, and multiple " "identical Invariant Sections may be replaced with a single copy. If there " "are multiple Invariant Sections with the same name but different contents, " "make the title of each such section unique by adding at the end of it, in " "parentheses, the name of the original author or publisher of that section if " "known, or else a unique number. Make the same adjustment to the section " "titles in the list of Invariant Sections in the license notice of the " "combined work." msgstr "" #: LVM-HOWTO.xml:5403(para) msgid "" "In the combination, you must combine any sections Entitled \"History\" in " "the various original documents, forming one section Entitled \"History\"; " "likewise combine any sections Entitled \"Acknowledgements\", and any " "sections Entitled \"Dedications\". You must delete all sections Entitled " "\"Endorsements\"." msgstr "" #: LVM-HOWTO.xml:5411(title) msgid "COLLECTIONS OF DOCUMENTS" msgstr "" #: LVM-HOWTO.xml:5413(para) msgid "" "You may make a collection consisting of the Document and other documents " "released under this License, and replace the individual copies of this " "License in the various documents with a single copy that is included in the " "collection, provided that you follow the rules of this License for verbatim " "copying of each of the documents in all other respects." msgstr "" #: LVM-HOWTO.xml:5421(para) msgid "" "You may extract a single document from such a collection, and distribute it " "individually under this License, provided you insert a copy of this License " "into the extracted document, and follow this License in all other respects " "regarding verbatim copying of that document." msgstr "" #: LVM-HOWTO.xml:5428(title) msgid "AGGREGATION WITH INDEPENDENT WORKS" msgstr "" #: LVM-HOWTO.xml:5430(para) msgid "" "A compilation of the Document or its derivatives with other separate and " "independent documents or works, in or on a volume of a storage or " "distribution medium, is called an \"aggregate\" if the copyright resulting " "from the compilation is not used to limit the legal rights of the " "compilation's users beyond what the individual works permit. When the " "Document is included in an aggregate, this License does not apply to the " "other works in the aggregate which are not themselves derivative works of " "the Document." msgstr "" #: LVM-HOWTO.xml:5440(para) msgid "" "If the Cover Text requirement of section 3 is applicable to these copies of " "the Document, then if the Document is less than one half of the entire " "aggregate, the Document's Cover Texts may be placed on covers that bracket " "the Document within the aggregate, or the electronic equivalent of covers if " "the Document is in electronic form. Otherwise they must appear on printed " "covers that bracket the whole aggregate." msgstr "" #: LVM-HOWTO.xml:5449(title) msgid "TRANSLATION" msgstr "" #: LVM-HOWTO.xml:5451(para) msgid "" "Translation is considered a kind of modification, so you may distribute " "translations of the Document under the terms of section 4. Replacing " "Invariant Sections with translations requires special permission from their " "copyright holders, but you may include translations of some or all Invariant " "Sections in addition to the original versions of these Invariant Sections. " "You may include a translation of this License, and all the license notices " "in the Document, and any Warranty Disclaimers, provided that you also " "include the original English version of this License and the original " "versions of those notices and disclaimers. In case of a disagreement between " "the translation and the original version of this License or a notice or " "disclaimer, the original version will prevail." msgstr "" #: LVM-HOWTO.xml:5466(para) msgid "" "If a section in the Document is Entitled \"Acknowledgements\", \"Dedications" "\", or \"History\", the requirement (section 4) to Preserve its Title " "(section 1) will typically require changing the actual title." msgstr "" #: LVM-HOWTO.xml:5472(title) msgid "TERMINATION" msgstr "" #: LVM-HOWTO.xml:5474(para) msgid "" "You may not copy, modify, sublicense, or distribute the Document except as " "expressly provided for under this License. Any other attempt to copy, " "modify, sublicense or distribute the Document is void, and will " "automatically terminate your rights under this License. However, parties who " "have received copies, or rights, from you under this License will not have " "their licenses terminated so long as such parties remain in full compliance." msgstr "" #: LVM-HOWTO.xml:5484(title) msgid "FUTURE REVISIONS OF THIS LICENSE" msgstr "" #: LVM-HOWTO.xml:5486(para) msgid "" "The Free Software Foundation may publish new, revised versions of the GNU " "Free Documentation License from time to time. Such new versions will be " "similar in spirit to the present version, but may differ in detail to " "address new problems or concerns. See http://www.gnu.org/copyleft/." msgstr "" #: LVM-HOWTO.xml:5493(para) msgid "" "Each version of the License is given a distinguishing version number. If the " "Document specifies that a particular numbered version of this License \"or " "any later version\" applies to it, you have the option of following the " "terms and conditions either of that specified version or of any later " "version that has been published (not as a draft) by the Free Software " "Foundation. If the Document does not specify a version number of this " "License, you may choose any version ever published (not as a draft) by the " "Free Software Foundation." msgstr "" #: LVM-HOWTO.xml:5505(title) msgid "ADDENDUM: How to use this License for your documents" msgstr "" #: LVM-HOWTO.xml:5508(para) msgid "" "To use this License in a document you have written, include a copy of the " "License in the document and put the following copyright and license notices " "just after the title page:" msgstr "" #: LVM-HOWTO.xml:5513(para) msgid "" "Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/" "or modify this document under the terms of the GNU Free Documentation " "License, Version 1.2 or any later version published by the Free Software " "Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-" "Cover Texts. A copy of the license is included in the section entitled \"GNU " "Free Documentation License\"." msgstr "" #: LVM-HOWTO.xml:5522(para) msgid "" "If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, " "replace the \"with...Texts.\" line with this:" msgstr "" #: LVM-HOWTO.xml:5525(para) msgid "" "with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover " "Texts being LIST, and with the Back-Cover Texts being LIST." msgstr "" #: LVM-HOWTO.xml:5530(para) msgid "" "If you have Invariant Sections without Cover Texts, or some other " "combination of the three, merge those two alternatives to suit the situation." msgstr "" #: LVM-HOWTO.xml:5534(para) msgid "" "If your document contains nontrivial examples of program code, we recommend " "releasing these examples in parallel under your choice of free software " "license, such as the GNU General Public License, to permit their use in free " "software." msgstr "" #. Put one translator per line, in the form of NAME , YEAR1, YEAR2. #: LVM-HOWTO.xml:0(None) msgid "translator-credits" msgstr ""