Bug#760119: /dev/disk/by-uuid: Is a directory
* Norbert Preining [Mon Sep 01, 2014 at 02:44:36PM +0900]: On Mon, 01 Sep 2014, Michael Prokop wrote: Which version of initramfs-tools did you use before? in my aptitude.log I find: [UPGRADE] initramfs-tools:amd64 0.115 - 0.116 Ok. Did your upgrade also involve an update of the kernel/reboot of your system? sh -x /usr/sbin/mkinitramfs -o /tmp/initramfs.output 2/tmp/mkinitramfs.log Here it is. Thanks, so this commandline seems to be a problem for your system: blkid -o value -s UUID /dev/root Can you please provides its output and also attach output of: mount cat /proc/mounts ls -la /dev/root ? regards, -mika- signature.asc Description: Digital signature
Bug#760119: /dev/disk/by-uuid: Is a directory
Hi Michael, On Mon, 01 Sep 2014, Michael Prokop wrote: Ok. Did your upgrade also involve an update of the kernel/reboot of your system? Hmm, hard to say. I often update between kernels. So it might have been the same time I swtiched form 3.16 to 3.17-rc2. blkid -o value -s UUID /dev/root no output. mount /dev/root on / type btrfs (rw,relatime,ssd,space_cache) devtmpfs on /dev type devtmpfs (rw,relatime,size=4041792k,nr_inodes=1010448,mode=755) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) mqueue on /dev/mqueue type mqueue (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tmpfs on /run/user type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) debug on /sys/kernel/debug type debugfs (rw,relatime) /dev/sda5 on /xp type fuseblk (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) /dev/sda3 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=850,iocharset=iso8859-15,shortname=mixed,errors=remount-ro) rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / btrfs rw,relatime,ssd,space_cache 0 0 devtmpfs /dev devtmpfs rw,relatime,size=4041792k,nr_inodes=1010448,mode=755 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0 tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/debug cgroup rw,nosuid,nodev,noexec,relatime,debug 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=27,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 tmpfs /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 debug /sys/kernel/debug debugfs rw,relatime 0 0 /dev/sda5 /xp fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0 /dev/sda3 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=850,iocharset=iso8859-15,shortname=mixed,errors=remount-ro 0 0 rpc_pipefs /run/rpc_pipefs rpc_pipefs rw,relatime 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 rootfs / rootfs rw 0 0 /dev/root / btrfs rw,relatime,ssd,space_cache 0 0 devtmpfs /dev devtmpfs
Bug#760119: /dev/disk/by-uuid: Is a directory
* Norbert Preining [Mon Sep 01, 2014 at 04:11:17PM +0900]: On Mon, 01 Sep 2014, Michael Prokop wrote: Ok. Did your upgrade also involve an update of the kernel/reboot of your system? Hmm, hard to say. I often update between kernels. So it might have been the same time I swtiched form 3.16 to 3.17-rc2. 3.17-rc2 isn't part of any Debian repos AFAICS, is that a self compiled one? blkid -o value -s UUID /dev/root no output. ok, as expected mount /dev/root on / type btrfs (rw,relatime,ssd,space_cache) devtmpfs on /dev type devtmpfs (rw,relatime,size=4041792k,nr_inodes=1010448,mode=755) [...] cat /proc/mounts rootfs / rootfs rw 0 0 /dev/root / btrfs rw,relatime,ssd,space_cache 0 0 devtmpfs /dev devtmpfs rw,relatime,size=4041792k,nr_inodes=1010448,mode=755 0 0 [...] rootfs / rootfs rw 0 0 /dev/root / btrfs rw,relatime,ssd,space_cache 0 0 devtmpfs /dev devtmpfs rw,relatime,size=4041792k,nr_inodes=1010448,mode=755 0 0 [...] ls -la /dev/root ls: cannot access /dev/root: No such file or directory This is strange, reporting /dev/root in /proc/mounts but not having the file/symlink actually. Please verify: * You're booting using GRUB * You used btrfs for the root filesystem also before the upgrade * initramfs-tools v0.115 generates an initramfs just fine If the answer to all those question is yes please test an older Linux kernel version as present in an official Debian repository. regards, -mika- signature.asc Description: Digital signature
Bug#678696: Event based block device handling (fixes USB and nested devices problem)
On Sun, Aug 31, 2014 at 10:14:18AM +0200, Michael Prokop wrote: Hi, f'up to our recent discussion we had on IRC * Goswin von Brederlow [Sat Jun 23, 2012 at 09:25:28PM +0200]: the attached patch adds an event based loop for block devices to the init script. New blockdevices are recorded in /run/initramfs/block-events by an udev rule as they appear. The init script repeadately waits for that and then calls /scripts/local-block/* with a list of new devices storedin NEWDEVS until $ROOT and $resume (if set) exists or a timeout is reached. This fixes the problem that USB devices take too long to be discovered and crypto, raid, lvm or multipath can't be started on them. It also adds support for arbitrary nestings of them, e.g. raid5 over raid1. [...] First of all thanks again for the patch and your helpful feedback on IRC. I've tested your patch based on top of current i-t git master (v0.116) with a setup like: BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 root=/dev/mapper/vg0-root ro quiet but it sadly fails to work as intended (it boots but doesn't find the block devices until the timeout is kicking in). I didn't investigate closer yet, but AFAICS it seems to be related to the fact that /dev/mapper/vg0-root doesn't exist at that time yet. If it boots after the timeout then the device must exist. So either the test for it is wrong or the device only gets created after the timeout. If you or someones else finds time to try and possibly further investigate I'd very much welcome and appreciate that. regards, -mika- Questions: Does your system boot without the patch? If not then you also need the lvm patch to provide the hook script that scans for a VG when new block devices are detected. Do you see any messages about vg0 being activated before the timeout or after? MfG Goswin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140901092406.GA23999@frosties
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Another accidental discovery: I have started to use a USB mouse recently, and when I leave the mouse plugged in when shutting down, the problem reoccurs. When I click Shutdown, then unplug the mouse, power down completes successfully. (Always assuming that I run only Debian between power on and power down.) Another observation: With the USB mouse plugged in, Ubuntu 14.04 runs into the same issue. So, Ubuntu will power down OK, whether or not I ran a mix of Debian and Ubuntu since last power on. It will, however, fail to power down when I leave the USB mouse plugged in. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5404c044.9060...@skynet.be
Bug#760215: linux-image-3.14-2-kirkwood: Not enough space in MTD RootFS1 (need 9768399 but is actually 9437184)
Package: src:linux Version: 3.14.15-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Upgrading the package linux-image-kirkwood that depends on this one. * What exactly did you do (or not do) that was effective (or ineffective)? dpkg-reconfigure the package reproduces the error. * What was the outcome of this action? The following error messages: Processing triggers for flash-kernel (3.21) ... flash-kernel: installing version 3.14-2-kirkwood Not enough space in MTD RootFS1 (need 9768399 but is actually 9437184). dpkg: error processing package flash-kernel (--configure): el subproceso instalado el script post-installation devolvió el código de salida de error 1 Se encontraron errores al procesar: flash-kernel * What outcome did you expect instead? Proper installation of the package. -- Package-specific info: This kernel could not be booted because it can't get installed. ** Model information Hardware: QNAP TS-41x Revision: ** PCI devices: 00:00.0 Host bridge [0600]: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC [11ab:6281] (rev 02) Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 9 Region 0: Memory at ignored (64-bit, prefetchable) Capabilities: access denied 00:01.0 SCSI storage controller [0100]: Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II [11ab:7042] (rev 02) Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 9 Region 0: Memory at e000 (64-bit, non-prefetchable) [size=1M] Region 2: I/O ports at 1000 [size=256] Capabilities: access denied Kernel driver in use: sata_mv ** USB devices: Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: armel (armv5tel) Kernel: Linux 3.9-1-kirkwood Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.14-2-kirkwood depends on: ii debconf [debconf-2.0] 1.5.53 ii initramfs-tools [linux-initramfs-tool] 0.115 ii kmod17-2 ii linux-base 3.5 ii module-init-tools 17-2 Versions of packages linux-image-3.14-2-kirkwood recommends: ii firmware-linux-free 3.3 ii uboot-mkimage2012.04.01-2 Versions of packages linux-image-3.14-2-kirkwood suggests: pn debian-kernel-handbook none pn fdutils none pn linux-doc-3.14 none Versions of packages linux-image-3.14-2-kirkwood is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimax none pn firmware-ipw2x00none pn firmware-ivtv none pn firmware-iwlwifinone pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information: linux-image-3.14-2-kirkwood/postinst/depmod-error-initrd-3.14-2-kirkwood: false linux-image-3.14-2-kirkwood/postinst/mips-initrd-3.14-2-kirkwood: linux-image-3.14-2-kirkwood/prerm/removing-running-kernel-3.14-2-kirkwood: true -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140901215142.29468.22709.reportbug@localhost
Bug#760119: /dev/disk/by-uuid: Is a directory
Hi Michael, On Mon, 01 Sep 2014, Michael Prokop wrote: 3.17-rc2 isn't part of any Debian repos AFAICS, is that a self compiled one? Yes, like all my kernels, since ever. * You're booting using GRUB Yes. * You used btrfs for the root filesystem also before the upgrade Yes. * initramfs-tools v0.115 generates an initramfs just fine Yes-No. It depends on the *running* kernel: - running 3.16 initramfs 0.115 and 0.116 can create proper initrams for *all* kernels, also for 17-rc2 - running 3.17-rc2 initramfs fails When I switch to a new kernel I normally to make oldconfig and check through the new options and that works. How to proceed? Do you want to close the bug because it is a 3.17-rc2 bug? Or search for the reason? Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140901230917.gb2...@auth.logic.tuwien.ac.at
Bug#760127: initramfs-tools: creating initrd fails
fwiw I commented-out line MODULES=dep (there's only one line in this file) /etc/initramfs-tools/initramfs.conf and installation(apt-get -f install) was able to complete while making an initrd image for kernel 3.14-2-amd64 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5405050c.5030...@videotron.ca
Bug#760239: fs/aufs/i_op.c:435:28: error: 'struct mutex' has no member named 'owner'
Package: linux-source Version: 3.14+59 Severity: normal Dear Maintainer, I am attempting to compile a realtime kernel on and for Jessie i386. I started with the configuration file /boot/config-3.14-2-686-pae and made two changes via menuconfig: Preemption Model= Fully Preemptible Kernel (RT) Timer frequency = 1000 HZ When I attempt to build the kernel package, it fails: 2014-09-01 16:26:54 root@dc86yxb1 /usr/src/linux-source-3.14 # make-kpkg --append-to-version -rt --initrd kernel_image exec make kpkg_version=13.014 -f /usr/share/kernel-package/ruleset/minimal.mk debian APPEND_TO_VERSION=-rt INITRD=YES == making target debian/stamp/conf/minimal_debian [new prereqs: ]== This is kernel package version 13.014. CC [M] fs/aufs/iinfo.o CC [M] fs/aufs/inode.o CC [M] fs/aufs/i_op.o fs/aufs/i_op.c: In function 'au_pin_hdir_set_owner': fs/aufs/i_op.c:435:28: error: 'struct mutex' has no member named 'owner' p-hdir-hi_inode-i_mutex.owner = task; ^ scripts/Makefile.build:308: recipe for target 'fs/aufs/i_op.o' failed make[3]: *** [fs/aufs/i_op.o] Error 1 scripts/Makefile.build:455: recipe for target 'fs/aufs' failed make[2]: *** [fs/aufs] Error 2 Makefile:847: recipe for target 'fs' failed make[1]: *** [fs] Error 2 make[1]: Leaving directory '/usr/src/linux-source-3.14' debian/ruleset/targets/common.mk:295: recipe for target 'debian/stamp/build/kernel' failed make: *** [debian/stamp/build/kernel] Error 2 TIA, David -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages linux-source depends on: ii linux-source-3.14 3.14.15-2 linux-source recommends no packages. linux-source suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140902002905.15231.47223.report...@dc86yxb1.holgerdanske.com
Bug#760119: /dev/disk/by-uuid: Is a directory
* Norbert Preining [Tue Sep 02, 2014 at 08:09:17AM +0900]: On Mon, 01 Sep 2014, Michael Prokop wrote: * initramfs-tools v0.115 generates an initramfs just fine Yes-No. It depends on the *running* kernel: - running 3.16 initramfs 0.115 and 0.116 can create proper initrams for *all* kernels, also for 17-rc2 - running 3.17-rc2 initramfs fails Ha perfect, that's what I was hoping for. :) (I really couldn't imagine that i-t 0.116 triggered your problem.) When I switch to a new kernel I normally to make oldconfig and check through the new options and that works. How to proceed? Do you want to close the bug because it is a 3.17-rc2 bug? Or search for the reason? I'm definitely interested in getting to the root of the problem. Could you please provide output of mount and cat /proc/mounts when running the 3.16 kernel? regards, -mika- signature.asc Description: Digital signature
