A bit more about the dd-is-bad-topic:
IMHO it doesn't matter at all.
a) For this specific problem here, fixing a security problem automatically
fixes the risk of data corruption because careless cloning+mounting
(without UUID adjustments) too.
So, if the user likes to use dd with its
Hey.
I'd have an additional question about subvols O:-)
Given the following setup:
5
|
+--root (subvol, /)
+-- mnt (dir)
with the following done:
- init 1
- remount,ro / (i.e. the subvol root)
- mount /dev/btrfs-device /mnt (i.e. mount the top subvol at /mnt)
The following happened:
- /
Am 10.12.2015 13:41, schrieb Hugo Mills:
On Thu, Dec 10, 2015 at 07:08:51AM -0500, Austin S Hemmelgarn wrote:
On 2015-12-09 16:48, S.J. wrote:
1. better practices, we really need to tell users, and documentation
writers, that using dd (or variant) to copy Btrfs volumes has a
consequence
1. better practices, we really need to tell users, and documentation
writers, that using dd (or variant) to copy Btrfs volumes has a
consequence and should not be used to make copies.
2. Btrfs needs a better way to make a copy of a volume when there are
snapshots (including even rw snapshots);
Hello
As we know, two file systems with the same UUID (like reported by eg. "blkid")
are problematic, especially if both are mounted at the same time it leads to
data corruption. So, copying a BTRFS partition with eg. dd to another and use
it immediately is bad. To prevent this, "btrfstune -u
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
