-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathREADME.install
More file actions
65 lines (55 loc) · 3.33 KB
/
README.install
File metadata and controls
65 lines (55 loc) · 3.33 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
0) All PLFS installations need a valid plfsrc file. Check examples to
create one either in $HOME/.plfsrc or in /etc/plfsrc. Check it with
tools/plfs_check_config after building PLFS. Please note that the
'map' directive has been deprecated and is not included in plfsrc's
even since 2.0. All of the documentation should be updated to reflect
this. Any old plfsrc's containing this directive need to be edited
beforing updating to 2.0 or above.
0.0) if you are a developer and check out PLFS code from sourceforge, you
will need to run ./autogen.sh which will probably complain about version
build tool versions. We do supply a Makefile.tools which tries to download,
configure, and install the correct versions of these tools in buildtools/bin.
So you can do 'make -f Makefile.tools' and then prefix `pwd`/buildtools/bin
to your PATH environment.
1) To install PLFS as a FUSE filesystem.
0) you'll need to have fuse installed and have /dev/libfuse loaded
1) ./configure ; make
2) then create a $HOME/.plfsrc or /etc/plfsrc file. Check the examples.
3) check your .plfsrc file with tools/plfs_check_config
4) launch your plfs executable (e.g. plfs -obig_writes /mnt/plfs)
5) cat /mnt/plfs/.plfsdebug to see if it's working
6) use /mnt/plfs as you would any posix file system
2) To install PLFS as a ROMIO ADIO layer for MPI-IO.
This should be straight-forward for openmpi-1.4.3. For other mpi's, you'll
need to adjust accordingly. The instruction marked with '>>>>' is for
developers only who have checked out PLFS. For typical cases in which
you are instead building from a distribution tarball, you can skip that
line. Please note that all other patch files have
been deprecated. You must use the two patch files below.
> make install of plfs
> XXXXXXX # see below
> get openmpi-1.4.3
> cd openmpi-1.4.3
> patch -p1 < /path/to/plfs/ad-patches/openmpi/ompi-1.4.3-plfs-prep.patch
> patch -p1 < /path/to/plfs/ad-patches/openmpi/ompi-1.4.3-plfs.patch
> ./autogen.sh # since we patched a Makefile.am
> ./configure; make
One tricky bit is that you have to make sure that your mpi build knows
how to find your plfs.h and your libplfs files. We do that with a
platform file that has lines like this in it:
with_io_romio_flags=--with-file-system=ufs+nfs+panfs+plfs
LDFLAGS="-m64 -L/users/johnbent/plfs/lib -lz -lpthread -lplfs -lstdc++ "
CFLAGS="-I/opt/panfs/include -m64 -I/users/johnbent/plfs/include "
CXXFLAGS="-I/opt/panfs/include -m64 -I/users/johnbent/plfs/include "
CCASFLAGS="-I/opt/panfs/include -m64 -I/users/johnbent/plfs/include "
Then your configure line is like this: ./configure --with-platform=./platform
You may also need to set LD_LIBRARY_PATH to where you install the plfs lib
[XXXXXX If you are a user and downloaded a distribution tarball, then skip
this. If, on the other hand, you are a developer and you checked out the
source, at this point you need to run ./scripts/make_plfs_patch. This will
build the patch file needed for the next steps.]
3) To build the PLFS library and link apps against it.
Build and install PLFS. Then look at plfs.h and figure out how to use it.
Basically you just change your opens to plfs_opens and etc.
Email plfs-users@lists.sourceforge.net with any user questions.
Email plfs-devel@lists.sourceforge.net with any developer questions.