From: Andi Kleen <ak@suse.de>
To: Ramon van Alteren <ramon@vanalteren.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Writing to an NFS share truncates files on >8Tb Raid + LVM2
Date: 22 Feb 2006 18:36:32 +0100 [thread overview]
Message-ID: <p73pslf2t3z.fsf@verdi.suse.de> (raw)
In-Reply-To: <43FB3208.7020303@vanalteren.nl>
Ramon van Alteren <ramon@vanalteren.nl> writes:
>
> Which seems to indicate that RAID + LVM + complex storage and
> 4KSTACKS can cause problems. However I can't find the 4KSTACK symbol
> anywhere in my config. Can't find the 8KSTACK symbol anywhere either :-(
4K stacks is unlikely to cause problems like this. If you have a stack
overflow things crash badly, not break subtly like they do in your case.
Sounds like a bad bug. Best you work with the NFS maintainers to
track it down. See MAINTAINERS how to reach them.
-Andi
prev parent reply other threads:[~2006-02-22 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 15:30 Writing to an NFS share truncates files on >8Tb Raid + LVM2 Ramon van Alteren
2006-02-21 22:55 ` Lee Revell
2006-02-22 10:30 ` Ramon van Alteren
2006-02-22 17:36 ` Andi Kleen [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=p73pslf2t3z.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ramon@vanalteren.nl \
/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