[DragonFlyBSD - Bug #3092] (Resolved) dumpon: sysctl: kern.dumpdev: Device busy
bugtracker-admin at leaf.dragonflybsd.org
bugtracker-admin at leaf.dragonflybsd.org
Sat Sep 22 21:41:16 PDT 2018
Issue #3092 has been updated by liweitianux.
Category changed from Kernel to Userland
Status changed from New to Resolved
% Done changed from 0 to 100
This bug has been fixed in commits:
03f2fdd26fee309abfe7c8bdf799f8d35a4e18bf
and
bfbb599bba9fbf988628bb6dd678cd03d68dfda5.
----------------------------------------
Bug #3092: dumpon: sysctl: kern.dumpdev: Device busy
http://bugs.dragonflybsd.org/issues/3092#change-13470
* Author: liweitianux
* Status: Resolved
* Priority: Normal
* Assignee:
* Category: Userland
* Target version:
----------------------------------------
Hello, I had the problem that "dumpon" couldn't let me change the dump device, which complained "Device busy", as shown below:
dfly# dumpon /dev/serno/WD-WCAS25235448.s1b
dumpon: sysctl: kern.dumpdev: Device busy
(I previously wrongly configured the "dumpdev" to be "/dev/mapper/swap", which is the mapped name of the dm-crypt'ed swap device. Therefore I used "dumpon" to change the dump device the underlying swap device but failed, as shown here.)
In addition, I also did such a test within a virtual machine using DFly-5.0. After partitioned the swap partition, I can "dumpon" to it successfully at the first time, but later it fails with "Device busy" error. See also the attached screenshot.
I suspect this issue exists in the "setdumpdev()" function in "sys/kern/kern_shutdown.c".
Cheers,
Aly
---Files--------------------------------
dfly.dumpon.devicebusy.png (10.3 KB)
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
More information about the Bugs
mailing list