From: Timothy Shimmin <tes@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Jay Sullivan <jpspgd@rit.edu>, xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c
Date: Fri, 02 Nov 2007 15:37:45 +1100 [thread overview]
Message-ID: <472AA999.6090900@sgi.com> (raw)
In-Reply-To: <472A87FA.7000804@sandeen.net>
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
next prev parent reply other threads:[~2007-11-02 4:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 20:06 xfs_force_shutdown called from file fs/xfs/xfs_trans_buf.c Jay Sullivan
2007-11-02 2:14 ` Eric Sandeen
2007-11-02 2:22 ` Jay Sullivan
2007-11-02 2:30 ` Eric Sandeen
2007-11-02 9:07 ` Ralf Gross
2007-11-02 16:10 ` Eric Sandeen
2007-11-02 14:00 ` Jay Sullivan
2007-11-02 14:49 ` Jay Sullivan
2007-11-14 15:05 ` Jay Sullivan
2007-11-15 3:26 ` Eric Sandeen
2007-11-02 4:37 ` Timothy Shimmin [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 2:08 Jay Sullivan
2007-11-02 5:18 ` David Chinner
[not found] <B3EDBE0F860AF74BAA82EF17A7CDEDC660BE05A3@svits26.main.ad.rit.edu>
2007-12-21 2:01 ` Jay Sullivan
2008-01-03 15:55 ` Jay Sullivan
2008-08-04 16:55 ` Richard Freeman
2009-02-24 13:04 Federico Sevilla III
2009-02-24 22:46 ` Dave Chinner
2009-02-25 10:00 ` Federico Sevilla III
2009-02-25 11:51 ` Michael Monnerie
2009-02-25 18:47 ` Federico Sevilla III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=472AA999.6090900@sgi.com \
--to=tes@sgi.com \
--cc=jpspgd@rit.edu \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox