maidsafe-archive/maidsafe-drive

MaidSafe-Drive is a virtual drive offering services to store and retrieve information to any storage media including network file systems

maidsafe-drive's Issues

Drive tests seg faulting on teardown

Migrated from maidsafe-archive/MaidSafe#33

running virtual_filesystem tests results in seg fault during the teardown after all tests have completed.

further details to follow

fstest-chown-00 failing test

Fstest-chown-00, run through a series of ownership checks and returns if each has passed or failed. Currently 4 of these checks consistently fail (checks 141, 145, 149, 153)

Fails on both 32 and 64 bit versions of Ubuntu

Test drive failing to unmount during unit test runs on virtualized machines

When running the Drive unit tests, after and sometimes during the testing the execute the TestDrive executable, the TestDrive will remain mounted, quickly consuming all system resources, and causing all later tests to fails. This only appears to occur on virtualized machines.

Running the failed tests through the debugger after cleaning up the TestDrive mounts left behind from the unit test run, will obviously work, as the system now has resources available again.

This is a big issue for continuous integration servers as it prevents them running uninterrupted for more than one night.

Test Machines affected:

CI-Ubuntu11-32bit
CI-Ubuntu11-64bit

Accessing non-existing chunk floods network with requests

Migrated from maidsafe-archive/MaidSafe#57

When we try to read a file which has a chunk missing, for each increment of the offset pointer that falls within the chunk we re-try to retrieve it, only to fail every time.

Encrypt needs to be aware which chunks it already tried to retrieve unsuccessfully to prevent this. Since we don't know whether the chunk is only unavailable temporarily, we need to re-try after a certain period of time.

Test Drive failing

  Start 573: Real Disk Filesystem Test

20/21 Test #573: Real Disk Filesystem Test ........................_Timeout 120.02 sec
Start 574: Local Drive Filesystem Test
21/21 Test #574: Local Drive Filesystem Test ......................_Timeout 120.03 sec

90% tests passed, 2 tests failed out of 21

: on linux zorin8 (64)

do I need to install install anything or change setting ?

btw the mounted maidsafe was locked "Transport endpoint is not connected"

that i need to run : fusermount -u

Fix allowed filename chars

In windows the following are disallowed
|?*<":>+[]/

also the following filenames (in DOS even starting with these is bad sometimes ie com.h woudl fail)

CON, PRN, AUX, CLOCK$, NUL
COM0, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9
LPT0, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9.

In OS/x the colon : is also banned

I think our system should allow for all of these with
so in Linux if I create a david:.doc it should show as that always in linux and in win or OS/X I suggest change the name to
david(case conflict).doc

This keeps the file order and also allows the file still to be associated with the correct app (unlike dropbox which changes the extension which is poor).

For disallowed filenames I would have com for instance show up as com on Linux/OS/X and (name conflict)com in windows.

Drive depends on 'Shared Stuff' directory

When mounting a drive (independent of LifeStuff), unmounting it and then trying to mount it again, it fails because there is no 'Shared Stuff' directory in root. This happens when using the SigmoidPro client.

This should not be a fatal error. Actually, it should not be hardcoded at all, because Drive might be used in applications without shares. Drive should be agnostic of LifeStuff, so it would be better if this were passed in or at least triggered by a switch in constructor/init or similar.

Windows permissions for hidden files not being maintained

Create a text file in windows and make it hidden

Copy the file over to the Sigmoid Drive (Linux based shared over Samba)

When you view the properties using the drive mount on Windows it'll not retain the hidden file attribute.

Doing the same with the read only attribute for example works fine, this only appears to be an issue with hidden files.

Environment

Win 7 32 bit, Samba shared sigmoid drive, mounted on the windows drive letter Z
Ubuntu 11 64bit, drive shared using Samba. Chunkstore located on a separate partition.

Dangling ChunkStore object

When using Drive in Linux, after unmounting and destroying the FuseDriveInUserSpace object there is still a reference to the ChunkStore object kept alive which was passed in via shared pointer. This happens even when Unmount() and WaitUntilUnMounted() are called after Mount() returned.

If there are still processes running in Drive or Encrypt, ideally WaitUntilUnMounted() would wait until all of them are finished (or timed out) so no objects remain in memory which could have a pointer to the ChunkStore and other shared resources. This should happen as a guarantee that once Drive is closed no more changes will be made to the ChunkStore and that its state at that point can be considered final.

This happens using the latest commit of the 'next' branch and must have been introduced during the last 3 weeks. The problem can be observed when running SigmoidPro, there is a lack of debug output normally printed by ~RemoteChunkStore().

Building with ArchLinux

for building with Arch Linux I had to change line 251 of cmake_modules/add_boost.cmake to:
find_library(Icui18nLib libicui18n.so)
find_library(IcuucLib libicuuc.so)
find_library(IcudataLib libicudata.so)
(i.e. replace .a with .so)

Size of lifestuff drive undecided

Migrated from maidsafe-archive/MaidSafe#60

The lifestuff drive reports a size of 1GB.

Can you make an interim release?

I read about the project and was disappointed that there are no binary builds available for installing a vault on Ubuntu. Is the network even online yet to connect to yet?