platform_external_e2fsprogs/tests/m_raid_opt, branch master Unnamed repository; edit this file 'description' to name the repository. mke2fs: set overhead in super block 2020-01-27T04:10:05+00:00 Li Dongyang dongyangli@ddn.com 2020-01-27T03:06:36+00:00 59037c5357d39c6d0f14a0aff70e67dc13eafc84 If overhead is not recorded in the super block, it is calculated during mount in kernel, for bigalloc file systems it takes O(groups**2) in time. For a 1PB device with 32K cluster size it takes ~12 mins to mount, with most of the time spent on figuring out overhead. While we can not improve the overhead algorithm in kernel due to the nature of bigalloc, we can work out the overhead during mke2fs and set it in the super block, avoiding calculating it every time when it mounts. Overhead is s_first_data_block plus internal journal blocks plus the block and inode bitmaps, inode table, super block backups and group descriptor blocks for every group. This patch introduces ext2fs_count_used_clusters(), which calculates the clusters used in the block bitmap for the given range. When bad blocks are involved, it gets tricky because the blocks counted as overhead and the bad blocks can end up in the same allocation cluster. In this case we will unmark the bad blocks from the block bitmap, convert to cluster bitmap and get the overhead, then mark the bad blocks back in the cluster bitmap. Reset the overhead to zero when resizing, we can not simply count the used blocks as overhead like we do when mke2fs. The overhead can be calculated by kernel side during mount. Signed-off-by: Li Dongyang <dongyangli@ddn.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> 
If overhead is not recorded in the super block, it is calculated
during mount in kernel, for bigalloc file systems it takes
O(groups**2) in time.  For a 1PB device with 32K cluster size it takes
~12 mins to mount, with most of the time spent on figuring out
overhead.

While we can not improve the overhead algorithm in kernel due to the
nature of bigalloc, we can work out the overhead during mke2fs and set
it in the super block, avoiding calculating it every time when it
mounts.

Overhead is s_first_data_block plus internal journal blocks plus the
block and inode bitmaps, inode table, super block backups and group
descriptor blocks for every group.  This patch introduces
ext2fs_count_used_clusters(), which calculates the clusters used in
the block bitmap for the given range.

When bad blocks are involved, it gets tricky because the blocks
counted as overhead and the bad blocks can end up in the same
allocation cluster.  In this case we will unmark the bad blocks from
the block bitmap, convert to cluster bitmap and get the overhead, then
mark the bad blocks back in the cluster bitmap.

Reset the overhead to zero when resizing, we can not simply count the
used blocks as overhead like we do when mke2fs.  The overhead can be
calculated by kernel side during mount.

Signed-off-by: Li Dongyang <dongyangli@ddn.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
dumpe2fs: reduce dumpe2fs output to 80 columns or less 2014-12-14T02:51:48+00:00 Darrick J. Wong darrick.wong@oracle.com 2014-12-14T02:50:19+00:00 6aa8cff3ee8c528729357e3621ab38d2dc9657f1 Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> 
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
mke2fs: only print the low-level file system stats in verbose mode 2014-05-05T03:15:29+00:00 Theodore Ts'o tytso@mit.edu 2014-04-26T23:00:50+00:00 6d82e1f4c7af427975009063d387f66cf9672962 Also print the file system UUID if it is non-NULL. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 
Also print the file system UUID if it is non-NULL.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
mke2fs: sort option parsing, deprecate "-R" 2013-06-15T22:47:30+00:00 Andreas Dilger adilger@dilger.ca 2013-06-15T22:47:30+00:00 2a83b3c3741bdc9a1b2af73114c778f4b21a9ab1 A minor cleanup to order the command-line option parsing in alphabetical order, except for "-E" and "-R", which need to be co-located. Print a message that the "-R" option is deprecated. It has been deprecated since 2005 (commit c6a44136b9b). Signed-off-by: Andreas Dilger <adilger@dilger.ca> Signed-off-by: Theodore Ts'o <tytso@mit.edu> 
A minor cleanup to order the command-line option parsing in
alphabetical order, except for "-E" and "-R", which need to
be co-located.

Print a message that the "-R" option is deprecated.  It has
been deprecated since 2005 (commit c6a44136b9b).

