From: Pedro Ribeiro <pedrib@gmail.com>
To: Eric Sandeen <sandeen@sandeen.net>, linux-xfs@vger.kernel.org
Subject: Re: Bug when mounting XFS with external SATA drives in USB enclosures
Date: Sun, 24 Nov 2019 13:49:53 +0700 [thread overview]
Message-ID: <4728bdc7-3f6e-9abf-34a5-712156c40db3@gmail.com> (raw)
In-Reply-To: <2543ac40-63ba-7a33-8ec5-2ef0797c6cc6@sandeen.net>
On 24/11/2019 01:26, Eric Sandeen wrote:
> I haven't looked very closely at your config deltas for what might change
> alignment but it'd be worth giving:
>
> f8f9ee479439 xfs: add kmem_alloc_io()
> d916275aa4dd xfs: get allocation alignment from the buftarg
> 0ad95687c3ad xfs: add kmem allocation trace points
>
> a try.
>
> -Eric
Hi Eric,
That did the trick. Took me some time to resolve the rejects, but now
5.3.11 and 5.3.12 work like a charm.
While trying to track down the patches, I found your reply here:
https://bugzilla.redhat.com/show_bug.cgi?id=1762596
I ended up applying:
f8f9ee479439 xfs: add kmem_alloc_io()
d916275aa4dd xfs: get allocation alignment from the buftarg
0ad95687c3ad xfs: add kmem allocation trace points
And I don't know why at the time (I was sleepy), I ended up applying
this one too:
xfs: assure zeroed memory buffers for certain kmem allocations
I had to remove the second argument to kmem_alloc_io when applying this
last one, as kmem_alloc_io had two arguments in the 5.3.12 tree + those
3 patches above, instead of three arguments in the actual patch:
return kmem_alloc_io(BBTOB(nbblks), align_mask, KM_MAYFAIL | KM_ZERO);
return kmem_alloc_io(BBTOB(nbblks), KM_MAYFAIL | KM_ZERO);
Do you think it's safe to keep these 4 patches on top of the 5.3.12
tree? So far it all looks fine, filesystems mount and work fine.
Regards,
Pedro
next prev parent reply other threads:[~2019-11-24 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 3:21 Bug when mounting XFS with external SATA drives in USB enclosures Pedro Ribeiro
2019-11-23 16:56 ` Chris Murphy
2019-11-23 18:12 ` Pedro Ribeiro
2019-11-23 18:26 ` Eric Sandeen
2019-11-24 6:49 ` Pedro Ribeiro [this message]
2019-11-24 19:16 ` Eric Sandeen
2019-11-25 2:30 ` Pedro Ribeiro
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=4728bdc7-3f6e-9abf-34a5-712156c40db3@gmail.com \
--to=pedrib@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).