From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 117421] New: e2fsprogs: mke2fs ignores sparse_super2 when also using extent or 64bit
Date: Sat, 30 Apr 2016 11:08:21 +0000 [thread overview]
Message-ID: <bug-117421-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=117421
Bug ID: 117421
Summary: e2fsprogs: mke2fs ignores sparse_super2 when also
using extent or 64bit
Product: File System
Version: 2.5
Kernel Version: 4.2.8
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: kellyc@surroundbackgrounds.com
Regression: No
Package: e2fsprogs
Version: 1.42.12-1.1
Severity: normal
File: /sbin/mke2fs
When creating an ext3/ext4 filesystem the sparse_super2 option is ignored and
defaults back to sparse_super when using extent or 64bit.
mke2fs should respect the use of sparse_super2 when using either or both -O
extent or -O 64bit.
Normal formatting using sparse_super and works as expected creating 2 backup
superblocks.
mke2fs /dev/sdq1 -t ext4 -b 4096 -O sparse_super2
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 61049344 4k blocks and 15269888 inodes
Filesystem UUID: cdaa09a3-dcb2-473a-9da8-7517a632db14
Superblock backups stored on blocks:
32768, 61046784
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Using extent option with sparse_super2 creates more than 2 backup superblocks.
mke2fs /dev/sdq1 -t ext4 -b 4096 -O sparse_super2 -O extent
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 61049344 4k blocks and 15269888 inodes
Filesystem UUID: 4634627d-bd41-4f96-923d-21746f12cf1f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Using 64bit option with sparse_super2 creates more than 2 backup superblocks.
mke2fs /dev/sdq1 -t ext4 -b 4096 -O sparse_super2 -O 64bit
mke2fs 1.42.12 (29-Aug-2014)
Creating filesystem with 61049344 4k blocks and 15269888 inodes
Filesystem UUID: ef3ed24c-0183-40c9-b2de-0b8e9bb868bb
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
mke2fs (mkfs.ext4) should respect the sparse_super2 option when used with 64bit
or extent.
-- System Information:
Debian Release: 8.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.8-1-pve (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages e2fsprogs depends on:
ii e2fslibs 1.42.12-1.1
ii libblkid1 2.25.2-6
ii libc6 2.19-18+deb8u3
ii libcomerr2 1.42.12-1.1
ii libss2 1.42.12-1.1
ii libuuid1 2.25.2-6
ii util-linux 2.25.2-6
e2fsprogs recommends no packages.
Versions of packages e2fsprogs suggests:
pn e2fsck-static <none>
pn gpart <none>
ii parted 3.2-7
-- no debconf information
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2016-04-30 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 11:08 bugzilla-daemon [this message]
2016-05-09 2:47 ` [Bug 117421] e2fsprogs: mke2fs ignores sparse_super2 when also using extent or 64bit bugzilla-daemon
2016-05-10 21:40 ` bugzilla-daemon
2016-05-10 21:41 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-117421-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.