Comment 14 for bug 1741096

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): mounted filesystem with ordered data mode. Opts: (null)
[4998071.372544] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[4998071.485091] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[4998071.593007] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[4998071.716770] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[4998072.500496] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[4998074.532148] EXT4-fs (nbd1p1): mounted filesystem with ordered data mode. Opts: (null)
[4998074.549530] print_req_error: I/O error, dev nbd0, sector 0
[4998074.607975] print_req_error: I/O error, dev nbd0, sector 0
[4998074.633572] Buffer I/O error on dev nbd0, logical block 0, async page read
[4998074.841685] print_req_error: I/O error, dev nbd0, sector 0
[4998074.867993] Buffer I/O error on dev nbd0, logical block 0, async page read
[4998074.907662] block nbd10: shutting down sockets
[4998074.909787] Buffer I/O error on dev nbd10p2, logical block 90113, lost sync page write
[4998074.909796] JBD2: Error -5 detected when updating journal superblock for nbd10p2-8.
[4998074.941009] EXT4-fs (nbd1p2): write access will be enabled during recovery
[4998075.276217] block nbd1: NBD_DISCONNECT
[4998075.276643] nbd1: detected capacity change from 0 to 316669952
[4998075.276796] Dev nbd1: unable to read RDB block 0

I think I need to break down the test to the most simple form that triggers it and check then.