On Mon, Mar 15, 2010 at 12:58:31PM -0000, Scott James Remnant wrote:
> On Sun, 2010-03-14 at 22:44 +0000, Theodore Ts'o wrote:
>
> > On Sun, Mar 14, 2010 at 10:05:01PM -0000, Martin Pool wrote:
> > > I think this should be considered critical for Lucid, because
> > > 1- when you hit this, it can leave the filesystem unusable
> > > 2- it can presumably happen even if you don't use -D, because the fsck
> > > manpage says this only forces an operation that may sometimes happen
> > > anyhow
> >
> > I'm working on the airplane flight from Boston to San Francisco to get
> > e2fsprogs 1.41.11. It's going to be a bug-fix only release only, and
> > it'd be nice to get a freeze exception for it....
> >
> I'm sure we can do that; let me know when it's out and I'll chat to the
> RMs
It's out now, and a bunch of the bug fixes address Launchpad-reported
issues:
E2fsck will no longer give a fatal error and abort if the physical
device has been resized beyond 2**32 blocks. (Addresses Launchpad
Bug: #521648)
Debugfs has a bug fixed so that "logdump -b <blk>" now properly shows
the allocation status of the block <blk>. (Addresses Debian Bug:
#564084)
E2fsck now prints a much more emphatic and hopefully scary message
when a file system is detected as mounted while doing a read/write
check of the filesystem. Hopefully this will dissuade users from
thinking, "surely that message doesn't apply to *me*" :-(
(Addresses Launchpad Bug: #537483)
E2fsck -n will now always open the file system read-only. We now
disallow certain combination of options which previously were manual
exceptions; this is bad because it causes users to think they are
smarter than they really are. So "-n -c", "-n -l", "-n -L", and "-n
-D" are no longer supported. (Addresses Launchpad Bug: #537483)
In e2fsprogs 1.41.10, mke2fs would ask for confirmation to proceed if
it detected a badly aligned partition. Unfortunately, this broke some
distribution installation scripts, so it now just prints the warning
message and proceeds. (Addresses Red Hat Bug: #569021. Addresses
Launchpad Bug: #530071)
Mke2fs would take a long time to create very large journal files for
ext4. This was caused by a bug in ext2fs_block_iterate2(), which is
now fixed.
E2fsck now understands the EOFBLOCKS_FL flag which will be used in
2.6.34 kernels to make e2fsck not complain about blocks deliberately
fallocated() beyond an inode's i_size.
E2fsprogs 1.41.10 introduced a regression (in commit b71e018) where
e2fsck -fD can corrupt non-indexed directories when are exists one or
more file names which alphabetically sort before ".". This can happen
with ext2 filesystems or for small directories (take less than a lock)
which contain filenames that begin with a space or some other
punctuation mark. (Addresses Debian Bug: #573923, Addresses Launchpad
Bug: #525114)
- Ted
--
-D introduces corruption in directories
https://bugs.launchpad.net/bugs/525114
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
