maindavfs2 - Support: sr #108430, Problem: every file gets to...

 
 

sr #108430: Problem: every file gets to lost+found

Submitter:  Przemyslaw <przemhb>
Submitted:  Mon 04 Nov 2013 08:12:46 PM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  _71007
Open/Closed:  Closed Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 04 Feb 2014 06:38:41 PM UTC, comment #8: 

lost+found is part of the davfs2 file system. You can only access it while your file system is mounted. But then you may do whatever you want, e.g. delete the files.
This directory is there to save your local work in cases where davfs2 can't save the files to the server. So usually it is a good idea to look at the file contents whether there is anything you want to keep before deleting the files.

Werner

- <_71007>
Mon 03 Feb 2014 10:49:02 PM UTC, comment #7: 

Thanks you came back to my problem.

I have started to modify default settings when I have found out there is a problem, which I have described. I guess it was one of the tries.

Meantime I have found somewhere a post, where similar problem of a box.com user was described. It was solved by setting davfs in a way you suggested in your last post. I have done this a few weeks ago and it indeed helped. Now I have only a few files in the lost+found folder. None of them exists on the my box.com storage any more.

How to deal with files from the lost+found? Can I delete them after unmounting?
--
Cheers
Przemyslaw

Przemyslaw <przemhb>
Sun 02 Feb 2014 05:36:12 PM UTC, comment #6: 

After beeing busy for some time I forgett about your request. Now I noticed that your server is up again.

Looking at the log: when davfs2 tries to upload files with PUT the connection times out after an initial 100 OK response. The culprit most probably is the Expect-100-header. This option rarely works and is therefore off by default. Why did you turn it on?

I suggest to change your configuration:

  • set use_expect_100 to 0 (the default)
  • set if_match_bug to 0 (the nginx server does not suffer from this bug)
  • set use_locks to 0 (box.com has problems with this, but I'm not sure)


With this configuration box.com works for me. But there are occasional timeouts.

Werner

- <_71007>
Sat 16 Nov 2013 06:16:25 PM UTC, comment #5: 

My server is currently down as I am trying to upgrade it. It may take me some time. Would it it be ok with you if I mail you the logs?
--
cheers,
Przemyslaw

Przemyslaw <przemhb>
Sat 16 Nov 2013 05:56:27 PM UTC, comment #4: 

When small files are transferred to the server successfully but not big ones, then none of the options will help.

The error codes with the aborted message have this meaning:

-2: network timeout (no response from the server within appropriate time)

-3: socket was closed

-4: Connection was reset (e.g. server crashed)

So this looks like a network problem or a server problem.

I could not get the log files from your server, but got timeout errors all the time (even ping times out).

Cheers
Werner

- <_71007>
Wed 06 Nov 2013 06:07:36 PM UTC, comment #3: 

I have done the following things:
- sent a few small files; all were copied fine and no one get to lost+found,
- sent a few large files (>50MB); all of them got to lost+found,
- configure debug to 'most',
- set if_match_bug to 1, remount, transferred a large file once again; it didn't help,
- set use_excpect100 to 1, remount, transferred a large file once again; it didn't help,
-(*) set use_weak_etags to 1, remount, transferred a large file once again; it didn't help,
- took a look at the davfs logs - I've noticed many 'Aborted request (-3)', some 'Aborted request (-4)' and some 'Aborted request (-2)'.

I have replaced consecutive FUSE_WRITE blocks in log with just one and removed all cache size blocks. You can take a look at the log of the last (*) operation http://holubowski.com/messages_davfs3.log.

Przemyslaw <przemhb>
Tue 05 Nov 2013 11:00:16 PM UTC, comment #2: 

Thanks for your reply Werner. I will give the options you mentioned a try and let you know.

As to the file sizes and cache size I have given - I wasn't sure if they play a role here and that is why I have added this information.

Przemyslaw <przemhb>
Tue 05 Nov 2013 07:50:55 PM UTC, comment #1: 

- Files are successfully copied to mounted davfs2 filesystem (until cache size isn't exceeded),
- Every file is listed in lost+found too,
This looks like a problem with uploading files. Most probably it is a server bug, e.g. an old version of Apache/mod_dav, still used by my provider and others, with a bug in handling the If-Match-header. There are also servers with broken implementations of Locks.
Please look at 'man davfs2.conf' for the options to work araound this bugs, especially option 'if_match_bug'.

If none of these options helps please add option 'debug most', mount the file system, copy one small file, wait 20 seconds and then unmount. Search for the debug log in your log files and send them.


- cache index file is updated only after unmount, remount,
- newly cached files don't get listed in cache index until remount,
This is not improper behaviour it is intended. The index file is for use by the mount.davfs daemon. It stores there information about cached files between mounts. It does not need it while running.


- size of a single file is in the range 38-120MB,
- cache size is set to 512MB.
I don't understand what you want to say with this. What's the problem?

Werner

- <_71007>
Mon 04 Nov 2013 08:12:46 PM UTC, original submission:  

Hi,

What is the reason of improper davfs2 behaviour described below? How to fix it?

- Files are successfully copied to mounted davfs2 filesystem (until cache size isn't exceeded),
- Every file is listed in lost+found too,
- cache index file is updated only after unmount, remount,
- newly cached files don't get listed in cache index until remount,
- size of a single file is in the range 38-120MB,
- cache size is set to 512MB.

At the moment I use:
davfs2-1.4.7 built from sources.
Fedora 15.

Przemyslaw <przemhb>

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

    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 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-04-22 _71007 Open/ClosedOpen Closed
    2014-02-04 _71007 StatusIn Progress Done
    2013-11-05 _71007 StatusNone In Progress
        Assigned toNone _71007
    2013-11-04 przemhb Carbon-Copy- Added -email is unavailable-

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code