[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
Same here during boot, running 6.5.0-15-generic on Ubuntu 23.10:
$ dmesg | grep -C3 evict
[ 10.769204] EXT4-fs (xvda1): mounted filesystem
446b2699-dd26-4b84-9ada-d0cb48d21c93 r/w with ordered data mode. Quota mode:
none.
[ 11.061845] SGI XFS with ACLs, security attributes, realtime, quota, no
debug enabled
[ 11.069288] XFS (xvdb): Mounting V5 Filesystem
b2136bf4-6edc-4fb2-8ad9-1fc236c2671d
[ 11.109335] evict_inodes inode f37fffda, i_count = 1, was skipped!
[ 11.109345] evict_inodes inode e97e4ee2, i_count = 1, was skipped!
[ 11.109348] evict_inodes inode 92d4f6b3, i_count = 1, was skipped!
[ 11.109351] XFS (xvdb): Ending clean mount
However, mounting succeeds and no ill effects so far:
$ mount | grep xfs
/dev/xvdb on /home type xfs
(rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota)
$ xfs_info /dev/xvdb
meta-data=/dev/xvdb isize=512agcount=4, agsize=1638400 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1finobt=1, sparse=1, rmapbt=1
= reflink=1bigtime=1 inobtcount=1 nrext64=0
data = bsize=4096 blocks=6553600, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=16384, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
[Kernel-packages] [Bug 1742789] Re: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device
FWIW, this just happened again while trying out the latest mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline * Kernels up to v5.3-rc5 work fine, but booting it takes up ~36MB of /run (unpacking during boot) on the Dom0 here. * Kernel v5.3-rc6 seems to take up even more, filling up the 40MB /run filesystem completely and booting fails. But vt100 is correct of course, extending the /run filesystem solves this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742789 Title: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device Status in linux package in Ubuntu: Confirmed Bug description: # lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 This problem is related to the latest kernel for meltdown spectre patches for xen pv guest and pygrub. This is the kernel that was attempting to be upgraded. linux-image-4.4.0-109-generic 4.4.0-109.132 I tried to report this issue with the following command but it failed: ubuntu-bug linux *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Problem in linux-image-4.4.0-15-generic The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. Press any key to continue... No pending crash reports. Try --help for more information. I have an Ubuntu 14.04 running Xen and a VM running Ubuntu 16.04 LTS that I'm having issues with it booting after upgrading the kernel for meltdown and spectre vulnerability. sudo apt-get update sudo apt-get upgrade sudo apt-get dist-upgrade Ubuntu 14.04 xen host reboot failure log: $ tailf /var/log/xen/servername.log Domain 24 needs to be cleaned up: destroying the domain Done. Rebooting now libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - consult logfile /var/log/xen/bootloader.27.log libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [-1] exited with error status 1 libxl: error: libxl_create.c:1024:domcreate_rebuild_done: cannot (re-)build domain: -3 cat /var/log/xen/bootloader.27.log Using to parse /grub/grub.cfg pyGRUB version 0.6 ┌┐ │ Ubuntu │ │ Ubuntu, with Linux 4.4.0-109-generic │ │ Ubuntu, with Linux 4.4.0-109-generic (recovery mode) │ │ Ubuntu, with Linux 4.4.0-108-generic │ │ Ubuntu, with Linux 4.4.0-108-generic (recovery mode) │ │ Ubuntu, with Linux 4.4.0-104-generic │ │ Ubuntu, with Linux 4.4.0-104-generic (recovery mode) │ │ Ubuntu, with Linux 4.4.0-15-generic│ └┘ Use the ^ and ┴ keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command line. Traceback (most recent call last): File "/usr/lib/xen-4.4/bin/pygrub", line 905, in os.write(fd, ostring) OSError: [Errno 28] No space left on device I was able to get the vm to boot only by rapidly attempt to access the menu options and boot the old kernel (4.4.0-15-generic). Disk space and inodes seems fine on the host Ubuntu 14.04LTS and Ubuntu 16.04LTS Guest. Ubuntu 14.04 Host: root@host:/var/log/xen# df -hFilesystem Size Used Avail Use% Mounted on udev197M 12K 197M 1% /dev tmpfs42M 1.1M 41M 3% /run /dev/dm-0 104G 49G 50G 50% / none4.0K 0 4.0K 0% /sys/fs/cgroup none5.0M 0 5.0M 0% /run/lock none208M 0 208M 0% /run/shm none100M 0 100M 0% /run/user /dev/sda1 236M 40M 184M 18% /boot root@host:/var/log/xen# df -hi Filesystem Inodes IUsed IFree IUse% Mounted on udev 50K 721 49K2% /dev tmpfs 52K 849 52K2% /run /dev/dm-06.6M 86K 6.5M2% / none 52K 2 52K1% /sys/fs/cgroup none 52K 5 52K1% /run/lock none 52K 1 52K1% /run/shm none 52K 2 52K1% /run/user /dev/sda1 61K 298 61K1% /boot root@host:/var/log/xen# Ubuntu 16.04 PV Guest: root@guest:~# df -hFilesystem
[Kernel-packages] [Bug 1397652] Re: /dev/random and /dev/urandom world writeable
FWIW, Debian #81748 explains why it's safe to have world-writable
/dev/{u,}random devices.
** Bug watch added: Debian Bug tracker #81748
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81748
** Also affects: makedev (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81748
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1397652
Title:
/dev/random and /dev/urandom world writeable
Status in linux package in Ubuntu:
Invalid
Status in manpages package in Ubuntu:
Fix Released
Status in makedev package in Debian:
Unknown
Bug description:
It looks like in 14.04.1 that /dev/random and /dev/urandom are world-
writeable. This occurs in at least 14.04.1 Desktop for AMD64 and
Server for i386
$ ls -l /dev/*random
crw-rw-rw- 1 root root 1, 8 Nov 25 10:44 /dev/random
crw-rw-rw- 1 root root 1, 9 Nov 25 10:44 /dev/urandom
As far as I know, they should be 664 or 644.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: base-files 7.2ubuntu5.1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 30 12:06:43 2014
Dependencies:
InstallationDate: Installed on 2014-10-26 (34 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
SourcePackage: base-files
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397652/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1253155] Re: Failure to validate module signature at boot time
Why is this bug set to Fix released for Trusty? This is still happening: $ uname -rv 3.13.0-53-generic #88-Ubuntu SMP Wed May 13 18:10:29 UTC 2015 $ modprobe xfs $ dmesg -T | tail -2 [Fri May 29 10:41:08 2015] Request for unknown module key 'Magrathea: Glacier signing key: 9aac900abd0220fb93c8be10f20d6973dab829f5' err -11 [Fri May 29 10:41:08 2015] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time Status in linux package in Ubuntu: Fix Released Status in linux-lts-raring package in Ubuntu: Invalid Status in linux source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Fix Released Status in linux source package in Quantal: Invalid Status in linux-lts-raring source package in Quantal: Invalid Status in linux source package in Saucy: Fix Released Status in linux-lts-raring source package in Saucy: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-raring source package in Trusty: Invalid Bug description: When booting under secureboot and using a signed kernel, it's expected that all modules shipped alongside the kernel should validate and load successfully without tainting the kernel. Unfortunately it doesn't seem to always be the case. Looking through my kernel logs, I see: Nov 15 10:35:24 castiana kernel: [1.635132] video: module verification failed: signature and/or required key missing - tainting kernel or Nov 12 12:58:48 castiana kernel: [213981.753326] Request for unknown module key 'Magrathea: Glacier signing key: f440a253eb498df923d438caa09b3b5d99308405' err -11 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.7 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stgraber 2721 F pulseaudio /dev/snd/controlC0: stgraber 2721 F pulseaudio /dev/snd/pcmC0D0c: stgraber 2721 F...m pulseaudio /dev/snd/pcmC0D0p: stgraber 2721 F...m pulseaudio CurrentDesktop: Unity Date: Wed Nov 20 11:59:57 2013 InstallationDate: Installed on 2013-04-21 (213 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420) MachineType: LENOVO 2306CT0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic.efi.signed root=UUID=14de4e20-b139-488e-863f-ec710f776851 ro quiet splash acpi_osi=!Windows 2012 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-2-generic N/A linux-backports-modules-3.12.0-2-generic N/A linux-firmware1.117 SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CT0 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET96WW(2.56):bd08/27/2013:svnLENOVO:pn2306CT0:pvrThinkPadX230:rvnLENOVO:rn2306CT0:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CT0 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 398670] Re: eject: unable to eject, last error: Inappropriate ioctl for device
This just happened here with eject-2.1.5, but using eject -i off as suggested by zheoffec in comment #2 helped - thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/398670 Title: eject: unable to eject, last error: Inappropriate ioctl for device Status in “eject” package in Ubuntu: Invalid Bug description: When issuing an eject command on the console, I get: $ eject eject: unable to eject, last error: Inappropriate ioctl for device $ dmesg reports: [ 149.469374] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.469380] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.469385] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.469393] end_request: I/O error, dev sr0, sector 0 [ 149.469397] __ratelimit: 68 callbacks suppressed [ 149.469400] Buffer I/O error on device sr0, logical block 0 [ 149.469403] Buffer I/O error on device sr0, logical block 1 [ 149.469407] Buffer I/O error on device sr0, logical block 2 [ 149.469410] Buffer I/O error on device sr0, logical block 3 [ 149.469412] Buffer I/O error on device sr0, logical block 4 [ 149.469415] Buffer I/O error on device sr0, logical block 5 [ 149.469417] Buffer I/O error on device sr0, logical block 6 [ 149.469419] Buffer I/O error on device sr0, logical block 7 [ 149.469422] Buffer I/O error on device sr0, logical block 8 [ 149.469424] Buffer I/O error on device sr0, logical block 9 [ 149.486612] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.486618] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.486623] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.486630] end_request: I/O error, dev sr0, sector 0 [ 149.503096] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.503105] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.503112] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.503121] end_request: I/O error, dev sr0, sector 0 [ 149.505347] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 149.505360] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 149.505373] sr 1:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 149.505390] end_request: I/O error, dev sr0, sector 0 Even if the CD cannot be read, I should still be able to eject it! $ eject -v eject: using default device `cdrom' eject: device name is `cdrom' eject: expanded name is `/dev/cdrom' eject: `/dev/cdrom' is a link to `/dev/sr0' eject: `/dev/sr0' is not mounted eject: `/dev/sr0' is not a mount point eject: `/dev/sr0' is not a multipartition device eject: trying to eject `/dev/sr0' using CD-ROM eject command eject: CD-ROM eject command failed eject: trying to eject `/dev/sr0' using SCSI commands eject: SCSI eject failed eject: trying to eject `/dev/sr0' using floppy eject command eject: floppy eject command failed eject: trying to eject `/dev/sr0' using tape offline command eject: tape offline command failed eject: unable to eject, last error: Inappropriate ioctl for device $ lsb_release -rd Description: Ubuntu karmic (development branch) Release: 9.10 $ apt-cache policy eject eject: Installed: 2.1.5+deb1+cvs20081104-6 Candidate: 2.1.5+deb1+cvs20081104-6 Version table: *** 2.1.5+deb1+cvs20081104-6 0 500 http://de.archive.ubuntu.com karmic/main Packages 500 http://us.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/398670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
