| To: | Jay Sullivan <jpspgd@xxxxxxx> |
|---|---|
| Subject: | Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Fri, 2 Nov 2007 16:18:34 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <3A2120EF-3EB0-4CF1-8C4E-920B9688D51F@rit.edu> |
| References: | <3A2120EF-3EB0-4CF1-8C4E-920B9688D51F@rit.edu> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Thu, Nov 01, 2007 at 10:08:09PM -0400, Jay Sullivan wrote: > (Sorry if this is a dupe to the list; it has been a long day.) > > I have an XFS filesystem that has had the following happen twice in 3 > months, both times an impossibly large block number was requested. .... Sure sign of a corrupted btree. > I ran xfs_repair ?L on the FS and it could be mounted again, but how > long until it happens a third time? <shrug> What was the problem that xfs_repair fixed? BTW, why did you run xfs_repair -L? Also, when it happens next, what does xfs_check tell you is broken? Cheers, Dave. -- Dave Chinner Principal Engineer SGI Australian Software Group |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c, Timothy Shimmin |
|---|---|
| Next by Date: | Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c, Ralf Gross |
| Previous by Thread: | xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c, Jay Sullivan |
| Next by Thread: | Re: [PATCH] Implement fallocate, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |