I just looked at a few machines where I run sage and found that one of them has this problem. It is also the one where I've used @parallel the most.
I see at most one subdirectory per host in my .sage directory on *.math, so there's not much of a problem there. I have use @parallel a fair amount there, but not that much. On a different cluster that I use that has nfs mounted home directories I see one hostname with 7789 subdirectories and another with 4731 subdirectories. So whatever is going on, it doesn't seem to be isolated. On Mon, Sep 19, 2011 at 12:26 PM, Volker Braun <vbraun.n...@gmail.com>wrote: > On a big computation with many @parallel decorators I eventually get > > [Errno 31] Too many links: '/home/vbraun/.sage//temp/hostname/26457/' > > This is caused by trying to create >2^15 ~ 32k subdirectories, which is an > ext2/ext3 limitation. Is there any reason why the @parallel forker creates > its own temp directories but then does not clean them up? Each NNNN > subdirectory contains a single empty interface/ subdirectory. > > PS: This is on a NFS partition, just deleting 32k directories takes a > loooong time. > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
