This bug is believed to be fixed in cloud-utils in version 0.31. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-utils
Importance: Undecided
Status: New
** Changed in: cloud-utils
Status: New => Fix
I'm dropping the qemu-nbd. i'm not certain that there is actually
anything that was wrong there.
** No longer affects: qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741096
Title:
This bug was fixed in the package cloud-utils - 0.30-0ubuntu3
---
cloud-utils (0.30-0ubuntu3) bionic; urgency=medium
* sync to trunk at 322
- mount-image-callback: run blockdev and udevadm settle on nbd devices.
(LP: #1741096, #1741300)
- mount-image-callback: Drop
Only now saw your updates as I opened yesterday and didn't refresh since then.
With the workaround in cloud utils known consider it low for qmeu-nbd to find
more background details.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
** Branch linked: lp:cloud-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741096
Title:
test-mic can fail / writes to qemu-nbd device do not persist
To manage notifications about this bug go
Fetched cloud utils on a new (bionic) system.
Running go.sh just to see if I can trigger the case at all on my system.
I could and got to the
cat: data.txt: No such file or directory
I can confirm the IO errors, overall I see:
xtest-mic-0: start xtest-mic-0
[4998071.265687] EXT4-fs (loop0):
The fix that I've applied is to add the '2.5' to the list below.
1.) qemu-nbd --format=raw --connect $DEV $FILE
2.) wait until a 'pid' file appears in /sys/block/$BNAME/pid)
2.5) run 'blockdev --rereadpt' and 'udevadm settle'
3.) wait until $PART_PATH exists
4.) mount $PART_PATH to
** Branch linked: lp:~smoser/cloud-utils/trunk.1741096
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741096
Title:
test-mic can fail / writes to qemu-nbd device do not persist
To manage
that had some noise:
=== modified file 'bin/mount-image-callback'
--- bin/mount-image-callback2018-01-03 15:44:47 +
+++ bin/mount-image-callback2018-01-04 18:08:43 +
@@ -284,6 +284,10 @@
debug 1 "connected $img_in ($fmt) ${rwmode} to $nbd. waiting for
device."
this actually seems to fix the issue and I cannot recreate with it in place.
http://paste.ubuntu.com/26320756/
I suspect what this is showing is that we were operating on nbd devices that
existed from a previous run.
--
You received this bug notification because you are a member of Ubuntu
the recreate script demonstrates failure on xenial, artful and bionic in a VM.
xenial needs a change to mount-image-callback to run 'blockdev' on the nbd
device. i'm not actually sure how i've never seen that bug before.
with the change in place, all 3 can be made to show the issue. artful
and
** Attachment added: "recreate script v2 (support running on xenial)"
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1741096/+attachment/5031105/+files/test-1741096
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching a recreate script with loop included.
It should run correctly just about anywhere, with mount-image-callback
installed.
must be root.
to run with a different/modified mount-image-callback, just add it to your
PATH.
** Attachment added: "recreate script"
I considered the fact that maybe the partitioned image that test-mic was
creating was somehow invalid. To test that, I modifed mount-image-callback
to set the mount device in MOUNT_DEV, and then did:
cp "$pt1" /tmp/part1.img
cp "$pt2" /tmp/part2.img
mount-image-callback --read-only --part=1
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741096
Title:
test-mic can fail / writes to qemu-nbd device do not persist
To manage notifications about this bug go to:
http://paste.ubuntu.com/26315423/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741096
Title:
test-mic can fail / writes to qemu-nbd device do not persist
To manage notifications about this bug
heres another log of /var/log/syslog. http://paste.ubuntu.com/26315330/
I'm not certain if the order of entries in /varlog/syslog can be 100% trusted
or not.
If it can be, then we definitely see oddities.
* mount-image-callback definitly unmounts before running qemu-nbd --disconnect.
* the
I've played a bit. Attached patch here has logging done with logger in
an effort to serialize things.
Then, I have 'go.sh' (see below) that just loops over running test-mic until it
fails.
Then you get bookend messages in /var/log/syslog. I've collected a fail here.
** Patch added:
go.sh looks like
#!/bin/sh
[ "$(id -u)" = "0" ] || { echo "not root" 1>&2; exit 1; }
i=0
while true; do
logger --tag=xtest-mic-$i "start xtest-mic-$i"
echo -n .
{
read up idle out.log 2>&1
logger --tag=xtest-mic-$i "end xtest-mic-$i $r"
[ $r -eq 0 ] || { echo; echo "failed
run like
$ sudo PATH=$PWD/bin:$PATH ./go.sh
failed xtest-mic-3
smoser@milhouse:~/src/cloud-utils/trunk$ cat out.log
19536.67
cat: data.txt: No such file or directory
GPT:
== expected on 1 ==
partition 1
foo1
== found on 1 ==
partition 1
data.txt: cat failed rc=1
19543.86
1
** Attachment
20 matches
Mail list logo
