lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 30 May 2010 14:13:00 -0400
To:	Peter Hallberg <>
Subject: Re: What happened to mount option "noextents"

On Sun, May 30, 2010 at 03:52:10PM +0200, Peter Hallberg wrote:
> > Basically, since we couldn't think of a good use case where the mount
> > options made sense, and ext4 has way too many mount options already, we
> > decided to remove them.
> The ext2/3 Windows driver doesn't support extents yet so one common
> use would be to do a mount -o remount,noextents and make a dir and
> copy the files you want to read from Windows to it. I think mount -o
> remount is something that is well known, if you use tune2fs you
> would need to do research before you know if the change starts
> working right a way or after a reboot or if it is valid only until
> reboot or is static, with mount -o remount there is no risk that you
> forget to set the flag back to the right value.

Yeah, but.... it's a horrible interface to support.  If one or more
directories happen to be extent-mapped, then Windows won't be able to
read it.  And if there are other files that are created while the
filesystem is remounted noextents, they will be created w/o extents,
which means that fallocate won't work.  The opportunities for
hard-to-understand failures are very large, and especially for
clueless Ubuntu users, it's just not something where I want to see
whining on Launchpad because they read somewhere that they could do
it, and it doesn't quite work right.

This is more something where if someone wants to patch the kernel do
something hacky like this, it's almost better because then it's not
something where we have to worry about confused users wondering why
something broke when they tried to use this interface.  Something that
works 80% of the time can be far worse than something that doesn't
work at all.

The real right answer is to fix the Windows driver to support extents.
Or create a separate filesystem just for moving files from Linux to
Windows --- or just write the files directly onto the Windows

> Also when I tryed tune2fs as you said, I got the following error message:
>$ sudo tune2fs -O ^extents /dev/mapper/sannavg-home
> tune2fs 1.41.4 (27-Jan-2009)
> Clearing filesystem feature 'extent' not supported.

Yes, right now you can only enable extents; it's not something you
can disable.

					- Ted
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists