octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #31791] addpath fails on cifs (samba) mounted


From: anonymous
Subject: [Octave-bug-tracker] [bug #31791] addpath fails on cifs (samba) mounted network drives
Date: Sun, 05 Dec 2010 02:55:23 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Ubuntu/10.10 Chromium/7.0.517.44 Chrome/7.0.517.44 Safari/534.7

URL:
  <http://savannah.gnu.org/bugs/?31791>

                 Summary: addpath fails on cifs (samba) mounted network
drives
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sun 05 Dec 2010 02:55:22 AM UTC
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Paul Probert
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.2.4
        Operating System: GNU/Linux

    _______________________________________________________

Details:

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 ?





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31791>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]