Re: Atomic non-durable file write API

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

 



On Sun, Dec 26, 2010 at 4:55 PM, Boaz Harrosh <bharrosh@xxxxxxxxxxx> wrote:
> What if you use a soft link? wouldn't that solve all of your problems?
>
> - do your fsync/fdatasync of choice in a *backend thread* then at the return
> - point set to the new link, fsync the link it's very small, therefore fast.
> - Then delete the old source file.
>
> You need a simple "name-version" schema and the "name" is kept soft linked.
> (You might even skip the last step above and implement an undo stack, some
> Âbackground management caps on history size)
>
>>>
>>>> and this way has other
>>>> issues, like losing file meta-data.
>>>
>
> With soft links this is persevered?
>
> Same system can be used with lots of files. where the final switch is
> the set of a single soft-link say to a folder of related files.

Are you proposing to turn every single file into a symlink?
How would that solve the meta-data issue?

Olaf
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux