| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c |
| From: | Timothy Shimmin <tes@xxxxxxx> |
| Date: | Fri, 02 Nov 2007 15:37:45 +1100 |
| Cc: | Jay Sullivan <jpspgd@xxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <472A87FA.7000804@xxxxxxxxxxx> |
| References: | <06CCEA2EB1B80A4A937ED59005FA855101AED1BE@xxxxxxxxxxxxxxxxxxxxxxx> <472A87FA.7000804@xxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.6 (Macintosh/20070728) |
Eric Sandeen wrote: Jay Sullivan wrote:I ran xfs_repair -L on the FS and it could be mounted again,Was it not even mountable before this, or why did you use the -L flag? If the log is corrupted that points to more problems... perhaps you've had some power loss & your write caches evaporated, and lvm doesn't do barriers?-eric BTW, I occasionally wonder about the reason for log corruptions. If we have an "evaporated" write cache that would stop a write from going but it wouldn't do a partial sector (< 512 byte) write, would it? I have presumed that sector writes complete or not and that is what the log code is based on. OOI, Jay, how did it fail to mount - what was the log msg? I presume you couldn't mount such that even the log couldn't be replayed? Did it fail during replay? --Tim |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c, Jay Sullivan |
|---|---|
| Next by Date: | Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c, David Chinner |
| Previous by Thread: | Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c, Eric Sandeen |
| Next by Thread: | xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c, Jay Sullivan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |