Bug 13063
| Summary: | Devicemapper fails to load/initialise, root filesystem can not be accessed | ||
|---|---|---|---|
| Product: | IO/Storage | Reporter: | Heinz Diehl (htd) |
| Component: | Block Layer | Assignee: | Jens Axboe (axboe) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | high | CC: | lenb, rjw |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.30-rc1|-git | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 13070 | ||
| Attachments: |
Ingo Molnar's reversion
Screencopy |
||
Created attachment 20937 [details]
Screencopy
*** Bug 13044 has been marked as a duplicate of this bug. *** commit d6de2c80e9d758d2e36c21699117db6178c0f517 "async: Fix module loading async-work regression" is now in Linus' tree (before 2.6.30-rc1-git7) and should fix this. please re-open if it does not. Yes, that fixed it. Thanks! |
Created attachment 20936 [details] Ingo Molnar's reversion Hi, I have a machine which has a LUKS/dmcrypt encrypted root fs. Booting a 2.6.30-rc/git kernel (and also 2.6.29-git15), the root fs can not be mounted any longer, and the system boots into /bin/sh. The cause seems to be that the device-mapper can not be initialised before the root fs is going to be mounted at bootup, caused by the async boot process. I don't know... This happens both on openSuSE and Fedora laptops too, which have an encrypted root fs, my wife has one. The solution is to revert "9710794: async: remove the temporary (2.6.29) "async is off by default" I've attached the reversion, posted by Ingo Molnar som days ago, which was the fix for a bug which is unrelated to this one, and also a screencopy. Unfortunately, without any root fs available, I can't provide more information. If 9710794 goes into mainline, it breaks all systems which have encrypted root fs. Regards, Heinz.