Signed-off-by: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
tests: clean up sed filtering of test output 2013-06-15T22:44:09+00:00 Andreas Dilger adilger@dilger.ca 2013-06-15T22:44:09+00:00 f9fd342e568dbadaadbb0b242f14271cb384c38b The sed filters for test outputs that are used to remove build and test specific information (such as version strings, dates, times, UUIDs) were unconditionally deleting the first line of output. This would normally contain the tool version string, but in some cases contained other information that was being lost. This can lead to difficulty debugging test failures. The sed filtering has been changed to only remove the actual version strings. As well, similar filter strings were duplicated throughout many scripts, and "sed" and "tr" were often called multiple times in a pipeline. These have been consolidated into a single filter.sed file to avoid having to maintain these filters in multiple places. In a few cases, accidentally deleted messages have been restored to the expect output for the tests. In other cases, trivial whitespace has been changed in the expect files. Signed-off-by: Andreas Dilger <adilger@dilger.ca> Signed-off-by: Theodore Ts'o <tytso@mit.edu> 
The sed filters for test outputs that are used to remove build and
test specific information (such as version strings, dates, times,
UUIDs) were unconditionally deleting the first line of output.  This
would normally contain the tool version string, but in some cases
contained other information that was being lost.  This can lead to
difficulty debugging test failures.

The sed filtering has been changed to only remove the actual version
strings.  As well, similar filter strings were duplicated throughout
many scripts, and "sed" and "tr" were often called multiple times in
a pipeline.  These have been consolidated into a single filter.sed
file to avoid having to maintain these filters in multiple places.

In a few cases, accidentally deleted messages have been restored to
the expect output for the tests.  In other cases, trivial whitespace
has been changed in the expect files.

Signed-off-by: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
mke2fs: throttle allocating groups progress as well 2012-09-21T16:50:04+00:00 Theodore Ts'o tytso@mit.edu 2012-09-21T16:06:49+00:00 b2f5ce5516a0b6d261876884139043c8e6579f0a Throttle updates for the "Allocating Groups" progress updates to once a second as well. We now do this throttling in libext2fs, so we don't have to do this for each of mke2fs's progress updates, and because the updates from ext2fs_allocate_tables() come from within libext2fs anyway. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 
Throttle updates for the "Allocating Groups" progress updates to once
a second as well.  We now do this throttling in libext2fs, so we don't
have to do this for each of mke2fs's progress updates, and because the
updates from ext2fs_allocate_tables() come from within libext2fs
anyway.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
mke2fs: disable progress reporting in mke2fs.conf for regression tests 2012-09-17T00:43:07+00:00 Theodore Ts'o tytso@mit.edu 2012-09-17T00:43:07+00:00 a3e87bcc32a21b1420a15385e0183d58dcaf19b1 Add a configuration knob so the regression tests can disable progress reporting. This fixes a potential lack of predictability since the progress reports are now time based (once a second) which is problematic for regression tests which are comparing the expected output of mke2fs. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 
Add a configuration knob so the regression tests can disable progress
reporting.  This fixes a potential lack of predictability since the
progress reports are now time based (once a second) which is
problematic for regression tests which are comparing the expected
output of mke2fs.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Merge branch 'maint' into next 2009-10-05T00:40:46+00:00 Theodore Ts'o tytso@mit.edu 2009-10-05T00:40:46+00:00 95bcea9fc149e349865f9eb30988ad1b4e1c1342 Conflicts: configure configure.in misc/mke2fs.c 
Conflicts:
	configure
	configure.in
	misc/mke2fs.c
tests: Account for new mke2fs topology information 2009-10-04T20:21:13+00:00 Theodore Ts'o tytso@mit.edu 2009-10-04T20:21:13+00:00 a321afa8b7baca0ff90e06c1351b2054e61e11ee The previous commit adds a new line printed by mke2fs with the filesystem/device topology information. Update the regression test's expected output to account for this. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 
The previous commit adds a new line printed by mke2fs with the
filesystem/device topology information.  Update the regression test's
expected output to account for this.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
libext2fs: create generic numeric progress meters and use them 2009-08-23T23:20:03+00:00 Valerie Aurora Henson vaurora@redhat.com 2009-08-23T23:20:03+00:00 95fd65bb7fcf84e8d1e207f84b9d5a9f99626a38 With 64-bit file systems, mke2fs can take a long time to do things other than write inode tables. I exported the mke2fs numeric progress meter and used it for allocating group tables and the final file system flush. Signed-off-by: Valerie Aurora (Henson) <vaurora@redhat.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 
With 64-bit file systems, mke2fs can take a long time to do things
other than write inode tables.  I exported the mke2fs numeric progress
meter and used it for allocating group tables and the final file
system flush.

Signed-off-by: Valerie Aurora (Henson) <vaurora@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>