udevd / ext4 issue mounting 2.6.35-rc5
in [Kernel]
|
Prev: drivers/gpu/drm/radeon/r600_blit.c: fix possible NULL pointer derefernce
Next: Your patch: ARM: AMBA: Add pclk definition for platforms using primecells
From: Luis R. Rodriguez on 20 Jul 2010 20:40 I have been reluctant to boot to 2.6.35-rc due to the large set of regression list and the amount of work I needed to actually get done on 2.6.35. Last I checked the regression list it was getting small so I gave it a spin today. No luck. I get some bootup error from udevd and ext2/ext3/ext4, something like this: EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240) EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) VFS: Mounted root (ext4 filesystem) readonly on device 8:1 Freeing unused kernel memory: 708k freed Write protecting the kernel read-only data: 102040k Freeing unused kernel memory: 764k freed Freeing unused kernel memory: 1796k freed udevd: failed to create queue file: No such file or directory udevd: error creating queue file The picture: http://bombadil.infradead.org/~mcgrof/images/2010/ext4-option-240-fails-2.6.35-rc5.jpg I then decided to pull Linus' latest but it didn't help either. I don't recall seeing this reported on the regression list yet. Essentially I cannot move forward after this happens, even on single user boot and disabling wireless, which was my main suspect first as I'm using wireless-testing.git. I can certainly bisect but first wanted to see if this was already known. mcgrof(a)tux ~/wireless-testing (git::sfo-02)$ grep CONFIG_EXT .config CONFIG_EXTRA_FIRMWARE="" CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4_FS=y CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set Let me know if you need more details. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Daniel J Blueman on 21 Jul 2010 04:50 Hi Luis, On 21 July 2010 01:36, Luis R. Rodriguez <mcgrof(a)gmail.com> wrote: > I have been reluctant to boot to 2.6.35-rc due to the large set of > regression list and the amount of work I needed to actually get done > on 2.6.35. Last I checked the regression list it was getting small so > I gave it a spin today. No luck. I get some bootup error from udevd > and ext2/ext3/ext4, something like this: > > EXT3-fs (sda1): error: couldn't mount because of unsupported optional > features (240) > EXT2-fs (sda1): error: couldn't mount because of unsupported optional > features (240) > EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) This succeeded. > VFS: Mounted root (ext4 filesystem) readonly on device 8:1 > Freeing unused kernel memory: 708k freed > Write protecting the kernel read-only data: 102040k > Freeing unused kernel memory: 764k freed > Freeing unused kernel memory: 1796k freed > udevd: failed to create queue file: No such file or directory > udevd: error creating queue file It looks like you need to enable: CONFIG_DEVTMPFS CONFIG_DEVTMPFS_MOUNT > The picture: > > http://bombadil.infradead.org/~mcgrof/images/2010/ext4-option-240-fails-2.6.35-rc5.jpg > > I then decided to pull Linus' latest but it didn't help either. I > don't recall seeing this reported on the regression list yet. > Essentially I cannot move forward after this happens, even on single > user boot and disabling wireless, which was my main suspect first as > I'm using wireless-testing.git. > > I can certainly bisect but first wanted to see if this was already known. > > > mcgrof(a)tux ~/wireless-testing (git::sfo-02)$ grep CONFIG_EXT .config > CONFIG_EXTRA_FIRMWARE="" > CONFIG_EXT2_FS=y > CONFIG_EXT2_FS_XATTR=y > CONFIG_EXT2_FS_POSIX_ACL=y > CONFIG_EXT2_FS_SECURITY=y > # CONFIG_EXT2_FS_XIP is not set > CONFIG_EXT3_FS=y > # CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set > CONFIG_EXT3_FS_XATTR=y > CONFIG_EXT3_FS_POSIX_ACL=y > CONFIG_EXT3_FS_SECURITY=y > CONFIG_EXT4_FS=y > CONFIG_EXT4_FS_XATTR=y > CONFIG_EXT4_FS_POSIX_ACL=y > CONFIG_EXT4_FS_SECURITY=y > # CONFIG_EXT4_DEBUG is not set > > Let me know if you need more details. > > �Luis -- Daniel J Blueman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Luis R. Rodriguez on 21 Jul 2010 21:10 On Wed, Jul 21, 2010 at 1:43 AM, Daniel J Blueman <daniel.blueman(a)gmail.com> wrote: > Hi Luis, > > On 21 July 2010 01:36, Luis R. Rodriguez <mcgrof(a)gmail.com> wrote: >> I have been reluctant to boot to 2.6.35-rc due to the large set of >> regression list and the amount of work I needed to actually get done >> on 2.6.35. Last I checked the regression list it was getting small so >> I gave it a spin today. No luck. I get some bootup error from udevd >> and ext2/ext3/ext4, something like this: >> >> EXT3-fs (sda1): error: couldn't mount because of unsupported optional >> features (240) >> EXT2-fs (sda1): error: couldn't mount because of unsupported optional >> features (240) >> EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) > > This succeeded. Heh, OK :) >> VFS: Mounted root (ext4 filesystem) readonly on device 8:1 >> Freeing unused kernel memory: 708k freed >> Write protecting the kernel read-only data: 102040k >> Freeing unused kernel memory: 764k freed >> Freeing unused kernel memory: 1796k freed >> udevd: failed to create queue file: No such file or directory >> udevd: error creating queue file > > It looks like you need to enable: > > CONFIG_DEVTMPFS > CONFIG_DEVTMPFS_MOUNT Thanks, it also turned out that when I upgraded from Ubuntu 9.10 to Ubuntu 10.04 it replaced my own /sbin/installkernel so this was likely another issue. My /sbin/installkernel changes allow for easy initramfs installation on Debian/Ubuntu but my patches have been ignored my the maintainer. --- installkernel-ubuntu-10.04 2010-07-21 18:03:34.607678010 -0700 +++ installkernel 2010-01-29 13:17:10.000000000 -0800 @@ -36,7 +36,8 @@ # Create backups of older versions before installing updatever () { if [ -f "$dir/$1-$ver" ] ; then - mv "$dir/$1-$ver" "$dir/$1-$ver.old" + #mv "$dir/$1-$ver" "$dir/$1-$ver.old" + rm -f "$dir/$1-$ver" "$dir/$1-$ver.old" fi cat "$2" > "$dir/$1-$ver" @@ -75,5 +76,16 @@ if [ -f "$config" ] ; then updatever config "$config" fi + +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) + +case $LSB_RED_ID in +"Ubuntu") + update-initramfs -c -k $ver + update-grub + ;; +*) + ;; +esac exit 0 But anyway I also now get another boot failure with: mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /sys on /root/sys failed: No such file or directory http://bombadil.infradead.org/~mcgrof/images/2010/bleh-boot-2.6.35-rc5.jpg Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Daniel J Blueman on 22 Jul 2010 05:20 On 22 July 2010 02:06, Luis R. Rodriguez <mcgrof(a)gmail.com> wrote: > On Wed, Jul 21, 2010 at 1:43 AM, Daniel J Blueman > <daniel.blueman(a)gmail.com> wrote: >> Hi Luis, >> >> On 21 July 2010 01:36, Luis R. Rodriguez <mcgrof(a)gmail.com> wrote: >>> I have been reluctant to boot to 2.6.35-rc due to the large set of >>> regression list and the amount of work I needed to actually get done >>> on 2.6.35. Last I checked the regression list it was getting small so >>> I gave it a spin today. No luck. I get some bootup error from udevd >>> and ext2/ext3/ext4, something like this: >>> >>> EXT3-fs (sda1): error: couldn't mount because of unsupported optional >>> features (240) >>> EXT2-fs (sda1): error: couldn't mount because of unsupported optional >>> features (240) >>> EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) >> >> This succeeded. > > Heh, OK :) > >>> VFS: Mounted root (ext4 filesystem) readonly on device 8:1 >>> Freeing unused kernel memory: 708k freed >>> Write protecting the kernel read-only data: 102040k >>> Freeing unused kernel memory: 764k freed >>> Freeing unused kernel memory: 1796k freed >>> udevd: failed to create queue file: No such file or directory >>> udevd: error creating queue file >> >> It looks like you need to enable: >> >> CONFIG_DEVTMPFS >> CONFIG_DEVTMPFS_MOUNT > > Thanks, it also turned out that when I upgraded from Ubuntu 9.10 to > Ubuntu 10.04 it replaced my own /sbin/installkernel so this was likely > another issue. My /sbin/installkernel changes allow for easy initramfs > installation on Debian/Ubuntu but my patches have been ignored my the > maintainer. > > --- installkernel-ubuntu-10.04 �2010-07-21 18:03:34.607678010 -0700 > +++ installkernel � � � 2010-01-29 13:17:10.000000000 -0800 > @@ -36,7 +36,8 @@ > �# Create backups of older versions before installing > �updatever () { > � if [ -f "$dir/$1-$ver" ] ; then > - � �mv "$dir/$1-$ver" "$dir/$1-$ver.old" > + � �#mv "$dir/$1-$ver" "$dir/$1-$ver.old" > + � �rm -f "$dir/$1-$ver" "$dir/$1-$ver.old" > � fi > > � cat "$2" > "$dir/$1-$ver" > @@ -75,5 +76,16 @@ > �if [ -f "$config" ] ; then > � updatever config "$config" > �fi > + > +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) > + > +case $LSB_RED_ID in > +"Ubuntu") > + � � � update-initramfs -c -k �$ver > + � � � update-grub > + � � � ;; > +*) > + � � � ;; > +esac > > �exit 0 > > But anyway I also now get another boot failure with: > > mount: mounting /dev on /root/dev failed: No such file or directory > mount: mounting /sys on /root/sys failed: No such file or directory Hmm...the scripts in the initrd are not doing what is expected - perhaps if you didn't use: linux$ fakeroot make-kpkg --append-to-version -luis1 --initrd kernel-image ....or if there are eg initrd script modifications on the filesystem when it cooked the initd. You could just try eg: http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.35-9-generic_2.6.35-9.14_amd64.deb ....although it will regenerate it's initrd, so may suffer the same fate. > http://bombadil.infradead.org/~mcgrof/images/2010/bleh-boot-2.6.35-rc5.jpg > > �Luis -- Daniel J Blueman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Luis R. Rodriguez on 23 Jul 2010 13:00
On Thu, Jul 22, 2010 at 2:10 AM, Daniel J Blueman <daniel.blueman(a)gmail.com> wrote: > On 22 July 2010 02:06, Luis R. Rodriguez <mcgrof(a)gmail.com> wrote: >> On Wed, Jul 21, 2010 at 1:43 AM, Daniel J Blueman >> <daniel.blueman(a)gmail.com> wrote: >>> Hi Luis, >>> >>> On 21 July 2010 01:36, Luis R. Rodriguez <mcgrof(a)gmail.com> wrote: >>>> I have been reluctant to boot to 2.6.35-rc due to the large set of >>>> regression list and the amount of work I needed to actually get done >>>> on 2.6.35. Last I checked the regression list it was getting small so >>>> I gave it a spin today. No luck. I get some bootup error from udevd >>>> and ext2/ext3/ext4, something like this: >>>> >>>> EXT3-fs (sda1): error: couldn't mount because of unsupported optional >>>> features (240) >>>> EXT2-fs (sda1): error: couldn't mount because of unsupported optional >>>> features (240) >>>> EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) >>> >>> This succeeded. >> >> Heh, OK :) >> >>>> VFS: Mounted root (ext4 filesystem) readonly on device 8:1 >>>> Freeing unused kernel memory: 708k freed >>>> Write protecting the kernel read-only data: 102040k >>>> Freeing unused kernel memory: 764k freed >>>> Freeing unused kernel memory: 1796k freed >>>> udevd: failed to create queue file: No such file or directory >>>> udevd: error creating queue file >>> >>> It looks like you need to enable: >>> >>> CONFIG_DEVTMPFS >>> CONFIG_DEVTMPFS_MOUNT >> >> Thanks, it also turned out that when I upgraded from Ubuntu 9.10 to >> Ubuntu 10.04 it replaced my own /sbin/installkernel so this was likely >> another issue. My /sbin/installkernel changes allow for easy initramfs >> installation on Debian/Ubuntu but my patches have been ignored my the >> maintainer. >> >> --- installkernel-ubuntu-10.04 2010-07-21 18:03:34.607678010 -0700 >> +++ installkernel 2010-01-29 13:17:10.000000000 -0800 >> @@ -36,7 +36,8 @@ >> # Create backups of older versions before installing >> updatever () { >> if [ -f "$dir/$1-$ver" ] ; then >> - mv "$dir/$1-$ver" "$dir/$1-$ver.old" >> + #mv "$dir/$1-$ver" "$dir/$1-$ver.old" >> + rm -f "$dir/$1-$ver" "$dir/$1-$ver.old" >> fi >> >> cat "$2" > "$dir/$1-$ver" >> @@ -75,5 +76,16 @@ >> if [ -f "$config" ] ; then >> updatever config "$config" >> fi >> + >> +LSB_RED_ID=$(/usr/bin/lsb_release -i -s) >> + >> +case $LSB_RED_ID in >> +"Ubuntu") >> + update-initramfs -c -k $ver >> + update-grub >> + ;; >> +*) >> + ;; >> +esac >> >> exit 0 >> >> But anyway I also now get another boot failure with: >> >> mount: mounting /dev on /root/dev failed: No such file or directory >> mount: mounting /sys on /root/sys failed: No such file or directory > > Hmm...the scripts in the initrd are not doing what is expected - > perhaps if you didn't use: > linux$ fakeroot make-kpkg --append-to-version -luis1 --initrd kernel-image I am not using that to build my kernels I just build my kernels with make sudo make modules_install install > ...or if there are eg initrd script modifications on the filesystem > when it cooked the initd. I haven't modified any initrd scripts. > You could just try eg: > http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.35-9-generic_2.6.35-9.14_amd64.deb Going to give that a shot, thanks. > ...although it will regenerate it's initrd, so may suffer the same fate. OK we'll see then. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |