From: Chris Murphy <lists@colorremedies.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: "Niccolò Belli" <darkbasic@linuxsystems.it>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: My system mounts the wrong btrfs partition, from the wrong disk!
Date: Fri, 25 Nov 2016 16:56:28 -0700 [thread overview]
Message-ID: <CAJCQCtQNpoYHkjYtiW6kd+CF0ic-qZWFRC1RHnSavj3ntUcFxg@mail.gmail.com> (raw)
In-Reply-To: <20161125161712.1df4f7b6@natsu>
On Fri, Nov 25, 2016 at 4:17 AM, Roman Mamedov <rm@romanrm.net> wrote:
> On Fri, 25 Nov 2016 12:05:57 +0100
> Niccolò Belli <darkbasic@linuxsystems.it> wrote:
>
>> This is something pretty unbelievable, so I had to repeat it several times
>> before finding the courage to actually post it to the mailing list :)
>>
>> After dozens of data loss I don't trust my btrfs partition that much, so I
>> make a backup copy with dd weekly.
>
> https://btrfs.wiki.kernel.org/index.php/Gotchas#Block-level_copies_of_devices
>
> "don't make copies with dd."
Yeah.
In the user's defense, it's way overdue for the kernel to refuse to
mount without some override flag like XFS does. This behavior is just
plain user hostile right now, and Btrfs gets an extra ding because
it's supposed to be better: easier to admin and have better data
integrity. Basically this is Btrfs eating at least one, possibly both,
file systems at the same time without warning, and it's not good
enough to warn in the wiki.
--
Chris Murphy
next prev parent reply other threads:[~2016-11-25 23:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 11:05 My system mounts the wrong btrfs partition, from the wrong disk! Niccolò Belli
2016-11-25 11:17 ` Roman Mamedov
2016-11-25 23:56 ` Chris Murphy [this message]
2016-11-26 13:24 ` Goffredo Baroncelli
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=CAJCQCtQNpoYHkjYtiW6kd+CF0ic-qZWFRC1RHnSavj3ntUcFxg@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=darkbasic@linuxsystems.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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).