From: Markus <markus.rhonheimer@web.de>
To: xfs@oss.sgi.com
Subject: Re: Virtual Block device resize corrupts XFS
Date: Tue, 18 Nov 2014 19:24:40 +0100 [thread overview]
Message-ID: <546B8EE8.4040903@web.de> (raw)
In-Reply-To: <5468FC60.10901@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 989 bytes --]
Hi,
I am in a foreign country right now, but I will be back next week, will
write all information down as soon as I am back.
kind regards
Markus
Am 16.11.2014 um 20:34 schrieb Markus Rhonheimer:
> 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.
>
> 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"
>
> /Is there the possibility to rescue some files?
>
> kind regards
>
> Markus
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
[-- Attachment #1.2: Type: text/html, Size: 1929 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:[~2014-11-18 18:24 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
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 [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=546B8EE8.4040903@web.de \
--to=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