All of lore.kernel.org
 help / color / mirror / Atom feed
From: Velimir Galic <veli.galic@gmail.com>
To: xfs@oss.sgi.com
Subject: xfs_repair - segemnation fault | git error
Date: Fri, 10 Aug 2012 10:23:03 +0200	[thread overview]
Message-ID: <CADcDJaR52zwL+aMaUuQTvbYx2d11LRmzdURE2Ok8z0tKsYTv8A@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1410 bytes --]

hi Guys,

I hope you are able to help me, because i think that i
tried everything that i know off to repair my raid after a disk failure.

Systemspecs:

   - HP N40L
      - CPU: AMD Turion II @ 1,5GHZ
      - 8GB ECC RAM
      - Disks:
         - 250GB | OS
         - 4x2GB | RAID 5 | Softraid
      - OS: Openmediavault @ 3.0.20 (last version)


Problem:

In my raid a disk was fault so mdadm kicked the disk out of the raid. I put
a replacement in the box and started a resync of the raid and than
is happened, a second disk got lost in the raid. The raidsync wasn't
finished and now i'm fighting 3 weeks or more i don't no any more :-( to
repair the file system.

I tried a lot of different versions of xfs_repair (2.9.4, 2.9.8, 2.10.2,
3.0.4, 3.1.2, 3.1.6, 3.1,8), but every precompiled version got an
"segmentation fault" or hung at phase 3 with 100% cpu load for few day. I
also tried different distros like ubuntu, debian, redhat, gentoo (yes, i'm
a little bit desperate :-) )  Than i tried the git version and at first it
looked good but than i got an another error but i don't understand what the
problem is.

tried options without any luck: xfs_repair -v -P | xfs_repair -v -P -m 6144
| xfs_repair -v -P -L

Metadump of the filesystem isn't possible at this moment, but i could
bootup a live cd and give it a try with it. I'm pretty stuck and don't no
what to do any more.


with kind regards
Veli

[-- Attachment #1.2: Type: text/html, Size: 1789 bytes --]

[-- Attachment #2: md127.metadump.err --]
[-- Type: application/octet-stream, Size: 3536 bytes --]

root@hpbox:~# xfs_metadump /dev/md127 /media/localhdd/md127.metadump
*** glibc detected *** xfs_db: double free or corruption (!prev): 0x0000000001ccb000 ***
======= Backtrace: =========
/lib/libc.so.6(+0x71bd6)[0x7f5e34b55bd6]
/lib/libc.so.6(cfree+0x6c)[0x7f5e34b5a94c]
xfs_db[0x41a8e3]
xfs_db[0x41c3ec]
xfs_db[0x41e2bc]
xfs_db[0x41c152]
xfs_db[0x41dfd4]
xfs_db[0x41c152]
xfs_db[0x41eedb]
xfs_db[0x418d08]
/lib/libc.so.6(__libc_start_main+0xfd)[0x7f5e34b02c8d]
xfs_db[0x4027d9]
======= Memory map: ========
00400000-00475000 r-xp 00000000 08:41 2338                               /usr/sbin/xfs_db
00675000-00676000 rw-p 00075000 08:41 2338                               /usr/sbin/xfs_db
00676000-00689000 rw-p 00000000 00:00 0 
01c83000-01f1d000 rw-p 00000000 00:00 0                                  [heap]
7f5e30000000-7f5e30021000 rw-p 00000000 00:00 0 
7f5e30021000-7f5e34000000 ---p 00000000 00:00 0 
7f5e348c7000-7f5e348dd000 r-xp 00000000 08:41 21105                      /lib/libgcc_s.so.1
7f5e348dd000-7f5e34adc000 ---p 00016000 08:41 21105                      /lib/libgcc_s.so.1
7f5e34adc000-7f5e34add000 rw-p 00015000 08:41 21105                      /lib/libgcc_s.so.1
7f5e34ae4000-7f5e34c3d000 r-xp 00000000 08:41 3222                       /lib/libc-2.11.3.so
7f5e34c3d000-7f5e34e3c000 ---p 00159000 08:41 3222                       /lib/libc-2.11.3.so
7f5e34e3c000-7f5e34e40000 r--p 00158000 08:41 3222                       /lib/libc-2.11.3.so
7f5e34e40000-7f5e34e41000 rw-p 0015c000 08:41 3222                       /lib/libc-2.11.3.so
7f5e34e41000-7f5e34e46000 rw-p 00000000 00:00 0 
7f5e34e46000-7f5e34e5d000 r-xp 00000000 08:41 3217                       /lib/libpthread-2.11.3.so
7f5e34e5d000-7f5e3505c000 ---p 00017000 08:41 3217                       /lib/libpthread-2.11.3.so
7f5e3505c000-7f5e3505d000 r--p 00016000 08:41 3217                       /lib/libpthread-2.11.3.so
7f5e3505d000-7f5e3505e000 rw-p 00017000 08:41 3217                       /lib/libpthread-2.11.3.so
7f5e3505e000-7f5e35062000 rw-p 00000000 00:00 0 
7f5e35062000-7f5e35069000 r-xp 00000000 08:41 3219                       /lib/librt-2.11.3.so
7f5e35069000-7f5e35268000 ---p 00007000 08:41 3219                       /lib/librt-2.11.3.so
7f5e35268000-7f5e35269000 r--p 00006000 08:41 3219                       /lib/librt-2.11.3.so
7f5e35269000-7f5e3526a000 rw-p 00007000 08:41 3219                       /lib/librt-2.11.3.so
7f5e3526a000-7f5e3526e000 r-xp 00000000 08:41 21195                      /lib/libuuid.so.1.3.0
7f5e3526e000-7f5e3546d000 ---p 00004000 08:41 21195                      /lib/libuuid.so.1.3.0
7f5e3546d000-7f5e3546e000 rw-p 00003000 08:41 21195                      /lib/libuuid.so.1.3.0
7f5e3546e000-7f5e3548c000 r-xp 00000000 08:41 3218                       /lib/ld-2.11.3.so
7f5e354c7000-7f5e35509000 rw-p 00000000 00:00 0 
7f5e35509000-7f5e3567e000 r--p 00000000 08:41 2104                       /usr/lib/locale/locale-archive
7f5e3567e000-7f5e35682000 rw-p 00000000 00:00 0 
7f5e35689000-7f5e3568b000 rw-p 00000000 00:00 0 
7f5e3568b000-7f5e3568c000 r--p 0001d000 08:41 3218                       /lib/ld-2.11.3.so
7f5e3568c000-7f5e3568d000 rw-p 0001e000 08:41 3218                       /lib/ld-2.11.3.so
7f5e3568d000-7f5e3568e000 rw-p 00000000 00:00 0 
7fff33b52000-7fff33b73000 rw-p 00000000 00:00 0                          [stack]
7fff33bff000-7fff33c00000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Aborted

[-- Attachment #3: Type: text/plain, Size: 121 bytes --]

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

             reply	other threads:[~2012-08-10  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  8:23 Velimir Galic [this message]
2012-08-10 22:53 ` xfs_repair - segemnation fault | git error Dave Chinner
2012-08-11 10:57 ` Michael Monnerie
2012-08-13 11:58   ` Velimir Galic

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=CADcDJaR52zwL+aMaUuQTvbYx2d11LRmzdURE2Ok8z0tKsYTv8A@mail.gmail.com \
    --to=veli.galic@gmail.com \
    --cc=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 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.