sector-fuse: Zero filesize

Help
skirrow
2012-01-12
2012-10-08
  • skirrow
    skirrow
    2012-01-12

    I have setup Sector/Sphere across two servers using 'sector-fuse' to mount the
    file system.

    When I copy a file to the fused directory it indicates it is saved, but the
    filesize is displayed as 0 bytes using both 'ls' on the fused file system and
    when using 'sector_ls', and the file contents are not accessible via the file
    system or using 'sector_download'. Looking at the actual data store the file
    is saved correctly - it reports the correct filesize and the contents appear
    correct.

    If I upload a file using 'sector_upload' it is saved correctly and the
    filesize is reported correctly using both 'sector_ls' and 'ls'. I'm also able
    to access the file via the file system and using 'sector_download'.

    Is anyone able to offer any suggestions why 'sector-fuse' is not functioning
    correctly when files are uploaded through the file system?

    Many thanks for your help!

    • Neil
     
  • Sergey Cherepanov
    Sergey Cherepanov
    2012-01-13

    What version of sector yu are using - release, from trunk, or from stable
    branch?

     
  • skirrow
    skirrow
    2012-01-13

    Sector version 2.6 build 04/05/2011 - stable version I believe... Running on
    CentOS 5.7.

    Thank you for your help!

    • Neil
     
  • skirrow
    skirrow
    2012-01-16

    I have found that shutting down and restarting the master/slave causes the
    files to be indexed correctly - the 0 byte files then show the correct
    filesizes through 'ls' and 'sector_ls'. I am able to open a test text file
    using 'nano' but when I save the file it is not updated when re-opened, but
    the file in the data store is updated correctly.

    I also found the master log shows the following:

    Rejected Req from system 0 X.X.X.X 48906 15605 -2000
    

    What causes the -2000/E_SECURITY 'security check failed' error?

    Please let me know if I can provide any further information to assist with
    debugging!

    • Neil
     
  • skirrow
    skirrow
    2012-01-17

    This issue has now been resolved!

    The issue occurred because the users/groups were not setup correctly.
    'sector_fuse' should not be run as root, and the user must be assigned to the
    'fuse' group as is outlined in the documentation.

    • Neil