From owner-freebsd-fs@FreeBSD.ORG Mon Oct 31 19:59:08 2005 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D500316A420 for ; Mon, 31 Oct 2005 19:59:08 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (geri.cc.fer.hr [161.53.72.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0549843D48 for ; Mon, 31 Oct 2005 19:59:07 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (localhost.cc.fer.hr [127.0.0.1]) by geri.cc.fer.hr (8.13.4/8.13.1) with ESMTP id j9VJqoDO069001; Mon, 31 Oct 2005 20:52:50 +0100 (CET) (envelope-from ivoras@fer.hr) Received: from localhost (ivoras@localhost) by geri.cc.fer.hr (8.13.4/8.13.1/Submit) with ESMTP id j9VJqmxu068998; Mon, 31 Oct 2005 20:52:49 +0100 (CET) (envelope-from ivoras@fer.hr) X-Authentication-Warning: geri.cc.fer.hr: ivoras owned process doing -bs Date: Mon, 31 Oct 2005 20:52:48 +0100 (CET) From: Ivan Voras Sender: ivoras@geri.cc.fer.hr To: Bruce Evans In-Reply-To: <20051101042444.K40281@delplex.bde.org> Message-ID: <20051031201719.S68800@geri.cc.fer.hr> References: <20051030183340.B19470@geri.cc.fer.hr> <46D894BD-16E0-4CBA-B40A-EEBAAC2547D2@classicalguitar.net> <20051031191139.J38757@delplex.bde.org> <20051031160354.G67271@geri.cc.fer.hr> <20051101042444.K40281@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org Subject: Re: ext2 large_file X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 19:59:08 -0000 On Tue, 1 Nov 2005, Bruce Evans wrote: > Unless the file system already has or had a large file. Possible > workarounds: > (1) Boot Linux and create a large file. Hopefully e2fsck only sets the > flag so you only have to do this once. I did this but e2fsck doesn't set the flag. Fortunately, I found out that e2fsprogs includes "debugfs" utility with which I manually set the flag. It works now! ext2 filesystem access is still a bit slower than with WindowsXP with ext2+ext3 IFS driver (~20.5MB/s vs ~25MB/s). The reason I brought up this subject is that I'm experimenting with using ext2 instead of msdosfs for exchanging data between the systems in dual-boot configuration. Because ext2 large_file support works now, I think it's much more safer and even somewhat faster (less fragmentation! FreeBSD's msdosfs looks like it's pessimized for fragmentation!) to use instead. I propose this patch to the mount_ext2fs manual page: --- mount_ext2fs.8_old Mon Oct 31 20:43:17 2005 +++ mount_ext2fs.8 Mon Oct 31 20:56:45 2005 @@ -60,6 +60,21 @@ .Xr mount 8 man page for possible options and their meanings. .El +.Sh BUGS +Unlike the original Linux implementation, the "large_file" +flag is not set automatically when first file larger than +2GB is created. Instead, +.Xr debugfs 8 +utility from the e2fsprogs port must be used to manually +set the flag with `feature large_file` command. Other than +this, large files are fully supported. + +Support for journaling (ext3) is missing, and filesystems that +have it enabled are treated as plain ext2 filesystems. +This means that +.Xr e2fsck 8 +will have to be used to repair the journal when the filesystem +is to be used in Linux. .Sh SEE ALSO .Xr mount 2 , .Xr unmount 2 ,