From: David Brown <davidb@davidb.org>
To: xfs@oss.sgi.com
Subject: xfsrestore: incorrect restore if file becomes a dir
Date: Mon, 26 Dec 2011 12:18:56 -0800 [thread overview]
Message-ID: <20111226201856.GA3909@davidb.org> (raw)
http://oss.sgi.com/bugzilla/show_bug.cgi?id=915
I've had this happen again. It appears to be the case if between
incremental dumps, a file is deleted and a directory is created that
gets the same inode number. The restore leaves a file in place of the
directory. If the new directory has any contents, xfsrestore prints a
warning, and doesn't restore the subdirectory contents.
Given the sparseness of inodes, this doesn't seem to occur all that
frequently, but I do have a couple of backups that exhibit the
behavior. If no one has any ideas, I'll start digging through
xfsrestore to see if I can figure out what is happening.
Thanks,
David Brown
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-12-26 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 20:18 David Brown [this message]
2012-01-03 21:15 ` xfsrestore: incorrect restore if file becomes a dir Bill Kendall
2012-01-03 21:31 ` Dave Chinner
2012-01-03 22:43 ` Bill Kendall
2012-01-03 23:16 ` Dave Chinner
2012-01-04 14:56 ` Bill Kendall
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=20111226201856.GA3909@davidb.org \
--to=davidb@davidb.org \
--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