Attempt to treat "metadata" as a collectively singular noun.

Or at least more consistent.

Input from: matteo, ian

Improve grammar concerning "metadata".

Remove unnecessary space while here.

ext2fs: Add uninit_bg feature support.

From the linux tune2fs(8) manpage:
"Allow the kernel to initialize bitmaps and inode tables and keep a high
watermark for the unused inodes in a filesystem, to

ext2fs: Add uninit_bg feature support.

From the linux tune2fs(8) manpage:
"Allow the kernel to initialize bitmaps and inode tables and keep a high
watermark for the unused inodes in a filesystem, to reduce e2fsck(8) time.
This first e2fsck run after enabling this feature will take the full time,
but subsequent e2fsck runs will take only a fraction of the original time,
depending on how full the file system is."

Submitted by: Fedor Uporov
Differential Revision: https://reviews.freebsd.org/D11211

show more ...

ext2fs: Enable RO huge_file feature support.

We can have support for reading ext4 "huge" files but we can't write
(anything) on ext4. and some filesystem. Formally enable the feature so
that we can

ext2fs: Enable RO huge_file feature support.

We can have support for reading ext4 "huge" files but we can't write
(anything) on ext4. and some filesystem. Formally enable the feature so
that we can mount such filesystems.

Submitted by: Fedor Uponov
Differential Revision: https://reviews.freebsd.org/D11209

show more ...

ext2fs: Initial support for Extended Attributes.

Currently read-only.

Submitted by: Fedor Uporov
MFC after: 3 weeks
Differential Revision: https://reviews.freebsd.org/D10151

style(9) cleanups.

Just to reduce some of the issues found with indent(1).

MFC after: 1 week

Merge ^/head r303250 through r304235.

ext2fs: Add defines for some missing ext4 feature flags.

These are currently unused in our implementation and some even appear to
have not been implemented yet on linux but it is good to keep them f

ext2fs: Add defines for some missing ext4 feature flags.

These are currently unused in our implementation and some even appear to
have not been implemented yet on linux but it is good to keep them for
reference.

Obtained from: NetBSD (CVS Rev. 1.41)
MFC after: 1 month

show more ...

ext2fs(5): Cosmetic cleanups, mostly to the ext4 code.

Obtained from: NetBSD

MFH

Sponsored by: The FreeBSD Foundation

Update superblock and inode structs for ext4.

Reviewed by: pfg

MFH

Sponsored by: The FreeBSD Foundation

Merge ^/head r294169 through r294598.

MFH @r294567

ext2fs: Bring back the htree dir_index implementation.

The htree dir_index is perhaps one of the most characteristic
features of the linux ext3 implementation. It was removed
in r281670, due to repe

ext2fs: Bring back the htree dir_index implementation.

The htree dir_index is perhaps one of the most characteristic
features of the linux ext3 implementation. It was removed
in r281670, due to repeated bug reports.

Damjan Jovanic detected and fixed three bugs and did some
stress testing by building Apache OpenOffice on top of it
so it is now in good shape to bring back.

Differential Revision: https://reviews.freebsd.org/D5007

Submitted by: Damjan Jovanovic
Reviewed by: pfg
Tested by: pho
Relnotes: Yes
MFC after: 2 months (only 10.x)

show more ...

MFH r289384-r293170

Sponsored by: The FreeBSD Foundation

ext2: recognize ext4 INCOMPAT_RECOVER flag

This is a flag specific for journalling in ext4.
Add it to the list of ext4 features we ignore for
read-only purposes.

PR: 205668
MFC after: 1 week

Catch up with HEAD (r280229-r284686).

Merge sync of head

Merge from head

MFH: r280643-r281852

Sponsored by: The FreeBSD Foundation

MFH: r281668 through r281783

Sponsored by: The FreeBSD Foundation

Drop experimental dir_index support.

The htree directory index is a highly desirable feature for research
purposes and was meant to improve performance in our ext2/3 driver.
Unfortunately our implem

Drop experimental dir_index support.

The htree directory index is a highly desirable feature for research
purposes and was meant to improve performance in our ext2/3 driver.
Unfortunately our implementation has two problems:

- It never really delivered any performance improvement.
- It appears to corrupt the filesystem in undetermined circumstances.

Strictly speaking dir_index is not required for read/write support in
ext2/3 and our limited ext4 support still works fine without it.

Regain stability in the ext2 driver by removing it. We may need it back
(fixed) if we want to support encrypted ext4 support but thanks to the
wonders of version control we can always revert this change and bring it
back.

PR: 191895
PR: 198731
PR: 199309

MFC after: 5 days

show more ...

MFC @ r266724

An SVM update will follow this.

Merge head