Project

General

Profile

Actions

Bug #3092

closed

dumpon: sysctl: kern.dumpdev: Device busy

Added by liweitianux over 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Userland
Target version:
-
Start date:
10/23/2017
Due date:
% Done:

100%

Estimated time:

Description

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) dfly.dumpon.devicebusy.png liweitianux, 10/23/2017 02:42 AM
Actions #1

Updated by swildner over 6 years ago

I think once set, you first have to 'dumpon off' before being able to set it again.

Actions #2

Updated by liweitianux over 6 years ago

swildner wrote:

I think once set, you first have to 'dumpon off' before being able to set it again.

True. Once I "dumpon off", I can "dumpon" another device to make the change. Thanks.

However, the current error message is unhelpful, which should be improved... And the dumpon(8) man page needs a note, something like:

Once the dump device is set, it must be first turned off using "dumpon off" before the new dump device can be set.

Maybe a new option can be added to take care of this. In addition, the "dumpon off" seems a bit wired... I think a symlink as "dumpoff" may be a good choice.

Cheers,
Aly

Actions #3

Updated by liweitianux over 5 years ago

  • 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.

Actions

Also available in: Atom PDF