From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: rsync and corrupt inodes (was xfs_dump problem)
Date: Fri, 2 Jul 2010 08:21:51 +0200 [thread overview]
Message-ID: <201007020821.51753@zmi.at> (raw)
In-Reply-To: <20100702024235.GX24712@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 2091 bytes --]
On Freitag, 2. Juli 2010 Dave Chinner wrote:
> So it's the rsync daemon on saturn that is doing all the IO?
Yes.
> > I rsynced today 3 times, twice with the openSUSE kernel and once
> > with 2.6.34, no problem. Sorry (or maybe "lucky me"?).
> >
> > > > 852c268f-cf1a-11de-b09b-806e6f6e6963.vhd* ??????????? ? ? ?
> > > > ? ? 852c2690-cf1a-11de-b09b-806e6f6e6963.vhd
> > >
> > > On the source machine, can you get a list of the xattrs on the
> > > inode?
> >
> > How would I do that? "getfattr" on that file gives no return, does
> > that mean it doesn't have anything to say? I never do that things,
> > so there shouldn't be any attributes set.
>
> "getfattr -d"
Sorry, doesn't work:
# getfattr -d 852c2690-cf1a-11de-b09b-806e6f6e6963.vhd
getfattr: 852c2690-cf1a-11de-b09b-806e6f6e6963.vhd: Structure needs
cleaning
> The first character of the name is bad, everything after that -
> including the attribute value - is identical to that on other
> inodes. What this implies is that we've overwritten the start of
> the attribute fork with something, and that looks exactly like the
> swap extents problems that we've fixed recently....
> >
> > Yes, xfs_fsdr was running. Disabled it now, and compiled and
> > changed to kernel 2.6.34 now. Hope that's OK ;-)
>
> Ok, so we have identified a potential cause. Either disabling fsr or
> upgrading to 2.6.34 should be sufficient to avoid the problem. If no
> problem show up now you are on 2.6.34, then I'd switch fsr back on
> and see if they show up again...
So far, so good. I'm on 2.6.34 now. Is there any chance for a fixed
version of xfs_repair, so that I can either get rid of the 4 broken
files (i.e. delete them), or repair the filesystem? ATM, xfs_repair
asserts on this filesystem.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-02 6:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 1:10 WARNING xfsdump [still] Cannot allocate memory for list of [root|non-root] attributes for nondir ino xxyz Linda A. Walsh
2010-06-28 2:27 ` Dave Chinner
2010-06-29 22:33 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Linda Walsh
2010-06-29 23:25 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-29 23:55 ` Michael Weissenbacher
2010-06-30 0:42 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30 1:16 ` Dave Chinner
2010-06-30 2:45 ` Linda A. Walsh
2010-07-01 23:58 ` Dave Chinner
2010-07-07 3:18 ` Linda A. Walsh
2010-07-07 5:56 ` Linda Walsh
2010-07-07 6:36 ` Dave Chinner
2010-07-07 9:30 ` Linda A. Walsh
2010-07-07 21:01 ` Linda Walsh
2010-06-30 0:01 ` Linda A. Walsh
2010-06-30 1:06 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ;-/ " Dave Chinner
2010-06-30 1:52 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ " Linda A. Walsh
2010-06-30 21:01 ` Stan Hoeppner
2010-07-07 21:40 ` utf-8' chars from Winxp machine may be problem related (was Re: xfs file system in process of becoming corrupt; though xfs_repair...) Linda A. Walsh
2010-07-07 23:40 ` Stan Hoeppner
2010-07-08 0:38 ` Linda A. Walsh
2010-06-30 18:25 ` xfs file system in process of becoming corrupt; though xfs_repair thinks it's fine! ; -/ (was xfs_dump problem...) Michael Monnerie
2010-06-30 23:30 ` rsync and corrupt inodes (was xfs_dump problem) Dave Chinner
2010-07-01 8:25 ` Michael Monnerie
2010-07-02 2:42 ` Dave Chinner
2010-07-02 6:21 ` Michael Monnerie [this message]
2010-07-04 22:53 ` Dave Chinner
2010-07-12 11:28 ` Michael Monnerie
2010-07-07 21:56 ` Linda Walsh
-- strict thread matches above, loose matches on Subject: below --
2010-07-15 20:58 Michael Monnerie
2010-07-15 22:57 ` Dave Chinner
2010-07-16 14:17 ` Michael Monnerie
2010-07-16 14:40 ` Michael Monnerie
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=201007020821.51753@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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