Skip to content

Commit dd09802

Browse files
Martin Brandenburghubcapsc
authored andcommitted
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 <[email protected]> Signed-off-by: Mike Marshall <[email protected]>
1 parent 209469d commit dd09802

File tree

1 file changed

+103
-23
lines changed

1 file changed

+103
-23
lines changed

Documentation/filesystems/orangefs.txt

Lines changed: 103 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -42,48 +42,128 @@ Orangefs versions prior to 2.9.3 would not be compatible with the
4242
upstream version of the kernel client.
4343

4444

45-
BUILDING THE USERSPACE FILESYSTEM ON A SINGLE SERVER
46-
====================================================
45+
RUNNING ORANGEFS ON A SINGLE SERVER
46+
===================================
4747

48-
You can omit --prefix if you don't care that things are sprinkled around in
49-
/usr/local. As of version 2.9.6, Orangefs uses Berkeley DB by default, we
50-
will probably be changing the default to lmdb soon.
48+
OrangeFS is usually run in large installations with multiple servers and
49+
clients, but a complete filesystem can be run on a single machine for
50+
development and testing.
51+
52+
On Fedora, install orangefs and orangefs-server.
53+
54+
dnf -y install orangefs orangefs-server
55+
56+
There is an example server configuration file in
57+
/etc/orangefs/orangefs.conf. Change localhost to your hostname if
58+
necessary.
59+
60+
To generate a filesystem to run xfstests against, see below.
61+
62+
There is an example client configuration file in /etc/pvfs2tab. It is a
63+
single line. Uncomment it and change the hostname if necessary. This
64+
controls clients which use libpvfs2. This does not control the
65+
pvfs2-client-core.
66+
67+
Create the filesystem.
68+
69+
pvfs2-server -f /etc/orangefs/orangefs.conf
70+
71+
Start the server.
72+
73+
systemctl start orangefs-server
74+
75+
Test the server.
76+
77+
pvfs2-ping -m /pvfsmnt
78+
79+
Start the client. The module must be compiled in or loaded before this
80+
point.
81+
82+
systemctl start orangefs-client
83+
84+
Mount the filesystem.
85+
86+
mount -t pvfs2 tcp://localhost:3334/orangefs /pvfsmnt
87+
88+
89+
BUILDING ORANGEFS ON A SINGLE SERVER
90+
====================================
91+
92+
Where OrangeFS cannot be installed from distribution packages, it may be
93+
built from source.
94+
95+
You can omit --prefix if you don't care that things are sprinkled around
96+
in /usr/local. As of version 2.9.6, OrangeFS uses Berkeley DB by
97+
default, we will probably be changing the default to LMDB soon.
5198

5299
./configure --prefix=/opt/ofs --with-db-backend=lmdb
53100

54101
make
55102

56103
make install
57104

58-
Create an orangefs config file:
105+
Create an orangefs config file.
106+
59107
/opt/ofs/bin/pvfs2-genconfig /etc/pvfs2.conf
60108

61-
for "Enter hostnames", use the hostname, don't let it default to
62-
localhost.
109+
Create an /etc/pvfs2tab file.
110+
111+
echo tcp://localhost:3334/orangefs /pvfsmnt pvfs2 defaults,noauto 0 0 > \
112+
/etc/pvfs2tab
113+
114+
Create the mount point you specified in the tab file if needed.
115+
116+
mkdir /pvfsmnt
63117

64-
create a pvfs2tab file in /etc:
65-
cat /etc/pvfs2tab
66-
tcp://myhostname:3334/orangefs /mymountpoint pvfs2 defaults,noauto 0 0
118+
Bootstrap the server.
67119

68-
create the mount point you specified in the tab file if needed:
69-
mkdir /mymountpoint
120+
/opt/ofs/sbin/pvfs2-server -f /etc/pvfs2.conf
70121

71-
bootstrap the server:
72-
/opt/ofs/sbin/pvfs2-server /etc/pvfs2.conf -f
122+
Start the server.
73123

74-
start the server:
75124
/opt/osf/sbin/pvfs2-server /etc/pvfs2.conf
76125

77-
Now the server is running. At this point you might like to
78-
prove things are working with:
126+
Now the server is running. At this point you might like to
127+
prove things are working with.
128+
129+
/opt/ofs/bin/pvfs2-ls /pvfsmnt
130+
131+
If 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+
135+
Mount your filesystem (load the kernel module first if necessary).
136+
137+
mount -t pvfs2 tcp://localhost:3334/orangefs /pvfsmnt
138+
139+
140+
RUNNING XFSTESTS
141+
================
142+
143+
It is useful to use a scratch filesystem with xfstests. This can be
144+
done with only one server.
145+
146+
Make a second copy of the FileSystem section in the server configuration
147+
file, which is /etc/orangefs/orangefs.conf. Change the Name to scratch.
148+
Change the ID to something other than the ID of the first FileSystem
149+
section (2 is usually a good choice).
150+
151+
Then there are two FileSystem sections: orangefs and scratch.
152+
153+
This change should be made before creating the filesystem.
154+
155+
pvfs2-server -f /etc/orangefs/orangefs.conf
156+
157+
To run xfstests, create /etc/xfsqa.config.
79158

80-
/opt/osf/bin/pvfs2-ls /mymountpoint
159+
TEST_DIR=/orangefs
160+
TEST_DEV=tcp://localhost:3334/orangefs
161+
SCRATCH_MNT=/scratch
162+
SCRATCH_DEV=tcp://localhost:3334/scratch
81163

82-
If stuff seems to be working, turn on the client core:
83-
/opt/osf/sbin/pvfs2-client -p /opt/osf/sbin/pvfs2-client-core
164+
Then xfstests can be run
84165

85-
Mount your filesystem.
86-
mount -t pvfs2 tcp://myhostname:3334/orangefs /mymountpoint
166+
./check -pvfs2
87167

88168

89169
OPTIONS

0 commit comments

Comments
 (0)