From: Dave Chinner <david@fromorbit.com>
To: Markus Rhonheimer <markus.rhonheimer@web.de>
Cc: xfs@oss.sgi.com
Subject: Re: Virtual Block device resize corrupts XFS
Date: Mon, 17 Nov 2014 09:36:30 +1100 [thread overview]
Message-ID: <20141116223630.GH23575@dastard> (raw)
In-Reply-To: <5468FC60.10901@web.de>
On Sun, Nov 16, 2014 at 08:34:56PM +0100, Markus Rhonheimer wrote:
> Hi,
>
> I am running Centos 7 and have created a virtual block device with
> ZFS (ZVOL). I put XFS onto the block device without partitioning it.
>
> This worked very well as storage disk for a VM.
>
> A few days ago I wanted to increase the size of the block device,
> but accidently decreased it by 1 TB (from 7 to 6). I found out about
> it and immediately increased the size of the drive to 8 TB
> afterward.
If that was a normal LVM block device, there would have been no
trouble. But you're using something special, unusual and completely
untested, so the most likely outcome is going to be that you still
have a pile of broken bits.
> The XFS partition can still be mounted and I can list the files on
> it, but xfs_repair -n says: "/Sorry/, /could not find valid
> secondary superblock"
Full output, please, as well as the version of xfs_repair you are
using...
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-11-16 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 19:34 Virtual Block device resize corrupts XFS Markus Rhonheimer
2014-11-16 22:36 ` Dave Chinner [this message]
2014-11-16 23:07 ` Spelic
2014-11-17 9:42 ` Spelic
2014-11-23 11:37 ` Markus Rhonheimer
2014-11-18 18:24 ` Markus
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=20141116223630.GH23575@dastard \
--to=david@fromorbit.com \
--cc=markus.rhonheimer@web.de \
--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