From: Dave Chinner <david@fromorbit.com>
To: "jamie@x-edit.co.uk" <jamie@x-edit.co.uk>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair no modify output
Date: Tue, 31 Jul 2012 08:07:59 +1000 [thread overview]
Message-ID: <20120730220759.GJ2877@dastard> (raw)
In-Reply-To: <769346391.171271.1343664034505.JavaMail.open-xchange@oxwebmail.registrar-servers.com>
On Mon, Jul 30, 2012 at 06:00:34PM +0200, jamie@x-edit.co.uk wrote:
> Hi List,
> Sorry for the stupid question, just wanted a quick clarification on the
> following excerpts from an xfs_repair no modify.
>
> # xfs_repair -nv /dev/sdc1
.....
> entry "YYYY" in dir 4294967424 points to an already connected directory inode 145
> would clear entry "YYYY"
......
> disconnected dir inode 4294967424, would move to lost+found
......
> Does this in effect mean that the file YYYY will end up and lost+found
Yes.
> and
> directory (and its contents) will end up in lost+found.
Assuming you mean directory entry XXXX, no.
> Namely easy enough to move back. Or will the contents of XXXX be lost?
XXXX was an invalid directory entry. It got removed from the
directory, and the directory is otherwise unmodified. FWIW, it was
on inode 128, so it's probably an entry in the root directory....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-07-30 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 16:00 xfs_repair no modify output jamie
2012-07-30 22:07 ` Dave Chinner [this message]
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=20120730220759.GJ2877@dastard \
--to=david@fromorbit.com \
--cc=jamie@x-edit.co.uk \
--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