[tahoe-lafs-trac-stream] [tahoe-lafs] #1884: mention symlinking the shares directory in configuration.rst

[tahoe-lafs]

#1884: mention symlinking the shares directory in configuration.rst
--------------------------+------------------------------------------------
     Reporter:            |      Owner:  marlowe
  davidsarah              |     Status:  new
         Type:  defect    |  Milestone:  undecided
     Priority:  normal    |    Version:  1.9.2
    Component:            |   Keywords:  configuration docs symlink storage
  documentation           |
   Resolution:            |
Launchpad Bug:            |
--------------------------+------------------------------------------------

Comment (by marlowe):

 Appropriate references

 " Q8: Can there be more than one storage directory on a storage node? So
 if a storage server contains 3 drives without RAID, can it use all 3 for
 storage?

 A: Not directly. Each storage server has a single "base directory" which
 we term $BASEDIR. The server keeps all of its shares in a subdirectory
 named $BASEDIR/storage/shares/. (Note that you can symlink this to
 whatever you want: you can keep the rest of the node's files in one place,
 and store all the shares somewhere else). Since there's only one such
 subdirectory, you can only use one filesystem per node. On the other hand,
 shares are stored in a set of 1024 subdirectories of that one, named
 $BASEDIR/storage/shares/aa/, $BASEDIR/storage/shares/ab/, etc. If you were
 to symlink the first third of these to one filesystem, the next third to a
 second filesystem, etc, (hopefully with a script!), then you'd get about
 1/3rd of the shares stored on each disk. The "how much space is available"
 and space-reservation tools would be confused (including making the
 reserved_space parameter unusable), but basically everything else should
 work normally.

 A cleaner solution would be to use LVM instead, which can combine several
 physical disks (or loop devices consisting of common files) to a single
 logical volume. This logical volume can then be mounted or symlinked to
 $BASEDIR/storage. This also is a more flexible solution because new disks
 can then be added seamlessly to the volume with LVM."

 in NEWS.rst

 - Storage servers now calculate their remaining space based on the
 filesystem
   containing the ``storage/shares/`` directory. Previously they looked at
 the
   filesystem containing the ``storage/`` directory. This allows
   ``storage/shares/``, rather than ``storage/``, to be a mount point or a
   symlink pointing to another filesystem. (`#1384`_)

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1884#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage