From: Alexander Fieroch <alexander.fieroch@mpi-dortmund.mpg.de>
To: <1i5t5.duncan@cox.net>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: unable to fixup (regular) error
Date: Tue, 27 Nov 2018 09:28:51 +0100 [thread overview]
Message-ID: <1a5bfda2-ffe7-00a3-579b-a92e2e33e1f5@mpi-dortmund.mpg.de> (raw)
In-Reply-To: <pan$f1f1$ae87783$50df180$b6b94f2a@cox.net>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
Actually the data on raid0 is not my data but of my users and they knew
and accepted the risk for raid0. So in my case it should be ok - I don't
know the importance of the data files which are affected. I just wanted
to help finding a possible bug and experiment with a broken btrfs
filesystem before I recreate it.
For my own files I'd prefer raid5 or raid6...
But thanks Duncan for your explanation! Of course there are people out
there who do not know the difference between different raid levels and
should be warned!
Best regards,
Alexander
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5184 bytes --]
next prev parent reply other threads:[~2018-11-27 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 7:19 unable to fixup (regular) error Alexander Fieroch
2018-11-26 8:13 ` Qu Wenruo
2018-11-26 10:23 ` Alexander Fieroch
2018-11-27 7:18 ` Duncan
2018-11-27 8:28 ` Alexander Fieroch [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 22:17 Cameron Berkenpas
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=1a5bfda2-ffe7-00a3-579b-a92e2e33e1f5@mpi-dortmund.mpg.de \
--to=alexander.fieroch@mpi-dortmund.mpg.de \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).