New nbd-client hangs when connecting a second time to a server
Bug #711951 reported by
Stéphane Graber
This bug report is a duplicate of:
Bug #700165: qemu-nbd kthread becomes defunct on disconnect.
Edit
Remove
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
High
|
Andy Whitcroft | ||
nbd (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
At boot time LTSP connects using NBD to get its root device.
Then, the login prompt is shown, it checks for a new version of its root device by opening a second connection and checking the first few bytes. That part is now broken in Natty, possibly since the latest nbd update (2.9.16).
nbd-client now hangs in I/O wait (D status) indefinitely and so blocking the login prompt from appearing.
Changed in nbd (Ubuntu): | |
importance: | Undecided → High |
Changed in linux (Ubuntu): | |
status: | Incomplete → In Progress |
assignee: | nobody → Andy Whitcroft (apw) |
Changed in nbd (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
@Jonathan -- as you can see that ndb-client hangs I assume you have shell access when its broken. If so can you strace the ndb-client to see what it was trying to do when it gets stuck? What its last system call is. Also is anything emmitted into dmesg related to the hang; please wait long enough for the 120 second 'its stuck' timer to fire and report issues.
As this is hanging with the client in a D there may be a kernel componet here. I have had a look and little has changed since Maverick (where I am assuming it worked). There has been some locking work for BKL removal which may be related, difficult to say.