Re: unable to write via nfs to aufs of zfs branches
Hello Pui Yong Ng, Thankx for the detailed report. I am trying reproducing the problem on my test machine. But I am very novice for zfs, will you guide me a little more? In your procedure, # zpool create d1 /run/shm/d1 # zpool create d2 /run/shm/d2 # mount -t aufs none /ds -o br:/d1=rw:/d2=rw,xino=/run/shm/ds.aufs.xino zpool create seems to be as mount -t zfs, right? I mean that after zpool create d1, we can access ./d1 as a mount-point. And for unmounting ./d1, is zpool destroy d1 correct? I tried actually, but after zpool destroy d1 I can see all entries alive under d1. Would you teach me how to mount/unmount zfs? And if I send you a debug patch for mainline kernel, aufs module, or zfs module, can you apply and test it? J. R. Okajima -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk
Re: aufs3.12 will kill aufs3.{2,2.x,4} (Re: aufs3 GIT release)
Hello Ben, Ben Hutchings: Thanks for maintaining the 3.2.x branch. I didn't take all the changes from it but I cherry-picked these to include in a stable update for the Debian kernel: The current version of aufs in debian is aufs3.2 20130204, right? 28de369 2013-02-04 aufs3.2 20130204 And if we run git log --no-merges 28de369..aufs3.2.x, we get 85 commits. You chose 12 of them and I guess you want the fixes for critical problmes only, but I'd suggest you to pick up all 85, including the updated version string. If you really really don't want all, I'd suggest you to pick these commits too and change the version string to something like debianized 20130204. 048c785 2013-08-27 aufs: bugfix, support an error in copy-up 06e68b0 2013-08-07 aufs: remove some obsoleted CONFIGs 3356185 2013-05-18 aufs: copyup supports for a sticky bit of the parent 6cec032 2013-04-27 aufs: bugfix, au_pin verifies the positive dentries c5cdbbd 2013-04-20 aufs: pin the branch dir 5/5, set DCACHE_MOUNTED a8d06d5 2013-04-20 aufs: pin the branch dir 4/5, remove some parameters 1c08502 2013-04-20 aufs: pin the branch dir 3/5, replace br_mnt by br_path fa73e4d 2013-04-20 aufs: pin the branch dir 2/5, tiny, au_br_sb() 5272e64 2013-04-20 aufs: pin the branch dir 1/5, tiny, au_br_mnt() 37fbf7f 2013-04-20 aufs: stop locking for au_h_open_pre() c6b0de1 2013-03-02 aufs: possible bugfix, limit the access to -comm 066d25c 2013-03-01 aufs: possible bugfix, replace -comm by get_task_comm() J. R. Okajima -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk
Re: aufs3.12 will kill aufs3.{2,2.x,4} (Re: aufs3 GIT release)
On Mon, 2013-09-30 at 12:33 +0900, sf...@users.sourceforge.net wrote: Hello Ben, Ben Hutchings: Thanks for maintaining the 3.2.x branch. I didn't take all the changes from it but I cherry-picked these to include in a stable update for the Debian kernel: The current version of aufs in debian is aufs3.2 20130204, right? 28de369 2013-02-04 aufs3.2 20130204 And if we run git log --no-merges 28de369..aufs3.2.x, we get 85 commits. You chose 12 of them and I guess you want the fixes for critical problmes only, but I'd suggest you to pick up all 85, including the updated version string. So far as I could tell, the rest were new features - which aren't suitable for a Debian stable update - or adding donors to the documentation. Are you concerned that some bug fix might have a dependency I didn't notice? If you really really don't want all, I'd suggest you to pick these commits too and change the version string to something like debianized 20130204. [...] Well I also cherry-picked the change of version string to '3.2.x', which seemed suitably ambiguous. :-) The Debian changelog lists the cherry-picked changes. I can change the version string again if you think it should have 'debian' in it. Ben. -- Ben Hutchings Life is like a sewer: what you get out of it depends on what you put into it. signature.asc Description: This is a digitally signed message part -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk
Re: unable to write via nfs to aufs of zfs branches
On 30 Sep 2013 11:21, [1]sf...@users.sourceforge.net wrote: In your procedure, # zpool create d1 /run/shm/d1 # zpool create d2 /run/shm/d2 # mount -t aufs none /ds -o br:/d1=rw:/d2=rw,xino=/run/shm/ds.aufs.xino zpool create seems to be as mount -t zfs, right? I mean that after zpool create d1, we can access ./d1 as a mount-point. Thanks Okajima. Yes, zpool create d1 is equivalent to mkfs and mount to /d1 (not ./d1). Upon reboot, it should be automatically mounted without need for entries in fstab. And for unmounting ./d1, is zpool destroy d1 correct? I tried actually, but after zpool destroy d1 I can see all entries alive under d1. To umount, you can do zfs umount d1 and zfs mount d1 to mount again. I believe that zpool destroy should be equivalent to umount and removing the metadata that causes it to mount on reboot. But the data on disk /run/shm/d1 would still remain if you recover them again. Would you teach me how to mount/unmount zfs? And if I send you a debug patch for mainline kernel, aufs module, or zfs module, can you apply and test it? I am not familiar with these steps, but I can try :) References 1. mailto:sf...@users.sourceforge.net -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk
Re: aufs3.12 will kill aufs3.{2,2.x,4} (Re: aufs3 GIT release)
Ben Hutchings: So far as I could tell, the rest were new features - which aren't suitable for a Debian stable update - or adding donors to the documentation. Are you concerned that some bug fix might have a dependency I didn't notice? I understand that there are unimportant (for debian) commits in all 85, and you exclude them. But the commit list I wrote in my previous mail contains important ones. So they are recommendation from me. Of course the choice is yours. If we think the word bugfix strictly, you should pick ca0e87b 2013-04-20 aufs: new copyup 6/6, the inode attributes 724b70b 2013-04-20 aufs: new copyup 5/6, actually unlock the parent and relock ead9579 2013-04-20 aufs: new copyup 4/6, aufs_rename() always copies-up the src dentry 8b550ff 2013-04-20 aufs: new copyup 3/6, aufs_link() copyup dentry using src_dentry's name 8a4170f 2013-04-20 aufs: new copyup 2/6, au_pin supports temporary unlock/relock c90d846 2013-04-20 aufs: new copyup 1/6, copyup as a hidden name too. They are for the bug Al Viro pointed out. As my very personal opinion, the problem will not occur while it is surely a bug. Theoritically it should be fixed and these commits did. I can change the version string again if you think it should have 'debian' in it. Yes please. It is important. J. R. Okajima -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk
Re: unable to write via nfs to aufs of zfs branches
Pui Yong Ng: To umount, you can do zfs umount d1 and zfs mount d1 to mount again. Ok, thanks. I will try later and send you a debug patch (probably) in a few days. J. R. Okajima -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60133471iu=/4140/ostg.clktrk
