Excellent; thanks for testing.
On Thu, Feb 8, 2018 at 7:05 AM, Dmitrii Shcherbakov < <email address hidden>> wrote:
> HWE (no patch applied) > https://paste.ubuntu.com/26537602/ > > * Below is a test on GA with bcache patch applied and bcache-export-cached > commented out (post-deployment kernel change + udev rule modification) > * Looks good based on the previous configuration - all symlinks are where > they should be https://paste.ubuntu.com/26534615/ > > 69-bcache-rules: > https://paste.ubuntu.com/26540975/ > > > # Ubuntu-4.4.0-113.136 with 3454b682755f9a800ba368334afa40dd9d821a88 > bcache uevent patch applied > > root@maas-xenial6:~# uname -a > Linux maas-xenial6 4.4.98-ueventbcache #1 SMP Thu Feb 8 10:59:26 MSK 2018 > x86_64 x86_64 x86_64 GNU/Linux > > root@maas-xenial6:~# tree /dev/bcache > /dev/bcache > ├── by-label > │ ├── bcache0 -> ../../bcache2 > │ ├── bcache2 -> ../../bcache3 > │ ├── bcache3 -> ../../bcache0 > │ ├── bcache4 -> ../../bcache1 > │ └── bcache5 -> ../../bcache4 > └── by-uuid > ├── 07d7270c-ed0e-4814-bbc6-affd8d4585a9 -> ../../bcache0 > ├── 2ad4aecf-cb7c-495f-946d-21b59377e0fe -> ../../bcache4 > ├── 5bd523eb-0256-4700-ae6e-2db5ce82eca0 -> ../../bcache1 > ├── dc1f2545-cb5d-4420-80eb-59eb8b83a8a7 -> ../../bcache2 > └── eaa6bc7f-8a9c-495a-9f8b-92132cc49c49 -> ../../bcache3 > > 2 directories, 10 files > root@maas-xenial6:~# lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 64G 0 disk > └─sda1 8:1 0 64G 0 part / > sdb 8:16 0 64G 0 disk > ├─bcache1 252:1 0 32.3G 0 disk > ├─bcache2 252:2 0 64G 0 disk > └─bcache3 252:3 0 32.3G 0 disk > sdc 8:32 0 64G 0 disk > └─bcache2 252:2 0 64G 0 disk > sdd 8:48 0 64G 0 disk > └─bcache4 252:4 0 64G 0 disk > sde 8:64 0 64G 0 disk > ├─sde1 8:65 0 31.7G 0 part > │ ├─bcache0 252:0 0 31.7G 0 disk > │ └─bcache4 252:4 0 64G 0 disk > └─sde2 8:66 0 32.3G 0 part > └─bcache3 252:3 0 32.3G 0 disk > sdf 8:80 0 64G 0 disk > ├─sdf1 8:81 0 31.7G 0 part > │ └─bcache0 252:0 0 31.7G 0 disk > └─sdf2 8:82 0 32.3G 0 part > └─bcache1 252:1 0 32.3G 0 disk > root@maas-xenial6:~# tree /dev/disk/by-dname/ > /dev/disk/by-dname/ > ├── bcache0 -> ../../bcache2 > ├── bcache2 -> ../../bcache3 > ├── bcache3 -> ../../bcache0 > ├── bcache4 -> ../../bcache1 > ├── bcache5 -> ../../bcache4 > ├── sda -> ../../sda > ├── sda-part1 -> ../../sda1 > ├── sde-part1 -> ../../sde1 > ├── sde-part2 -> ../../sde2 > ├── sdf-part1 -> ../../sdf1 > └── sdf-part2 -> ../../sdf2 > > 0 directories, 11 files > root@maas-xenial6:~# uname -a > Linux maas-xenial6 4.4.98-ueventbcache #1 SMP Thu Feb 8 10:59:26 MSK 2018 > x86_64 x86_64 x86_64 GNU/Linux > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1728742 > > Title: > curtin dname for bcache uses unstable devname instead of UUID > > To manage notifications about this bug go to: > https://bugs.launchpad.net/bcache-tools/+bug/1728742/+subscriptions >
Excellent; thanks for testing.
On Thu, Feb 8, 2018 at 7:05 AM, Dmitrii Shcherbakov <
<email address hidden>> wrote:
> HWE (no patch applied) /paste. ubuntu. com/26537602/ export- cached /paste. ubuntu. com/26534615/ /paste. ubuntu. com/26540975/ 4.4.0-113. 136 with 3454b682755f9a8 00ba368334afa40 dd9d821a88 xenial6: ~# uname -a xenial6: ~# tree /dev/bcache ed0e-4814- bbc6-affd8d4585 a9 -> ../../bcache0 cb7c-495f- 946d-21b59377e0 fe -> ../../bcache4 0256-4700- ae6e-2db5ce82ec a0 -> ../../bcache1 cb5d-4420- 80eb-59eb8b83a8 a7 -> ../../bcache2 8a9c-495a- 9f8b-92132cc49c 49 -> ../../bcache3 xenial6: ~# lsblk xenial6: ~# tree /dev/disk/by-dname/ xenial6: ~# uname -a /bugs.launchpad .net/bugs/ 1728742 /bugs.launchpad .net/bcache- tools/+ bug/1728742/ +subscriptions
> https:/
>
> * Below is a test on GA with bcache patch applied and bcache-
> commented out (post-deployment kernel change + udev rule modification)
> * Looks good based on the previous configuration - all symlinks are where
> they should be https:/
>
> 69-bcache-rules:
> https:/
>
>
> # Ubuntu-
> bcache uevent patch applied
>
> root@maas-
> Linux maas-xenial6 4.4.98-ueventbcache #1 SMP Thu Feb 8 10:59:26 MSK 2018
> x86_64 x86_64 x86_64 GNU/Linux
>
> root@maas-
> /dev/bcache
> ├── by-label
> │ ├── bcache0 -> ../../bcache2
> │ ├── bcache2 -> ../../bcache3
> │ ├── bcache3 -> ../../bcache0
> │ ├── bcache4 -> ../../bcache1
> │ └── bcache5 -> ../../bcache4
> └── by-uuid
> ├── 07d7270c-
> ├── 2ad4aecf-
> ├── 5bd523eb-
> ├── dc1f2545-
> └── eaa6bc7f-
>
> 2 directories, 10 files
> root@maas-
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 64G 0 disk
> └─sda1 8:1 0 64G 0 part /
> sdb 8:16 0 64G 0 disk
> ├─bcache1 252:1 0 32.3G 0 disk
> ├─bcache2 252:2 0 64G 0 disk
> └─bcache3 252:3 0 32.3G 0 disk
> sdc 8:32 0 64G 0 disk
> └─bcache2 252:2 0 64G 0 disk
> sdd 8:48 0 64G 0 disk
> └─bcache4 252:4 0 64G 0 disk
> sde 8:64 0 64G 0 disk
> ├─sde1 8:65 0 31.7G 0 part
> │ ├─bcache0 252:0 0 31.7G 0 disk
> │ └─bcache4 252:4 0 64G 0 disk
> └─sde2 8:66 0 32.3G 0 part
> └─bcache3 252:3 0 32.3G 0 disk
> sdf 8:80 0 64G 0 disk
> ├─sdf1 8:81 0 31.7G 0 part
> │ └─bcache0 252:0 0 31.7G 0 disk
> └─sdf2 8:82 0 32.3G 0 part
> └─bcache1 252:1 0 32.3G 0 disk
> root@maas-
> /dev/disk/by-dname/
> ├── bcache0 -> ../../bcache2
> ├── bcache2 -> ../../bcache3
> ├── bcache3 -> ../../bcache0
> ├── bcache4 -> ../../bcache1
> ├── bcache5 -> ../../bcache4
> ├── sda -> ../../sda
> ├── sda-part1 -> ../../sda1
> ├── sde-part1 -> ../../sde1
> ├── sde-part2 -> ../../sde2
> ├── sdf-part1 -> ../../sdf1
> └── sdf-part2 -> ../../sdf2
>
> 0 directories, 11 files
> root@maas-
> Linux maas-xenial6 4.4.98-ueventbcache #1 SMP Thu Feb 8 10:59:26 MSK 2018
> x86_64 x86_64 x86_64 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> curtin dname for bcache uses unstable devname instead of UUID
>
> To manage notifications about this bug go to:
> https:/
>