From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Subject: xfs_repair: phase7.c:148: phase7: Assertion `no_modify || nrefs > 0' failed.
Date: Mon, 20 Feb 2012 16:00:18 +0100 [thread overview]
Message-ID: <201202201600.19086.arekm@maven.pl> (raw)
xfs_repair from xfsprogs-dev git.kernel.org repository
on http://routing.com.pl/xfs-metadump-2012-02-20.bz2 fails with:
resetting inode 268740837 nlinks from 6 to 5
resetting inode 268742728 nlinks from 178 to 172
resetting inode 268861622 nlinks from 45 to 44
resetting inode 268902438 nlinks from 4 to 3
resetting inode 268920918 nlinks from 10500 to 10483
resetting inode 269133820 nlinks from 14501 to 9527
resetting inode 269496340 nlinks from 61 to 55
resetting inode 269768793 nlinks from 4 to 3
resetting inode 270532626 nlinks from 9 to 8
resetting inode 339630321 nlinks from 5 to 4
resetting inode 339630322 nlinks from 45 to 39
resetting inode 339630327 nlinks from 25 to 20
resetting inode 536872960 nlinks from 2 to -4276
nlinks -4276 will overflow v1 ino, ino 536872960 will be converted to version 2
resetting inode 536872961 nlinks from 2 to 317
xfs_repair: phase7.c:148: phase7: Assertion `no_modify || nrefs > 0' failed.
whole log: http://ixion.pld-linux.org/~arekm/xfs-log.gz
Patches to test welcome :-)
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-02-20 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 15:00 Arkadiusz Miśkiewicz [this message]
2012-02-28 16:01 ` xfs_repair: phase7.c:148: phase7: Assertion `no_modify || nrefs > 0' failed Christoph Hellwig
2012-03-01 7:58 ` Arkadiusz Miśkiewicz
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=201202201600.19086.arekm@maven.pl \
--to=arekm@maven.pl \
--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