From: Timothy Shimmin <tes@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: David Greaves <david@dgreaves.com>, David Chinner <dgc@sgi.com>,
xfs@oss.sgi.com,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>, asg-qa <asgqa@sgi.com>
Subject: Re: Regression- XFS won't mount on partitioned md array
Date: Mon, 19 May 2008 13:46:57 +1000 [thread overview]
Message-ID: <4830F831.40102@sgi.com> (raw)
In-Reply-To: <482FBD4C.20608@sandeen.net>
Eric Sandeen wrote:
> Eric Sandeen wrote:
>> Eric Sandeen wrote:
>>
>>> I'll see if I have a little time today to track down the problem.
>>
>> Does this patch fix it for you? Does for me though I can't yet explain
>> why ;)
>>
>> http://www.linux.sgi.com/archives/xfs/2008-05/msg00190.html
>>
>> -Eric
>
> So what's happening is that xfs is trying to read a page-sized IO from
> the last sector of the log... which goes off the end of the device.
> This looks like another regression introduced by
> a9759f2de38a3443d5107bddde03b4f3f550060e, but fixed by Christoph's patch
> in the URL above, which should be headed towards -stable.
>
> (aside: it seems that this breaks any external log setup where the log
> consists of the entire device... but I'd have expected the xfsqa suite
> to catch this...?)
>
The only way I can see that we'd catch this (by testing external logs)
in the current qa setup is
if one sets up SCRATCH_LOGDEV and/or TEST_LOGDEV and USE_EXTERNAL.
There are no specific tests to test out external logs (there is 044 but
it requires the env vars set anyway) such as using a loop back device
for the log. Perhaps we should do this.
I should check that our QA group are setting the vars in some runs.
--Tim
prev parent reply other threads:[~2008-05-19 3:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 17:11 Regression- XFS won't mount on partitioned md array David Greaves
2008-05-16 17:16 ` Justin Piszcz
2008-05-16 18:05 ` David Greaves
2008-05-16 18:35 ` Oliver Pinter
2008-05-17 14:48 ` David Greaves
2008-05-17 15:20 ` David Greaves
2008-05-16 18:59 ` Eric Sandeen
2008-05-17 14:46 ` David Greaves
2008-05-17 15:15 ` Eric Sandeen
2008-05-17 19:10 ` Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system David Lethe
2008-05-17 19:29 ` Peter Rabbitson
2008-05-17 20:26 ` Guy Watkins
2008-05-26 11:17 ` Jan Engelhardt
2008-05-19 2:54 ` Neil Brown
2008-05-17 23:18 ` Regression- XFS won't mount on partitioned md array Eric Sandeen
2008-05-18 5:23 ` Eric Sandeen
2008-05-18 8:48 ` David Greaves
2008-05-18 15:38 ` Eric Sandeen
2008-05-24 13:33 ` RFI for 2.6.25.5 : " David Greaves
2008-05-24 13:52 ` Willy Tarreau
2008-05-24 15:39 ` Eric Sandeen
2008-05-19 3:46 ` Timothy Shimmin [this message]
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=4830F831.40102@sgi.com \
--to=tes@sgi.com \
--cc=asgqa@sgi.com \
--cc=david@dgreaves.com \
--cc=dgc@sgi.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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