Bug 249115
| Summary: | The zfs command in the installer fails to log a set command | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Dennis Clarke <dclarke> | ||||
| Component: | bin | Assignee: | freebsd-fs (Nobody) <fs> | ||||
| Status: | New --- | ||||||
| Severity: | Affects Only Me | CC: | swills | ||||
| Priority: | --- | ||||||
| Version: | CURRENT | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Created attachment 217753 [details]
image of the screen during install
image of the screen during install
Confirmed, I have reproduced this bug as well. (In reply to Steve Wills from comment #2) zfs-devel@ is effectively dead, please use fs@. I just checked with the latest ALPHA3 installer image for amd64 and the bug is still in place. It is strange that only the first command entered gets ignored and even returns an error to the console but the command succeeds. The change of a property to a ZFS filesystem works as expected but it is not logged in any way in the zpool history. Any command entered afterwards is logged. I used FreeBSD-13.0-ALPHA3-amd64-20210129-40cb0344eb2-256214-disc1.iso as the installer disk image. Testing with 13.0 RC3 and not able to reproduce ... yet. I did a test with 13 RELEASE installer iso images and the error still persists but it seems to only happen during installation. I see this bug in the installer stage with a snapshot of 15-CURRENT : root@triton:~ # uname -apKU FreeBSD triton 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-n268793-220ee18f1964: T hu Mar 14 02:58:39 UTC 2024 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/am d64.amd64/sys/GENERIC amd64 amd64 1500015 1500015 root@triton:~ # Strange that it only ever occurs during install. I may need to check the OpenZFS stuff on a Linux machine just to see what happens there. However I would rather yank out my teeth with pliers. May need to be done. Dennis |
During install of FreeBSD 13.0-CURRENT #0 c122cf32f2a-c252857 from the snapshots of 3 Sept 2020 I did select the option to open a shell at end of install. Therein I use to two following commands for the zpool foo : # zfs set checksum=sha512 foo # zfs set atime=on foo The first command works fine and does indeed set the checksum to sha512 on all datasets whereas the second command SEEMS to fail with an error message : cannot mount 'foo': Invalid argument property may be set but unable to remount filesystem Then we check with : zfs list -o name,used,avail,atime,setuid,exec,checksum,mountpoint where we see that indeed the atime property is set on everywhere and the zpool history fails to log this event. The zpool history does log the set checksum fine. This only is seen during install as tests after first boot seem fine. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken