All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: xfs@oss.sgi.com
Subject: Re: BUG in xfs_trans_binval
Date: Tue, 29 Mar 2016 19:34:19 +0200	[thread overview]
Message-ID: <20160329173419.GA18970@aepfle.de> (raw)
In-Reply-To: <20160329171553.GA17885@aepfle.de>

On Tue, Mar 29, Olaf Hering wrote:

> "_xfs_buf_find: Block out of range: block 0x81ffff3f8, EOFS 0x7fffd000"


root@optiplex:~ # env -i /sbin/xfs_repair -n /dev/disk/by-label/WD15_optiplx
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
agi unlinked bucket 0 is 40829376 in ag 1 (inode=577700288)
sb_icount 3932864, counted 4365696
sb_ifree 3488, counted 96
sb_fdblocks 55910963, counted 53073251
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
entry contains illegal value in attribute named SGI_ACL_FILE or SGI_ACL_DEFAULT
bad security value for attribute entry 0 in attr block 0, inode 1710299980
problem with attribute contents in inode 1710299980
would clear attr fork
bad nblocks 2 for inode 1710299980, would reset to 1
bad anextents 1 for inode 1710299980, would reset to 0
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 577700288, would move to lost+found
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

Olaf

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

  reply	other threads:[~2016-03-29 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 17:15 BUG in xfs_trans_binval Olaf Hering
2016-03-29 17:34 ` Olaf Hering [this message]
2016-03-29 23:54 ` Dave Chinner
2016-03-30 19:33   ` Olaf Hering

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=20160329173419.GA18970@aepfle.de \
    --to=olaf@aepfle.de \
    --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.