[opensuse] The system is mad, it is trying to automatically mount an EXTENDED partition.
Hi, I see this in the log right now:
2014-03-03T22:06:17.091409+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/sda3 2014-03-03T22:06:17.094946+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/sda3 2014-03-03T22:06:17.098840+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/sda3 2014-03-03T22:06:17.102397+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/sda3 2014-03-03T22:06:17.106027+01:00 Elessar 83haiku: debug: /dev/sda3 is not a BeFS partition: exiting 2014-03-03T22:06:17.106830+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/sda3 2014-03-03T22:06:17.113704+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sda3 2014-03-03T22:06:17.132656+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda4 2014-03-03T22:06:17.172800+01:00 Elessar kernel: [ 866.836703] EXT4-fs (sda4): unable to read superblock 2014-03-03T22:06:17.173789+01:00 Elessar kernel: [ 866.837863] EXT4-fs (sda4): unable to read superblock 2014-03-03T22:06:17.174787+01:00 Elessar kernel: [ 866.838986] EXT4-fs (sda4): unable to read superblock 2014-03-03T22:06:17.176788+01:00 Elessar kernel: [ 866.840154] isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32 2014-03-03T22:06:17.179808+01:00 Elessar kernel: [ 866.843013] XFS (sda4): bad magic number 2014-03-03T22:06:17.179815+01:00 Elessar kernel: [ 866.843017] ffff88022cdb7000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T22:06:17.179816+01:00 Elessar kernel: [ 866.843019] ffff88022cdb7010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T22:06:17.179817+01:00 Elessar kernel: [ 866.843020] ffff88022cdb7020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T22:06:17.179818+01:00 Elessar kernel: [ 866.843021] ffff88022cdb7030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T22:06:17.179819+01:00 Elessar kernel: [ 866.843024] XFS (sda4): Internal error xfs_sb_read_verify at line 780 of file /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.6/linux-3.11/fs/xfs/xfs_mount.c. Caller 0xffffffffa0ed87b5 2014-03-03T22:06:17.179820+01:00 Elessar kernel: [ 866.843024] 2014-03-03T22:06:17.179821+01:00 Elessar kernel: [ 866.843027] CPU: 1 PID: 163 Comm: kworker/1:1H Tainted: P O 3.11.6-4-desktop #1
2014-03-03T22:06:17.179838+01:00 Elessar kernel: [ 866.843228] XFS (sda4): Corruption detected. Unmount and run xfs_repair 2014-03-03T22:06:17.179839+01:00 Elessar kernel: [ 866.843234] XFS (sda4): SB validate failed with error 22. 2014-03-03T22:06:17.205799+01:00 Elessar kernel: [ 866.869894] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 8, size 1024) 2014-03-03T22:06:17.205813+01:00 Elessar kernel: [ 866.869900] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 64, size 1024) 2014-03-03T22:06:17.205814+01:00 Elessar kernel: [ 866.869902] REISERFS warning (device sda4): sh-2021 reiserfs_fill_super: can not find reiserfs on sda4 2014-03-03T22:06:17.208802+01:00 Elessar kernel: [ 866.872660] FAT-fs (sda4): bogus number of reserved sectors 2014-03-03T22:06:17.208819+01:00 Elessar kernel: [ 866.872663] FAT-fs (sda4): Can't find a valid FAT filesystem 2014-03-03T22:06:17.210794+01:00 Elessar kernel: [ 866.874197] FAT-fs (sda4): bogus number of reserved sectors 2014-03-03T22:06:17.210800+01:00 Elessar kernel: [ 866.874201] FAT-fs (sda4): Can't find a valid FAT filesystem 2014-03-03T22:06:17.211793+01:00 Elessar kernel: [ 866.875760] MINIX-fs: unable to read superblock 2014-03-03T22:06:17.229862+01:00 Elessar kernel: [ 866.893903] attempt to access beyond end of device
2014-03-03T22:37:05.240821+01:00 Elessar kernel: [ 2714.904760] XFS (sdb4): Internal error xfs_sb_read_verify at line 780 of file /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.6/linux-3.11/fs/xfs/xfs_mount.c. Caller 0xffffffffa0ed87b5 2014-03-03T22:37:05.240822+01:00 Elessar kernel: [ 2714.904760] 2014-03-03T22:37:05.240842+01:00 Elessar kernel: [ 2714.905010] XFS (sdb4): Corruption detected. Unmount and run xfs_repair 2014-03-03T22:37:05.241793+01:00 Elessar kernel: [ 2714.905558] XFS (sdb4): SB validate failed with error 22. 2014-03-03T22:37:05.246795+01:00 Elessar kernel: [ 2714.910864] REISERFS warning (device sdb4): sh-2006 read_super_block: bread failed (dev sdb4, block 8, size 1024) 2014-03-03T22:37:05.246801+01:00 Elessar kernel: [ 2714.910870] REISERFS warning (device sdb4): sh-2006 read_super_block: bread failed (dev sdb4, block 64, size 1024) 2014-03-03T22:37:05.246802+01:00 Elessar kernel: [ 2714.910873] REISERFS warning (device sdb4): sh-2021 reiserfs_fill_super: can not find reiserfs on sdb4 2014-03-03T22:37:05.249794+01:00 Elessar kernel: [ 2714.913967] FAT-fs (sdb4): bogus number of reserved sectors 2014-03-03T22:37:05.251791+01:00 Elessar kernel: [ 2714.915215] FAT-fs (sdb4): bogus number of reserved sectors 2014-03-03T22:37:05.252802+01:00 Elessar kernel: [ 2714.916302] MINIX-fs: unable to read superblock 2014-03-03T22:37:05.253801+01:00 Elessar kernel: [ 2714.917382] hfsplus: unable to find HFS+ superblock 2014-03-03T22:37:05.254799+01:00 Elessar kernel: [ 2714.918700] qnx4: wrong fsid in superblock. 2014-03-03T22:37:05.256800+01:00 Elessar kernel: [ 2714.920407] You didn't specify the type of your ufs filesystem
It it is going on an on, endlessly, probing sda4, sdb4, sdc4... all of them extended partitions, causing kernel oopses. It has apparently started with os-prober. This is happening while I run YOU, with many official updates (including kernel) so the system is unstable at the moment. Process tree:
su - \_ -bash \_ /bin/bash /sbin/yast2 --qt online_update \_ /usr/lib/YaST2/bin/y2base online_update qt \_ rpm --root / --dbpath /var/lib/rpm -U --percent --force --nodeps -- /var/cache/zypp/packages/repo-update/x86_64/lvm2-2.02.98-0.28.14.1.x86_64.rpm \_ /bin/sh /var/tmp/rpm-tmp.REHLHS 1 \_ /bin/bash /sbin/mkinitrd \_ /usr/bin/perl /sbin/update-bootloader --refresh \_ sh -c /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1 \_ /bin/sh /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg \_ /bin/sh /etc/grub.d/30_os-prober \_ /bin/sh /etc/grub.d/30_os-prober \_ /bin/sh /etc/grub.d/30_os-prober | \_ /bin/sh /etc/grub.d/30_os-prober | \_ /usr/sbin/grub2-probe --device /dev/sdb1 --target=partmap \_ /bin/sh /etc/grub.d/30_os-prober \_ sed -e s/^/?/
And it has hung on that rpm, yast does not progress. [...] I had to " killall 30_os-prober" to let it progress. And possibly grub will now be broken and this system will not boot. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-03 22:52, Carlos E. R. wrote:
I had to " killall 30_os-prober" to let it progress. And possibly grub will now be broken and this system will not boot.
Well, it booted. But all entries have disappeared from grub 2 menu, except the current system. Obviously, as os-prober failed. I started yast, selected boot module, unclicked the box to probe for other operating systems, and accepted. Fine. Then started the module again, and this time I activated that box. It is happening again, and this time the system (13.1) is fully updated.
root 3608 0.0 0.0 11968 1736 pts/4 S 23:02 0:00 /bin/bash /sbin/yast2 bootloader root 3625 3.8 2.7 934412 225060 pts/4 Sl 23:02 0:11 \_ /usr/lib/YaST2/bin/y2base bootloader qt root 3834 0.0 0.0 11832 1396 pts/4 S 23:02 0:00 \_ sh -c /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1 root 3835 0.0 0.0 11968 1776 pts/4 S 23:02 0:00 \_ /bin/sh /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg root 4280 0.0 0.0 11964 1676 pts/4 S 23:02 0:00 \_ /bin/sh /etc/grub.d/30_os-prober root 4286 0.0 0.0 11964 696 pts/4 S 23:02 0:00 \_ /bin/sh /etc/grub.d/30_os-prober root 4287 0.0 0.0 11972 1820 pts/4 S 23:02 0:00 \_ /bin/sh /usr/bin/os-prober root 5516 0.0 0.0 11972 1768 pts/4 S 23:03 0:00 | \_ /bin/sh /usr/lib/os-probes/50mounted-tests /dev/sdb8 root 5562 0.0 0.0 11968 1648 pts/4 S 23:03 0:00 | \_ /bin/sh /usr/lib/os-probes/mounted/90linux-distro /dev/sdb8 /var/lib/os-prober/mount xfs root 5563 0.0 0.0 11968 824 pts/4 S 23:03 0:00 | \_ /bin/sh /usr/lib/os-probes/mounted/90linux-distro /dev/sdb8 /var/lib/os-prober/mount xfs root 4288 0.0 0.0 4544 576 pts/4 S 23:02 0:00 \_ tr ^ root 4289 0.0 0.0 4524 560 pts/4 S 23:02 0:00 \_ paste -s -d root 5522 91.7 0.3 57500 32508 ? Rs 23:03 3:27 grub2-mount /dev/sdb8 /var/lib/os-prober/mount li
Well, this time it finished without killing. Does someone want an official report, full logs? It tries to mount all partitions on all disks, even the _extended_ partitions, with all known filesystems, failing, and causing kernel oopses, many of them, and taking a long time:
2014-03-03T23:03:12.885504+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdb4 2014-03-03T23:03:12.912018+01:00 Elessar kernel: [ 440.854874] EXT4-fs (sdb4): unable to read superblock 2014-03-03T23:03:12.914009+01:00 Elessar kernel: [ 440.856300] EXT4-fs (sdb4): unable to read superblock 2014-03-03T23:03:12.915012+01:00 Elessar kernel: [ 440.857646] EXT4-fs (sdb4): unable to read superblock 2014-03-03T23:03:12.917008+01:00 Elessar kernel: [ 440.859047] isofs_fill_super: bread failed, dev=sdb4, iso_blknum=16, block=32 2014-03-03T23:03:12.921034+01:00 Elessar kernel: [ 440.863210] XFS (sdb4): bad magic number 2014-03-03T23:03:12.921041+01:00 Elessar kernel: [ 440.863214] ffff8801e292f000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T23:03:12.921043+01:00 Elessar kernel: [ 440.863216] ffff8801e292f010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T23:03:12.921044+01:00 Elessar kernel: [ 440.863218] ffff8801e292f020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T23:03:12.921045+01:00 Elessar kernel: [ 440.863219] ffff8801e292f030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2014-03-03T23:03:12.921046+01:00 Elessar kernel: [ 440.863222] XFS (sdb4): Internal error xfs_sb_read_verify at line 780 of file /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.10/linux-3.11/fs/xfs/xfs_mount.c. Caller 0xffffffffa0eca7b5 2014-03-03T23:03:12.921047+01:00 Elessar kernel: [ 440.863222] 2014-03-03T23:03:12.921048+01:00 Elessar kernel: [ 440.863226] CPU: 2 PID: 166 Comm: kworker/2:1H Tainted: P O 3.11.10-7-desktop #1 2014-03-03T23:03:12.921049+01:00 Elessar kernel: [ 440.863227] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7516/MS-7516, BIOS V1.5 10/10/2008 2014-03-03T23:03:12.921050+01:00 Elessar kernel: [ 440.863253] Workqueue: xfslogd xfs_buf_iodone_work [xfs] 2014-03-03T23:03:12.921051+01:00 Elessar kernel: [ 440.863256] 0000000000000001 ffffffff8159ff82 ffff8801e28a3000 ffffffffa0ecd4a6 2014-03-03T23:03:12.921052+01:00 Elessar kernel: [ 440.863259] 0000030c00000000 ffffffffa0eca7b5 ffff8801f3847500 0000000000000016 2014-03-03T23:03:12.921053+01:00 Elessar kernel: [ 440.863262] ffff8801e28a3000 ffffe8ffffd01000 ffffffffa0f215ed ffffffffa0eca7b5 2014-03-03T23:03:12.921054+01:00 Elessar kernel: [ 440.863265] Call Trace: 2014-03-03T23:03:12.921055+01:00 Elessar kernel: [ 440.863276] [<ffffffff81004a18>] dump_trace+0x88/0x310 2014-03-03T23:03:12.921056+01:00 Elessar kernel: [ 440.863280] [<ffffffff81004d70>] show_stack_log_lvl+0xd0/0x1d0 2014-03-03T23:03:12.921057+01:00 Elessar kernel: [ 440.863284] [<ffffffff810061ac>] show_stack+0x1c/0x50 2014-03-03T23:03:12.921058+01:00 Elessar kernel: [ 440.863288] [<ffffffff8159ff82>] dump_stack+0x50/0x89 2014-03-03T23:03:12.921059+01:00 Elessar kernel: [ 440.863303] [<ffffffffa0ecd4a6>] xfs_corruption_error+0x56/0x80 [xfs]
...
2014-03-03T23:03:12.921066+01:00 Elessar kernel: [ 440.863463] XFS (sdb4): Corruption detected. Unmount and run xfs_repair 2014-03-03T23:03:12.921067+01:00 Elessar kernel: [ 440.863470] XFS (sdb4): SB validate failed with error 22. 2014-03-03T23:03:12.927119+01:00 Elessar kernel: [ 440.869374] REISERFS warning (device sdb4): sh-2006 read_super_block: bread failed (dev sdb4, block 8, size 1024) 2014-03-03T23:03:12.927129+01:00 Elessar kernel: [ 440.869380] REISERFS warning (device sdb4): sh-2006 read_super_block: bread failed (dev sdb4, block 64, size 1024) 2014-03-03T23:03:12.927130+01:00 Elessar kernel: [ 440.869383] REISERFS warning (device sdb4): sh-2021 reiserfs_fill_super: can not find reiserfs on sdb4 2014-03-03T23:03:12.931021+01:00 Elessar kernel: [ 440.873066] FAT-fs (sdb4): bogus number of reserved sectors 2014-03-03T23:03:12.931032+01:00 Elessar kernel: [ 440.873070] FAT-fs (sdb4): Can't find a valid FAT filesystem 2014-03-03T23:03:12.932011+01:00 Elessar kernel: [ 440.874902] FAT-fs (sdb4): bogus number of reserved sectors 2014-03-03T23:03:12.932014+01:00 Elessar kernel: [ 440.874905] FAT-fs (sdb4): Can't find a valid FAT filesystem 2014-03-03T23:03:12.934013+01:00 Elessar kernel: [ 440.876502] MINIX-fs: unable to read superblock 2014-03-03T23:03:12.935012+01:00 Elessar kernel: [ 440.877920] attempt to access beyond end of device 2014-03-03T23:03:12.935017+01:00 Elessar kernel: [ 440.877923] sdb4: rw=0, want=3, limit=2 2014-03-03T23:03:12.935019+01:00 Elessar kernel: [ 440.877924] hfsplus: unable to find HFS+ superblock 2014-03-03T23:03:12.937012+01:00 Elessar kernel: [ 440.879792] qnx4: wrong fsid in superblock. 2014-03-03T23:03:12.939012+01:00 Elessar kernel: [ 440.881186] You didn't specify the type of your ufs filesystem 2014-03-03T23:03:12.939018+01:00 Elessar kernel: [ 440.881186] 2014-03-03T23:03:12.939019+01:00 Elessar kernel: [ 440.881186] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... 2014-03-03T23:03:12.939021+01:00 Elessar kernel: [ 440.881186] 2014-03-03T23:03:12.939022+01:00 Elessar kernel: [ 440.881186] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old 2014-03-03T23:03:12.940013+01:00 Elessar kernel: [ 440.882392] hfs: can't find a HFS filesystem on dev sdb4 2014-03-03T23:03:12.978674+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdb5
I will now reboot to see if I have back the other systems entries. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" (Elessar)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 03 Mar 2014 22:52:51 +0100
"Carlos E. R."
В Tue, 04 Mar 2014 03:34:48 +0100
"Carlos E. R."
On 2014-03-04 03:16, Andrey Borzenkov wrote:
В Mon, 03 Mar 2014 22:52:51 +0100 "Carlos E. R." <> пишет:
Which openSUSE version?
It was on my signature:
(from 13.1 x86_64 "Bottle" (Elessar))
Care to open bug report and attach /var/log/messages from the time os-prober was run? Please do not grep for os-prober, there may be other interesting messages. You can assign it to me right away.
On 2014-03-04 16:10, Andrey Borzenkov wrote:
В Tue, 04 Mar 2014 03:34:48 +0100 "Carlos E. R." <> пишет:
(from 13.1 x86_64 "Bottle" (Elessar))
Care to open bug report and attach /var/log/messages from the time os-prober was run? Please do not grep for os-prober, there may be other interesting messages. You can assign it to me right away.
Sure. I can attach that, and also the yast logs while the update run. I had to kill os-prober to let the "yast online update" to continue, it was stuck there for a long time. And I can also attach messages log for the much older session, using an older kernel, not tainted, in case that is an issue. It depends on what interests you, the kernel oops when xfs tries to mount it, of the issue of os-prober to try to mount those partitions. It may also of interest this:
Telcontar:~ # file -s /dev/sda4 /dev/sda4: DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x4c,1,1), end-CHS (0x3ff,254,63), startsector 63, 31455207 sectors; partition 2 : ID=0x5, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 31455270, 20964825 sectors Telcontar:~ #
'file' does not say it is an extended partition. Nor this is clear: Telcontar:~ # lsblk /dev/sda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 203.9M 0 part /other/test_a1/boot ├─sda2 8:2 0 196.1M 0 part /boot ├─sda3 8:3 0 196.1M 0 part ├─sda4 8:4 0 1K 0 part But it is indeed an extended: Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 500.1 GB, 500107862016 bytes, 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000ccd24 Device Boot Start End Blocks Id System /dev/sda1 63 417689 208813+ 83 Linux /dev/sda2 * 417690 819314 200812+ 83 Linux /dev/sda3 819315 1220939 200812+ 83 Linux /dev/sda4 1220940 976768064 487773562+ f W95 Ext'd (LBA) ... -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
В Tue, 04 Mar 2014 17:09:52 +0100
"Carlos E. R."
I can attach that, and also the yast logs while the update run.
Just run os-prober. It does not matter whether it is run as part of RPM or not.
And I can also attach messages log for the much older session, using an older kernel, not tainted, in case that is an issue.
It depends on what interests you, the kernel oops when xfs tries to mount it, of the issue of os-prober to try to mount those partitions.
There is already bug report for XFS (I cannot find it right now). I'm interested in os-prober behavior.
On 2014-03-04 17:14, Andrey Borzenkov wrote:
В Tue, 04 Mar 2014 17:09:52 +0100 "Carlos E. R." <> пишет:
I can attach that, and also the yast logs while the update run.
Just run os-prober. It does not matter whether it is run as part of RPM or not.
And I can also attach messages log for the much older session, using an older kernel, not tainted, in case that is an issue.
It depends on what interests you, the kernel oops when xfs tries to mount it, of the issue of os-prober to try to mount those partitions.
There is already bug report for XFS (I cannot find it right now). I'm interested in os-prober behavior.
Fair enough. What I have currently are the entries on syslog, from when os-prober was automatically run. If you want the output on the terminal of running os-prober, I'll have to reboot to that partition (see signature: this post is sent from "Telcontar", which has grub 1. Posts sent from the test partition, with grub 2, read "Elessar"). As I have never used os-prober on the terminal, do you want any options on the command line, or none? About the XFE problem, yes, I found many reports on many distributions, searchin for on google for "Internal error xfs_sb_read_verify at line". For instance, at openSUSE: Bug 854646 - Running grub2-mkconfig -o /boot/grub2/grub.cfg crashes some fs kernel modules which has been closed as invalid. «It's from the kernel, but I wouldn't call it a "problem" other than it dropping a stack trace. That's the XFS core corruption handling and we actually want that.» (J.M). Then there is «Bug 849028 - grub2-probe create kernel segfault» and «Bug 849843 - initrd produces insane messages in dmesg», both in "new" state. «Bug 849028» is the same issue as the one on this thread, and I see one comment from you on it. Do you want a new report, or do I simply update that bugzilla with my info? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2014-03-04 at 20:39 +0100, Carlos E. R. wrote:
On 2014-03-04 17:14, Andrey Borzenkov wrote:
Do you want a new report, or do I simply update that bugzilla with my info?
Well, as you didn't say anything, I took the liberty of creating a new bugzilla and assigned it to you, as you requested: Bug 867118 - os-prober tries to mount all extended partitions, causing awful kernel messages I added information about the bugzillas I have seen related to this same issue, so that you can choose which one to handle and close the rest as duplicates :-) On my side, I have disabled os-prober in yast bootloader configuration. I will try instead to add custom configs to boot my other partitions. If you need more tests from me, notice that as it is a test partition I have to stop my work, boot that partition, perhaps update it (on a slow internet), and do whatever it needs doing. Takes hours. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMYeTIACgkQtTMYHG2NR9Uv7QCdHZdsfjZsK1xl2mKIpuvB6xXi JToAn1s+JdglblZ5zh4XuBtPy6LVsXFw =ZjoS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 03/03/14 18:52, Carlos E. R. escribió:
Hi,
I see this in the log right now:
(sda4): Internal error xfs_sb_read_verify at line 780 of file /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.6/linux-3.11/fs/xfs/xfs_mount.c. Caller 0xffffffffa0ed87b5 2014-03-03T22:06:17.179820+01:00 Elessar kernel: [ 866.843024] 2014-03-03T22:06:17.179821+01:00 Elessar kernel: [ 866.843027] CPU: 1 PID: 163 Comm: kworker/1:1H Tainted: P O 3.11.6-4-desktop #1
Stop right there, that's the first thing that needs fixing.. userspace shall not make the kernel BUG, oops or warn .. however your kernel is tainted with proprietary modules.. developers are usually unwilling to debug that.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
El 03/03/14 18:52, Carlos E. R. escribió:
Hi,
I see this in the log right now:
(sda4): Internal error xfs_sb_read_verify at line 780 of file /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.6/linux-3.11/fs/xfs/xfs_mount.c. Caller 0xffffffffa0ed87b5 2014-03-03T22:06:17.179820+01:00 Elessar kernel: [ 866.843024] 2014-03-03T22:06:17.179821+01:00 Elessar kernel: [ 866.843027] CPU: 1 PID: 163 Comm: kworker/1:1H Tainted: P O 3.11.6-4-desktop #1
Stop right there, that's the first thing that needs fixing.. userspace shall not make the kernel BUG, oops or warn .. however your kernel is tainted with proprietary modules.. developers are usually unwilling to debug that..
That's a lame excuse and you know that. For your info, I have seen the same kernel crash since many months ago, without that taint, when the system tries to somehow mount the wrong partition with the wrong kernel filesystem. Look, I searched the system, and found earlier instances of the same event: 2013-12-20T17:45:57.533843+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/sda3 2013-12-20T17:45:57.555904+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda4 2013-12-20T17:45:57.613626+01:00 Elessar kernel: [ 1601.539266] EXT4-fs (sda4): unable to read superblock 2013-12-20T17:45:57.614532+01:00 Elessar kernel: [ 1601.540402] EXT4-fs (sda4): unable to read superblock 2013-12-20T17:45:57.615531+01:00 Elessar kernel: [ 1601.541508] EXT4-fs (sda4): unable to read superblock 2013-12-20T17:45:57.616532+01:00 Elessar kernel: [ 1601.542619] isofs_fill_super: bread failed, dev=sda4, iso_blknum=16, block=32 2013-12-20T17:45:57.618553+01:00 Elessar kernel: [ 1601.544081] XFS (sda4): bad magic number 2013-12-20T17:45:57.618558+01:00 Elessar kernel: [ 1601.544085] ffff88023321f000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2013-12-20T17:45:57.618560+01:00 Elessar kernel: [ 1601.544086] ffff88023321f010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2013-12-20T17:45:57.618561+01:00 Elessar kernel: [ 1601.544088] ffff88023321f020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2013-12-20T17:45:57.618562+01:00 Elessar kernel: [ 1601.544089] ffff88023321f030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 2013-12-20T17:45:57.618563+01:00 Elessar kernel: [ 1601.544091] XFS (sda4): Internal error xfs_sb_read_verify at line 780 of file /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.6/linux-3.11/fs/xfs/xfs_mount.c. Caller 0xffffffffa04b97b5 2013-12-20T17:45:57.618565+01:00 Elessar kernel: [ 1601.544091] 2013-12-20T17:45:57.618565+01:00 Elessar kernel: [ 1601.544094] CPU: 3 PID: 171 Comm: kworker/3:1H Not tainted 3.11.6-4-desktop #1 2013-12-20T17:45:57.618566+01:00 Elessar kernel: [ 1601.544096] Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7516/MS-7516, BIOS V1.5 10/10/2008 2013-12-20T17:45:57.618568+01:00 Elessar kernel: [ 1601.544121] Workqueue: xfslogd xfs_buf_iodone_work [xfs] 2013-12-20T17:45:57.618569+01:00 Elessar kernel: [ 1601.544123] 0000000000000001 ffffffff815a9bd7 ffff880218855000 ffffffffa04bc4a6 2013-12-20T17:45:57.618570+01:00 Elessar kernel: [ 1601.544126] 0000030c00000000 ffffffffa04b97b5 ffff88023246f240 0000000000000016 2013-12-20T17:45:57.618571+01:00 Elessar kernel: [ 1601.544128] ffff880218855000 ffffe8ffffd80c00 ffffffffa05105ed ffffffffa04b97b5 2013-12-20T17:45:57.618572+01:00 Elessar kernel: [ 1601.544131] Call Trace: 2013-12-20T17:45:57.618573+01:00 Elessar kernel: [ 1601.544141] [<ffffffff81004a18>] dump_trace+0x88/0x310 2013-12-20T17:45:57.618574+01:00 Elessar kernel: [ 1601.544144] [<ffffffff81004d70>] show_stack_log_lvl+0xd0/0x1d0 2013-12-20T17:45:57.618575+01:00 Elessar kernel: [ 1601.544147] [<ffffffff810061bc>] show_stack+0x1c/0x50 2013-12-20T17:45:57.618576+01:00 Elessar kernel: [ 1601.544151] [<ffffffff815a9bd7>] dump_stack+0x50/0x89 2013-12-20T17:45:57.618577+01:00 Elessar kernel: [ 1601.544163] [<ffffffffa04bc4a6>] xfs_corruption_error+0x56/0x80 [xfs] 2013-12-20T17:45:57.618578+01:00 Elessar kernel: [ 1601.544199] [<ffffffffa05105ed>] xfs_sb_read_verify+0xfd/0x120 [xfs] 2013-12-20T17:45:57.618579+01:00 Elessar kernel: [ 1601.544267] [<ffffffffa04b97b5>] xfs_buf_iodone_work+0x75/0x110 [xfs] 2013-12-20T17:45:57.618580+01:00 Elessar kernel: [ 1601.544282] [<ffffffff8106ac48>] process_one_work+0x168/0x490 2013-12-20T17:45:57.618581+01:00 Elessar kernel: [ 1601.544286] [<ffffffff8106b8e4>] worker_thread+0x114/0x3a0 2013-12-20T17:45:57.618582+01:00 Elessar kernel: [ 1601.544289] [<ffffffff81071c0f>] kthread+0xaf/0xc0 2013-12-20T17:45:57.618583+01:00 Elessar kernel: [ 1601.544293] [<ffffffff815b777c>] ret_from_fork+0x7c/0xb0 2013-12-20T17:45:57.618584+01:00 Elessar kernel: [ 1601.544296] XFS (sda4): Corruption detected. Unmount and run xfs_repair 2013-12-20T17:45:57.618585+01:00 Elessar kernel: [ 1601.544302] XFS (sda4): SB validate failed with error 22. 2013-12-20T17:45:57.620540+01:00 Elessar kernel: [ 1601.546473] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 8, size 1024) 2013-12-20T17:45:57.620546+01:00 Elessar kernel: [ 1601.546480] REISERFS warning (device sda4): sh-2006 read_super_block: bread failed (dev sda4, block 64, size 1024) 2013-12-20T17:45:57.620547+01:00 Elessar kernel: [ 1601.546483] REISERFS warning (device sda4): sh-2021 reiserfs_fill_super: can not find reiserfs on sda4 2013-12-20T17:45:57.646548+01:00 Elessar kernel: [ 1601.572804] FAT-fs (sda4): bogus number of reserved sectors 2013-12-20T17:45:57.646566+01:00 Elessar kernel: [ 1601.572807] FAT-fs (sda4): Can't find a valid FAT filesystem 2013-12-20T17:45:57.648533+01:00 Elessar kernel: [ 1601.574073] FAT-fs (sda4): bogus number of reserved sectors 2013-12-20T17:45:57.648543+01:00 Elessar kernel: [ 1601.574076] FAT-fs (sda4): Can't find a valid FAT filesystem 2013-12-20T17:45:57.649533+01:00 Elessar kernel: [ 1601.575194] MINIX-fs: unable to read superblock 2013-12-20T17:45:57.650535+01:00 Elessar kernel: [ 1601.576466] attempt to access beyond end of device 2013-12-20T17:45:57.650541+01:00 Elessar kernel: [ 1601.576469] sda4: rw=0, want=3, limit=2 2013-12-20T17:45:57.650542+01:00 Elessar kernel: [ 1601.576471] hfsplus: unable to find HFS+ superblock 2013-12-20T17:45:57.651531+01:00 Elessar kernel: [ 1601.577904] qnx4: wrong fsid in superblock. 2013-12-20T17:45:57.653543+01:00 Elessar kernel: [ 1601.579174] You didn't specify the type of your ufs filesystem 2013-12-20T17:45:57.653549+01:00 Elessar kernel: [ 1601.579174] 2013-12-20T17:45:57.653550+01:00 Elessar kernel: [ 1601.579174] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... 2013-12-20T17:45:57.653552+01:00 Elessar kernel: [ 1601.579174] 2013-12-20T17:45:57.653553+01:00 Elessar kernel: [ 1601.579174] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old 2013-12-20T17:45:57.656536+01:00 Elessar kernel: [ 1601.582274] hfs: can't find a HFS filesystem on dev sda4 2013-12-20T17:45:57.705886+01:00 Elessar os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda5 That kernel was not tainted, so you can not blame Nvidia for that issue. There are two issues here: one, os-prober is trying to mount the extended partition. two, xfs code in the kernel breaks attempting it. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMVr20ACgkQtTMYHG2NR9UIHACeOkRxzuIlhwoF1zCMDSZCtzXE wKcAniihzpncsCrOy8h5SNC6JDg7mRUF =GPGc -----END PGP SIGNATURE-----
Cristian Rodr�������������������������������� wrote:
Stop right there, that's the first thing that needs fixing.. userspace shall not make the kernel BUG, oops or warn .. however your kernel is tainted with proprietary modules.. developers are usually unwilling to debug that..
Very good reason NOT to run open Suse kernels. Most of the time when I have run them, I get some tainted module or another. So by saying userspace is broken -- you've just broken many instances of the opensuse kernel -- likely depending on which packages you have installed, but I would have no way of knowing any complete list. I think one of the virtual machine packages taints it, among others. So... do you want to modify your statement and say that devels will debug such oopses, or should users just not run opensuse kernels on the risk that they install proprietary and/or non-standard modules that can cause tainting? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrey Borzenkov -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
Linda Walsh