From 3dd66ed95dd59adc6060c521966fdb359ccf0fb0 Mon Sep 17 00:00:00 2001 From: Andreas Dilger Date: Mon, 16 Sep 2013 17:32:20 -0600 Subject: [PATCH] LUDOC-184 misc: change URLs to *.hpdd.intel.com Update the URLs in the manual to use *.hpdd.intel.com instead of the older *.whamcloud.com addresses. Signed-off-by: Andreas Dilger Change-Id: I262abeee78bfd09f2c5f81b3dfe46859c0a4db4b Reviewed-on: http://review.whamcloud.com/7677 Tested-by: Hudson Reviewed-by: Linda Bebernes Reviewed-by: Richard Henwood --- BackupAndRestore.xml | 22 ++++++++++++++++++++-- BenchmarkingTests.xml | 2 +- ConfiguringQuotas.xml | 3 ++- LustreDebugging.xml | 2 +- Makefile | 2 +- Preface.xml | 12 +++++++----- SystemConfigurationUtilities.xml | 2 +- UnderstandingLustre.xml | 2 +- 8 files changed, 34 insertions(+), 13 deletions(-) diff --git a/BackupAndRestore.xml b/BackupAndRestore.xml index 2a8d5ba..2cf9599 100644 --- a/BackupAndRestore.xml +++ b/BackupAndRestore.xml @@ -194,7 +194,16 @@ Changelog records consumed: 42 Keeping an updated full backup of the MDT is especially important because a permanent failure of the MDT file system renders the much larger amount of data in all the OSTs largely inaccessible and unusable. - In Lustre 2.0 through 2.2, the only successful way to backup and restore an MDT is to do a device-level backup as is described in this section. File-level restore of an MDT is not possible before Lustre 2.3, as the Object Index (OI) file cannot be rebuilt after restore without the OI Scrub functionality. Since Lustre 2.3, Object Index files are automatically rebuilt at first mount after a restore is detected (see LU-957), and file-level backup is supported (see ). + In Lustre 2.0 through 2.2, the only successful way to backup and + restore an MDT is to do a device-level backup as is described in this + section. File-level restore of an MDT is not possible before Lustre 2.3, + as the Object Index (OI) file cannot be rebuilt after restore without + the OI Scrub functionality. + Since Lustre 2.3, Object Index files + are automatically rebuilt at first mount after a restore is detected + (see LU-957), + and file-level backup is supported + (see ). If hardware replacement is the reason for the backup or if a spare storage device is available, it is possible to do a raw copy of the MDT or OST from one block device to the other, as long as the new device is at least as large as the original device. To do this, run: dd if=/dev/{original} of=/dev/{newdev} bs=1M @@ -211,7 +220,16 @@ Changelog records consumed: 42 <indexterm><primary>backup</primary><secondary>OST file system</secondary></indexterm><indexterm><primary>backup</primary><secondary>MDT file system</secondary></indexterm>Making a File-Level Backup of an OST or MDT File System This procedure provides an alternative to backup or migrate the data of an OST or MDT at the file level. At the file-level, unused space is omitted from the backed up and the process may be completed quicker with smaller total backup size. Backing up a single OST device is not necessarily the best way to perform backups of the Lustre file system, since the files stored in the backup are not usable without metadata stored on the MDT and additional file stripes that may be on other OSTs. However, it is the preferred method for migration of OST devices, especially when it is desirable to reformat the underlying file system with different configuration options or to reduce fragmentation. - Prior to Lustre 2.3, the only successful way to perform an MDT backup and restore is to do a device-level backup as is described in . The ability to do MDT file-level backups is not available for Lustre 2.0 thru 2.2, because restoration of the Object Index (OI) file does not return the MDT to a functioning state. Since Lustre 2.3, Object Index files are automatically rebuilt at first mount after a restore is detected (see LU-957), so file-level MDT restore is supported. + Prior to Lustre 2.3, the only successful way to perform an MDT + backup and restore is to do a device-level backup as is described in + . The ability to do MDT + file-level backups is not available for Lustre 2.0 thru 2.2, because + restoration of the Object Index (OI) file does not return the MDT to + a functioning state. Since Lustre 2.3, + Object Index files are automatically rebuilt at first mount after a + restore is detected (see + LU-957), + so file-level MDT restore is supported. For Lustre 2.3 and newer with MDT file-level backup support, substitute mdt for ost in the instructions below. diff --git a/BenchmarkingTests.xml b/BenchmarkingTests.xml index fb300ec..b044aff 100644 --- a/BenchmarkingTests.xml +++ b/BenchmarkingTests.xml @@ -71,7 +71,7 @@ Download the Lustre I/O kit (lustre-iokit)from: - http://downloads.whamcloud.com/ + http://downloads.hpdd.intel.com/
diff --git a/ConfiguringQuotas.xml b/ConfiguringQuotas.xml index d521207..a2f2a11 100644 --- a/ConfiguringQuotas.xml +++ b/ConfiguringQuotas.xml @@ -98,7 +98,8 @@ Lustre 2.4 and beyond requires a version of e2fsprogs that supports quota (i.e. newer or equal to 1.42.3.wc1) to be installed on the server nodes using ldiskfs backend (e2fsprogs isn't needed with ZFS backend). In general, we recommend to use the latest - e2fsprogs version available on http://downloads.whamcloud.com/public/e2fsprogs. + e2fsprogs version available on http://downloads.hpdd.intel.com/public/e2fsprogs/. + The ldiskfs OSD relies on the standard Linux quota to maintain accounting information on disk. As a consequence, the Linux kernel running on the Lustre servers using ldiskfs backend must have CONFIG_QUOTA, CONFIG_QUOTACTL and diff --git a/LustreDebugging.xml b/LustreDebugging.xml index ad61059..42eab3f 100644 --- a/LustreDebugging.xml +++ b/LustreDebugging.xml @@ -121,7 +121,7 @@ Diagnostic and Debugging Tools tcpdump and can read packet dumps generated by it. There are plug-ins available to dissassemble the LNET and Lustre protocols. They are located within the Lustre git repository + xl:href="http://git.hpdd.intel.com/">Lustre git repository under lustre/contrib/wireshark/. Installation instruction are included in that directory. See also Wireshark Website for diff --git a/Makefile b/Makefile index a5b78cd..b829e94 100644 --- a/Makefile +++ b/Makefile @@ -100,7 +100,7 @@ diff: $(TGT_BASE).xhtml $(TGT_MASTER).xhtml .PHONY: push push: - git push ssh://review.whamcloud.com:29418/doc/manual HEAD:refs/for/master + git push ssh://review.hpdd.intel.com:29418/doc/manual HEAD:refs/for/master .PHONY: clean clean: diff --git a/Preface.xml b/Preface.xml index 95741f8..f9538fd 100644 --- a/Preface.xml +++ b/Preface.xml @@ -8,7 +8,9 @@ system.
About this Document - This document is maintained by Intel in Docbook format. The canonical version is available at http://wiki.whamcloud.com/display/PUB/Documentation. + This document is maintained by Intel in Docbook format. The + canonical version is available at + http://wiki.hpdd.intel.com/display/PUB/Documentation.
UNIX Commands @@ -84,7 +86,7 @@
Related Documentation The documents listed as online are available at: - http://wiki.whamcloud.com/display/PUB/Documentation + http://wiki.hpdd.intel.com/display/PUB/Documentation @@ -148,13 +150,13 @@ These web sites provide additional resources: - Documentation http://wiki.whamcloud.com/display/PUB/Documentation + Documentation http://wiki.hpdd.intel.com/display/PUB/Documentation - Support http://www.whamcloud.com/ + Support http://www.hpdd.intel.com/ - Training http://www.whamcloud.com/ + Training http://www.hpdd.intel.com/
diff --git a/SystemConfigurationUtilities.xml b/SystemConfigurationUtilities.xml index 4080633..37da705 100644 --- a/SystemConfigurationUtilities.xml +++ b/SystemConfigurationUtilities.xml @@ -66,7 +66,7 @@ <indexterm><primary>e2scan</primary></indexterm> e2scan The e2scan utility is an ext2 file system-modified inode scan program. The e2scan program uses libext2fs to find inodes with ctime or mtime newer than a given time and prints out their pathname. Use e2scan to efficiently generate lists of files that have been modified. The e2scan tool is included in the e2fsprogs package, located at: - http://downloads.whamcloud.com/public/e2fsprogs/latest/ + http://downloads.hpdd.intel.com/public/e2fsprogs/latest/
Synopsis e2scan [options] [-f file] block_device diff --git a/UnderstandingLustre.xml b/UnderstandingLustre.xml index dd95bc5..14c17c4 100644 --- a/UnderstandingLustre.xml +++ b/UnderstandingLustre.xml @@ -56,7 +56,7 @@ features Lustre Features Lustre file systems run on a variety of vendor's kernels. For more details, see the - Lustre Support + Lustre Support Matrix on the Intel Lustre community wiki. A Lustre installation can be scaled up or down with respect to the number of client nodes, disk storage and bandwidth. Scalability and performance are dependent on available -- 1.8.3.1