From 6e8583d1349c66af839c2000b1d00ddfaef067ea Mon Sep 17 00:00:00 2001 From: Valentin Dudouyt Date: Tue, 5 May 2015 11:40:53 +0500 Subject: [PATCH 1/2] Delete README Overlaps with README.md --- README | 168 --------------------------------------------------------- 1 file changed, 168 deletions(-) delete mode 100644 README diff --git a/README b/README deleted file mode 100644 index 9091604..0000000 --- a/README +++ /dev/null @@ -1,168 +0,0 @@ - -The driver combines a several mount points into the single one. - -Using -~~~~~ -mhddfs /path/to/dir1,/path/to/dir2[,/path/to/dir3] /path/to/mount -fusermount -u /path/to/mount - -with an "-o option" you can specify some additional options: - --o logfile=/path/to/file.log - specify a file that will contain debug information. - --o loglevel=x - 0 - debug messages - 1 - info messages - 2 - standart (default) messages - --o mlimit=size[m|k|g] - - a free space size threshold - If a drive has the free space less than the threshold - specifed then another drive will be choosen while - creating a new file. If all the drives have free space - less than the threshold specified then a drive containing - most free space will be choosen. - -Default value is 25%, minimum value is 100M. -This option accepts suffixes: -[mM] - megabytes -[gG] - gigabytes -[kK] - kilobytes -[%] - percent - -If mlimit is equal 100% or contain a number which is more than the -largest of mount directories, mhddfs will try to allocate files -regularly. - -For an information about the additional options see output of -'mhddfs -h'. - -It's necessary to get installed fuse-utils, libfuse for driver -working. - -Working -~~~~~~~ - -Consider we have two hard drives with the content below: - -/hdd1 /hdd2 -| | -+-- /dir1 +-- /dir1 -| | | | -| +- file2 | +- file4 -| | +- file2 -+-- file1 | -| +-- file5 -+-- /dir2 | - | +-- /dir3 - +- file3 | - +- file6 - -mounting this tree with the command: - -mhddfs /hdd1,/hdd2 /hdd_common - -into the specified file system point we will see a combined tree. - -In the united tree we can see all the directories and files. Note -file2 of 2nd hdd is not visible (because 1st hdd has the file2 -already). - -/hdd_common -| -+-- /dir1 -| | -| +-- file2 -> /hdd1/dir1/file2 -| +-- file4 -| -|-- /dir2 -| | -| + file3 -| -+-- /dir3 -| | -| +-- file6 -| -+-- file1 -+-- file5 - - -While writing files they are written to a 1st hdd until the hdd -has the free space (see mlimit option), then they are written on -a 2nd hdd, then to 3rd etc. - -df will show a total statistics of all filesystems like there is -a big one hdd. - -If an overflow arises while writing to the hdd1 then a file -content already written will be transferred to a hdd containing -enough of free space for a file. The transferring is processed -on-the-fly, fully transparent for the application that is -writing. So this behaviour simulates a big file system. - -WARNING: The filesystems are combined must provide a possibility -to get their parameters correctly (e.g. size of free space). -Otherwise the writing failure can occur (but data consistency -will be ok anyway). For example it is a bad idea to combine a -several sshfs systems together. - -File system's functions -~~~~~~~~~~~~~~~~~~~~~~~ - -Most of the functions are supported. - -Functions are supported: -- get/set attributes of file system objects; -- get/set file system information (total size, size of - free space is calculated as summary size of file systems); -- read/remove/create directories; -- read/remove/create/write files; -- symbolic links; -- device files, sockets and fifo; -- file locks; -- hardlinks (only on a single device; no moving support for - hardlinked files) -- extended file attributes (xattr); - -Install -~~~~~~~ - -It's neccessary for install to have: -1. FUSE header files -2. GCC -3. libc6 header files -4. uthash header files -5. libattr1 header files (optional) - -Run 'make' in the source directory produces mhddfs binary. - -Put the binary into /usr/bin or /usr/local/bin and now you -can use it. - -Please read FUSE documentation for a further conception. - - -GET IT -~~~~~~ - -Last version of the mhddfs drivers you can get at -http://mhddfs.uvw.ru/downloads. -SVN version is located at: http://svn.uvw.ru/mhddfs/trunk -To checkout SVN files run: - -svn co http://svn.uvw.ru/mhddfs/trunk mhddfs - - -BUGS -~~~~ -Please use Debian-BTS as the bugtracking system. Feel free to -submit a bug information to the Debian bugtracker for mhddfs -project. See the additional information here: -http://www.debian.org/Bugs - -COPYRIGHT -~~~~~~~~~ -Distributed under GPLv3 and higher -Copyright (C) 2008 Dmitry E. Oboukhov From 4e54a0f0f4eb54727cb419b3a7c5cb4d691681b4 Mon Sep 17 00:00:00 2001 From: Valentin Dudouyt Date: Tue, 5 May 2015 11:43:35 +0500 Subject: [PATCH 2/2] Update README.md --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index ec640d4..4e9310a 100644 --- a/README.md +++ b/README.md @@ -1,2 +1,14 @@ # mhddfs-nosegfault Mhddfs without a 'Transport endpoint is not connected' bug which was introduced in 0.1.39. This repository will be discounted as soon as I'll receive a response from maintainer. + +## Preamble + +Here are some descriptions of that issue which I've found across the internets. If you've found this repository while searching a solution for that one then you're in a right place. + +https://bugs.launchpad.net/ubuntu/+source/mhddfs/+bug/1429402 + +http://serverfault.com/questions/677352/mhddfs-randomly-breaks + +http://stackoverflow.com/questions/24966676/transport-endpoint-is-not-connected + +http://stackoverflow.com/questions/18006602/mhddfs-automount-failure-and-home-disconnection