public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* xfs_db -c frag -r /dev/sdb1 segmentation fault
@ 2010-10-01 20:06 Robert Pipca
  2010-10-02 10:39 ` Dave Chinner
  0 siblings, 1 reply; 4+ messages in thread
From: Robert Pipca @ 2010-10-01 20:06 UTC (permalink / raw)
  To: xfs, Robert Pipca

Hi,

I'm using kernel 2.6.34.7 on a gentoo amd64 system.

Towards the end of the command, I get:

read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 352256, SEEK_SET)              = 352256
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 376832, SEEK_SET)              = 376832
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 393216, SEEK_SET)              = 393216
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 417792, SEEK_SET)              = 417792
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 434176, SEEK_SET)              = 434176
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 450560, SEEK_SET)              = 450560
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 475136, SEEK_SET)              = 475136
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 491520, SEEK_SET)              = 491520
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 516096, SEEK_SET)              = 516096
read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
16384) = 16384
lseek(4, 14190936064, SEEK_SET)         = 14190936064
read(4, "BMAP\0\0\0\n\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
lseek(4, 532480, SEEK_SET)              = 532480
read(4, "IN\201\240\2\3\0\0\0\0\377\376\0\0\377\376\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\21L"...,
16384) = 16384
lseek(4, 37129601024, SEEK_SET)         = 37129601024
read(4, "BMAP\0\0\0\n\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
lseek(4, 37028130816, SEEK_SET)         = 37028130816
read(4, "BMAP\0\0\0\n\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\0\0\0\0\0\0\0\0\0"...,
4096) = 4096
lseek(4, 36522024960, SEEK_SET)         = 36522024960
read(4, "\177\260g\203\223s\231\364\273\222\276\34\363~\253\355\271\271\17h\237\v\357\274\230\25\334\351x\2719&\34"...,
4096) = 4096
brk(0x26af000)                          = 0x26af000
brk(0x26a0000)                          = 0x26a0000
mmap(NULL, 200704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x7ff07237e000
brk(0x2690000)                          = 0x2690000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++


Is this a kernel or a XFS problem?

Cheers,

- Robert

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xfs_db -c frag -r /dev/sdb1 segmentation fault
  2010-10-01 20:06 xfs_db -c frag -r /dev/sdb1 segmentation fault Robert Pipca
@ 2010-10-02 10:39 ` Dave Chinner
  2010-10-03  6:45   ` Christoph Hellwig
  0 siblings, 1 reply; 4+ messages in thread
From: Dave Chinner @ 2010-10-02 10:39 UTC (permalink / raw)
  To: Robert Pipca; +Cc: xfs

On Fri, Oct 01, 2010 at 05:06:08PM -0300, Robert Pipca wrote:
> Hi,
> 
> I'm using kernel 2.6.34.7 on a gentoo amd64 system.
> 
> Towards the end of the command, I get:
> 
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 352256, SEEK_SET)              = 352256
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 376832, SEEK_SET)              = 376832
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 393216, SEEK_SET)              = 393216
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 417792, SEEK_SET)              = 417792
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 434176, SEEK_SET)              = 434176
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 450560, SEEK_SET)              = 450560
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 475136, SEEK_SET)              = 475136
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 491520, SEEK_SET)              = 491520
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 516096, SEEK_SET)              = 516096
> read(4, "INA\350\2\1\0\0\0\0\377\376\0\0\377\376\0\0\0\2\0\0\0\0\0\0\0\0\0\0\0\1L"...,
> 16384) = 16384
> lseek(4, 14190936064, SEEK_SET)         = 14190936064
> read(4, "BMAP\0\0\0\n\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\0\0\0\0\0\0\0\0\0"...,
> 4096) = 4096
> lseek(4, 532480, SEEK_SET)              = 532480
> read(4, "IN\201\240\2\3\0\0\0\0\377\376\0\0\377\376\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\21L"...,
> 16384) = 16384
> lseek(4, 37129601024, SEEK_SET)         = 37129601024
> read(4, "BMAP\0\0\0\n\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\0\0\0\0\0\0\0\0\0"...,
> 4096) = 4096
> lseek(4, 37028130816, SEEK_SET)         = 37028130816
> read(4, "BMAP\0\0\0\n\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\0\0\0\0\0\0\0\0\0"...,
> 4096) = 4096
> lseek(4, 36522024960, SEEK_SET)         = 36522024960
> read(4, "\177\260g\203\223s\231\364\273\222\276\34\363~\253\355\271\271\17h\237\v\357\274\230\25\334\351x\2719&\34"...,
> 4096) = 4096
> brk(0x26af000)                          = 0x26af000
> brk(0x26a0000)                          = 0x26a0000
> mmap(NULL, 200704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0) = 0x7ff07237e000
> brk(0x2690000)                          = 0x2690000
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> 
> 
> Is this a kernel or a XFS problem?

It's an xfs_db problem. what version are you running (xfs_db -V)?
Can you build a non-stripped xfs_db executable and run it under gdb
so we can get a stack trace and location of where the SEGV is
occurring?

Note that the crash could be caused by a corrupted filesystem.
Running xfs_repair -n over the filesystem will tell you if there are
any problems in the filesystem. If there are, can you post the
output of the repair command as well?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xfs_db -c frag -r /dev/sdb1 segmentation fault
  2010-10-02 10:39 ` Dave Chinner
@ 2010-10-03  6:45   ` Christoph Hellwig
  2010-10-04 19:43     ` Robert Pipca
  0 siblings, 1 reply; 4+ messages in thread
From: Christoph Hellwig @ 2010-10-03  6:45 UTC (permalink / raw)
  To: Dave Chinner; +Cc: Robert Pipca, xfs

On Sat, Oct 02, 2010 at 08:39:03PM +1000, Dave Chinner wrote:
> Note that the crash could be caused by a corrupted filesystem.

Or running it on a mounted filesystem.  Robert, did you run the command
on a mounted or unmounted filesystem?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: xfs_db -c frag -r /dev/sdb1 segmentation fault
  2010-10-03  6:45   ` Christoph Hellwig
@ 2010-10-04 19:43     ` Robert Pipca
  0 siblings, 0 replies; 4+ messages in thread
From: Robert Pipca @ 2010-10-04 19:43 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: xfs

Hi,

I ran it on a mounted filesystem.

It's a squid webcache machine, and I ran it on the HD that's doing the
cache, to see how fragmented it is....

This thing is: After I ran xfs_fsr on the same partition, xfs_db
started working again (even though both times I used "-r").

Should this have happened?

Cheers,

- Robert

2010/10/3 Christoph Hellwig <hch@infradead.org>:
> On Sat, Oct 02, 2010 at 08:39:03PM +1000, Dave Chinner wrote:
>> Note that the crash could be caused by a corrupted filesystem.
>
> Or running it on a mounted filesystem.  Robert, did you run the command
> on a mounted or unmounted filesystem?
>
>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-10-04 19:42 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-01 20:06 xfs_db -c frag -r /dev/sdb1 segmentation fault Robert Pipca
2010-10-02 10:39 ` Dave Chinner
2010-10-03  6:45   ` Christoph Hellwig
2010-10-04 19:43     ` Robert Pipca

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox