From: Shaya Potter <spotter-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: directory entries
Date: Mon, 01 Sep 2008 10:27:54 -0400 [thread overview]
Message-ID: <48BBFBEA.2000308@cs.columbia.edu> (raw)
In-Reply-To: <20080901.171643.74124381.ryusuke-sG5X7nlA6pw@public.gmane.org>
Ryusuke Konishi wrote:
>
> I've tried this without making sub directories:
>
> # mkdir /nilfs /snap-ro /snap-rw /change
> # mount -t nilfs2 /dev/sdb1 /nilfs
> ...
> # mkcp -s
> # lscp
> CNO DATE TIME MODE SKT NBLKINC ICNT
> ...
> 62305 2008-09-01 16:13:28 ss - 488 39
> 62306 2008-09-01 16:13:33 cp - 8 39
>
> # mount -t nilfs2 -o ro,cp=62305 /dev/sdb1 /snap-ro
> # mount -t unionfs -o dirs=/snap-ro=rw unionfs /snap-rw
> # unionctl /snap-rw --add --before /snap-ro --mode rw /change
> <use /snap-rw as a writable snapshot mount>
>
> # mount
> ...
> /dev/sdb1 on /nilfs type nilfs2 (rw,gcpid=9512)
> /dev/sdb1 on /snap-ro type nilfs2 (ro,cp=62305)
> unionfs on /snap-rw type unionfs (rw,dirs=/snap-ro=rw)
>
> It's working fine.
> Is there a quicker way? (Or something to add?)
well, with new unionfs, you wouldn't use unionctl, but what I did was
close, but something more along the lines of
- to setup
mkdir /base /nilfs /snap-ro /union
mount -t ext3 /dev/sdb1 /base
mount -t nilfs2 /dev/sdb2 /nilfs
mkdir /nilfs/1
mount -t unionfs -o dirs=/nilfs/1=rw,/base=ro none /union
(use union), all writes go to nilfs
- to rollback to a checkpoint, but keep it writable.
mount -t nilfs2 -o ro,cp=xyz /dev/sdb1 /snap-ro
mkdir /nilfs/2
mount -t unionfs -o dirs=/nilfs/2=rw,/nilfs/1=ro,/base=ro none /union
i.e. chaining the /nilfs/* dirs together with unionfs.
next prev parent reply other threads:[~2008-09-01 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-23 20:38 directory entries Reinoud Zandijk
[not found] ` <20080823203853.GA19421-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-08-25 3:21 ` Ryusuke Konishi
[not found] ` <20080825.122125.65657043.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-08-25 3:30 ` Ryusuke Konishi
[not found] ` <20080825.123047.128885778.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-08-25 15:52 ` Reinoud Zandijk
[not found] ` <20080825155243.GA12855-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-08-26 10:29 ` Ryusuke Konishi
[not found] ` <20080826.192942.104752679.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-08-26 13:29 ` Reinoud Zandijk
[not found] ` <20080901.143956.08023399.ryusuke@osrg.net>
[not found] ` <20080901.143956.08023399.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-09-01 5:51 ` Shaya Potter
[not found] ` <48BB82F7.4070607-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2008-09-01 8:16 ` Ryusuke Konishi
[not found] ` <20080901.171643.74124381.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-09-01 14:27 ` Shaya Potter [this message]
[not found] ` <48BBFBEA.2000308-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2008-09-01 17:31 ` Ryusuke Konishi
2008-09-01 11:07 ` Reinoud Zandijk
[not found] ` <20080901110730.GA21008-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-09-01 16:51 ` Ryusuke Konishi
[not found] ` <20080902.015156.126164477.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-09-02 15:02 ` Reinoud Zandijk
[not found] ` <20080902150226.GA28292-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-09-03 12:39 ` Reinoud Zandijk
2008-09-03 16:32 ` Ryusuke Konishi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48BBFBEA.2000308@cs.columbia.edu \
--to=spotter-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox