From owner-freebsd-stable@FreeBSD.ORG Fri Feb 19 09:11:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D19B1065672; Fri, 19 Feb 2010 09:11:40 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 285128FC12; Fri, 19 Feb 2010 09:11:40 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id o1J9BXNq017666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 19 Feb 2010 01:11:33 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id o1J9BX1r017665; Fri, 19 Feb 2010 01:11:33 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA08562; Fri, 19 Feb 10 01:06:40 PST Date: Fri, 19 Feb 2010 01:03:37 -0800 From: perryh@pluto.rain.com To: hawei@free.fr, ivoras@freebsd.org Message-Id: <4b7e53e9.ncAxiSQAvpijczMn%perryh@pluto.rain.com> References: <20100218152601.GA3076@pollux.local.net> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Incorrect super block X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2010 09:11:40 -0000 Ivan Voras wrote: > On 02/18/10 16:26, Harald Weis wrote: > > Has anybody encountered the following problem ? > > > > Mac OS X does recognize FreeBSD partitions on USB disks, but > > doesn't want to mount them because ``Incorrect super block''. > > This is extremely annoying for my ``client'' because he relies > > on dayly backups on USB keys. Is there a solution ? > > Are you using UFS1 or UFS2? If one, try the other :) This is not the first time I've heard of one OS having problems with another OS' instantiation of UFS. For the particular application at hand, I'd use tar(1) to collect the files into a single stream and write the tarfile onto a USB key formatted as FAT32. OS X should have no trouble reading a FreeBSD tarfile.