From: Jan <bug-reporter@tuta.io>
To: Linux Xfs <linux-xfs@vger.kernel.org>
Subject: Re: 'stripe width' inconsistency
Date: Thu, 25 Apr 2019 16:34:32 +0200 (CEST) [thread overview]
Message-ID: <LdJupgK--3-1@tuta.io> (raw)
In-Reply-To: <LUbcIN3--3-1@tuta.io>
Hi!
It's been some time but if anybody finds this thread later on, here is how I solved the problem:
Dec 26, 2018, 12:09 AM by bug-reporter@tuta.io:
> Recently, I ran into problems mounting one of my XFS file systems. It's been a while since I used that HDD but I'm almost certain there were no problems. 'xfs_repair' complains about 'bad stripe width in superblock' but 'xfs_db' has no problems parsing the filesystem. It reports (among other information)
>
> > unit = 8
> > width = 65535
> [...]
> > crc = 0xe9e260b (correct)
>
In the end it worked to use 'xfs_db -x' to change the width to '65536'. (Actually, I used a dm snapshot so I did not have to touch the actual block device, but that was just a safety measure.) After that, I could mount the filesystem normally again. Just to be safe, I mounted it read-only, made a backup and recreated the filesystem with (manually set) sane parameters.
As a recommendation: it would be nice if such "defect" filesystems were still mountable, even if read only ;-)
Regards, Jan
prev parent reply other threads:[~2019-04-25 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 23:09 'stripe width' inconsistency Jan
2019-04-25 14:34 ` Jan [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=LdJupgK--3-1@tuta.io \
--to=bug-reporter@tuta.io \
--cc=linux-xfs@vger.kernel.org \
/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.