1 POHMELFS usage information.
5 Each mountpoint is associated with a special index via this option.
6 Administrator can add or remove servers from the given index, so all mounts,
7 which were attached to it, are updated.
11 This timeout, expressed in milliseconds, specifies time to scan transaction
12 trees looking for stale requests, which have to be resent, or if number of
13 retries exceed specified limit, dropped with error.
17 Internal timeout, expressed in milliseconds, which specifies how frequently
18 inodes marked to be dropped are freed. It also specifies how frequently
19 the system checks that servers have to be added or removed from current working set.
22 wait_on_page_timeout=%u
23 Number of milliseconds to wait for reply from remote server for data reading command.
24 If this timeout is exceeded, reading returns an error.
28 This is the number of times that a transaction will be resent to a server that did
29 not answer for the last @trans_scan_timeout milliseconds.
30 When the number of resends exceeds this limit, the transaction is completed with error.
34 Number of crypto processing threads. Threads are used both for RX and TX traffic.
35 Default is 2, or no threads if crypto operations are not supported.
38 Maximum number of pages in a single transaction. This parameter also controls
39 the number of pages, allocated for crypto processing (each crypto thread has
40 pool of pages, the number of which is equal to 'trans_max_pages'.
43 crypto_fail_unsupported
44 If specified, mount will fail if the server does not support requested crypto operations.
45 By default mount will disable non-matching crypto operations.
48 Maximum number of milliseconds to wait for the mcache objects to be processed.
49 Mcache includes locks (given lock should be granted by server), attributes (they should be
50 fully received in the given timeframe).
55 Add (or remove if it already exists) server server1.net:1025 into the working set with index $idx
56 with appropriate hash algorithm and key file and cipher algorithm, mode and key file:
57 $cfg -a server1.net -p 1025 -i $idx -K $hash_key -k $cipher_key
59 Mount filesystem with given index $idx to /mnt mountpoint.
60 Client will connect to all servers specified in the working set via previous command:
61 mount -t pohmel -o idx=$idx q /mnt
63 One can add or remove servers from working set after mounting too.
68 Creating a server, which listens at port 1025 and 0.0.0.0 address.
69 Working root directory (note, that server chroots there, so you have to have appropriate permissions)
70 is set to /mnt, server will negotiate hash/cipher with client, in case client requested it, there
71 are appropriate key files.
72 Number of working threads is set to 10.
74 # ./fserver -a 0.0.0.0 -p 1025 -r /mnt -w 10 -K hash_key -k cipher_key
76 -A 6 - listen on ipv6 address. Default: Disabled.
77 -r root - path to root directory. Default: /tmp.
78 -a addr - listen address. Default: 0.0.0.0.
79 -p port - listen port. Default: 1025.
80 -w workers - number of workers per connected client. Default: 1.
81 -K file - hash key size. Default: none.
82 -k file - cipher key size. Default: none.
85 Number of worker threads specifies how many workers will be created for each client.
86 Bulk single-client transafers usually are better handled with smaller number (like 1-3).