https://bugzilla.suse.com/show_bug.cgi?id=1169774
https://bugzilla.suse.com/show_bug.cgi?id=1169774#c35
Fabian Vogt
Fabian, are you sure this is the same problem? I mean was this consistently failing like this for past 6 months when the change was introduced? AFAIU you're speaking about the 'failed' builds on 'sheep' and 'goat' hosts, aren't you? 'lamb', 'cloud', and 'build' hosts seem to work fine.
The osc jobhist only goes back until beginning of october. In that timeframe, it's been consistently slow/failing i586 goat/sheep builds. I did some tests using different filesystems inside the VM using "Buildflags: vmfstype:foo" in the prjconf. Using btrfs made no difference (compared to ext4). XFS appears to work much better. So the issue apparently impacts ext4 and btrfs the most. Kiwi is still using ext4 for the filesystem on the livecd though, so I could only compare the time until the final rsync. XFS on sheep81, 23s for kernel-firmware: [ 94s] [ DEBUG ]: 16:02:24 | system: ( 47/1065) Installing: kbd-legacy-2.3.0-1.1.noarch [............done] [ 94s] [ DEBUG ]: 16:02:24 | system: Additional rpm output: [ 94s] [ DEBUG ]: 16:02:24 | system: warning: /var/cache/kiwi/packages/f796d7d2bc4daf38063ff386ebbc072d/kbd-legacy.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY [ 117s] [ DEBUG ]: 16:02:47 | system: ( 48/1065) Installing: kernel-firmware-20201023-1.1.noarch [.......................done] [ 117s] [ INFO ]: Processing: [# ] 2%[ DEBUG ]: 16:02:47 | system: Additional rpm output: [ 117s] [ DEBUG ]: 16:02:47 | system: warning: /var/cache/kiwi/packages/f796d7d2bc4daf38063ff386ebbc072d/kernel-firmware.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY btrfs on sheep82, 141s for kernel-firmware: [ 108s] [ DEBUG ]: 16:27:22 | system: ( 47/1065) Installing: kbd-legacy-2.3.0-1.1.noarch [............done] [ 108s] [ DEBUG ]: 16:27:22 | system: Additional rpm output: [ 108s] [ DEBUG ]: 16:27:22 | system: warning: /var/cache/kiwi/packages/f796d7d2bc4daf38063ff386ebbc072d/kbd-legacy.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY [ 249s] [ DEBUG ]: 16:29:43 | system: ( 48/1065) Installing: kernel-firmware-20201023-1.1.noarch [...................................................................done] [ 249s] [ INFO ]: Processing: [# ] 2%[ DEBUG ]: 16:29:43 | system: Additional rpm output: [ 249s] [ DEBUG ]: 16:29:43 | system: warning: /var/cache/kiwi/packages/f796d7d2bc4daf38063ff386ebbc072d/kernel-firmware.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY
If the start of the problem indeed dates back 6 months, I'd like to check whether mounting the filesystem with 'dioread_lock' mount option indeed fixes the issue. What would be the easiest way to try that with OBS? The option needs to be passed either to mount, to mke2fs (as part of default mount options), or I can provide patched kernel with modified defaults...
I don't think it's possible for users to influence mount options directly, so if you think that test makes sense, a kernel-obs-build package for i586 would be ideal. FTR, my test projects are at https://build.opensuse.org/project/show/home:favogt:boo1169774 (xfs) https://build.opensuse.org/project/show/home:favogt:boo1169774-btrfs (btrfs) -- You are receiving this mail because: You are on the CC list for the bug.