aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMartin Brandenburg <martin@omnibond.com>2018-04-03 12:27:15 -0400
committerMike Marshall <hubcap@omnibond.com>2018-04-03 21:55:28 -0400
commitdd0980226f89c89e531a64b34a2a350358de46dd (patch)
tree791396c72899f0f3d8016660d0b27c280f16af4f
parent209469d978ae91e460b37b32f2c2834d93e1ff13 (diff)
orangefs: document package install and xfstests procedure
Unless one is working on the userspace code, there's no need to compile OrangeFS. The package works just fine. (But leave the documentation for building from source since not everyone uses distributions which include the package.) Also document the process to run xfstests against OrangeFS. Signed-off-by: Martin Brandenburg <martin@omnibond.com> Signed-off-by: Mike Marshall <hubcap@omnibond.com>
-rw-r--r--Documentation/filesystems/orangefs.txt126
1 files changed, 103 insertions, 23 deletions
diff --git a/Documentation/filesystems/orangefs.txt b/Documentation/filesystems/orangefs.txt
index e2818b60a5c2..9f8e7902d31d 100644
--- a/Documentation/filesystems/orangefs.txt
+++ b/Documentation/filesystems/orangefs.txt
@@ -42,12 +42,59 @@ Orangefs versions prior to 2.9.3 would not be compatible with the
42upstream version of the kernel client. 42upstream version of the kernel client.
43 43
44 44
45BUILDING THE USERSPACE FILESYSTEM ON A SINGLE SERVER 45RUNNING ORANGEFS ON A SINGLE SERVER
46==================================================== 46===================================
47 47
48You can omit --prefix if you don't care that things are sprinkled around in 48OrangeFS is usually run in large installations with multiple servers and
49/usr/local. As of version 2.9.6, Orangefs uses Berkeley DB by default, we 49clients, but a complete filesystem can be run on a single machine for
50will probably be changing the default to lmdb soon. 50development and testing.
51
52On Fedora, install orangefs and orangefs-server.
53
54dnf -y install orangefs orangefs-server
55
56There is an example server configuration file in
57/etc/orangefs/orangefs.conf. Change localhost to your hostname if
58necessary.
59
60To generate a filesystem to run xfstests against, see below.
61
62There is an example client configuration file in /etc/pvfs2tab. It is a
63single line. Uncomment it and change the hostname if necessary. This
64controls clients which use libpvfs2. This does not control the
65pvfs2-client-core.
66
67Create the filesystem.
68
69pvfs2-server -f /etc/orangefs/orangefs.conf
70
71Start the server.
72
73systemctl start orangefs-server
74
75Test the server.
76
77pvfs2-ping -m /pvfsmnt
78
79Start the client. The module must be compiled in or loaded before this
80point.
81
82systemctl start orangefs-client
83
84Mount the filesystem.
85
86mount -t pvfs2 tcp://localhost:3334/orangefs /pvfsmnt
87
88
89BUILDING ORANGEFS ON A SINGLE SERVER
90====================================
91
92Where OrangeFS cannot be installed from distribution packages, it may be
93built from source.
94
95You can omit --prefix if you don't care that things are sprinkled around
96in /usr/local. As of version 2.9.6, OrangeFS uses Berkeley DB by
97default, we will probably be changing the default to LMDB soon.
51 98
52./configure --prefix=/opt/ofs --with-db-backend=lmdb 99./configure --prefix=/opt/ofs --with-db-backend=lmdb
53 100
@@ -55,35 +102,68 @@ make
55 102
56make install 103make install
57 104
58Create an orangefs config file: 105Create an orangefs config file.
106
59/opt/ofs/bin/pvfs2-genconfig /etc/pvfs2.conf 107/opt/ofs/bin/pvfs2-genconfig /etc/pvfs2.conf
60 108
61 for "Enter hostnames", use the hostname, don't let it default to 109Create an /etc/pvfs2tab file.
62 localhost. 110
111echo tcp://localhost:3334/orangefs /pvfsmnt pvfs2 defaults,noauto 0 0 > \
112 /etc/pvfs2tab
113
114Create the mount point you specified in the tab file if needed.
115
116mkdir /pvfsmnt
63 117
64create a pvfs2tab file in /etc: 118Bootstrap the server.
65cat /etc/pvfs2tab
66tcp://myhostname:3334/orangefs /mymountpoint pvfs2 defaults,noauto 0 0
67 119
68create the mount point you specified in the tab file if needed: 120/opt/ofs/sbin/pvfs2-server -f /etc/pvfs2.conf
69mkdir /mymountpoint
70 121
71bootstrap the server: 122Start the server.
72/opt/ofs/sbin/pvfs2-server /etc/pvfs2.conf -f
73 123
74start the server:
75/opt/osf/sbin/pvfs2-server /etc/pvfs2.conf 124/opt/osf/sbin/pvfs2-server /etc/pvfs2.conf
76 125
77Now the server is running. At this point you might like to 126Now the server is running. At this point you might like to
78prove things are working with: 127prove things are working with.
128
129/opt/ofs/bin/pvfs2-ls /pvfsmnt
130
131If stuff seems to be working, turn on the client core.
132
133/opt/ofs/sbin/pvfs2-client -p /opt/osf/sbin/pvfs2-client-core
134
135Mount your filesystem (load the kernel module first if necessary).
136
137mount -t pvfs2 tcp://localhost:3334/orangefs /pvfsmnt
138
139
140RUNNING XFSTESTS
141================
142
143It is useful to use a scratch filesystem with xfstests. This can be
144done with only one server.
145
146Make a second copy of the FileSystem section in the server configuration
147file, which is /etc/orangefs/orangefs.conf. Change the Name to scratch.
148Change the ID to something other than the ID of the first FileSystem
149section (2 is usually a good choice).
150
151Then there are two FileSystem sections: orangefs and scratch.
152
153This change should be made before creating the filesystem.
154
155pvfs2-server -f /etc/orangefs/orangefs.conf
156
157To run xfstests, create /etc/xfsqa.config.
79 158
80/opt/osf/bin/pvfs2-ls /mymountpoint 159TEST_DIR=/orangefs
160TEST_DEV=tcp://localhost:3334/orangefs
161SCRATCH_MNT=/scratch
162SCRATCH_DEV=tcp://localhost:3334/scratch
81 163
82If stuff seems to be working, turn on the client core: 164Then xfstests can be run
83/opt/osf/sbin/pvfs2-client -p /opt/osf/sbin/pvfs2-client-core
84 165
85Mount your filesystem. 166./check -pvfs2
86mount -t pvfs2 tcp://myhostname:3334/orangefs /mymountpoint
87 167
88 168
89OPTIONS 169OPTIONS