[Bug 201003] forcibly unmounting a filesystem with running binaries results in panic

Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 20 Feb 2023 11:45:58 UTC

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201003

--- Comment #3 from Fernando Apesteguía <fernape@FreeBSD.org> ---
(In reply to Edward Tomasz Napierala from comment #2)
Sorry I didn't clarify, I did.

root@hammer:/usr/home/fernape# whoami
root
root@hammer:/usr/home/fernape# mdconfig -s1g
md0
root@hammer:/usr/home/fernape# newfs /dev/md0 
/dev/md0: 1024.0MB (2097152 sectors) block size 32768, fragment size 4096
        using 4 cylinder groups of 256.03MB, 8193 blks, 32896 inodes.
super-block backups (for fsck_ffs -b #) at:
 192, 524544, 1048896, 1573248
root@hammer:/usr/home/fernape# mount /dev/md 
root@hammer:/usr/home/fernape# cp test/loop /mnt/
root@hammer:/usr/home/fernape# /mnt/loop 
loop: mlockall: Cannot allocate memory
root@hammer:/usr/home/fernape# whoami 
root
root@hammer:/usr/home/fernape# uname -a
FreeBSD hammer 14.0-CURRENT FreeBSD 14.0-CURRENT #9 main-n260951-fe01817876a0:
Wed Feb 15 18:45:38 CET 2023    
root@hammer:/usr/obj/usr/home/fernape/FreeBSD-repos/src/amd64.amd64/sys/GENERIC
amd64

-- 
You are receiving this mail because:
You are the assignee for the bug.