From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Cc: debian-user@lists.debian.org
Subject: xfs_db -c frag -r /dev/hda1 - Segmentation fault
Date: Sun, 23 Oct 2005 07:39:34 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0510230736490.30489@p34> (raw)
In-Reply-To: <4080C826.F4C53CD@dmministries.org>
p34:~# xfs_db -c frag -r /dev/hda1
Segmentation fault
p34:~# xfs_db -c frag -r /dev/hde1
Segmentation fault
p34:~# xfs_db -c frag -r /dev/hdk1
Segmentation fault
p34:~#
Debian Etch, 2.6.13.4, stopped working a while ago, either before newer
debian packages or a newer kernel, does anyone who uses Debian+XFS have
this problem as well?
Towards the end of the strace:
munmap(0xb7fb6000, 4096) = 0
open("/proc/meminfo", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7fb6000
read(3, "MemTotal: 1035452 kB\nMemFre"..., 1024) = 598
close(3) = 0
munmap(0xb7fb6000, 4096) = 0
rt_sigaction(SIGINT, {0x80628f4, [], 0}, NULL, 8) = 0
_llseek(4, 512, [512], SEEK_SET) = 0
read(4, "XAGF\0\0\0\1\0\0\0\0\0:pn\0\0\0\1\0\0\0\2\0\0\0\0\0\0\0"..., 512)
= 512
_llseek(4, 1024, [1024], SEEK_SET) = 0
read(4, "XAGI\0\0\0\1\0\0\0\0\0:pn\0\0\3@\0\0\0\3\0\0\0\1\0\0\000"...,
512) = 512
_llseek(4, 12288, [12288], SEEK_SET) = 0
read(4, "IABT\0\0\0\r\377\377\377\377\377\377\377\377\0\0\0\200"..., 4096)
= 4096
_llseek(4, 32768, [32768], SEEK_SET) = 0
read(4, "INA\355\1\1\0\3\0\0\0\0\0\0\0\0\0\0\0\3\0\0\0\0\0\0\0\0"...,
16384) = 16384
mmap2(NULL, 268443648, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xa7df7000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
p34:~#
Is this a kernel, XFS or Debian problem?
Thanks!
Justin.
next parent reply other threads:[~2005-10-23 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4080C826.F4C53CD@dmministries.org>
2005-10-23 11:39 ` Justin Piszcz [this message]
2005-10-23 22:54 ` Nathan Scott
2005-10-23 23:40 ` Justin Piszcz
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=Pine.LNX.4.64.0510230736490.30489@p34 \
--to=jpiszcz@lucidpixels.com \
--cc=debian-user@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®