View previous topic :: View next topic |
Author |
Message |
swiss-se
Posts: 2
Joined: 04 Jan 2011
|
Posted: Tue Jan 04, 2011 6:21 am Post subject: UVLayout file browser doesn't support lage filesystems |
|
|
Hello, we've found that the UVLayout file browser will fail to read the contents of large filesystems, i.e. filesystems where contain entries where either the inode or offset exceeds 32 bits.
The file browser returns no contents, and the console logs "uvlayoutP: scandir: num_files=-1: Value too large for defined data type".
The system call failing is:
getdents(6, 0x8b919c0, 32768) = -1 EOVERFLOW (Value too large for defined data type)
This is probably due to calling readdir instead of readdir64. |
|
Back to top |
|
 |
headus Site Admin

Posts: 2902
Joined: 24 Mar 2005
Location: Perth, Australia
|
Posted: Tue Jan 04, 2011 7:58 pm Post subject: |
|
|
Excellent debugging!
It looks like the getdents() call writes into a structure that uses longs for the inode number of the returned entry, so my best guess is that's where the problem is. On the usual 32bit build of UVLayout, that would be limited to 32bit inode numbers.
A 64bit build of UVLayout might be the answer in that case, and there's one of those available on your uvlayout.com Support Extras page. Its not the current release, but if it fixes your problem, I can easily build the latest as 64bit.
Phil |
|
Back to top |
|
 |
SLI_Fallen
Posts: 66
Joined: 19 Dec 2008
|
Posted: Wed Jan 05, 2011 4:50 am Post subject: |
|
|
I dont know how much time is involved with this but IMO it would be nice to have both 32bit and 64 bit builds available for registered users on the support page when they are released. Just a thought.  |
|
Back to top |
|
 |
headus Site Admin

Posts: 2902
Joined: 24 Mar 2005
Location: Perth, Australia
|
Posted: Wed Jan 05, 2011 7:30 pm Post subject: |
|
|
Thanks for the thought :) But there's a few reasons why the 64bit version is hidden away like that ...
- Because the meshes that you might ever load into UVLayout are relatively small (i.e. tens of thousands or polys max, not tens of millions) then 32bit builds are perfectly fine. You are never going to get near the 3Gb or so per-process memory limit that 32bit apps have.
- There's some issues with the USB dongle driver for the 64bit builds of UVLayout, which pretty much restricts its use to those with floating licenses.
- Currently I can only build 64bit versions under Linux, and supporting 64bit for Windows and OS X too would be extra work to set up for little or no pay-off at this point in time.
Phil |
|
Back to top |
|
 |
SLI_Fallen
Posts: 66
Joined: 19 Dec 2008
|
Posted: Thu Jan 06, 2011 2:53 am Post subject: |
|
|
This is one reason I am not a computer programmer! (I do hardware)
(Plus i'm using Windows)
Very simple and clear explanation Phil, Thanks!
Last edited by SLI_Fallen on Thu Jan 06, 2011 4:07 am; edited 1 time in total |
|
Back to top |
|
 |
swiss-se
Posts: 2
Joined: 04 Jan 2011
|
Posted: Thu Jan 06, 2011 3:57 am Post subject: |
|
|
Hi Phil, I can confirm the 64-bit version does not have this issue. It would be great if you could create a current 64-bit build for us, too. Thanks! |
|
Back to top |
|
 |
headus Site Admin

Posts: 2902
Joined: 24 Mar 2005
Location: Perth, Australia
|
Posted: Fri Jan 07, 2011 6:16 pm Post subject: |
|
|
Done! There's now a 64bit build of the latest 2.07.00 release up on the Support Extras page.
Phil |
|
Back to top |
|
 |
|