Your message dated Sun, 26 Oct 2014 22:37:18 -0400 with message-id <[email protected]> and subject line Re: Bug#766799: resizing root partition with resize2fs makes system unbootable has caused the Debian Bug report #766799, regarding resizing root partition with resize2fs makes system unbootable to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 766799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766799 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: e2fsprogs Version: 1.42.12-1 Severity: grave Dear Maintainer, Fortunately, this bug happened on a virtual machine, so I can repeat the experiment if needed. I have a virtual machine with a 1GB hdd and jessie installed on it. The hdd has only one partition which is /dev/sda1, and formatted as ext2. At first, I enlarge (via virtualbox "vboxmanage" command) the hdd size to 2GB. Then boot the virtual machine. Then enlarge the root partition to 2GB with cfdisk. Then reboot. Everything is fine. Then do # resize2fs /dev/sda1 It says something like "/dev/sda1 is now 2000061 (1k) blocks long". Then reboot. Grub says "error: unknown filesystem" and drops to rescue prompt. (It might be bug in grub, not e2fsprogs - I'm not sure. Grub version is 2.00-22) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages e2fsprogs depends on: ii e2fslibs 1.42.12-1 ii libblkid1 2.20.1-5.11 ii libc6 2.19-11 ii libcomerr2 1.42.12-1 ii libss2 1.42.12-1 ii libuuid1 2.20.1-5.11 ii util-linux 2.20.1-5.11 e2fsprogs recommends no packages. Versions of packages e2fsprogs suggests: pn e2fsck-static <none> pn gpart <none> pn parted <none> -- no debconf information
--- End Message ---
--- Begin Message ---OK, I see what's going on. How are you creating the root file system, originally? It's getting created without the resize inode being initialized: Filesystem features: filetype sparse_super With the default /etc/mke2fs.conf, the command: mke2fs -t ext2 /tmp/foo.img 32M creates a file system with the following filesystem features (as displayed by dumpe2fs): Filesystem features: ext_attr resize_inode dir_index filetype sparse_super So you must be doing something non-standard when you create the file system. Without the resize_inode, when doing an online resize, resize2fs, ends up falling back to using the meta_bg format, resulting in the following filesystem features: Filesystem features: filetype meta_bg sparse_super Apparently graub doesn't know how to deal with meta_bg, so it calls the file system an invalid format. Anyway, it's partially a grub shortcoming, and partially caused by the fact that you created the ext2 file system without the resize inode. - Ted
--- End Message ---
