Bug 1058111
Summary: | Kernel panic at power down when rootfs on NBD device | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dag <den.mail> | |
Component: | nbd | Assignee: | Christopher Meng <i> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 20 | CC: | enslaver, gansalmon, harald, i, itamar, johannbg, jonathan, kernel-maint, lnykryn, madhu.chinakonda, msekleta, plautrba, systemd-maint, vpavlin, wtogami, xjakub, zbyszek | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | i686 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1098499 (view as bug list) | Environment: | ||
Last Closed: | 2014-05-16 15:14:34 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1098499 |
Description
Dag
2014-01-27 03:18:06 UTC
The kernel paniced because init died. The init process is responsible for shutdown order, so perhaps the systemd guys have a suggestion here. The kernel paniced because init died. The init process is responsible for shutdown order, so perhaps the systemd guys have a suggestion here. Well, i nbd wants to survive the final killing spree then it needs to be run from the initrd and mark itself appropriately. http://www.freedesktop.org/wiki/Software/systemd/RootStorageDaemons/ Otherwise it will be killed, and thus the root fs goes away, and thus the init process might crash, which causes the kernel to panic. REassigning to nbd. I will backport a fix later or in Thursday maybe. nbd-3.7-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/nbd-3.7-2.fc20 Sorry for the belated update, I'm celebrating Chinese New Year recently. Please see -m option and manpages of -m option after this update, and test if it still crashes then leave a karma in bodhi. Or tell me directly here if you don't have any Fedora account. Thanks! Package nbd-3.7-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nbd-3.7-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2024/nbd-3.7-2.fc20 then log in and leave karma (feedback). Hi, I updated to nbd-3.7-2.fc20 from the Fedora 20 testing repository. Then I updated kernel to 3.12.10-300-fc20.i686+PAE. Then rebooted on the new kernel/iniramfs. I then made a "dracut --force -vv" to be sure to have updated nbd-client in initramfs. I then rebooted on the new initramfs : I still get the very same error on shutdown (poweroff/reboot). So this update didn't fix the issue : nbd-client gets killed seemingly too early when shuting down resulting in kernel pannic. Regards, Daggett nbd-client is started in the dracut-initqueue.service from a shell script in the initramfs. So a dracut patch is needed to add the "-m" option to the nbd-client call. You can also mirror the behavior of mdmon. 301 if (in_initrd()) { 302 /* 303 * set first char of argv[0] to @. This is used by 304 * systemd to signal that the task was launched from 305 * initrd/initramfs and should be preserved during shutdown 306 */ 307 argv[0][0] = '@'; 308 } 309 ... 1945 int in_initrd(void) 1946 { 1947 /* This is based on similar function in systemd. */ 1948 struct statfs s; 1949 return statfs("/", &s) >= 0 && 1950 ((unsigned long)s.f_type == TMPFS_MAGIC || 1951 (unsigned long)s.f_type == RAMFS_MAGIC); 1952 } nbd-3.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/nbd-3.8-1.fc20 nbd-3.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. Hi, I updated the system with the new nbd package (nbd-3.8-1.fc20). Then I updated kernel to 3.13.8.200.fc20.i686+PAE. Then I rebooted on new kernel/initramfs. Then I made a "dracut --force -vv" to be sure to have updated nbd-client in initramfs. I then rebooted on the new initramfs : I still get the very same error on shutdown (poweroff/reboot). So this update didn't fix the issue : nbd-client gets killed seemingly too early when shuting down resulting in kernel panic. As Harald Hoyer said : dracut may need an update. I made a new bug report as I believe it is NOT a nbd issue anymore : https://bugzilla.redhat.com/show_bug.cgi?id=1084763 May be this bug report could be closed as "fixed" for nbd ? or reassigned to systemd ? or reassigned to dracut ? regards, Dag this problem was solved by Harald Hoyer in git.kernel.org. see https://bugzilla.redhat.com/show_bug.cgi?id=1098499 Thanks Harald ! Dag |