From: Dave Chinner <david@fromorbit.com>
To: David Dal Ben <dalben@gmail.com>
Cc: Eric Sandeen <esandeen@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: Inconsistent "EXPERIMENTAL online shrink feature in use. Use at your own risk" alert
Date: Tue, 8 Mar 2022 10:31:32 +1100 [thread overview]
Message-ID: <20220307233132.GA661808@dread.disaster.area> (raw)
In-Reply-To: <CALwRca2Xdp8F_xjXSFXxO-Ra96W685o2qY1xoo=Ko9OWF4oRvw@mail.gmail.com>
On Tue, Mar 08, 2022 at 06:46:58AM +0800, David Dal Ben wrote:
> This is where I get out of my depth. I added the drives to unraid, it
> asked if I wanted to format them, I said yes, when that was completed
> I started migrating data.
>
> I didn't enter any XFS or disk commands from the CLI.
Is there any sort of verbose logging you can turn on from the
applicance web interface?
>
> What I can tell you is that there are a couple of others who have
> reported this alert on the Unraid forums, all seem to have larger
> disks, over 14tb.
I'd suggest that you ask Unraid to turn off XFS shrinking support in
the 6.10 release. It's not ready for production release, and
enabling it is just going to lead to user problems like this.
Indeed, this somewhat implies that Unraid haven't actually tested
shrink functionality at all, because otherwise the would have
noticed just how limited the current XFS shrink support is and
understood that it simply cannot be used in a production environment
yet.
IOWs, if Unraid want to support shrink in their commercial products
right now, their support engineers need to be testing, triaging and
reporting shrink problems to upstream and telling us exactly what is
triggering those issues. Whilst the operations and commands they are
issuing remains hidden from Unraid users, there's not a huge amount
we can do upstream to triage the issue...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-03-07 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALwRca2+UsEZMPwiCtecM87HVVMs27SdawdWXns+PU7+S-DFaQ@mail.gmail.com>
2022-03-07 12:19 ` Inconsistent "EXPERIMENTAL online shrink feature in use. Use at your own risk" alert David Dal Ben
2022-03-07 13:27 ` Gao Xiang
2022-03-07 15:16 ` David Dal Ben
2022-03-07 15:29 ` Eric Sandeen
2022-03-07 22:46 ` David Dal Ben
2022-03-07 23:31 ` Dave Chinner [this message]
2022-03-07 23:51 ` Gao Xiang
2022-03-08 0:04 ` David Dal Ben
2022-03-09 18:22 ` Eric Sandeen
2022-03-09 21:19 ` Dave Chinner
2022-03-09 22:18 ` Eric Sandeen
2022-03-09 22:37 ` 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=20220307233132.GA661808@dread.disaster.area \
--to=david@fromorbit.com \
--cc=dalben@gmail.com \
--cc=esandeen@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox