From: Eric Sandeen <sandeen@sandeen.net>
To: "Arkadiusz Bubała" <arkadiusz.bubala@open-e.com>
Cc: xfs@oss.sgi.com
Subject: Re: [BUG] XFS: Assertion failed: atomic_read(&pag->pag_ref) == 0, file: fs/xfs/xfs_mount.c, line: 272
Date: Wed, 22 May 2013 09:04:48 -0500 [thread overview]
Message-ID: <519CD080.2030501@sandeen.net> (raw)
In-Reply-To: <519C7D97.50909@open-e.com>
On 5/22/13 3:11 AM, Arkadiusz Bubała wrote:
> Hello,
>> On Tue, May 21, 2013 at 02:23:20PM +0200, Arkadiusz Bubała wrote:
>>
>>> Hello,
>>> I've got a call trace which should be fixed by "drop buffer io
>>> reference when a bad bio is built" patch
>>> (http://patchwork.xfs.org/patch/3956/). Error occured on already
>>> patched Linux kernel 3.2.42.
>>>
>> That's an old kernel. Can you reproduce on a current TOT kernel?
>> It's entirely possible that this problem has been fixed as we
>> definitely mae some changes to the mount error handling path since
>> 3.2....
>>
>>
> Ok. I'll try.
>>> Test environment consist two machines target and initiator.
>>> First machine works as target with QLogic Corp. ISP2432-based 4Gb
>>> Fibre Channel device. Storage is placed on two KINGSTON SNV425S SSD
>>> working as RAID0 array. RAID is managed by LSI MegaRAID SAS 1068
>>> controller.
>>> Second machine works as initiator with the same QLogic card.
>>>
>>> After few days of running test script I got following call trace and
>>> XFS stopped working.
>>>
>> Can you narrow this down from "takes several days" to the simplest
>> possible reproducer? It happened due to IO errors during mount, so
>> maybe you can did that part out of your script and give us a test
>> case that reproduces on the first mount?
>>
>>
> I 'll try. This errors occurs only on heavy load.
> Is there any possibility to simulate I/O errors on XFS filesystem?
You can use something like a dm-flakey or md-faulty block devices perhaps.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-22 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 12:23 [BUG] XFS: Assertion failed: atomic_read(&pag->pag_ref) == 0, file: fs/xfs/xfs_mount.c, line: 272 Arkadiusz Bubała
2013-05-21 12:31 ` Arkadiusz Bubała
2013-05-21 18:26 ` Ben Myers
2013-05-22 8:06 ` Arkadiusz Bubała
2013-05-21 23:39 ` Dave Chinner
2013-05-22 8:11 ` Arkadiusz Bubała
2013-05-22 14:04 ` Eric Sandeen [this message]
2013-05-27 12:40 ` Arkadiusz Bubała
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=519CD080.2030501@sandeen.net \
--to=sandeen@sandeen.net \
--cc=arkadiusz.bubala@open-e.com \
--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