* Error in `xfs_repair': double free or corruption
[not found] <trinity-16122364-b1e6-4dc9-9057-f2df3aa193bb-1445001446455@3capp-gmx-bs54>
@ 2015-10-16 13:18 ` Dragon
2015-10-16 13:26 ` Emmanuel Florac
0 siblings, 1 reply; 5+ messages in thread
From: Dragon @ 2015-10-16 13:18 UTC (permalink / raw)
To: xfs
[-- Attachment #1: Type: text/html, Size: 715 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Error in `xfs_repair': double free or corruption
2015-10-16 13:18 ` Dragon
@ 2015-10-16 13:26 ` Emmanuel Florac
0 siblings, 0 replies; 5+ messages in thread
From: Emmanuel Florac @ 2015-10-16 13:26 UTC (permalink / raw)
To: Dragon; +Cc: xfs
Le Fri, 16 Oct 2015 15:18:57 +0200
Dragon <Sunghost@gmx.de> écrivait:
> Hello,
> i have a problem after repaired a degraded Softare Raid6. System is
> Debian Jessi and Root and Boot are on Raid1, and Data on Raid6 on md2
> which miss one Disk. The mainproblem was a missing Disk because of
> badblocks which i cloned and exchanged agains a new one. After that i
> could successfully rebuild the raid (md2), while now only one disk is
> midding. But i recognised that xfs reports inode problems. Therefor i
> run xfs_repair on the raid device md2, but get message "Error in
> `xfs_repair': double free or corruption" What can i do the fix
> this? thx
You didn't provide enough information (kernel and xfs-progs version at
the very least) but you should use the latest version of xfs_repair, the
one included in Debian is probably quite old. Here's one new:
http://update.intellique.com/pub/xfs_repair-4.2.0.gz
Or if you like it better in debian form:
http://update.intellique.com/repository/pool/storiq3/unstable/amd64/xfsprogs_4.2.0+1_amd64.deb
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Error in `xfs_repair': double free or corruption
@ 2015-10-16 14:26 Dragon
2015-10-16 16:29 ` Eric Sandeen
0 siblings, 1 reply; 5+ messages in thread
From: Dragon @ 2015-10-16 14:26 UTC (permalink / raw)
To: xfs
Hello Emmanuel,
kernel version is 3.16-0.bpo.2-amd64 and xfsprogs in version 3.2.1 from stable. the question is if xfs_repair can repair a raid which has missed a disk with over 240gb bad blocks.
gretings
Hello,
i have a problem after repaired a degraded Softare Raid6. System is
Debian Jessi and Root and Boot are on Raid1, and Data on Raid6 on md2
which miss one Disk. The mainproblem was a missing Disk because of
badblocks which i cloned and exchanged agains a new one. After that i
could successfully rebuild the raid (md2), while now only one disk is
midding. But i recognised that xfs reports inode problems. Therefor i
run xfs_repair on the raid device md2, but get message "Error in
`xfs_repair': double free or corruption" What can i do the fix
this? thx
You didn't provide enough information (kernel and xfs-progs version at
the very least) but you should use the latest version of xfs_repair, the
one included in Debian is probably quite old. Here's one new:
http://update.intellique.com/pub/xfs_repair-4.2.0.gz
Or if you like it better in debian form:
http://update.intellique.com/repository/pool/storiq3/unstable/amd64/xfsprogs_4.2.0+1_amd64.deb
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Error in `xfs_repair': double free or corruption
2015-10-16 14:26 Error in `xfs_repair': double free or corruption Dragon
@ 2015-10-16 16:29 ` Eric Sandeen
0 siblings, 0 replies; 5+ messages in thread
From: Eric Sandeen @ 2015-10-16 16:29 UTC (permalink / raw)
To: xfs
On 10/16/15 9:26 AM, Dragon wrote:
> Hello Emmanuel,
>
> kernel version is 3.16-0.bpo.2-amd64 and xfsprogs in version 3.2.1
> from stable. the question is if xfs_repair can repair a raid which
> has missed a disk with over 240gb bad blocks.
Well, we shouldn't hit that "double free or corruption" bug. But you
have an old xfsprogs, so the suggestion of using something up to date
is a good one.
As for "can xfs_repair repair a raid which is missing a disk with 240g
of bad blocks?" -
xfs_repair cannot make something out of nothing; it should always end
up with a filesystem which has consistent metadata, but that might be
the result of throwing away a lot of un-fixable things.
All too often I see people try to use xfs_repair on a raid which is
in bad shape; not properly reassembled, etc, and that's only going to
make things worse. You must get your storage into the best shape you
can, first, and then xfs_repair will do its best to create consistency,
but it cannot recreate lost (meta)data, in general.
Running xfs_repair -n, or creating a metadump image, and running a full
repair on that as a test, is often a good idea before you commit to
changes on your original filesystem.
-Eric
> gretings
>
>
> Hello,
> i have a problem after repaired a degraded Softare Raid6. System is
> Debian Jessi and Root and Boot are on Raid1, and Data on Raid6 on md2
> which miss one Disk. The mainproblem was a missing Disk because of
> badblocks which i cloned and exchanged agains a new one. After that i
> could successfully rebuild the raid (md2), while now only one disk is
> midding. But i recognised that xfs reports inode problems. Therefor i
> run xfs_repair on the raid device md2, but get message "Error in
> `xfs_repair': double free or corruption" What can i do the fix
> this? thx
>
>
> You didn't provide enough information (kernel and xfs-progs version at
> the very least) but you should use the latest version of xfs_repair, the
> one included in Debian is probably quite old. Here's one new:
>
> http://update.intellique.com/pub/xfs_repair-4.2.0.gz
>
> Or if you like it better in debian form:
> http://update.intellique.com/repository/pool/storiq3/unstable/amd64/xfsprogs_4.2.0+1_amd64.deb
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Error in `xfs_repair': double free or corruption
@ 2015-10-19 11:16 Dragon
0 siblings, 0 replies; 5+ messages in thread
From: Dragon @ 2015-10-19 11:16 UTC (permalink / raw)
To: xfs
Hi Eric,
in meanwhile i upgraded my debian wheezy to stretch which has the latest xfsprogs 4.2 on bord. i had repaired the filesytem, but lost 10Gb of files. ok better than all.
so all is "fine" and i will now do next steps to get some data back.
thx
sunny
On 10/16/15 9:26 AM, Dragon wrote:
Hello Emmanuel,
kernel version is 3.16-0.bpo.2-amd64 and xfsprogs in version 3.2.1
from stable. the question is if xfs_repair can repair a raid which
has missed a disk with over 240gb bad blocks.
Well, we shouldn't hit that "double free or corruption" bug. But you
have an old xfsprogs, so the suggestion of using something up to date
is a good one.
As for "can xfs_repair repair a raid which is missing a disk with 240g
of bad blocks?" -
xfs_repair cannot make something out of nothing; it should always end
up with a filesystem which has consistent metadata, but that might be
the result of throwing away a lot of un-fixable things.
All too often I see people try to use xfs_repair on a raid which is
in bad shape; not properly reassembled, etc, and that's only going to
make things worse. You must get your storage into the best shape you
can, first, and then xfs_repair will do its best to create consistency,
but it cannot recreate lost (meta)data, in general.
Running xfs_repair -n, or creating a metadump image, and running a full
repair on that as a test, is often a good idea before you commit to
changes on your original filesystem.
-Eric
gretings
Hello,
i have a problem after repaired a degraded Softare Raid6. System is
Debian Jessi and Root and Boot are on Raid1, and Data on Raid6 on md2
which miss one Disk. The mainproblem was a missing Disk because of
badblocks which i cloned and exchanged agains a new one. After that i
could successfully rebuild the raid (md2), while now only one disk is
midding. But i recognised that xfs reports inode problems. Therefor i
run xfs_repair on the raid device md2, but get message "Error in
`xfs_repair': double free or corruption" What can i do the fix
this? thx
You didn't provide enough information (kernel and xfs-progs version at
the very least) but you should use the latest version of xfs_repair, the
one included in Debian is probably quite old. Here's one new:
http://update.intellique.com/pub/xfs_repair-4.2.0.gz
Or if you like it better in debian form:
http://update.intellique.com/repository/pool/storiq3/unstable/amd64/xfsprogs_4.2.0+1_amd64.deb
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-10-19 11:16 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-16 14:26 Error in `xfs_repair': double free or corruption Dragon
2015-10-16 16:29 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2015-10-19 11:16 Dragon
[not found] <trinity-16122364-b1e6-4dc9-9057-f2df3aa193bb-1445001446455@3capp-gmx-bs54>
2015-10-16 13:18 ` Dragon
2015-10-16 13:26 ` Emmanuel Florac
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox