bugGNU Octave - Bugs: bug #31791, addpath fails on cifs (samba)...

 
 

bug #31791: addpath fails on cifs (samba) mounted network drives

Submitted by:  None
Submitted on:  Sun 05 Dec 2010 02:55:22 AM UTC  
 
Category: LibrariesSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Incorrect Result
Status: FixedAssigned to: None
Originator Name: Paul ProbertOriginator Email: -unavailable-
Open/Closed: ClosedRelease: 3.2.4
Operating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 05 Sep 2013 01:16:40 AM UTC, comment #2:

This appears to be addressed in the development version of Octave:

http://hg.savannah.gnu.org/hgweb/octave/rev/8122286c69a9

In addition, the released 3.6.x Debian and Ubuntu packages all appear to have been compiled with _FILE_OFFSET_BITS=64. Please test with an updated package for Debian or Ubuntu and report back if you still experience problems accessing files over CIFS.

Mike Miller <mtmiller>
Project Administrator
Fri 17 Dec 2010 05:59:48 PM UTC, comment #1:

The Octave developers don't distribute binaries, so I guess it is up to people who package Octave to decide what options to use.

OTOH, if there are changes to Octave that are needed to better support large files, I would be happy to accept patches or get some guidance about what needs to be done since I am certain I don't understand all the issues involved.

John W. Eaton <jwe>
Project Administrator
Sun 05 Dec 2010 02:55:22 AM UTC, original submission:

Folks,
On octave 3.2.4, 32 bit Ubuntu 10.10 x86, I get a failure on a call to addpath('/netmnt/some_shared_dir') where the path refers to a mounted cifs (samba) network shared folder. The error is:
'warning: addpath: /netmnt/some_shared_dir: Value too large for defined data type'

It seems the problem is that a cifs (smbmount or mount.cifs) mounted share has 64 bit inode numbers. If you add "noserverino" to the mount parameters for the share in fstab, then addpath works.

The man page (man mount.cifs) says:
"It is strongly recommended to compile your programs with LFS support (i.e. with -D_FILE_OFFSET_BITS=64) to prevent this problem. You can also use "noserverino" mount option to generate inode numbers smaller than 2 power 32 on the client. But you may not be able to detect hardlinks properly."

So, should octave developers be compiling with D_FILE_OFFSET_BITS=64 ?

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by rik5 (Updated the item)
  • -unavailable- added by mtmiller (Posted a comment)
  • -unavailable- added by jwe (Posted a comment)
  • -unavailable- added by None (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 17 Oct 2013 06:07:41 PM UTCrik5StatusNeed Info=>Fixed
      Open/ClosedOpen=>Closed
    Thu 05 Sep 2013 01:16:40 AM UTCmtmillerStatusNone=>Need Info

    Back to the top


    Powered by Savane 3.1-cleanup1