[sheepdog] [sheepdog-users] [ANNOUNCE] sheepdog stable release v0.7.3-rc0

[Gerald Richter - ECOS]

There seems to be a segfault in an empty cluster, when doing dog cluster info. It goes away as soon as I add a vdi (see gdb output below).

In addition I had some old test data from a sheepdog 0.6 install, so when have done the dog cluster format it asks me to delete this data and I answered with yes. Afterwards I got a crash of sheep, when I run a dog node recovery.

I cleaned up all my data, cache and journal directories and restarted and reformatted everything. While the segfault with dog cluster info persists, the crash on the node recovery has gone away.

Regards Gerald


#dog cluster format
#gdb --args dog cluster info
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/src/packages/sheepdog-0.7.3-rc0/dog/dog...done.
(gdb) r
Starting program: /usr/src/packages/sheepdog-0.7.3-rc0/dog/dog cluster info
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7fff000
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff7836700 (LWP 108027)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7836700 (LWP 108027)]
0x00007ffff78baf9b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff78baf9b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x0000000000413ccf in alloc_bitmap (new_bits=131072, old_bits=<optimized out>, old_bmap=<optimized out>) at ../include/bitops.h:46
#2  worker_routine (arg=0x11c8170) at work.c:264
#3  0x00007ffff7bc7b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007ffff7911a7d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x0000000000000000 in ?? ()


> -----Ursprüngliche Nachricht-----
> Von: sheepdog-users-bounces at lists.wpkg.org [mailto:sheepdog-users-
> bounces at lists.wpkg.org] Im Auftrag von Hitoshi Mitake
> Gesendet: Freitag, 6. September 2013 16:59
> An: sheepdog-users at lists.wpkg.org; sheepdog at lists.wpkg.org
> Betreff: [sheepdog-users] [ANNOUNCE] sheepdog stable release v0.7.3-rc0
> 
> Hi sheepdog users and developers,
> 
> I released v0.7.3-rc0 of stable branch. You can download a source archive
> from these URLs:
> tar.gz: https://github.com/sheepdog/sheepdog/archive/v0.7.3-rc0.tar.gz
> zip: https://github.com/sheepdog/sheepdog/archive/v0.7.3-rc0.zip
> 
> The most important updates of this release are:
>  - some bugfixes for vdi deletion process
>  - prevent losing vdi information at cluster initialization sequence
>  - remove possibility of segfault in main event loop
> 
> If no one complains about this release in 2 days, it will be v0.7.3 officialy.
> 
> Below is the summary of commits this release contains.
> 
> Hitoshi Mitake (5):
>       tests/functional: let check clean directories of passed tests in default
>       tests/functional: unmount loopback devices before cleaning directories
>       sheep: make the vid deletion proceduer correct order
>       sheep: initialize vdi bitmap after completion of reading inode object
>       sheep: set bit in vdi_inuse in atomic manner
> 
> MORITA Kazutaka (3):
>       sheep: don't remove vdi object from object list cache
>       sheep: wait until there is no get_vdis work in wait_get_vdis_done()
>       event: refresh event info after unregistering
> 
> Robin Dong (1):
>       fix error-io in sheepfs when using ext4 filesystem
> 
> 
> Thanks,
> Hitoshi
> --
> sheepdog-users mailing lists
> sheepdog-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/sheepdog-users