Re: rename(2) on open file loose unsync data

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

 





On Sun, Apr 1, 2012 at 11:13 AM, Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote:
Amar Tumballi <amar@xxxxxxxxxxx> wrote:

> Can you try with disabling 'write-behind' and 'quick-read' ? We have these
> type of tests in our QA which works fine on master branch as of now. Will
> reconfirm the behavior with master on GNU/Linux.

I tracked this down to NetBSD not sending FSYNC before RENAME. The data
is therefore not flushed at rename time. I will change that behavior in
NetBSD FUSE to fix the issue.


I don't see that as a necessity, unless the system crashes and reboots immediately after the rename(). Did you get to try amar's suggestions?

Avati
 

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux