On Sat, 06 Oct 2018 12:25:17 -0700 L A Walsh <suse@tlinx.org> wrote:
On 10/6/2018 5:07 AM, Dave Howorth wrote:
On 2018-10-06 7:11 a.m., Dave Howorth wrote:
I'm a bit stuck now; my XFS foo is not strong today, it seems.
Let me guess, both you and Anton are in Murrica, but different parts. That's how I account for my apparent time travel. :) The timezone is part of the time, folks!
Depends on what levels of risk you want to undertake. If real real low risk, then do a block-level backup (dd) to another partition of the affected partition before you do anything.
Then try the xfs_repair without the '-n' option -- i.e. let it repair it. then try mounting and see how things look. If ok, great, if no, well -- that's what the block-level-backup was for. So other than that, sending a message off to linux-xfs@vger.kernel.org might be a next step.
Yeah, that's what I did and Eric Sandeen suggested a solution very quickly.
Usually I don't see probs like this on an xfs volume.
Me neither.
What are your mount parameters, BTW?
Default? Nothing about barriers, right?
They are now, but they were the problem. noacl is not a recognized option for XFS and rather than ignore it, they choose to log the error and not complete the mount. They were in my original email, BTW. Apparently I've never mounted that relatively new filesystem at boot before :( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org