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 ? Thank you in advance. -- Harald Weis
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 :)
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 ? > > Thank you in advance. >You could use another file system such as Fat32 or NTFS (fuse ntfs from ports). OS X can read both of those. Apple has been moving away from UFS support in OS X for awhile; snow leopard is quite stale on this front. Luke
This problem is caused by a big-endian, little-endian difference between the OSX implementation of UFS and the FreeBSD implementation. http://forums.macosxhints.com/showthread.php?t=86385 I solved this problem for myself by installing MacFuse -Chris On Thu, Feb 18, 2010 at 7:26 AM, Harald Weis <hawei@free.fr> 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 ? > > Thank you in advance. > -- > Harald Weis > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
On Mon, Feb 22, 2010 at 02:51:59PM -0800, Chris Knight wrote:> This problem is caused by a big-endian, little-endian difference > between the OSX implementation of UFS and the FreeBSD implementation. > http://forums.macosxhints.com/showthread.php?t=86385Yes, that's a good reason why both ufs1 and ufs2 don't work.> > I solved this problem for myself by installing MacFuseMacFuse is not yet available for Snow Leopard (10.6). I've made some trials to understand the tar options and had a big surprise yesterday: tar seems to have an enormous bug. For example: tar -c -f etc.tar /etc tar -r -f etc.tar /home/me/.icewm/ tar -u -f etc.tar /etc The last command should not modify etc.tar. But that's not the case. There seems to be no difference between the -r and -u option. How on earth is this possible ? Harald