bugdavfs2 - Bugs: bug #52964, Not working on ppc64le


bug #52964: Not working on ppc64le

Submitter:  None
Submitted:  Wed 24 Jan 2018 12:25:25 AM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  In Progress
Privacy:  Public Assigned to:  _71007
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup

Thu 25 Jan 2018 03:24:49 PM UTC, comment #3: 

Hello, Werner

Seems like changing the buf_size solves the issue, I was able to "ls" and "cp" from remote to local.

If you have interest in a ppc VM to further investigate the issue, I will be glad to provide you.

You can request it here: http://openpower.ic.unicamp.br/minicloud/

Guilherme Tiaki Sato <guilhermetiaki>
Thu 25 Jan 2018 03:05:56 PM UTC, comment #2: 

The error happens here:

Jan 24 17:10:06 controller mount.davfs: FUSE_READDIR:
Jan 24 17:10:06 controller mount.davfs:   n 0x10033e1cc00, fd 6
Jan 24 17:10:06 controller mount.davfs:   pid 10114
Jan 24 17:10:06 controller mount.davfs:   size 65536, off 0
Jan 24 17:10:06 controller mount.davfs: RET: Invalid argument

The fuse kernel module tries to read a block of 65536 Bytes. But the buffer for davfs2-kernel-communication is only 16 KiB and davfs2 returns an error.

I don't know why fuse does this on ppc64le and it is hard for me to debug because I don't have any ppc hardware.

What you could try first:
Set option "buf_size 65" (or something bigger than 65, e.g. 128) in your davfs2.conf file. Now the buffer should be big enough, except when the kernel now requests more than 64 KiB of data.

The error might be caused by different integer format of ppc64. If davfs2 defines the wrong data type somewhere in the communication with the kernel this might result in the kernel getting wrong information about maximum read size. Maybe someone (you?) with this kind of hardware could try to look at the bits?


- <_71007>
Wed 24 Jan 2018 06:29:54 PM UTC, comment #1: 

Please do:
- set option "debug most" in your davfs2.conf file
- mount
- do a "ls"-command
- unmount
- search your log-files for messages from mount.davfs
- attach a file with these messages to this item.


- <_71007>
Wed 24 Jan 2018 12:25:25 AM UTC, original submission:  

After mounting box.com, it is not possible to list the directory. The following error is shown:
# ls
ls: reading directory '.': Invalid argument

I can cd into directories that I know that exists, copy files to the remote server and create directories. Copying files from the remote server results in an empty file created at the destination and the following error (c is a file in the remote server).
# cp c ~
cp: error reading 'c': Invalid argument

All these tests succeeded when running on amd64. Both running Ubuntu 16.04 and davfs2 1.5.2-1.2



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

Attach Files:

Attached Files
file #43068:  syslog added by guilhermetiaki (26KiB - application/octet-stream - I included in the log the moments when I ran the commands (lines beginning with #))


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by guilhermetiaki (Updated the item)
  • -email is unavailable- added by _71007 (Posted a comment)
  • -email is unavailable- added by guilhermetiaki

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.


    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-01-24 guilhermetiaki Attached File- Added syslog, #43068
    2018-01-24 _71007 StatusNone In Progress
        Assigned toNone _71007
    2018-01-24 guilhermetiaki Carbon-Copy- Added guilhermetiaki

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code