All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
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: Tue, 21 May 2013 13:26:30 -0500	[thread overview]
Message-ID: <20130521182630.GJ20028@sgi.com> (raw)
In-Reply-To: <519B6915.2010407@open-e.com>

Hey Arkadiusz,

On Tue, May 21, 2013 at 02:31:17PM +0200, Arkadiusz Bubała wrote:
> On 21.05.2013 14:23, 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.
> >
> >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.
> >
> Sorry I provided incomplete dmesg logs. These should provide more
> information:
> 
> [90011.884812] XFS (dm-46): metadata I/O error: block 0x1 ("xfs_trans_read_buf") error 5 buf count 512
> [90011.941376] XFS (dm-46): xlog_recover_check_summary agf read failed agno 0 error 5
> [90011.987890] XFS (dm-46): metadata I/O error: block 0x2 ("xfs_trans_read_buf") error 5 buf count 512
> [90012.044179] XFS (dm-46): xlog_recover_check_summary agi read failed agno 0 error 5
> [90012.092176] XFS (dm-46): metadata I/O error: block 0x7d0001 ("xfs_trans_read_buf") error 5 buf count 512
> [90012.150379] XFS (dm-46): xlog_recover_check_summary agf read failed agno 1 error 5
> [90012.196776] XFS (dm-46): metadata I/O error: block 0x7d0002 ("xfs_trans_read_buf") error 5 buf count 512
> [90012.196780] XFS (dm-46): xlog_recover_check_summary agi read failed agno 1 error 5
> [90012.196791] XFS (dm-46): metadata I/O error: block 0xfa0001 ("xfs_trans_read_buf") error 5 buf count 512
> [90012.196795] XFS (dm-46): xlog_recover_check_summary agf read failed agno 2 error 5
> [90012.196802] XFS (dm-46): metadata I/O error: block 0xfa0002 ("xfs_trans_read_buf") error 5 buf count 512
> [90012.196806] XFS (dm-46): xlog_recover_check_summary agi read failed agno 2 error 5
> [90012.196813] XFS (dm-46): metadata I/O error: block 0x1770001 ("xfs_trans_read_buf") error 5 buf count 512
> [90012.196817] XFS (dm-46): xlog_recover_check_summary agf read failed agno 3 error 5
> [90012.196823] XFS (dm-46): metadata I/O error: block 0x1770002 ("xfs_trans_read_buf") error 5 buf count 512
> [90012.196827] XFS (dm-46): xlog_recover_check_summary agi read failed agno 3 error 5
> [90012.196843] XFS (dm-46): metadata I/O error: block 0x40 ("xfs_trans_read_buf") error 5 buf count 8192
> [90012.196847] XFS (dm-46): xfs_imap_to_bp: xfs_trans_read_buf() returned error 5.
> [90012.196852] XFS (dm-46): failed to read root inode
> [90012.196963] XFS: Assertion failed: atomic_read(&pag->pag_ref) == 0, file: fs/xfs/xfs_mount.c, line: 272

Any 'xlog_space_left' messages as were reported with the commit you mentioned?
Have you attempted to backport the patch yet?

Regards,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-05-21 18:26 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 [this message]
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
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=20130521182630.GJ20028@sgi.com \
    --to=bpm@sgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.