All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schultz <aschultz@warp10.net>
To: linux-ext4@vger.kernel.org
Cc: Andreas Dilger <adilger@sun.com>
Subject: Re: "tune2fs -I 256" runtime---can it be interrupted safely?
Date: Fri, 14 Nov 2008 13:49:32 +0100	[thread overview]
Message-ID: <200811141349.39160.aschultz@warp10.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

Hi,

[...]

> Unfortunately, ltrace doesn't show what is calling this code, so
> a stack trace is needed from GDB.

Got the same problem, here is a GDB backtrace done on Ubuntu Intrepid, e2fsprogs 1.41.3:

(gdb) bt
#0  0x00007fa619228bcc in ext2fs_new_block (fs=0x1fea860, goal=263012, map=0x1feaa30, ret=0x7fff21668cac) at /build/buildd/e2fsprogs-1.41.3/lib/ext2fs/alloc.c:166
#1  0x000000000040408d in resize_inode (fs=0x1fea860, new_size=<value optimized out>) at /build/buildd/e2fsprogs-1.41.3/misc/tune2fs.c:1020
#2  0x0000000000404d83 in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/e2fsprogs-1.41.3/misc/tune2fs.c:1638

Cheers
Andreas

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-11-14 13:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 12:49 Andreas Schultz [this message]
2008-11-14 21:06 ` "tune2fs -I 256" runtime---can it be interrupted safely? Andreas Dilger
2008-11-15  5:50   ` Theodore Tso
2008-11-16 12:11     ` Andreas Schultz
  -- strict thread matches above, loose matches on Subject: below --
2008-11-01 19:10 Michael B. Trausch
2008-11-01 23:46 ` Michael B. Trausch
2008-11-07 21:16   ` Andreas Dilger
2008-11-11 16:09     ` Michael B. Trausch
2008-11-14  8:30       ` Andreas Dilger

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=200811141349.39160.aschultz@warp10.net \
    --to=aschultz@warp10.net \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.