linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Thorsten Glaser <tg@mirbsd.de>
Cc: Josef Bacik <jbacik@fusionio.com>, Joe Perches <joe@perches.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Debian GNU/Linux m68k <debian-68k@lists.debian.org>,
	<linux-btrfs@vger.kernel.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: btrfs zero divide
Date: Tue, 30 Jul 2013 16:40:01 -0400	[thread overview]
Message-ID: <20130730204001.GG24583@localhost.localdomain> (raw)
In-Reply-To: <Pine.BSM.4.64L.1307301741360.20305@herc.mirbsd.org>

On Tue, Jul 30, 2013 at 07:02:29PM +0000, Thorsten Glaser wrote:
> Josef Bacik dixit:
> 
> >Can you gdb btrfs.ko and do
> >
> >list *(__btrfs_map_block+0x11c)
> 
> Not easily (the kernel image is from a .deb package),
> and even in a compile tree gdb just says:
> No symbol table is loaded.  Use the "file" command.
> 
> With a bit of cheating and a cross-compiler, this is:
> 
> (gdb) list *0x0000106e
> 0x106e is in __btrfs_map_block (/var/lib/gforge/chroot/home/users/tg/Xl/linux-3.10.1/fs/btrfs/volumes.c:4447).
> 4442            stripe_nr = offset;
> 4443            /*
> 4444             * stripe_nr counts the total number of stripes we have to stride
> 4445             * to get to this block
> 4446             */
> 4447            do_div(stripe_nr, stripe_len);
> 4448
> 4449            stripe_offset = stripe_nr * stripe_len;
> 4450            BUG_ON(offset < stripe_offset);
> 4451
> 

So stripe_len shouldn't be 0, if it is you have bigger problems :).  Is this a
corrupt fs or something?  If there was some sort of corruption that occured then
I suppose stripe_len could be 0 and we'd need to catch that somewhere higher up
the stack and error out.  Is there a way you could check and see if that's the
case?  Thanks,

Josef

  reply	other threads:[~2013-07-30 20:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.BSM.4.64L.1307300820160.20675@herc.mirbsd.org>
2013-07-30  9:07 ` btrfs zero divide (was: Re: Linux 3.10 problem reports (yes, plural)) Geert Uytterhoeven
2013-07-30 15:40   ` btrfs zero divide Thorsten Glaser
2013-07-30 17:13   ` btrfs zero divide (was: Re: Linux 3.10 problem reports (yes, plural)) Josef Bacik
2013-07-30 17:36     ` Joe Perches
2013-07-30 19:02     ` btrfs zero divide Thorsten Glaser
2013-07-30 20:40       ` Josef Bacik [this message]
2013-07-30 21:05         ` Joe Perches
2013-07-30 21:25           ` Thorsten Glaser
2013-08-08 20:01           ` Thorsten Glaser
2013-08-09 12:26         ` Andreas Schwab
2013-08-09 12:30           ` Andreas Schwab
2013-08-09 14:35             ` Josef Bacik
2013-08-13 12:12             ` Geert Uytterhoeven
2013-08-09 18:04           ` Zach Brown
2013-08-13 16:32             ` Geert Uytterhoeven
2013-08-14  8:40               ` Geert Uytterhoeven
2013-08-14  8:56                 ` Geert Uytterhoeven
2013-08-14 18:07                   ` Joe Perches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130730204001.GG24583@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=debian-68k@lists.debian.org \
    --cc=geert@linux-m68k.org \
    --cc=joe@perches.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tg@mirbsd.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).