From: Patrik Lundquist <patrik.lundquist@gmail.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: Graham Cobb <g.btrfs@cobb.uk.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
calestyo@scientia.net
Subject: Re: "btrfs: harden agaist duplicate fsid" spams syslog
Date: Fri, 12 Jul 2019 15:35:50 +0200 [thread overview]
Message-ID: <CAA7pwKM_Le3FO8qprqn4busbTzWHeUTB+9h1zwBQ+KOjKqZuvw@mail.gmail.com> (raw)
In-Reply-To: <7766d592-525e-67fa-5db0-bcfff17fbf83@oracle.com>
On Fri, 12 Jul 2019 at 14:48, Anand Jain <anand.jain@oracle.com> wrote:
> I am unable to reproduce, I have tried with/without dm-crypt on both
> oraclelinux and opensuse (I am yet to try debian).
I'm using Debian testing 4.19.0-5-amd64 without problem. Raid1 with 5
LUKS disks. Mounting with the UUID but not(!) automounted.
Running "btrfs device scan --all-devices" doesn't trigger the fsid move.
$ sudo btrfs fi show /raid/
Label: 'btrfs_pool' uuid: 4242423a-990c-4650-b615-14fe009b0edd
Total devices 5 FS bytes used 7.85TiB
devid 1 size 7.28TiB used 5.85TiB path /dev/mapper/sdb1_crypt
devid 2 size 1.82TiB used 1.44TiB path /dev/mapper/sda1_crypt
devid 3 size 1.82TiB used 1.34TiB path /dev/mapper/sdc1_crypt
devid 4 size 5.46TiB used 4.98TiB path /dev/mapper/sdd1_crypt
devid 5 size 2.73TiB used 2.25TiB path /dev/mapper/sdf1_crypt
$ ll /dev/dm-*
brw-rw---- 1 root disk 254, 0 jul 9 15:08 /dev/dm-0
brw-rw---- 1 root disk 254, 1 jul 9 15:08 /dev/dm-1
brw-rw---- 1 root disk 254, 2 jul 9 15:08 /dev/dm-2
brw-rw---- 1 root disk 254, 3 jul 9 15:08 /dev/dm-3
brw-rw---- 1 root disk 254, 4 jul 9 15:08 /dev/dm-4
$ ll /dev/mapper/
total 0
drwxr-xr-x 2 root root 160 jul 9 15:08 ./
drwxr-xr-x 18 root root 3640 jul 10 08:16 ../
crw------- 1 root root 10, 236 jul 9 15:08 control
lrwxrwxrwx 1 root root 7 jul 9 15:08 sda1_crypt -> ../dm-0
lrwxrwxrwx 1 root root 7 jul 9 15:08 sdb1_crypt -> ../dm-1
lrwxrwxrwx 1 root root 7 jul 9 15:08 sdc1_crypt -> ../dm-2
lrwxrwxrwx 1 root root 7 jul 9 15:08 sdd1_crypt -> ../dm-3
lrwxrwxrwx 1 root root 7 jul 9 15:08 sdf1_crypt -> ../dm-4
next prev parent reply other threads:[~2019-07-12 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 18:49 "btrfs: harden agaist duplicate fsid" spams syslog Graham Cobb
2019-07-11 2:46 ` Anand Jain
2019-07-11 18:00 ` Graham Cobb
2019-07-12 12:46 ` Anand Jain
2019-07-12 13:32 ` Graham Cobb
2019-07-19 15:38 ` David Sterba
2019-07-12 13:35 ` Patrik Lundquist [this message]
2019-07-12 13:41 ` Graham Cobb
2019-07-11 23:06 ` Christoph Anton Mitterer
2019-07-12 12:49 ` Anand Jain
2019-07-16 13:59 ` [PATCH] btrfs: ratelimit device path change info on mounted device Anand Jain
2019-07-16 14:08 ` Anand Jain
2019-07-19 14:58 ` David Sterba
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=CAA7pwKM_Le3FO8qprqn4busbTzWHeUTB+9h1zwBQ+KOjKqZuvw@mail.gmail.com \
--to=patrik.lundquist@gmail.com \
--cc=anand.jain@oracle.com \
--cc=calestyo@scientia.net \
--cc=g.btrfs@cobb.uk.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).