public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* What happened to mount option "noextents"
@ 2010-05-30 12:07 Peter Hallberg
  2010-05-30 12:32 ` tytso
  0 siblings, 1 reply; 5+ messages in thread
From: Peter Hallberg @ 2010-05-30 12:07 UTC (permalink / raw)
  To: linux-kernel


On Ubuntu 9.04 it is possible to mount an ext4 file system with the mount option "noextents" but on Ubuntu 10.04 it gives the error message: Ext4: Unrecognized mount option "noextents" in dmesg.
 		 	   		  
_________________________________________________________________
Surfa tryggt med Internet Explorer 8
http://www.microsoft.com/sverige/windows/internet-explorer/default.aspx

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: What happened to mount option "noextents"
  2010-05-30 12:07 What happened to mount option "noextents" Peter Hallberg
@ 2010-05-30 12:32 ` tytso
  2010-05-30 13:52   ` Peter Hallberg
  2010-05-30 13:53   ` Peter Hallberg
  0 siblings, 2 replies; 5+ messages in thread
From: tytso @ 2010-05-30 12:32 UTC (permalink / raw)
  To: Peter Hallberg; +Cc: linux-kernel

On Sun, May 30, 2010 at 02:07:06PM +0200, Peter Hallberg wrote:
> 
> On Ubuntu 9.04 it is possible to mount an ext4 file system with the
> mount option "noextents" but on Ubuntu 10.04 it gives the error
> message: Ext4: Unrecognized mount option "noextents" in dmesg.

Both the "extents" and "noexents" mount options were removed in newer
kernels.  If you want to turn on extents, the right answer is to use
the "tune2fs -O extents" command.  The "noextents" mount option didn't
really make much sense, since it basically was either no-op (if
extents were not enabled), and was mostly useless (if extents were
enabled in the file system), since it basically meant, "create new
files without using extents".  But since the old files were still
extents-based, it didn't make the file system any more compatible with
ext3 file systems.

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.

						- Ted

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: What happened to mount option "noextents"
  2010-05-30 12:32 ` tytso
@ 2010-05-30 13:52   ` Peter Hallberg
  2010-05-30 18:13     ` tytso
  2010-05-30 13:53   ` Peter Hallberg
  1 sibling, 1 reply; 5+ messages in thread
From: Peter Hallberg @ 2010-05-30 13:52 UTC (permalink / raw)
  To: tytso; +Cc: linux-kernel


> 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.

Also when I tryed tune2fs as you said, I got the following error message:

peter@sanna:~$ sudo tune2fs -O ^extents /dev/mapper/sannavg-home
tune2fs 1.41.4 (27-Jan-2009)
Clearing filesystem feature 'extent' not supported.
peter@sanna:~$ 

 		 	   		  
_________________________________________________________________
Klicka här!
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx

^ permalink raw reply	[flat|nested] 5+ messages in thread

* RE: What happened to mount option "noextents"
  2010-05-30 12:32 ` tytso
  2010-05-30 13:52   ` Peter Hallberg
@ 2010-05-30 13:53   ` Peter Hallberg
  1 sibling, 0 replies; 5+ messages in thread
From: Peter Hallberg @ 2010-05-30 13:53 UTC (permalink / raw)
  To: tytso; +Cc: linux-kernel


> 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.

Also when I tryed tune2fs as you said, I got the following error message:

peter@sanna:~$ sudo tune2fs -O ^extents /dev/mapper/sannavg-home
tune2fs 1.41.4 (27-Jan-2009)
Clearing filesystem feature 'extent' not supported.
peter@sanna:~$ 

 		 	   		  
_________________________________________________________________
Vårfina smileys till Messenger här!
http://springpack.msn.se

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: What happened to mount option "noextents"
  2010-05-30 13:52   ` Peter Hallberg
@ 2010-05-30 18:13     ` tytso
  0 siblings, 0 replies; 5+ messages in thread
From: tytso @ 2010-05-30 18:13 UTC (permalink / raw)
  To: Peter Hallberg; +Cc: linux-kernel

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
partition.


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

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

					- Ted

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-05-30 18:13 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-30 12:07 What happened to mount option "noextents" Peter Hallberg
2010-05-30 12:32 ` tytso
2010-05-30 13:52   ` Peter Hallberg
2010-05-30 18:13     ` tytso
2010-05-30 13:53   ` Peter Hallberg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox