From owner-freebsd-questions@FreeBSD.ORG Thu Oct 23 14:09:26 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FF6016A4B3 for ; Thu, 23 Oct 2003 14:09:26 -0700 (PDT) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF77743FAF for ; Thu, 23 Oct 2003 14:09:24 -0700 (PDT) (envelope-from andi_payn@speedymail.org) Received: from [10.1.0.9] ([68.65.235.109]) by mta11.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031023210927.JKIC24677.mta11.adelphia.net@[10.1.0.9]>; Thu, 23 Oct 2003 17:09:27 -0400 From: andi payn To: Miguel =?ISO-8859-1?Q?Gon=E7alves?= In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Message-Id: <1066943362.38004.1111.camel@verdammt.falcotronic.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 23 Oct 2003 14:09:23 -0700 Content-Transfer-Encoding: 8bit cc: freebsd-questions@freebsd.org Subject: Re: Migrating from Linux: mounting ext2fs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2003 21:09:26 -0000 On Wed, 2003-10-22 at 07:03, Miguel Gonçalves wrote: > How stable is the FreeBSD support for ext2fs? First, if you're planning to migrate your server permanently, you're probably better off reformatting in UFS: it's faster, and better for error recovery. And computers that mount nfs/Samba/whatever shares won't know the difference. If you insist on keeping your partitions in ext2fs: I've seen a couple of problems related to fsck. In particular, when a filesystem is dirty, fsck.ext2 sometimes finds and fixes the problems but then fails to mark the disk as clean (meaning that FreeBSD will refuse to mount it, if you've specified read/write, and it'll be checked again next time you reboot, and so forth). Personally, I've only seen this with ext3 (journaled) filesystems, but I don't know if that's universal. So, to be safe, you'll probably want an rc script that mounts -r any of your ext2 systems that were skipped. (Note that if /mnt/linux fails to mount because it was dirty, /mnt/linux/usr, etc. will also fail to mount.) This way, if the server gets hard-reset somehow, your users will still be able to access their files, even if they aren't able to update them, until you fix things.