Menu

nothing happens on sync after loading state

Help
Vortex
2015-05-06
2015-05-07
  • Vortex

    Vortex - 2015-05-06

    after a lot of working around on my 2 data disk. deleting and adding stuff, Im trying to sync the array. but nothing seems to happen after the disk have been scanned.
    This is what happens:

    *@ubuntuserver:~$ sudo snapraid sync
    [sudo] password for
    :
    Self test...
    Loading state from /var/snapraid.content...
    Scanning disk d1...
    Scanning disk d2...
    ***@ubuntuserver:~$ sudo snapraid sync -v
    Self test...
    Loading state from /var/snapraid.content...
    41883 files
    0 hardlinks
    0 symlinks
    513 empty dirs
    Scanning disk d1...
    Excluding content '/mnt/disk1/content1/snapraid.content'
    Scanning disk d2...
    Excluding content '/mnt/disk2/content2/snapraid.content'

    Then the process stops and returns to command input line.

    I then tried to run the status command, and got this.

    *@ubuntuserver:~$ sudo snapraid status
    [sudo] password for
    *:
    Self test...
    Loading state from /var/snapraid.content...
    Using 763 MiB of memory.
    SnapRAID status report:

    Files Fragmented Excess Wasted Used Free Use Name
    Files Fragments GB GB GB
    6445 295 3328 -93.9 2888 0 100% d1
    35438 76 149 - 1910 0 100% d2


    41883 371 3477 0.0 4798 0 100%

    WARNING! Free space info will be valid after the first sync.

    WARNING! The array is NOT fully synced.
    You have a sync in progress at 45%.
    No rehash is in progress or needed.
    No error detected.

    here it seems like I have an unfinished sync, so I let it run over night to finish up. but after running the status again this morning it still says 45%, so it seems to be stuck or crashed in some way.

    I Just updated from v6.4 to v8.0 can this affect my ability to sync in any way?
    If more info is needed just say so.
    hope someone can help.

     
  • xad

    xad - 2015-05-06

    Unless someone with experience is responding you would need to provide a more detailed log of the activities right before it exit (then there is a chance to be able to trace the activities in the source code).

    /X

     
  • Leifi Plomeros

    Leifi Plomeros - 2015-05-06

    How much available RAM do you have?

     
  • Vortex

    Vortex - 2015-05-07

    I just tried running a scan with the log option activated, and the proccess start scanning through all the new files, but while doing that, the log suddenly comes to an end while scanning disk 1, the last filename is unfinished.

    the server has 1 gig of RAM available, and only a couple of percentage (6-7%) is used while scanning.

    I just ran the sync command directly from the machine instead of putty. this is what I got:

    from the log:

    version:8.0
    unixtime:1430987661
    time:2015-05-07 10:34:21
    command:sync
    argv:0:snapraid
    argv:1:-l
    argv:2:synclog.log
    argv:3:sync
    selftest:
    msg:progress: Self test...
    conf:/etc/snapraid.conf
    blocksize:262144
    disk:d1:/mnt/disk1/
    disk:d2:/mnt/disk2/
    mode:par1
    parity:/mnt/diskp/snapraid.parity
    filter:exclude **
    content:/var/snapraid.content
    msg:progress: Loading state from /var/snapraid.content...
    msg:verbose: 41883 files
    msg:verbose: 0 hardlinks
    msg:verbose: 0 symlinks
    msg:verbose: 513 empty dirs
    msg:progress: Scanning disk d1...
    lots of files
    msg:progress: Scanning disk d2...

    then the log stops
    but in the terminal I get this:

    [ 3626.492062] out of memory: kill process 4565 (snapraid) score 538 or sacrifice child
    [ 3626.492858] killed process 4565 (snapraid) total-wm:1148600, anon-rss:563280kB, files-rss:4kB

    so it turns out it was the ram, but I do find it strange as I have synced plenty of times before without any problems and in the system overview it never goes beyond 20% of used memory.

     

    Last edit: Vortex 2015-05-07

Log in to post a comment.

MongoDB Logo MongoDB