Date: Thu, 24 Jan 2008 13:06:56 +1100
From: David Chinner <dgc@sgi.com>
To: Fong Vang <sudoyang@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS file system corrupted beyond repair?
Message-ID: <20080124020656.GE155259@sgi.com>
References: <4f52331f0801230915p1d3c4c3ala010d9066addb411@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4f52331f0801230915p1d3c4c3ala010d9066addb411@mail.gmail.com>
User-Agent: Mutt/1.4.2.1i
Sender: xfs-bounce@oss.sgi.com
Errors-to: xfs-bounce@oss.sgi.com
Precedence: bulk

On Wed, Jan 23, 2008 at 09:15:49AM -0800, Fong Vang wrote:
> One of our servers cannot mount an XFS file system after reboot.  xfs_check
> and xfs_repair cannot fix the problem.  Both indicate that there are no
> valid superblock can be found.

What happened before the reboot?

FWIW, is this on a md block device? If so, did it reconstruct correctly?

To find out what is in the superblock, can you post the output
of 'xfs_db -r -c "sb 0" -c p <dev>'?

Also, it could be instructive to see the exact errors check and
repair were outputting. Can you post the output of failing
xfs_repair/xfs_check?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group