summaryrefslogtreecommitdiff
path: root/resize
Commit message (Collapse)AuthorAgeFilesLines
* resize2fs: remove unused variable from adjust_superblock()Eric Biggers2023-01-271-4/+0
| | | | | | | | | | | | | | | In adjust_superblock(), the 'group_block' variable is declared and set, but it is never actually used. Remove it. This addresses the following compiler warning with clang -Wall: blk64_t group_block; ^ resize2fs.c:1119:11: warning: variable 'group_block' set but not used [-Wunused-but-set-variable] Reviewed-by: Lukas Czerner <lczerner@redhat.com> Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* Avoid potential NULL dereference when argv[0]Theodore Ts'o2022-08-111-1/+3
| | | | | | | | | Addresses-Coverity-Bug: 1500772 Addresses-Coverity-Bug: 1500769 Addresses-Coverity-Bug: 1500767 Addresses-Coverity-Bug: 1500758 Addresses-Coverity-Bug: 1500756 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* Fix Coverity unintentional integer overflow warningsTheodore Ts'o2022-08-111-1/+1
| | | | | | | | | | Neither of these two warnings can actually happen (other limits will be hit first), but widening the integer to a 64-bit unsigned integer is an cheap and effective way to silence the Coverity warnings. Addresses-Coverity-Bug: 1500760 Addresses-Coverity-Bug: 1507886 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: use ext2fs_get_arrayzero() instead of ext2fs_get_array() + memset()Theodore Ts'o2022-08-111-3/+1
| | | | | | | | | | The use of ext2fs_get_arrayzero() to replace using ext2fs_get_array() + memset() does not result in any functional change, but it (a) is slightly more efficient, and (b) makes it easier for Coverity to avoid signalling a false positive. Addresses-Coverity-Bug: 1500763 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: open device read-only when -P is passedMichael Hudson-Doyle2022-08-111-2/+6
| | | | | | | | | | | We ran into this because we noticed that resize2fs -P $device was triggering udev events. I added a very simple test that just checks resize2fs -P on a file lacking the w bit succeeds. Signed-off-by: Michael Hudson-Doyle <michael.hudson@ubuntu.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: trim resize to cluster boundaryKiselev, Oleg2022-08-111-0/+6
| | | | | | | | | | | | This patch rounds down the size provided to resize2fs to the nearest cluster boundary for bigalloc filesystems. This is similar to the trimming already done for page boundary alignment. Aligning the size in the user space provides the right value feedback from the resize2fs command, which is a better user experience than trimming the size in the kernel. Signed-off-by: Oleg Kiselev <okiselev@amazon.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* Fix UBSAN if s_log_groups_per_flex is 31Theodore Ts'o2022-08-072-2/+2
| | | | | | | | | | It is logal (albeit rare) for the number of block groups per flex_bg to 2**31 (which effectively means to put all of the block groups into a single flex_bg). However, in that case "1 << 31" is undefined on architectures with a 32-bit integer. Fix this UBSAN complaint by using "1U << 31" instead. Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: fix to respect the environment variable E2FSPROGS_FAKE_TIMETheodore Ts'o2022-08-041-2/+4
| | | | | | | | | | | | | | | When performing an off-line resize, if an inode's block map needs to be updated, resize2fs will update the inode's ctime. In addition, if inode numbers need to be renumbered due to the file system shrinking forcing the inode table to be shrunk, any directories which need to be modified will have their ctime and mtime updated. If the E2FSPROGS_FAkE_TIME environment variable is set, when the file system is opened, fs->now will be set to this value, and resize2fs needs to use it instead of calling time(0) to get their current time. Addresses-Google-Bug: 230874381 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* dumpe2fs, resize2fs: avoid memory leak on error pathzhanchengbin2022-05-111-2/+2
| | | | | | Link: https://lore.kernel.org/r/cbfd9852-bc89-1e83-f101-36fd29a0e70e@huawei.com Signed-off-by: zhanchengbin <zhanchengbin1@huawei.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* Use mallinfo2 instead of mallinfo if availableLukas Czerner2022-04-281-3/+10
| | | | | | | | | | mallinfo has been deprecated with GNU C library version 2.33 in favor of mallinfo2 which works exactly the same as mallinfo but with larger field widths. Use mallinfo2 if available. Signed-off-by: Lukas Czerner <lczerner@redhat.com> Reviewed-by: Andreas Dilger <adilger@dilger.ca> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: remove unused variable 'c'Lukas Czerner2022-04-281-1/+1
| | | | | | Signed-off-by: Lukas Czerner <lczerner@redhat.com> Reviewed-by: Andreas Dilger <adilger@dilger.ca> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* reisze2fs: sanity check free block group counts when calculating minimum sizeTheodore Ts'o2021-12-281-2/+11
| | | | | | | | | | | | | | | | | | If one or more block group descriptor's free blocks count is insane, it's possible this can lead to a infinite loop in the function calculate_minimum_resize_size(), which is called by resize2fs -P or resize2fs -M. Add some sanity checks to avoid this. In the case where the file system is corrupt, this will result in resize2fs -P reporting an incorrect value, but that's OK, since when we try to do an actual resize operation, resize2fs requires that the file system be freshly checked using e2fsck. https://github.com/tytso/e2fsprogs/issues/94 Fixes: ac94445fc01f ("resize2fs: make minimum size estimates more reliable for mounted fs") Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: optimize resize2fs_calculate_summary_stats()Theodore Ts'o2021-09-301-54/+25
| | | | | | | | | Speed up an off-line resize of a 10GB file system to 64TB located on tmpfs from 90 seconds to 16 seconds by extracting block group bitmaps using a population count function to count the blocks in use instead checking each bit in the block bitmap. Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: adjust new size of the file system to allow a successful resizeTheodore Ts'o2021-09-303-6/+90
| | | | | | | | | | | | | | | | | | | | | | The previous commit in this series (commit 50088b1996cc: "resize2fs: attempt to keep the # of inodes valid by removing the last bg") allows a successful off-line resize of a file system with the default 16k inode ratio to be grown to support a 64TB storage device by dropping the last block group so the number of inodes is just below the maximum 2**32-1 number of inodes. However, this is not a complete solution, for two reasons. First, this adjustment happens after resize2fs has started potentially making changes to the file system in the off-line (unmounted) case, which means resize2fs will do a lot of unnecessary work. Secondly, in the on-line resize case, passing the original requested size to the kernel causes the kernel fail the online resize request. So teach resize2fs to adjust the new size of the file system much earlier, which avoids both problems. Signed-off-by: Theodore Ts'o <tytso@mit.edu> Reviewed-by: Leah Rumancik <leah.rumancik@gmail.com>
* resize2fs: attempt to keep the # of inodes valid by removing the last bgTheodore Ts'o2021-09-301-0/+9
| | | | | | | | | | | | | | | | | If a the 10GB file system (with the default inode ratio size of 16k) is resized to 64TB, the number of inodes will become 2**32 --- one above the maximum allowed number of inodes of 2**32-1. In adjust_fs_info(), we already try drop the last block group if there isn't sufficient space in the last block group to support the metadata for that block group. So if dropping the last block group allows the number of inodes to valid, we should try that as well. In some cases this will mean resizing a file system to 64TB will result in it be resized to a size of 64TB - 128MB, which is close enough for government work. Addresses-Google-Bug: 199105099 Signed-off-by: Theodore Ts'o <tytso@mit.edu> Reviewed-by: Leah Rumancik <leah.rumancik@gmail.com>
* Change "filesystem" to "file system" in the man pagesTheodore Ts'o2021-08-151-17/+17
| | | | | | | To improve consistency, use "file system" in all of the man pages in preference over "filesystem". Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs.8.in: clarify the description of the progress bar optionTheodore Ts'o2021-08-151-3/+4
| | | | | | Addresses-Debian-Bug: #979411 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* AOSP: Move system_shared_libs into target.bionic clauseColin Cross2021-07-271-2/+0
| | | | | | | | | | | | | | | Use target.bionic.system_shared_libs when it is used to limit the default shared libraries (as opposed to remove them completely). This avoids attempting to add a host dependency on libc when system_shared_libs is modified to apply to all variants. Also remove system_shared_libs from static binaries where it has no effect, and consolidate it into e2fsprogs-defaults. Bug: 193559105 Test: m checkbuild Change-Id: I2d447b006afc783f4acd6c1acd93f338a68a01ed From AOSP commit: 48fa7248112701c30d3cabfb8d3360b2408d6491
* AOSP: [LSC] Add LOCAL_LICENSE_KINDS to external/e2fsprogsBob Badour2021-07-271-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added SPDX-license-identifier-0BSD SPDX-license-identifier-Apache-2.0 SPDX-license-identifier-BSD SPDX-license-identifier-GPL SPDX-license-identifier-GPL-2.0 SPDX-license-identifier-LGPL SPDX-license-identifier-LGPL-2.0 SPDX-license-identifier-LGPL-2.1 SPDX-license-identifier-LGPL-3.0 SPDX-license-identifier-MIT legacy_notice legacy_unencumbered to: Android.bp Added SPDX-license-identifier-0BSD SPDX-license-identifier-BSD SPDX-license-identifier-GPL SPDX-license-identifier-GPL-2.0 SPDX-license-identifier-LGPL SPDX-license-identifier-LGPL-2.1 SPDX-license-identifier-LGPL-3.0 SPDX-license-identifier-MIT legacy_unencumbered to: lib/Android.bp Added SPDX-license-identifier-0BSD SPDX-license-identifier-BSD SPDX-license-identifier-GPL-2.0 SPDX-license-identifier-MIT to: lib/et/Android.bp Added SPDX-license-identifier-0BSD SPDX-license-identifier-MIT to: lib/ss/Android.bp Added SPDX-license-identifier-Apache-2.0 to: contrib/android/Android.bp Added SPDX-license-identifier-Apache-2.0 SPDX-license-identifier-GPL to: contrib/Android.bp Added SPDX-license-identifier-BSD to: lib/uuid/Android.bp Added SPDX-license-identifier-GPL to: resize/Android.bp Added SPDX-license-identifier-GPL SPDX-license-identifier-GPL-2.0 to: debugfs/Android.bp Added SPDX-license-identifier-GPL SPDX-license-identifier-GPL-2.0 SPDX-license-identifier-LGPL to: e2fsck/Android.bp Added SPDX-license-identifier-GPL SPDX-license-identifier-GPL-2.0 SPDX-license-identifier-LGPL SPDX-license-identifier-LGPL-2.1 SPDX-license-identifier-LGPL-3.0 legacy_unencumbered to: lib/ext2fs/Android.bp Added SPDX-license-identifier-GPL SPDX-license-identifier-LGPL to: lib/e2p/Android.bp Added SPDX-license-identifier-GPL SPDX-license-identifier-LGPL SPDX-license-identifier-LGPL-2.1 SPDX-license-identifier-LGPL-3.0 to: lib/blkid/Android.bp misc/Android.bp Added SPDX-license-identifier-GPL SPDX-license-identifier-MIT to: lib/support/Android.bp Bug: 68860345 Bug: 151177513 Bug: 151953481 Test: m all Exempt-From-Owner-Approval: janitorial work Change-Id: I239a04a83f12ba051be911d18f6df4ae77fb3368 From AOSP commit: e86522c572b5715b85889cf8ca1c52a5cc350ca7
* resize2fs: close the file system on errors or early exitsTheodore Ts'o2021-03-061-20/+30
| | | | | | | | | When resize2fs exits early, perhaps because of an error, we should free the file system so that if MMP is in use, the MMP block is reset. This also releases the memory to avoid memory leak reports. Addresses-Debian-Bug: #984472 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: avoid allocating over the MMP blockTheodore Ts'o2021-03-061-0/+5
| | | | | | | | | | | | | | When resizing past the point where the reserve inode has reserved space for the block group descriptors to expand, and resize2fs (in an offline resize) needs to move the allocation bitmaps and/or inode table around, it's possible for resize2fs to allocate over the MMP block, which would be bad. Prevent this from happening by reserving the MMP block as a file system metadata block (which it is) in resize2fs's accounting. Addresses-Debian-Bug: #984472 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: prevent block bitmap warnings when doing extreme fs expansionsTheodore Ts'o2021-02-251-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | This commit fixes a bug where if a small file system is resized to ridiculous sizes, such that the size of the resized block group descriptor blocks exceed the original file system, and this would result in resize2fs triggering a large number of scary warning messages: Illegal block number passed to ext2fs_test_block_bitmap #12440 for block bitmap for broken.img This can be replicated via: ./misc/mke2fs broken.img -b 1024 -T default truncate -s +1500G broken.img ./resize/resize2fs broken.img Fortunately, aside from triggering these warning messages, the bug had no other bad effects. https://github.com/tytso/e2fsprogs/issues/60 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* Fix clang warnings on architectures with a 64-bit longTheodore Ts'o2021-02-115-31/+55
| | | | | | | | | | | | On most systems where we compile e2fsprogs, the u64 type is an unsigned long long. However, there are platforms (such as the PowerPC) where a long 64-bits and so u64 is typedef'ed to be unsigned long instead of a unsigned long long. Fix this by using explicit casts in printf statements. For scanf calls, we need to receive the value into a unsigned long long, and then assign it to a u64, after doing range checks. Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* Merge branch 'maint' into nextTheodore Ts'o2021-01-281-0/+1
|\
| * AOSP: tune2fs/resize2fs: make vendor_ramdisk_available.Yifan Hong2021-01-281-0/+1
| | | | | | | | | | | | | | | | | | The vendor_ramdisk variant is dynamic, unlike the ramdisk variant. Test: builds Google-Bug-Id: 173425293 Change-Id: I45547b5ea99aae98727121c038129844b7930ed6 From AOSP commit: 073ede3200afeffd82889cb61a71fa1947314476
* | Only build resize2fs.static when running "make all-static"Theodore Ts'o2021-01-231-1/+1
| | | | | | | | | | Fixes: 93df80d2409d ("Teach makefiles... the target all-static") Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* | ext2fs: move calculate_summary_stats to ext2fs libHarshad Shirwadkar2021-01-211-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | The function calculate_summary_stats sets the global metadata of the file system. Tune2fs had this function defined statically in tune2fs.c. Fast commit replay needs this function to set global metadata at the end of the replay phase. So, move this function to libext2fs. Signed-off-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com> Reviewed-by: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* | Enable threaded support for e2fsprogs' applications.Theodore Ts'o2021-01-211-1/+1
| | | | | | | | Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* | Merge branch 'maint' into nextTheodore Ts'o2021-01-192-0/+15
|\ \ | |/
| * Define MKDIR_P in the Makefile.in files instead in MCONFIG.inTheodore Ts'o2020-10-041-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | In the case where mkdir -p is not thread-safe (for example, if the build environment is using busybox's mkdir) the configure script will fall back to the slow (but safe) install-sh script. In that case MKDIR_P will be using a relative pathname; so we can't use speed optimization of defining configure substitutions in MCONFIG.in, since the substitution will be different depending on depth of the subdirectory in the Makefile.in file. https://github.com/tytso/e2fsprogs/issues/51 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
| * resize2fs: prevent block group descriptors from overflowing the first bgTheodore Ts'o2020-10-021-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For 1k block file systems, resizing a file system larger than 1073610752 blocks will result in the size of the block group descriptors to be so large that it will overlap with the backup superblock in block group #1. This problem can be reproduced via: mke2fs -t ext4 /tmp/foo.img 200M resize2fs /tmp/foo.img 1T e2fsck -f /tmp/foo.img https://github.com/tytso/e2fsprogs/issues/50 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* | Teach makefiles to build all static programs using the target all-staticTheodore Ts'o2020-04-101-0/+2
| | | | | | | | Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* | Merge tag 'v1.45.6' into nextTheodore Ts'o2020-03-211-11/+37
|\ \ | |/ | | | | v1.45.6
| * AOSP: tune2fs, resize2fs: make ramdisk binaries.Jaegeuk Kim2020-03-201-18/+29
| | | | | | | | | | | | | | Bug: 149391799 Change-Id: I5183755915710e28a603e3f718f16813ea9991a0 Signed-off-by: Jaegeuk Kim <jaegeuk@google.com> From AOSP commit: a13a88d0d557a396f63702fb8db008487e2384d7
| * AOSP: Allow resize2fs to compile with BUILD_HOST_staticDario Freni2020-03-201-7/+22
| | | | | | | | | | | | | | Bug: 144477678 Test: BUILD_HOST_static=1 m resize2fs; m resize2fs Change-Id: I0986deccfe496153e662dcc3cc2fb1ffb6973c21 From AOSP commit: 2c767b86591c64cd7b84c5619e8d8b8a0afd557e
* | mke2fs: set overhead in super blockLi Dongyang2020-01-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Merge branch 'maint' into nextTheodore Ts'o2019-11-141-4/+4
|\ \ | |/
| * resize2fs: make minimum size estimates more reliable for mounted fsJan Kara2019-11-101-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, the estimate of minimum filesystem size is using free blocks counter in the superblock. The counter generally doesn't get updated while the filesystem is mounted and thus the estimate is very unreliable for a mounted filesystem. For some usecases such as automated partitioning proposal to the user it is desirable that the estimate of minimum filesystem size is reasonably accurate even for a mounted filesystem. So use group descriptor counters of free blocks for the estimate of minimum filesystem size. These get updated together with block being allocated and so the resulting estimate is more accurate. Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* | AOSP: support the stable_inodes featureEric Biggers2019-10-311-0/+6
|/ | | | | | | | | | | | | | | | | Reserve the codepoint for EXT4_FEATURE_COMPAT_STABLE_INODES, allow it to be set and cleared, and teach resize2fs to forbid shrinking the filesystem if it is set. This feature will allow the use of encryption policies where the inode number is included in the IVs (initialization vectors) for encryption, so data would be corrupted if the inodes were to be renumbered. For more details, see the kernel patchset: https://lkml.kernel.org/linux-fsdevel/20191021230355.23136-1-ebiggers@kernel.org/T/#u Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> From AOSP commit: 9aa30c254dd57df54f00c5d520b7ac867ad7ca68
* Merge branch 'maint' into nextTheodore Ts'o2019-02-101-0/+1
|\
| * AOSP: E2fsprogs: fix ODR issueAndreas Gampe2019-02-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Do not use whole_static_libs and shared_libs at the same time. Fix up clients. Signed-off-by: Theodore Ts'o <tytso@mit.edu> Bug: 123590866 Test: mmma external/e2fsprogs Change-Id: I36d184dd878de2beacbb17c306e47076b44d68bb From AOSP commit: fece156b105719c782351e447298de073d4dab04
* | libext2fs: refactor code which fixes up the checksums in an extent treeTheodore Ts'o2018-10-211-54/+2
|/ | | | | | | | | | | | The code to recalculate the checksums in an extent tree (which is needed after an inode is relocated so it has a different inode number) was duplicated in tune2fs and resize2fs. In addition, this work could be done in a much more efficient way inside lib/ext2fs/extent.c. This commit creates a new library function which corrects the checksums in an inode's extent tree, named: ext2fs_fix_extents_checksums() Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: update checksums in the extent tree's relocated blockTheodore Ts'o2018-10-201-12/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When shrinking an file system, and we need to relocate an inode, the checksums in its extent tree must get updated to reflect its new inode number. When doing this, we need to do this *after* we update the extent tree to reflect any blocks which need to be relocated due to the file system shrink operation. Otherwise, in the case where only an interior node of the extent tree needs to get relocated, and none of the entries in that node need to be adjusted, the checksum for that interior node is updated in the old copy of that block, and then after the extent tree is updated to use the new copy of that interior node, the extent tree is left with an invalid checksum. This is a relatively rare case, since it requires the following conditions to be true: *) The metadata checksum feature must be enabled. *) An inode needs to be relocated. *) The inode needs to have an interior node. *) The block for that interior node needs to be relocated. *) None of blocks addressed by entries in that interior node needs to be relocated. When all of these conditions are true, though, the file system is left with corrupted with bad checksum for the extent tree block. Addresses-Launchpad-Bug: 1798562 Signed-off-by: Theodore Ts'o <tytso@mit.edu> Reported-by: Jean-Baptiste Lallement <jean-baptiste.lallement@ubuntu.com>
* AOSP: ODR violation in resize2fs during host buildJiyong Park2018-10-121-1/+0
| | | | | | | | | | | Bug: 112062612 Test: $ m SANITIZE_HOST=address $OUT_DIR/host/linux-x86/bin/resize2fs $OUT_DIR/host/linux-x86/bin/llvm-symbolizer $ $OUT_DIR/host/linux-x86/bin/resize2fs Signed-off-by: Theodore Ts'o <tytso@mit.edu> Change-Id: I72a8c183eb887137e3a414043b3d54771aa4eedc From AOSP commit: 9ba4dd69cfbf312c6015d5b007566e2467203f5e
* Remove obsolete files from the repositoryTheodore Ts'o2018-08-181-11/+0
| | | | | | | | They are removed when we generate the tarball, and they serve no useful purpose, so let's remove them. This will be help us to create the tarball using git archive more easily. Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* build: use MKDIR_P instead of MKINSTALLDIRSRoss Burton2018-08-111-2/+2
| | | | Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize2fs: Remove the real kilobytes rant from man pageLukas Czerner2018-07-221-12/+4
| | | | | | | | | Remove the rant about the "real" kilobytes from the man page and just make it more clear that the suffixed units are representing power-of-two units as we do in mke2fs man page. Also add terabytes to the list. Signed-off-by: Lukas Czerner <lczerner@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* tests: explicitly force resize2fs's use of lazy (or not)Theodore Ts'o2018-06-261-2/+3
| | | | | | | | | | | | Resize2fs will not enable lazy_itable if the kernel apparently does not support that feature. This will cause spurious test failures when the tests are running on such a system (or where sysfs is not mounted). So for the purposes of the regression test we need to force the use of lazy_itable so that the results conform to expected golden output. Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* Update Makefile.in files using "make depend"Theodore Ts'o2018-06-251-12/+12
| | | | Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* resize: remove calculation of unused variableTheodore Ts'o2018-06-241-8/+1
| | | | | Fix-Coverty-Bug: 1398367 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
View Lorry Controller Status