| To: | Ajeet Yadav <ajeet.yadav.77@xxxxxxxxx> |
|---|---|
| Subject: | Re: First 128KB of XFS partition is NULL. |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Mon, 21 Feb 2011 08:32:05 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <AANLkTindiB_D7shZKkrdkePM=xaAXCe1HAX5tPy87SCy@xxxxxxxxxxxxxx> |
| References: | <AANLkTindiB_D7shZKkrdkePM=xaAXCe1HAX5tPy87SCy@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
On Sun, Feb 20, 2011 at 11:22:34AM +0900, Ajeet Yadav wrote: > Dear All, > I have received a corrupted disk from team testing XFS, when I look > hexdump of partiton. Its 0000 in first 128KB. > Our kernel is 2.6.30.9 however we have backported XFS from 2.6.34, > Arch MIP with VIPT cache. > This arch previously had many issues but after properly implementing > "xfs: fix xfs to work with Virtually Indexed architectures " most > problem resolved. > > Can anyone make guess in what case first 128KB may become NULL, I seem > to be impossible because file system does not modify all 128KB at the > begining of partition at once. Something else wrote to the block device. Maybe a partitioning program, a boot loader or possibly something else entirely... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfstests 071 trips an ASSERT due to commit 055388a3188f56676c21e92962fc366ac8b5cb72, Dave Chinner |
|---|---|
| Next by Date: | [PATCH] Check for immutable flag in fallocate path, Marco Stornelli |
| Previous by Thread: | Re: First 128KB of XFS partition is NULL., Eric Sandeen |
| Next by Thread: | [PATCH] Check for immutable flag in fallocate path, Marco Stornelli |
| Indexes: | [Date] [Thread] [Top] [All Lists] |