From: Eric Sandeen <sandeen@sandeen.net>
To: Fanael Linithien <fanael4@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Metadata CRC error upon unclean unmount
Date: Tue, 24 Jun 2014 11:24:43 -0500 [thread overview]
Message-ID: <53A9A64B.7030808@sandeen.net> (raw)
In-Reply-To: <CA+o=1OXJZk2XjZhtEORQesDjb3VGzM1Ddk6DGXwuLhHJUEbjPQ@mail.gmail.com>
On 6/24/14, 11:19 AM, Fanael Linithien wrote:
> 2014-06-24 18:08 GMT+02:00 Eric Sandeen <sandeen@sandeen.net>:
>> Do you have any kind of reproducer for this?
>
> The closest thing to a reliable reproducer I found is:
> dd if=/dev/urandom of=some.file
> <VM reset while dd is still running>
>
>> Any chance you created an xfs_metadump before the xfs_repair?
>
> I still have the broken FS, but the dump is 225 MB. Will it be OK if I
> repro it on a clean FS?
absolutely, if you have a recipe starting at mkfs and ending with corruption,
that's even better.
>> What constitutes an "unclean unmount" in your case; a VM reset? A host
>> crash?
>
> A VM reset.
>
>> (This is a VM, right?)
>
> Right.
>
>> What sort of block device configuration does it have?
>
> What do you mean?
Is the VM using a host block device or an image file?
What type of image file, VDI, QCOW, or?
If an image, what type of filesystem hosts the image?
Have you done any "VBoxManage storagectl"-type modifications to virtualbox defaults?
Since this was a guest reset, not a host reset, it doesn't
matter as much, but it's worth getting the details I think.
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-24 16:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 16:01 Metadata CRC error upon unclean unmount Fanael Linithien
2014-06-24 16:04 ` Grozdan
2014-06-24 16:08 ` Eric Sandeen
2014-06-24 16:19 ` Fanael Linithien
2014-06-24 16:24 ` Eric Sandeen [this message]
2014-06-24 16:37 ` Fanael Linithien
2014-06-24 18:48 ` Eric Sandeen
2014-06-24 19:00 ` Fanael Linithien
2014-06-24 19:45 ` Eric Sandeen
2014-06-24 20:19 ` Dave Chinner
2014-06-24 20:44 ` Fanael Linithien
2014-06-24 21:50 ` Fanael Linithien
2014-06-25 1:21 ` Dave Chinner
2014-06-25 15:28 ` Fanael Linithien
2014-06-25 16:09 ` Fanael Linithien
2014-06-25 22:03 ` Dave Chinner
2014-06-25 22:33 ` Fanael Linithien
2014-06-25 23:22 ` Dave Chinner
2014-06-25 23:32 ` Fanael Linithien
2014-06-25 23:52 ` Dave Chinner
2014-06-26 0:28 ` Dave Chinner
2014-06-26 2:23 ` Dave Chinner
2014-06-26 20:03 ` Mark Tinguely
2014-06-26 22:47 ` Dave Chinner
2014-06-27 14:26 ` Mark Tinguely
2014-06-28 0:49 ` Dave Chinner
2014-06-29 16:19 ` Mark Tinguely
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=53A9A64B.7030808@sandeen.net \
--to=sandeen@sandeen.net \
--cc=fanael4@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox