|To:||Ruediger Meier <sweet_f_a@xxxxxx>|
|Subject:||Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop|
|From:||Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>|
|Date:||Wed, 27 Jul 2011 13:17:35 -0400 (EDT)|
|Cc:||Bryan Schumaker <bjschuma@xxxxxxxxxx>, "J. Bruce Fields" <bfields@xxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx|
|References:||<alpine.DEB.2.02.1107270952270.1451@xxxxxxxxxxxxxxxx> <alpine.DEB.2.02.1107271227340.1451@xxxxxxxxxxxxxxxx> <4E303F6F.8010706@xxxxxxxxxx> <201107271900.11091.sweet_f_a@xxxxxx>|
|User-agent:||Alpine 2.02 (DEB 1266 2009-07-14)|
On Wed, 27 Jul 2011, Ruediger Meier wrote:
On Wednesday 27 July 2011, Bryan Schumaker wrote:On 07/27/2011 12:28 PM, Justin Piszcz wrote:On Wed, 27 Jul 2011, J. Bruce Fields wrote:What filesystem on the server are you exporting?xfs. /dev/sda1 on / type xfs (rw,noatime) Nothing special, thoughts?Are there a lot of files in the directory you're exporting? It looks like cookie 10272 is mapped to multiple files.I thought xfs is immune to readdir loops!? Is your export directory really located directly within / on /dev/sda1?
Hi, I was sharing out a directory on the NFS server: /d1 192.168.0.0/24(async,rw,no_root_squash,no_subtree_check,fsid=1) Should I share out / instead? Is this a known problem? $ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 30G 13G 18G 43% / tmpfs 2.0G 8.0K 2.0G 1% /lib/init/rw udev 10M 192K 9.9M 2% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm $ Justin.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop, Justin Piszcz|
|Next by Date:||Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop, J. Bruce Fields|
|Previous by Thread:||Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop, Bryan Schumaker|
|Next by Thread:||Re: 2.6.xx: NFS: directory motion/cam2 contains a readdir loop, J. Bruce Fields|
|Indexes:||[Date] [Thread] [Top] [All Lists]|