From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair 3.1.2 crashing
Date: Mon, 14 Jun 2010 14:47:57 +0200 [thread overview]
Message-ID: <201006141448.01367@zmi.at> (raw)
In-Reply-To: <201006121533.36684@zmi.at>
[-- Attachment #1.1: Type: Text/Plain, Size: 1504 bytes --]
On Samstag, 12. Juni 2010 Michael Monnerie wrote:
> [167981.222861] [<ffffffff8000c868>]
> system_call_fastpath+0x16/0x1b
Now it's becoming weird. I had that crash with a directory named
/disks/daten/samba/backup/uranus/WindowsImageBackup/uranus/Backup\
2010-06-12\ 010016/ /bigbackup/Backup\ 2010-06-05\ 010014/
and the file in there is
852c2690-cf1a-11de-b09b-806e6f6e6963.vhd
I moved that broken dir away to /, and did a new rsync. And, guess what,
I got the same again: the file inside this dir is broken. The 3rd rsync
did not make the same error, it seems good. The problem is that the dump
is not the same any more, as that PC made a new image in the meantime.
But as I got the same error twice on copy via rsync from one PC to
another, it looks like I triggered the error just by copying via "rsync
-aPvHAXy source destpc::dest/".
I did an xfs_metadump and just left the 2 broken dirs inside, so you can
easily verify:
http://zmi.at/backup-metadump-20100614-broken.bz2
xfs_repair 3.1.2 can't repair that, it crashes.
The filesystem is mounted with these options:
relatime,logbufs=8,logbsize=256k,attr2,barrier,largeio,swalloc,allocsize=256k
--
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
prev parent reply other threads:[~2010-06-14 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 11:06 xfs_repair 3.1.2 crashing Michael Monnerie
2010-06-10 16:27 ` Eric Sandeen
2010-06-11 23:38 ` Michael Monnerie
2010-06-12 1:38 ` Eric Sandeen
2010-06-12 10:41 ` Michael Monnerie
2010-06-23 18:32 ` Michael Monnerie
2010-06-12 13:33 ` Michael Monnerie
2010-06-14 12:47 ` Michael Monnerie [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=201006141448.01367@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