From: Emmanuel Florac <eflorac@intellique.com>
To: xfs@oss.sgi.com
Subject: Re: Corrupted filesystem: thoughts?
Date: Tue, 7 Oct 2014 09:59:49 +0200 [thread overview]
Message-ID: <20141007095949.2dce6d72@galadriel.home> (raw)
In-Reply-To: <20141007093533.66ba8c7b@galadriel.home>
Le Tue, 7 Oct 2014 09:35:33 +0200 vous écriviez:
> Kernel is a plain vanilla 3.2.54 amd64. As a precaution I've made a
> list of the whole filesystem with inode numbers to be able to rename
> lost files in norecovery mode... Unfortunately I cannot do a metadump
> because of lack of room elsewhere.
At end of repair I've got loads of these:
libxfs_writebufr: write verifer failed on bno 0x10000f348/0x1000
Metadata corruption detected at block 0x802b2a88/0x1000
libxfs_writebufr: write verifer failed on bno 0x802b2a88/0x1000
Metadata corruption detected at block 0x800e4420/0x1000
libxfs_writebufr: write verifer failed on bno 0x800e4420/0x1000
Metadata corruption detected at block 0x9075d8/0x1000
libxfs_writebufr: write verifer failed on bno 0x9075d8/0x1000
Metadata corruption detected at block 0x143390/0x1000
libxfs_writebufr: write verifer failed on bno 0x143390/0x1000
Metadata corruption detected at block 0x142160/0x1000
libxfs_writebufr: write verifer failed on bno 0x142160/0x1000
Metadata corruption detected at block 0x197400/0x1000
libxfs_writebufr: write verifer failed on bno 0x197400/0x1000
Metadata corruption detected at block 0x10fee0/0x1000
libxfs_writebufr: write verifer failed on bno 0x10fee0/0x1000
Metadata corruption detected at block 0x145d00/0x1000
libxfs_writebufr: write verifer failed on bno 0x145d00/0x1000
Metadata corruption detected at block 0x18e658/0x1000
libxfs_writebufr: write verifer failed on bno 0x18e658/0x1000
Metadata corruption detected at block 0x192d98/0x1000
libxfs_writebufr: write verifer failed on bno 0x192d98/0x1000
Metadata corruption detected at block 0x116668/0x1000
libxfs_writebufr: write verifer failed on bno 0x116668/0x1000
Metadata corruption detected at block 0xf9428/0x1000
libxfs_writebufr: write verifer failed on bno 0xf9428/0x1000
Metadata corruption detected at block 0x42698/0x1000
libxfs_writebufr: write verifer failed on bno 0x42698/0x1000
Metadata corruption detected at block 0x44db8/0x1000
libxfs_writebufr: write verifer failed on bno 0x44db8/0x1000
and 10538 files in lost+found...
--
------------------------------------------------------------------------
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
next prev parent reply other threads:[~2014-10-07 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 7:35 Corrupted filesystem: thoughts? Emmanuel Florac
2014-10-07 7:59 ` Emmanuel Florac [this message]
2014-10-07 10:59 ` Dave Chinner
2014-10-07 10:56 ` Dave Chinner
2014-10-07 11:22 ` Emmanuel Florac
2014-10-07 19:53 ` Dave Chinner
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=20141007095949.2dce6d72@galadriel.home \
--to=eflorac@intellique.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.