From: NeilBrown <neilb@suse.de>
To: Ben Bucksch <linux.news@bucksch.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: md RAID5: Disk wrongly marked "spare", need to force re-add it
Date: Mon, 22 Apr 2013 07:50:26 +1000 [thread overview]
Message-ID: <20130422075026.04b63081@notabene.brown> (raw)
In-Reply-To: <5171F52D.4040701@bucksch.org>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Sat, 20 Apr 2013 03:53:49 +0200 Ben Bucksch <linux.news@bucksch.org> wrote:
> Ben Bucksch wrote, On 20.04.2013 03:26:
> > I can read my files again, without problem, all is happy.
>
> Actually, no. XFS filesystem structure is not sane. I must have done
> something wrong. (If possible, please let me know what, all data should
> be posted.)
>
> At first, it looked OK, as if only one recently written directory was
> broken. I unmounted one of the FS, did xfs_repair, and after
> re-mounting, almost all directories are gone. Almost 100% dataloss. I
> can't describe how upset I am against md.
So data was accessible before "xfs_repair", is not accessible after
'xfs_repair', yet you blame md rather than xfs_repair? Interesting.
You've clearly had a bad experience - I'm sorry about that.
I doubt there is anything you can do to unrepair whatever xfs_repair did, but
the place to ask would be on the xfs list.
NeilBrown
>
> Oh, and in case you're wondering about my backup: That's gone, too, due
> to bugs in btrfs that trashed the FS and also stopped the dedicated
> backup machine from booting automatically, so I don't have any current
> backup either.
>
> Ben
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-04-21 21:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 20:08 md RAID5: Disk wrongly marked "spare", need to force re-add it Ben Bucksch
2013-04-13 14:19 ` Roy Sigurd Karlsbakk
2013-04-14 22:40 ` Oliver Schinagl
2013-04-15 1:34 ` Ben Bucksch
2013-04-14 17:30 ` Oliver Schinagl
2013-04-15 10:26 ` Ben Bucksch
2013-04-14 18:16 ` Oliver Schinagl
2013-04-18 13:17 ` Ben Bucksch
2013-04-18 13:58 ` Maarten
2013-04-19 22:56 ` linux.news
2013-04-20 1:26 ` Ben Bucksch
2013-04-20 1:53 ` Ben Bucksch
2013-04-21 7:23 ` Brad Campbell
2013-04-21 8:20 ` Ben Bucksch
2013-04-21 10:45 ` Brad Campbell
2013-04-21 18:17 ` Phil Turmel
2013-04-21 22:00 ` Ben Bucksch
2013-04-21 11:07 ` Roy Sigurd Karlsbakk
2013-04-21 21:50 ` NeilBrown [this message]
2013-04-21 21:46 ` NeilBrown
2013-04-18 14:18 ` Roy Sigurd Karlsbakk
2013-04-18 14:38 ` Robin Hill
2013-04-20 13:44 ` Oliver Schinagl
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=20130422075026.04b63081@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=linux.news@bucksch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox