From: Ramon van Alteren <ramon@vanalteren.nl>
To: Ramon van Alteren <ramon@vanalteren.nl>
Cc: linux-kernel@vger.kernel.org, ramon@hyves.nl
Subject: Re: Writing to an NFS share truncates files on >8Tb Raid + LVM2
Date: Wed, 22 Feb 2006 11:30:55 +0100 [thread overview]
Message-ID: <43FC3D5F.1090607@vanalteren.nl> (raw)
In-Reply-To: <43FB3208.7020303@vanalteren.nl>
Ramon van Alteren wrote:
> I'd like to report a situation which looks like a bug in the kernelbased
> nfs server implementation.
>
> Based on responses from a different mailinglist and google I tried unfsd
> the userspace nfsd implementation which appears to work fine (still
> testing) The above test-case works for both loopback and remote
> mounted filesystems.
>
> I'm not on the list so please CC me.
unfsd appears to suffer from the same problem only it has a higher
treshold for them to appear.
We're seeing the same behaviour with larger files created.
for i in `seq 1 10`; do dd count=400000 bs=1024 if=/dev/zero
of=/root/test-tools/test.tst; ls -lha /root/test-tools/test.tst ; rm
/root/test-tools/test.tst ; done
400000+0 records in
400000+0 records out
dd: closing output file `/root/test-tools/test.tst': No space left on device
-rw-r--r-- 1 root root 328K Feb 22 09:53 /root/test-tools/test.tst
400000+0 records in
400000+0 records out
dd: closing output file `/root/test-tools/test.tst': No space left on device
-rw-r--r-- 1 root root 176K Feb 22 09:53 /root/test-tools/test.tst
400000+0 records in
400000+0 records out
dd: closing output file `/root/test-tools/test.tst': No space left on device
-rw-r--r-- 1 root root 168K Feb 22 09:53 /root/test-tools/test.tst
400000+0 records in
400000+0 records out
dd: closing output file `/root/test-tools/test.tst': No space left on device
-rw-r--r-- 1 root root 176K Feb 22 09:53 /root/test-tools/test.tst
A test with the same command directly onto the local filesystem runs
without problems.
for i in `seq 1 10`; do dd count=400000 bs=1024 if=/dev/zero
of=/data/bonnie++/test.tst; ls -la /data/bonnie++/test.tst ; rm
/data/bonnie++/test.tst ; done
400000+0 records in
400000+0 records out
-rw-r--r-- 1 root root 409600000 Feb 22 09:59 /data/bonnie++/test.tst
400000+0 records in
400000+0 records out
-rw-r--r-- 1 root root 409600000 Feb 22 09:59 /data/bonnie++/test.tst
400000+0 records in
400000+0 records out
-rw-r--r-- 1 root root 409600000 Feb 22 09:59 /data/bonnie++/test.tst
400000+0 records in
400000+0 records out
-rw-r--r-- 1 root root 409600000 Feb 22 09:59 /data/bonnie++/test.tst
400000+0 records in
400000+0 records out
-rw-r--r-- 1 root root 409600000 Feb 22 10:00 /data/bonnie++/test.tst
Any help would be much appreciated.
Based on a comment from Lee Revell, I can reproduce the same behaviour
with both sync & async options set on the nfs server (kernel and userspace)
Regards,
Ramon
--
To be stupid and selfish and to have good health are the three requirements for happiness, though if stupidity is lacking, the others are useless.
Gustave Flaubert
next prev parent reply other threads:[~2006-02-22 10:30 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 [this message]
2006-02-22 17:36 ` Andi Kleen
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=43FC3D5F.1090607@vanalteren.nl \
--to=ramon@vanalteren.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=ramon@hyves.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