From: David Mudrich <dmudrich@mudrichsystems.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: sfjro@users.sourceforge.net, linux-nfs@vger.kernel.org
Subject: Re: AUFS triggers Kernel BUG() in nfs_do_writepage (write.c:276)
Date: Mon, 30 Aug 2010 21:22:41 +0200 [thread overview]
Message-ID: <4C7C0501.4020302@mudrichsystems.com> (raw)
In-Reply-To: <87900623-DF1B-42EA-8E95-B7D2768D1122@oracle.com>
Am 30.08.2010 19:28, schrieb Chuck Lever:
> On Aug 30, 2010, at 9:57 AM, David Mudrich wrote:
>
>> Am 30.08.2010 09:41, schrieb sfjro@users.sourceforge.net:
>>> David Mudrich:
>>>> I attached the information you asked for. It seems difficult to have a
>>>> realistic test without AUFS, as it is mounted at the root directory.
>>> Thanx.
>>> It is difficult for me too.
>>> Although I am not confident, these commits (from latest mainline) are
>>> worth to try. If you have no way other than this, you should try.
>>>
>>>
>>> J. R. Okajima
>>>
>> Hello,
>>
>> I applied the patch, same issue.
>> I attached dmesg | tail -n 50.
>>
>> I just tried nfsvers=2 and it works.
>> The problem must be connected with nfs3 writeback.
> Two-phase NFSv3 writes are not like most other file system implementations, so it's not surprising that AUFS might be tripped up.
>
> A possible workaround: If you specify the "sync" mount option when the client mounts the NFS server, it will disable UNSTABLE NFSv3 writes.
mount -o sync was enabled all the time.
>> A copy of this mail goes to the linux-nfs list, maybe they can help to further narrow this.
>>
>>
>> Regards
>>
>> David Mudrich
>> <log.txt>
prev parent reply other threads:[~2010-08-30 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C7960EE.6060304@mudrichsystems.com>
[not found] ` <3217.1283139187@jrobl>
[not found] ` <4C7B53F3.8010709@mudrichsystems.com>
[not found] ` <7041.1283154060@jrobl>
2010-08-30 13:57 ` AUFS triggers Kernel BUG() in nfs_do_writepage (write.c:276) David Mudrich
2010-08-30 17:28 ` Chuck Lever
2010-08-30 19:22 ` David Mudrich [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=4C7C0501.4020302@mudrichsystems.com \
--to=dmudrich@mudrichsystems.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sfjro@users.sourceforge.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