Project

General

Profile

Actions

Bug #3325

closed

Revert sys/vfs/hammer2: Properly set rdonly flag for PFS

Added by davshao over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
09/10/2022
Due date:
% Done:

0%

Estimated time:

Description

After
sys/vfs/hammer2: Properly set rdonly flag for PFS
commit 5f5122fa2471887600e87e29917d577f65d73a05
Date: Wed Sep 7 00:11:28 2022 -0700

the system boots but there are read(only) errors reported with ttys not created, dhcp not working, etc.
Bisected to this particular commit.

Maybe unusual these days, I am using grub2 to boot from an ssd (not nvme) formatted mbr.

Here is the /etc/fstab:

  1. Device Mountpoint FStype Options Dump Pass#
    /dev/serno/2017E29D5A8C.s1a /boot ufs rw 2 2
    /dev/serno/2017E29D5A8C.s1b none swap sw 0 0
    /dev/serno/2017E29D5A8C.s1d / hammer2 rw 1 1
    /build/usr.obj /usr/obj null rw 0 0
    /build/var.crash /var/crash null rw 0 0
    /build/var.cache /var/cache null rw 0 0
    /build/var.spool /var/spool null rw 0 0
    /build/var.log /var/log null rw 0 0
    /build/var.tmp /var/tmp null rw 0 0
    tmpfs /tmp tmpfs rw 0 0
    proc /proc procfs rw 0 0

$ uname -a
DragonFly xxxxxx 6.3-DEVELOPMENT DragonFly v6.3.0.196.g64e301-DEVELOPMENT #0: Sat Sep 10 10:28:47 PDT 2022 xxxxxx@xxxxxx:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64

Actions #1

Updated by arcade@b1t.name over 1 year ago

I'll second this. UEFI+CRYPTO boot, it's possible to mount FS directly, but upgrading mount from RO to RW leaves FS in RO state, though it's actually reported as RW.

Actions #2

Updated by arcade@b1t.name over 1 year ago

Was reverted. All fine.

Actions #3

Updated by tkusumi over 1 year ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF