On Fri, Jul 31, 2015 at 10:46 AM, Hugh Dickins <hughd@xxxxxxxxxx> wrote:
>
> Sounds like a dcache problem, and 75a6f82a0d10 seemed the only
> likely candidate, so I experimented with reverting it yesterday,
> and ran successfully for 24 hours.
Hmm. Sounds odd. Are you running nfsd? That would explain why it
happens on ext4 but not tmpfs: ext4 has a get_parent method that can
get a disconnected entry, while tmpfs does not.
That said, your load doesn't sound like it would actually ever trigger
this, unless you just didn't mention that you also end up using that
filesystem over nfs on another machine.
So leave it running a while longer, but maybe it's 4bf46a272647 like
Dominique suspects. Although I don't see how that could trigger
anything either..
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
