Checking if machine is affected by ‘bsc#100…’
i don’t remember all the numbers
Hi
Bug report reference, #bsc is a SUSE reference, or for openSUSE #boo they should duplicate on https://bugzilla.opensuse.org;
When you see that in a bug you see a poor habit in use. It creates a link to a bugzilla.suse.com page, just as boo# creates a bugzilla.opensuse.org page. What should be used is simply <bug bugnumber>, which creates a link to either, depending on which URL is used to view the bug.
cf. Re: [opensuse-factory] M2: choose Grub, get Grub and Grub2 - openSUSE Factory - openSUSE Mailing Lists which resulted in
Bug Access Denied
I guess this is what you’re seeing:
paul@HP255G7:~> journalctl -b | grep -i bsc#
Oct 31 09:55:51 HP255G7 systemd[1]: Started Detect if the system suffers from bsc#1089761.
paul@HP255G7:~>
https://bugzilla.opensuse.org/show_bug.cgi?id=1089761
However, as I’m only a mere mortal…
“You are not authorized to access bug #1089761”
For the very curious… searching this page:
https://www.mail-archive.com/opensuse-commit@opensuse.org/msg203391.html
for “bsc#1089761” will give some insight…
Thanks everyone for your responses.
That message only shows up on the boot process on my desktop.
so far, neither laptop has it on boot.
ANYTHING I did wrong to cause it?
It is probably just an informational message being logged by the kernel during boot.
If I understand correctly, reading from, https://build.opensuse.org/package/view_file/openSUSE/systemd.8696/0001-udev-don-t-create-by-partlabel-primary-and-.-logical.patch?expand=0
"*udev: don’t create by-partlabel/primary and …/logical symlinks
These links are created by libstorage / parted by default. They are ambiguous and may be present hundred- or thousandfold on large systems. They are meaningless for device identification and may slow down udev processing. They aren’t used anywhere. Don’t create them.
A service has been added to detect at boot cases that likely need to be fixed: a warning is thrown at both the console and syslog to encourage sysadmin to consult the relevant TID explaining how to permanently fix the issue.
[fbui: added the detection part]
[fbui: fixes bsc#1089761]*"
If your system does indeed “suffers from bsc#1089761” then there is a further message:
“Warning: a high number of partitions uses “primary” or “logical” as partition label name, which may cause slow-down in the boot process. To prevent it, a workaround is **temporarly in place but we recommend to refer to TID #7023057 in order to permanently fix this issue (as the workaround will be dropped in the future).”
Procedures aren’t created equal. Could be related to /etc/fstab. Always use UUIDs.
erlangen:~ # grep /home /etc/fstab
UUID=704621ef-9b45-4e96-ba7f-1becd3924f08 /home ext4 defaults 0 0
erlangen:~ #
Maintain partitions and filesystems with ‘yast2 partitioner’. When editing /etc/fstab manually lsblk or blkid help to identify filesystems:
erlangen:~ # lsblk -o path,uuid
PATH UUID
/dev/sda
/dev/sda1 fad3604b-5a61-4653-8c14-518d850400ba
/dev/sda2 57bdbf64-b309-477c-b94c-8987e0c8032a
/dev/sda3 42f23f3c-9ff6-46f6-a9d9-6894062c37d7
/dev/sda4 f5177cae-4082-44ed-9471-b99030f06866
/dev/sdb
/dev/sdb1 5605f149-34a7-4301-9bf3-f1f177e35ed6
/dev/sdc
/dev/sdc1 4A24-B10D
/dev/sdc2 690b51d7-7034-4585-b362-615f8056be45
/dev/sdc3 492c5d5e-5d9b-4a99-9d34-e1f9cee09fe9
/dev/sdc4 f4c5463f-f43d-420a-a0ea-4456cfbc54fa
/dev/sdc5 204f7d0f-979a-41e1-a483-a597d0357e0b
/dev/sdc6 bf6ba7c9-9068-4a9b-b210-84b6d105df5c
/dev/sdc7 96df969e-8897-4a5c-8473-3ed007f97b29
/dev/sdc8 69774d55-8da2-4599-9c27-766b1012771d
/dev/sdc9 9a3eec78-dd20-44c0-a38a-f705b3bbbc66
/dev/sdc10
/dev/sdc11 7CB4EC04B4EBBEB0
/dev/sr0
/dev/nvme0n1
/dev/nvme0n1p1 6fe43319-8566-4a09-9d2d-fcf8c104671f
/dev/nvme0n1p2 e7ad401f-4f60-42ff-a07e-f54372bc1dbc
/dev/nvme0n1p3 704621ef-9b45-4e96-ba7f-1becd3924f08
/dev/nvme0n1p4 6DEC-64F9
erlangen:~ #
BTW: Manjaro’s default /etc/fstab sticks to the above:
erlangen:~ # cat /mnt/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=4A24-B10D /boot/efi vfat umask=0077 0 2
UUID=bf6ba7c9-9068-4a9b-b210-84b6d105df5c / ext4 defaults,noatime,discard 0 1
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
erlangen:~ #