From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 23:03:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3ABE16A4B3 for ; Sun, 21 Sep 2003 23:03:28 -0700 (PDT) Received: from hueymiccailhuitl.mtu.ru (hueytecuilhuitl.mtu.ru [195.34.32.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 831AD43FCB for ; Sun, 21 Sep 2003 23:03:27 -0700 (PDT) (envelope-from sem@ciam.ru) Received: from ciam.ru (ppp132-89.dialup.mtu-net.ru [62.118.132.89]) by hueymiccailhuitl.mtu.ru (Postfix) with ESMTP id 9F282B76DD; Mon, 22 Sep 2003 10:03:22 +0400 (MSD) (envelope-from sem@ciam.ru) Message-ID: <3F6E90AB.6040203@ciam.ru> Date: Mon, 22 Sep 2003 10:03:23 +0400 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Evans References: <3F6D92EB.1020102@ciam.ru> <20030921132145.W68357@carver.gumbysoft.com> <20030921173331.S6867@ganymede.hub.org> <20030922113019.T17142@gamplex.bde.org> In-Reply-To: <20030922113019.T17142@gamplex.bde.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: -current brake ufs for -stable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Sep 2003 06:03:29 -0000 Bruce Evans wrote: > -current doesn't write extended attributes unless you enabled them. OK. I'm wrong. Really I don't understand a problem. Superblock was corrupted. I've fix it with fsck (from other sector). But I decided remake the FS and run newfs from -stable again. Now I write on it buth -stable and -current and no problems have now. May be it was an accident. > Most likely the problem is some breakage of compatibility of superblocks. > When I tried sharing a filesystem between RELENG_3 and -current a few > months ago, IIRC the obvious bugs were that RELENG_3 crashed on filesystems > written to be -current, and running RELENG_3's fdisk fixed the problem > but was not run automatically and it reported an alarming number of errors. Just the same happened. ---- Sem.