[Bugs] [Bug 763999] apt-get fails to work inside a Proxmox container: Value too large for defined data type

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=763999

Niels de Vos <ndevos at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
                 CC|                            |alessandro.iurlano at gmail.co
                   |                            |m, ndevos at redhat.com
          Component|core                        |fuse
            Version|3.1.1                       |3.4.0-alpha
           Assignee|nsathyan at redhat.com         |bugs at gluster.org
            Summary|Gluster crashes when        |apt-get fails to work
                   |starting OpenVZ containers  |inside a Proxmox container:
                   |from it                     |Value too large for defined
                   |                            |data type
              Flags|                            |needinfo?(alessandro.iurlan
                   |                            |o at gmail.com)



--- Comment #26 from Niels de Vos <ndevos at redhat.com> ---
Summary/current status:

- Tested with 3.4.0qa8
- Running a proxmox container stored on a glusterfs mount-point
- When updating, apt-get throws the following error:
      W: unable to read /etc/apt/apt.conf.d/ - 
                 DirectoryExists (75: Value too large for defined data type)

This suggests that READDIR returned a structure that could not be used. These
structures contain 64-bit values (also when using 32-bit userspace). It it
expected to work on all recent versions of Linux, but some legacy operating
systems or applications may not accept things like 64-bit inodes (or > 4GB
files). If 64-bit inodes would be the issue, mounting the Gluster volume with
"-o enable-ino32" should work around this.

Investigation on what is happening, should be done in the Proxmox container. A
strace of the "apt-get" process that fails to read the content of the directory
would be a good start.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.