From nobody@FreeBSD.org  Wed Jan 28 17:06:57 2009
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 77586106567D
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 28 Jan 2009 17:06:57 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 64A518FC23
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 28 Jan 2009 17:06:57 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n0SH6vlZ029507
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 28 Jan 2009 17:06:57 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id n0SH6vjW029506;
	Wed, 28 Jan 2009 17:06:57 GMT
	(envelope-from nobody)
Message-Id: <200901281706.n0SH6vjW029506@www.freebsd.org>
Date: Wed, 28 Jan 2009 17:06:57 GMT
From: Elmar Stellnberger <estellnb@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: xfs destroys itself after copying data
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         131084
>Category:       kern
>Synopsis:       [xfs] xfs destroys itself after copying data
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kan
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 28 17:10:01 UTC 2009
>Closed-Date:    Mon May 18 16:56:56 UTC 2009
>Last-Modified:  Mon May 18 16:56:56 UTC 2009
>Originator:     Elmar Stellnberger
>Release:        FreeBSD 7.1
>Organization:
>Environment:
FreeBSD scaleo.studiob 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan  1 14:37:25 UTC 2009     root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
>How-To-Repeat:

>Fix:
By the way is there any effort to support ext3? Ext2 partitions corrupt on crashes, xfs seems to be unstable. Besides this ext3 would pose the only way to share a common home partition between Linux, FreeBSD and Windows.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-fs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Jan 29 07:43:28 UTC 2009 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=131084 

From: Russell Cattelan <cattelan@thebarn.com>
To: bug-followup@FreeBSD.org, estellnb@gmail.com
Cc:  
Subject: Re: kern/131084: [xfs] xfs destroys itself after copying data
Date: Tue, 03 Feb 2009 10:53:25 -0600

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 Write support is not anywhere close to finished.
 
 I have a much more modern version of XFS working with FreeBSD current
 but it also is very early stages of being able to write the and xfs
 filesystem.
 
 
 - -Russell Cattelan
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.7 (Darwin)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iD8DBQFJiHaFNRmM+OaGhBgRAkYHAJ9lnFSN64WSKTdOnn35y2+7DlPl5wCfb//H
 CCCrq6fRlHtlhTt7+3pX/UM=
 =hRXC
 -----END PGP SIGNATURE-----
 
State-Changed-From-To: open->closed 
State-Changed-By: kan 
State-Changed-When: Mon May 18 16:54:59 UTC 2009 
State-Changed-Why:  
Writes are not supported at this time. 


Responsible-Changed-From-To: freebsd-fs->kan 
Responsible-Changed-By: kan 
Responsible-Changed-When: Mon May 18 16:54:59 UTC 2009 
Responsible-Changed-Why:  
Grab to close. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=131084 
>Unformatted:
 >mkfs.xfs /dev/ad6s7
 >mount -t xfs /dev/ad6s7 tmp
 >cp -a /Users/elm/.thunderbird tmp/
 >ls tmp
 ls: tmp: Input/output error
 >touch /mnt/tmp/hug
 touch: /mnt/tmp/hug: Input/output error
 > umount tmp
 umount: tmp: stat: Input/output error
 umount: tmp: unknown file system
 > mount| grep tmp
 /dev/ad6s7 on /mnt/tmp (xfs, local)
 > umount /dev/ad6s7
 > mount| grep tmp
 > xfs_check /dev/ad6s7
 ERROR: The filesystem has valuable metadata changes in a log which needs to
 be replayed.  Mount the filesystem to replay the log, and unmount it before
 re-running xfs_check.  If you are unable to mount the filesystem, then use
 the xfs_repair -L option to destroy the log and attempt a repair.
 Note that destroying the log may cause corruption -- please attempt a mount
 of the filesystem before doing this.
 > mount -t xfs /dev/ad6s7 tmp
 mount: /dev/ad6s7 : Operation not supported
 
