[sheepdog-users] SIGABRT when doing: dog vdi check

Hitoshi Mitake mitake.hitoshi at gmail.com
Tue Jan 7 02:57:29 CET 2014


At Mon, 06 Jan 2014 11:41:16 +0900,
Hitoshi Mitake wrote:
> 
> At Sat, 4 Jan 2014 13:28:27 +0800,
> Liu Yuan wrote:
> > 
> > On Fri, Jan 03, 2014 at 10:51:26PM +0100, Marcin Mirosław wrote:
> > > Hi!
> > > I'm new on "sheep-run";) I'm starting to try sheepdog so probably I'm
> > > doing many things wrongly.
> > > I'm playing with sheepdog-0.7.6.
> > > 
> > > First problem (SIGABRT):
> > > I started multi sheep daemeon on localhost:
> > > # for x in 0 1 2 3 4; do sheep -c local -j size=128M -p 700$x
> > > /mnt/sheep/metadata/$x,/mnt/sheep/storage/$x; done
> > > 
> > > Next:
> > > # dog cluster info
> > > Cluster status: Waiting for cluster to be formatted
> > > 
> > > # dog cluster format -c 2:1
> > 
> > 0.7.6 doesn't support erasure code. Try latest master branch
> 
> Current stable-0.7 doesn't treat copy policies like "2:1" as an
> error. It would be confusing for users. I'll write a patch only for
> stable-0.7 for treating these options as errors.
> 
> > 
> > > using backend plain store
> > > # dog cluster info
> > > Cluster status: running, auto-recovery enabled
> > > 
> > > Cluster created at Fri Jan  3 20:33:43 2014
> > > 
> > > Epoch Time           Version
> > > 2014-01-03 20:33:43      1 [127.0.0.1:7000, 127.0.0.1:7001,
> > > 127.0.0.1:7002, 127.0.0.1:7003, 127.0.0.1:7004]
> > > # dog vdi create testowy 5G
> > > # gdb -q dog
> > > Reading symbols from /usr/sbin/dog...Reading symbols from
> > > /usr/lib64/debug/usr/sbin/dog.debug...done.
> > > done.
> > > (gdb)  set args  vdi check testowy
> > > (gdb) run
> > > Starting program: /usr/sbin/dog vdi check testowy
> > > warning: Could not load shared library symbols for linux-vdso.so.1.
> > > Do you need "set solib-search-path" or "set sysroot"?
> > > warning: File "/lib64/libthread_db-1.0.so" auto-loading has been
> > > declined by your `auto-load safe-path' set to
> > > "$debugdir:$datadir/auto-load".
> > > To enable execution of this file add
> > >         add-auto-load-safe-path /lib64/libthread_db-1.0.so
> > > line to your configuration file "/root/.gdbinit".
> > > To completely disable this security protection add
> > >         set auto-load safe-path /
> > > line to your configuration file "/root/.gdbinit".
> > > For more information about this security protection see the
> > > "Auto-loading safe path" section in the GDB manual.  E.g., run from the
> > > shell:
> > >         info "(gdb)Auto-loading safe path"
> > > warning: Unable to find libthread_db matching inferior's thread library,
> > > thread debugging will not be available.
> > > PANIC: can't find next new idx
> > 
> > seems that 0.7.x series is cracky about it. Hitoshi, can you verify
> > this?
> 
> OK, I'll dig in the problem soon.

Hi Marcin,

I've fixed a serious bug which might produce the bug you've
suffered. The commit is this:
https://github.com/sheepdog/sheepdog/commit/b82632b47978315a50e9ba0bbad59f56453f63f5

The patch is already backported to stable-0.7. Could you try the
latest stable-0.7? You can obtain the source code by the below step:

git clone https://github.com/sheepdog/sheepdog.git
cd sheepdog
git checkout -b 0.7 origin/stable-0.7

But the problem might depend on timing heavily. So reproducing the
problem will be not so easy... If you have time, I'd like you to try
the latest change.

Thanks,
Hitoshi



More information about the sheepdog-users mailing list