Bug 279732

Summary:	AWS/EC2 /dev/aws/disk/ebs/ devices not created after 14.1-STABLE stable/14-n267826-1e3dfe0c343c
Product:	Base System	Reporter:	Matthew Frost <matthewf-freebsdbugs>
Component:	misc	Assignee:	freebsd-virtualization (Nobody) <virtualization>
Status:	New ---
Severity:	Affects Only Me	CC:	cperciva, emaste, imp
Priority:	---
Version:	14.1-STABLE
Hardware:	arm64
OS:	Any

Description Matthew Frost 2024-06-14 10:18:18 UTC

/dev/aws/disk/ebs/ devices are not being created at some point after stable/14-n267826-1e3dfe0c343c

I am using (in eu-west-2) resolve:ssm:/aws/service/freebsd/arm64/base/zfs/14.1/STABLE

t4g.small instances

After 14.1-STABLE stable/14-n267826-1e3dfe0c343c (ami-0121539594d23cf66)

the next AMI was:

14.1-STABLE stable/14-n267883-e77813f7e4a3 (ami-06ddde50374d78dc4)

n267826 AMI - works fine:

[root@freebsdbox /dev/aws/disk/ebs]# ls -ltr
total 1
lrwxr-xr-x  1 root wheel 9 Jun 14 09:23 vol-007cdf77c590a4d7b -> /dev/nda0 

n267883 AMI - these links are no longer created

Comment 1 Mark Linimon freebsd_committer

2024-06-14 10:48:03 UTC

*** Bug 279733 has been marked as a duplicate of this bug. ***

Comment 2 Mark Linimon freebsd_committer

2024-06-14 10:48:28 UTC

*** Bug 279734 has been marked as a duplicate of this bug. ***

Comment 3 Mark Linimon freebsd_committer

2024-06-14 10:54:24 UTC

^Triage: Cc: committer of D45347 even though this does not seem cause-and-effect to me.

Comment 4 Warner Losh freebsd_committer

2024-06-28 18:29:15 UTC

I don't see any geom changes between these two snapshots. There's a devd change for autofs, but that wouldn't affect this.

I think cperciva needs to take a look and see why here, since it's non-obvious to me.

Comment 5 Colin Percival freebsd_committer

2024-06-28 18:37:18 UTC

It's a devd thing.  I install a devd conf file which triggers when the nvd/nda devices show up and creates the necessary symlinks.  It's on my list of things to dig more into.