From: Bas van der Vlies <basv@sara.nl>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Kernel 2.4.3 NFS problem in combo with xfs allocsize
Date: Wed, 27 Jun 2012 15:22:03 +0200 [thread overview]
Message-ID: <4FEB08FB.4010004@sara.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]
We just installed a new kernel 2.4.3 and experiencing problems with allocation of blocks. With the standard debian kernel from
squeeze (2.6.32-5-amd64) we do not have any problems with the same xfs settings
xfs mount options:
* LABEL=lisapool /lisapool xfs rw,uquota,prjquota,nobarrier,allocsize=1048576k,logbsize=256k
I do a nfs 3 mount on a node and when copying small files everything is ok:
{{{
mount -o rw,vers=3
}}}
Now on the mounted directory: ls -lsrh
{{{
288K -rw-r--r-- 1 root root 288K Jun 27 13:50 bash.1
}}}
When i do a copy the file size is correct
{{{
288K -rw-r--r-- 1 root root 288K Jun 27 15:14 bash.1_cp
}}}
When the file size is bigger: ls -lsrh
{{{
1.5M -rw-r--r-- 1 root root 1.5M Jun 27 13:55 bash.groot
}}}
Now copying this big file:
{{{
1.0G -rw-r--r-- 1 root root 1.5M Jun 27 15:14 bash.groot_cp
}}}
Note the size equals the xfs allocsize option and causing problems on our quota enabled file server. When i set an allocsize of 4K
we don't see these problem. Also copying between 2 local file system is behaving as expected. Have other people noticed this problem?
Regards
--
********************************************************************
* Bas van der Vlies e-mail: basv@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
********************************************************************
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4430 bytes --]
reply other threads:[~2012-06-27 13:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FEB08FB.4010004@sara.nl \
--to=basv@sara.nl \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.