arm64 devfs: /dev/diskid/*
John Kennedy
warlock at phouka.net
Fri Jul 27 23:20:53 UTC 2018
If you're following this thread, you know that I'm trying to get ZFS boot (but
have a UFS backup) RPI3B+ setup.
TL/DR: Initially had issues, mucked about, issues seemed to have stopped, why?
I can't say that I've seen that happen everywhere else, and I think I'd have
noticed since my swap space would have issues.
Looking at the web, it looks like I might get that under ZFS when it latches
onto the diskid. I "mucked" with it by booting into my UFS partition, mounting
the ZFS partition and put some previous kernels into the ZFS /boot. Maybe that
seeded it with the more current name? It was initially created hanging off
the system as an adapter-connected da0* but was then inserted back into the
SDCARD slot and should then be mmcsd0*.
* * * * *
Yesterday, a new version came out:
FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180726-r336739.img.xz
FreeBSD rpi3.phouka.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r336739: Thu Jul 26 18:05:26 UTC 2018 root at releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
When I boot into ZFS, My disk devices seem to have moved into /dev/diskid
[UFS gpart show]
=> 63 124735425 mmcsd0 MBR (59G)
63 8129 - free - (4.0M)
8192 98304 1 fat32lba [active] (48M)
106496 124624896 2 freebsd (59G)
124731392 4096 - free - (2.0M)
=> 0 124624896 mmcsd0s2 BSD (59G)
0 83886080 1 freebsd-zfs (40G)
83886080 25165824 2 freebsd-ufs (12G)
109051904 15572992 4 freebsd-swap (7.4G)
[ZFS gpart show]
=> 63 124735425 diskid/DISK-3C748841 MBR (59G)
63 8129 - free - (4.0M)
8192 98304 1 fat32lba [active] (48M)
106496 124624896 2 freebsd (59G)
124731392 4096 - free - (2.0M)
=> 0 124624896 diskid/DISK-3C748841s2 BSD (59G)
0 83886080 1 freebsd-zfs (40G)
83886080 25165824 2 freebsd-ufs (12G)
109051904 15572992 4 freebsd-swap (7.4G)
Booting UFS, I see my fstype-mapped names. Booting ZFS, I don't:
[ls -las /dev/msdosfs/* /dev/ufs/*]
0 crw-r----- 1 root operator 0x4f Jul 27 21:19 /dev/msdosfs/UBOOT
0 crw-r----- 1 root operator 0x56 Jul 27 13:06 /dev/ufs/uroot
Booting ZFS, /dev/mmcsd0* isn't populated, but /dev/diskid is:
[ls -las /dev/mmcsd0*]
0 crw-r----- 1 root operator 0x47 Jul 27 06:15 /dev/mmcsd0
[ls -las /dev/diskid]
total 1
1 dr-xr-xr-x 2 root wheel 512 Jul 27 06:15 .
1 dr-xr-xr-x 11 root wheel 512 Jul 27 06:15 ..
0 crw-r----- 1 root operator 0x4f Jul 27 06:15 DISK-3C748841
0 crw-r----- 1 root operator 0x54 Jul 27 06:15 DISK-3C748841s1
0 crw-r----- 1 root operator 0x55 Jul 27 06:15 DISK-3C748841s2
0 crw-r----- 1 root operator 0x58 Jul 27 06:15 DISK-3C748841s2a
0 crw-r----- 1 root operator 0x59 Jul 27 06:15 DISK-3C748841s2b
0 crw-r----- 1 root operator 0x5a Jul 27 06:15 DISK-3C748841s2d
Booting UFS, the SDCARD devices are where I've come to expect them:
[ls -las /dev/mmcsd0*]
0 crw-r----- 1 root operator 0x46 Jul 27 21:19 /dev/mmcsd0
0 crw-r----- 1 root operator 0x4c Jul 27 21:19 /dev/mmcsd0s1
0 crw-r----- 1 root operator 0x4d Jul 27 21:19 /dev/mmcsd0s2
0 crw-r----- 1 root operator 0x50 Jul 27 21:19 /dev/mmcsd0s2a
0 crw-r----- 1 root operator 0x51 Jul 27 21:19 /dev/mmcsd0s2b
0 crw-r----- 1 root operator 0x52 Jul 27 21:19 /dev/mmcsd0s2d
I tried to boot up into a previous kernel (from rpi3-20180719-r336479) once,
didn't get it right, but when I rebooted back with the normal kernel it worked.
I haven't messed with kern.geom.label.*:
[sysctl kern.geom.label]
kern.geom.label.disk_ident.enable: 1
kern.geom.label.gptid.enable: 1
kern.geom.label.gpt.enable: 1
kern.geom.label.ufs.enable: 1
kern.geom.label.ufsid.enable: 1
kern.geom.label.reiserfs.enable: 1
kern.geom.label.ntfs.enable: 1
kern.geom.label.msdosfs.enable: 1
kern.geom.label.iso9660.enable: 1
kern.geom.label.ext2fs.enable: 1
kern.geom.label.debug: 0
More information about the freebsd-fs
mailing list