Re: unionfs status

I should say that so sorry of my slow response. so sorry.

We are developing unionfs step by step and still have 5 next patches.

http://people.freebsd.org/~daichi/unionfs/experiments/
http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-1.diff
http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-2.diff
http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-3.diff
http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-4.diff
http://people.freebsd.org/~daichi/unionfs/experiments/unionfs-p20-5.diff

p20-1:
leads panic when "no error happens, eofflag is 0, response data is empty
and DIAGNOSTIC is defined" while involving VOP_READDIR(9) from unionfs.
This change fixes system hang-up using with NFS.

p20-2:
fixed fs access issue mounting on devfs.

p20-3:
fixed kern/109377.

p20-4:
fixed rename panic issue

p20-5:
fixed unix socket connection issue

On our long unionfs running test, It looks like works very well. Would you
try above patches? So sorry of my slow response. Please accept my deepest
apology.

We are planing to commit above patches to 8-current. 7-release has been
done. It is good time to commit it to current ;)

Alexander V. Chernikov wrote:
Hello people!

At this moment unionfs has got at least following problems:
1) File systems cannot mount onto upper/lower unionfs layer (partially described in kern/117829)
2) There are problems with multithreaded programs accessing(writing) files on unionfs (kern/109950)
3) As well there are problems with accessing unix sockets created on upper/lower unionfs layers (kern/118346)
4) Doing mv filename same-filename causes kernel to panic on 6.X (and printing warning about VOP_RENAME in 7+)
5) Making 'loops' when mounting unionfs causes kernel panic (kern/121385)

I have made patches solving first 4 problems
These patches are available at http://ipfw.ru/patches/
unionfs2.diff fixes fs mounting onto upper layer, unionfs_lmount.diff fixes lower
unionfs_threads.diff and unionfs_unix.diff fixes cases 2) and 3)
unionfs_rename.diff fixes case with renaming

Can anybody comment/review ?

--
Daichi GOTO, http://people.freebsd.org/~daichi
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: unionfs: several more problems
    ... I just posted a series of patches to unionfs (already in unionfs.git on ... korg), which fix every problem LTP found, as well as other problems ... I'd like to call your attention to one small unionfs_writepage fix. ...
    (Linux-Kernel)
  • Re: [GIT PULL -mm] Unionfs/fsstack/eCryptfs updates/cleanups/fixes
    ... are you talking about VFS/ecryptfs patches (which are in the stable ... I'm talking about Unionfs, which seems like a rather critical feature to ... It is possible that the bug is in the -mm code. ... either causes an EBUSY on unmount or an oops on unmount :-) ...
    (Linux-Kernel)
  • Re: unionfs: several more problems
    ... I just posted a series of patches to unionfs (already in unionfs.git on ... korg), which fix every problem LTP found, as well as other problems ... I'd like to call your attention to one small unionfs_writepage fix. ...
    (Linux-Kernel)
  • Unionfs: Stackable namespace unification filesystem
    ... The repository contains the following 35 commits (also available as patches ... struct path: Rename Reiserfs's struct path ... These patches make up stripped down version of Unionfs. ...
    (Linux-Kernel)
  • Re: unionfs_copy_attr_times oopses
    ... With the patches I just posted, ... commands in unionfs. ... bindex = ibstart; ... (including the lower level not supporting bmap, as in the tmpfs case), ...
    (Linux-Kernel)