From: Emmanuel Florac <eflorac@intellique.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: XFS corruption with rsync
Date: Wed, 19 Sep 2012 21:58:20 +0200 [thread overview]
Message-ID: <20120919215820.44e83ac4@galadriel.home> (raw)
In-Reply-To: <505A0369.3020708@sandeen.net>
Le Wed, 19 Sep 2012 12:39:53 -0500 vous écriviez:
> On 9/19/12 8:57 AM, Emmanuel Florac wrote:
> >
> > I'"ve seen this error showing up on the list previously: while
> > rsync'ing a large volume (66 TB copied to a 114 TB filesystem),
> > I've got this error showing up:
>
> I think you trimmed some relevant lines before these, what actual
> error did it hit, there's probably a file & line number?
Nothing else in dmesg but this error repeated many times. I'll check
through the /var/log/messages if there is more information.
> > Rsync logs says that "structure needs cleaning". After running
> > xfs_repair, there's a few files making reference to a free block.
>
> Including the xfs_repair output would be helpful too.
Unfortunately I forgot that all of xfs_repair output is to STDERR, so I
lost it... It said a lot of lines like "data fork in inode XXX claims
free block YYY". However no data was dropped to lost+found, and
apparently all is OK.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-09-19 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 13:57 XFS corruption with rsync Emmanuel Florac
2012-09-19 17:39 ` Eric Sandeen
2012-09-19 19:58 ` Emmanuel Florac [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=20120919215820.44e83ac4@galadriel.home \
--to=eflorac@intellique.com \
--cc=sandeen@sandeen.net \
--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