From: Simon Kirby <sim@hostway.ca>
To: xfs@oss.sgi.com
Subject: xfsprogs 3.0.3 seems to forget to increase nlinks in lost+found
Date: Mon, 21 Sep 2009 14:24:28 -0700 [thread overview]
Message-ID: <20090921212428.GA12139@hostway.ca> (raw)
After running xfs_repair on a 7 TB file system where the first 1 GB had
been accidentally formatted with mkfs.ext3, a number of paths and files
were found in lost+found, as expected. However, nlinks of the directory
itself was set to 2, causing "find" to become confused. A subsequent run
of xfs_progs found and repaired this error:
Phase 7 - verify and correct link counts...
resetting inode 265 nlinks from 2 to 11174
done
Perhaps it would be possible to remember to increment this while things
are being linked to it?
Simon-
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2009-09-21 21:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090921212428.GA12139@hostway.ca \
--to=sim@hostway.ca \
--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