Bug#509893: e2fsprogs: mkfs.ext4 produces unusable filesystem

View: New views
2 Messages — Rating Filter:   Alert me  

Bug#509893: e2fsprogs: mkfs.ext4 produces unusable filesystem

by Christoph Thomas :: Rate this Message:

Reply (Restricted by the Administrator) | View Threaded | Show Only this Message

Package: e2fsprogs
Version: 1.41.3-1
Followup-For: Bug #509893

Hi Ted,

sorry to bother you, but in my enviroment huge_file does not work:

With provided config file:

mkfs.ext4 /dev/mapper/hda11
mke2fs 1.41.3 (12-Oct-2008)
....
mount -t ext4 /dev/mapper/hda11 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/mapper/hda11,
       missing codepage or helper program, or other error

dmesg | tail
EXT4-fs: mballoc: 0 blocks 0 reqs (0 success)
EXT4-fs: mballoc: 0 extents scanned, 0 goal hits, 0 2^N hits, 0 breaks, 0 lost
EXT4-fs: mballoc: 3 generated and it took 46854
EXT4-fs: mballoc: 0 preallocated, 0 discarded
EXT4-fs: dm-5: Filesystem with huge files cannot be mounted read-write without CONFIG_LSF.

dumpe2fs  /dev/mapper/hda11
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg
sparse_super large_file huge_file uninit_bg dir_nlink extra_isize

without huge file:
mkfs.ext4 /dev/mapper/hda11
mount -t ext4 /dev/mapper/hda11 /mnt
EXT4 FS on dm-5, internal journal on dm-5:8
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
EXT4-fs: mounted filesystem with ordered data mode.

dumpe2fs  /dev/mapper/hda11
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent
flex_bg sparse_super large_file uninit_bg dir_nlink extra_isize

Best regards,
Christoph

-- System Information:
Debian Release: 5.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.28-0.2 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages e2fsprogs depends on:
ii  e2fslibs                      1.41.3-1   ext2 filesystem libraries
ii  libblkid1                     1.41.3-1   block device id library
ii  libc6                         2.7-16     GNU C Library: Shared libraries
ii  libcomerr2                    1.41.3-1   common error description library
ii  libss2                        1.41.3-1   command-line interface parsing lib
ii  libuuid1                      1.41.3-1   universally unique id library

e2fsprogs recommends no packages.

Versions of packages e2fsprogs suggests:
ii  e2fsck-static                 1.41.3-1   statically-linked version of the e
pn  gpart                         <none>     (no description available)
pn  parted                        <none>     (no description available)

-- no debconf information



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Bug#509893: e2fsprogs: mkfs.ext4 produces unusable filesystem

by Ted Ts'o :: Rate this Message:

Reply (Restricted by the Administrator) | View Threaded | Show Only this Message

On Sun, Dec 28, 2008 at 04:33:28PM +0100, Christoph Thomas wrote:
> Package: e2fsprogs
> Version: 1.41.3-1
> Followup-For: Bug #509893
>
> EXT4-fs: dm-5: Filesystem with huge files cannot be mounted read-write without CONFIG_LSF.

Is there a particular reason why you are choosing to build your kernel
without CONFIG_LSF?  This is really more of a kernel configuration
problem than anything else.  Unfortunately there is no way for mke2fs
to know whether or not the user has disabled CONFIG_LSF in their
kernel.

If you must disable CONFIG_LSF (it saves a massive 4 bytes per inode),
you can create the filesystem with mke2fs -O ^huge_file.  Or you can
edit /etc/mke2fs.conf.  Just remove "huge_file," from the
configuration stanza:

[fs_types]
        ext4 = {
                features = has_journal,extents,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
                inode_size = 256
        }

It may be possible to enhance the kernel to allow mounting a
filesystem with huge_file, but to force the system to fail open() or
stat() operations for files that are bigger than 2TB, and to prohibit
creating files larger than 2TB, but this would be a kernel fix, and
not anything we can do in mke2fs.

For I'm going to have to treat this as either a kernel or mke2fs.conf
misconfiguration.

Regards,

                                                - Ted



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...