tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

add a suggested solution for Q8 

[Imported from Trac: page FAQ, version 71]
zooko 2012-04-18 21:44:27 +00:00
parent 0de0e2c299
commit 08f8b2fb91
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
FAQ.md

@ -45,6 +45,8 @@ A: Not directly. Each storage server has a single "base directory" which we term
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. 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.
Another clean solution is to run three tahoe-lafs storage server processes—one for each of your three drives. That's what the Tahoe-LAFS developers would do.
**<a name="Q9_use_raid_with_tahoe_lafs">Q9:</a> Would it make sense to not use any RAID and let Tahoe-LAFS deal with the redundancy?** **<a name="Q9_use_raid_with_tahoe_lafs">Q9:</a> Would it make sense to not use any RAID and let Tahoe-LAFS deal with the redundancy?**
A: The Allmydata grid didn't bother with RAID at all: each Tahoe-LAFS storage server node used a single spindle. A: The Allmydata grid didn't bother with RAID at all: each Tahoe-LAFS storage server node used a single spindle.