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=60133471&iu=/4140/ostg.clktrk
